AMP autostart systemctl not working

OS Name/Version: Ubuntu 24.04.5 LTS

Product Name/Version: AMP Instance Manager v2.8.0.6 build 20260923.2

Problem Description: autostart of amp failed, but I’m able to start AMP manually via AMP user - systemctl journal output is below:

```Subject: A start job for unit ampinstmgr.service has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ A start job for unit ampinstmgr.service has finished with a failure.
░░ 
░░ The job identifier is 177 and the job result is failed.
Sep 25 17:09:55 basement systemd[1]: Starting ampinstmgr.service - AMP Instance Manager...
░░ Subject: A start job for unit ampinstmgr.service has begun execution
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ A start job for unit ampinstmgr.service has begun execution.
░░ 
░░ The job identifier is 1447.
Sep 25 17:09:55 basement ampinstmgr[2756]: [Info/1] AMP Instance Manager v2.8.0.6 build 20260923.2 built 23/09/2026 16:25
Sep 25 17:09:55 basement ampinstmgr[2756]: [Info/1] Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV
Sep 25 17:09:55 basement ampinstmgr[2756]: 'true' is not a valid value for the 'Delay' argument.
Sep 25 17:09:55 basement ampinstmgr[2756]: --StartBoot, -b:
Sep 25 17:09:55 basement ampinstmgr[2756]: Start boot-time AMP instances.
Sep 25 17:09:55 basement ampinstmgr[2756]: Starts AMP instances which have had the 'Start On Boot' flag enabled.
Sep 25 17:09:55 basement ampinstmgr[2756]: Parameters:
Sep 25 17:09:55 basement ampinstmgr[2756]:  - Delay                Int32 -  (Optional, default is 0)
Sep 25 17:09:55 basement ampinstmgr[2756]:  - ADSOnly              Boolean -  (Optional, default is False)
Sep 25 17:09:55 basement ampinstmgr[2756]:  - ExcludeServices      Boolean -  (Optional, default is False)
Sep 25 17:09:55 basement systemd[1]: ampinstmgr.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ An ExecStart= process belonging to unit ampinstmgr.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
Sep 25 17:09:55 basement systemd[1]: ampinstmgr.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ The unit ampinstmgr.service has entered the 'failed' state with result 'exit-code'.
Sep 25 17:09:55 basement systemd[1]: Failed to start ampinstmgr.service - AMP Instance Manager.
░░ Subject: A start job for unit ampinstmgr.service has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ A start job for unit ampinstmgr.service has finished with a failure.
░░ 
░░ The job identifier is 1447 and the job result is failed.```

Steps to reproduce:

  • Step 1 reboot system

Actions taken to resolve so far:

try to start manually with succsess

This is a current known bug. I expect they will fix it next patch.

Fix: AMP fails to start on boot (mistyped ExecStart)

Cause: The ExecStart line in the AMP systemd service is missing the boot delay argument, causing a syntax error that prevents the instance manager service from starting.

Fix:

  1. Open the service file:
   sudo nano /etc/systemd/system/ampinstmgr.service
  1. Find this line:
   ExecStart=/opt/cubecoders/amp/ampinstmgr startboot true
  1. Change it to:
   ExecStart=/opt/cubecoders/amp/ampinstmgr startboot 0 true
  1. Save and exit.
  2. Reload systemd and start the service:
   sudo systemctl daemon-reload
   sudo systemctl start ampinstmgr.service

Why this works: The startboot command expects a delay value (in milliseconds) as an argument. Without it, the line is malformed and systemd fails to parse it. Adding 0 sets the delay to none, which resolves the syntax error and allows auto-boot to run correctly.

Note! I saw in discord that if you make this change, Iceofwraith indicated the next update will break! If you do this make sure to revert before you run the next patch!

Ok - thanks for that hint.