After updating my server to Debian 12, I found that AMP is not running anymore.
I don’t think it’s related to the upgrade as I see that the ADS01 latest log is from 08/04/2023.
This AMP is mostly used by my son for Minecraft so I suppose he didn’t used it a lot lately
This is what I get when trying to start/restart the service:
root@deb-gma-01:~# service ampinstmgr restart
Job for ampinstmgr.service failed because a fatal signal was delivered to the control process.
See “systemctl status ampinstmgr.service” and “journalctl -xeu ampinstmgr.service” for details.
Jun 12 13:16:36 deb-gma-01 systemd[1]: Starting ampinstmgr.service - AMP Instance Manager…
Jun 12 13:16:36 deb-gma-01 systemd[1]: ampinstmgr.service: Main process exited, code=killed, status=11/SEGV
Jun 12 13:16:36 deb-gma-01 systemd[1]: ampinstmgr.service: Failed with result ‘signal’.
Jun 12 13:16:36 deb-gma-01 systemd[1]: Failed to start ampinstmgr.service - AMP Instance Manager.
root@deb-gma-01:~# su -l amp
CubeCoders AMP amp@deb-gma-01 ~ ampinstmgr status
Segmentation fault
Any idea on what I can do to restart the instance?
Sorry you are having trouble after upgrading. Debian 12 is brand new and may require Mike to take a look as this is now the second report of segmentation fault when trying to run AMP. What was recommended to a user with the same problem was to back up your .ampdata directory - rebuild your system by installing the operating system again. I would recommend Debian 11 for now until 12 is more thoroughly tested. Install AMP - copy your .ampdata directory over - run this command to fix permissions - ampinstmgr fixperms
Totally understand. You can give that a try for sure. Just for your information Mike has tested AMP on a fresh install of Debian 12 and it is working correctly. Post any more logs from what you get so that Mike can take a look and try to troubleshoot.
root@deb-gma-01:~# apt purge ampinstmgr && apt install ampinstmgr Reading package lists… Done Building dependency tree… Done Reading state information… Done The following packages were automatically installed and are no longer required:
lib32gcc-s1 lib32stdc++6 libc6-i386 libevent-core-2.1-7 numactl tmux* Use ‘apt autoremove’ to remove them. The following packages will be REMOVED:
ampinstmgr** 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y (Reading database … 41235 files and directories currently installed.) Removing ampinstmgr (2.4.3.6) … Reading package lists… Done Building dependency tree… Done Reading state information… Done The following NEW packages will be installed:
ampinstmgr* 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 112 MB of archives. After this operation, 0 B of additional disk space will be used. Get:1 https://repo.cubecoders.com debian/ ampinstmgr 2.4.3.6 [112 MB] Fetched 112 MB in 6s (18.1 MB/s) Selecting previously unselected package ampinstmgr. (Reading database … 40121 files and directories currently installed.) Preparing to unpack …/ampinstmgr_2.4.3.6_amd64.deb … Unpacking ampinstmgr (2.4.3.6) … Setting up ampinstmgr (2.4.3.6) … root@deb-gma-01:~# ampinstmgr fixperms Segmentation fault root@deb-gma-01:~#
Hmmm… It don’t like it
As AMP doesn’t seems to start, which log can help you to dig a bit into the problem?
The application is clearly not happy with something. The reinstallation put AMP in a loop trying to reconfigure itself and dmesg is filled with this kind of error:
I’ve currently moved my instances data in a backup folder and purged AMP from my server as AMP is in an install loop that never finish becauce ampinstmgr can’t start.
@Mike , let me know if you want something and I’ll reinstall it for troubleshooting
amp@deb-gma-01 
~ ampinstmgr status