AMP Instance Manager randomly stops

  • 40 Views
  • Last Post 21 May 2021
Nanobug posted this 15 May 2021

Hello CubeCoders, Before I start on the actual issue, this is my setup: Proxmox (version 6.4) with 4 (one inactive) Ubuntu Server 20.04 VMs

  • gs-controller (Ubuntu Server 20.04)
  • gs-10 (Ubuntu Server 20.04)
  • gs-20 (Ubuntu Server 20.04)
  • gs-30 ( inactive Ubuntu Server 20.04)

My AMP version is:

AMP Release "Ganymede" v2.1.1.4, built 07/05/2021 19:00

For some reason "ampinstmgr" just stops out of nowhere, it's both the controller and the target. If I SSH into one of them, and type "systemctl status ampinstmgr.service" it responds with this:

ampinstmgr.service - AMP Instance Manager Loaded: loaded (/etc/systemd/system/ampinstmgr.service; enabled; vendor preset: enabled) Active: inactive (dead) Docs: https://github.com/CubeCoders/AMP/wiki/AMP-systemd-script-(Linux)

So I need to type: "systemctl restart ampinstmgr.service" in order to start it again.

The Proxmor server and the VM's haven't been shutdown between the last status check and this one where I found out the service isn't started.

I've also enabled it so it will start on boot up, just in case.

The only things I've installed on the Ubuntu servers is:

Any ideas on why it stops out of no where?

Order By: Standard | Newest | Votes
Mike posted this 16 May 2021

Because its meant to. The ampinstmgr service runs once on system startup then stops. Its sole job is to perform any boot time tasks.

Nanobug posted this 16 May 2021

Because its meant to. The ampinstmgr service runs once on system startup then stops. Its sole job is to perform any boot time tasks.

Alright. But I couldn't connect to AMPbefore I started the service again. Is it used for both?

Mike posted this 16 May 2021

That meant the instances were stopped, you can check this by running ampinstmgr status as the amp user. Restarting the service has the effect of starting up any boot-time AMP instances so it is a valid way to get things going again if AMP has been shut down.

Nanobug posted this 21 May 2021

Sorry, busy week.

That meant the instances were stopped, you can check this by running ampinstmgr status as the amp user. Restarting the service has the effect of starting up any boot-time AMP instances so it is a valid way to get things going again if AMP has been shut down.

I did enable it with the AMP user when I first set it up, so it starts automatically, but down the road, it just goes shuts down for whatever reason. I'll try your command next time I spot the issue.

Close