ampfirewall.timer is always inactive after upgrade of ampinstmgr via apt

  • 196 Views
  • Last Post 03 February 2021
  • Topic Is Solved
AbhorrentJoel posted this 08 October 2020

OS Name/Version: Ubuntu 20.04.1 LTS

Product Name/Version: AMP (apt version 2.0.6.8)

Problem Description: Every time ampinstmgr is updated, it stops the service (ampfirewall.service) but after the upgrade it is not started again. During apt upgrade, the following messages appear:

Warning: Stopping ampfirewall.service, but it can still be activated by:
  ampfirewall.timer

After the upgrade, checking the service for the ampfirewall.timer returns that it is dead:

root@[redacted]:~# systemctl status ampfirewall.timer
● ampfirewall.timer - AMP Instance Manager Firewall
     Loaded: loaded (/etc/systemd/system/ampfirewall.timer; enabled; vendor preset: enabled)
     Active: inactive (dead) since Thu 2020-10-08 22:53:03 UTC; 5min ago
    Trigger: n/a
   Triggers: ● ampfirewall.service
       Docs: https://github.com/CubeCoders/AMP/wiki/AMP-systemd-script-(Linux)

Sep 18 11:06:57 [redacted] systemd[1]: Started AMP Instance Manager Firewall.
Oct 08 22:53:03 [redacted] systemd[1]: ampfirewall.timer: Succeeded.
Oct 08 22:53:03 [redacted] systemd[1]: Stopped AMP Instance Manager Firewall.

The ampfirewall.service shows that if has failed:

root@[redacted]:~# systemctl status ampfirewall.service
● ampfirewall.service - AMP Instance Manager Firewall
     Loaded: loaded (/etc/systemd/system/ampfirewall.service; disabled; vendor preset: enabled)
     Active: failed (Result: signal) since Thu 2020-10-08 22:53:03 UTC; 9min ago
TriggeredBy: ● ampfirewall.timer
       Docs: https://github.com/CubeCoders/AMP/wiki/AMP-systemd-script-(Linux)
   Main PID: 1979663 (code=killed, signal=TERM)

Oct 08 22:53:03 [redacted] systemd[1]: Starting AMP Instance Manager Firewall...
Oct 08 22:53:03 [redacted] systemd[1]: ampfirewall.service: Main process exited, code=killed, status=15/TERM
Oct 08 22:53:03 [redacted] systemd[1]: ampfirewall.service: Failed with result 'signal'.
Oct 08 22:53:03 [redacted] systemd[1]: Stopped AMP Instance Manager Firewall.

A few lines from syslog around the time of the update (it should cover all ampinstmgr references):

Oct  8 22:53:03 [redacted] systemd[1]: Starting AMP Instance Manager Firewall...
Oct  8 22:53:03 [redacted] systemd[1]: Starting AMP Instance Manager Pending Tasks...
Oct  8 22:53:03 [redacted] systemd[1]: ampfirewall.service: Main process exited, code=killed, status=15/TERM
Oct  8 22:53:03 [redacted] systemd[1]: ampfirewall.service: Failed with result 'signal'.
Oct  8 22:53:03 [redacted] systemd[1]: Stopped AMP Instance Manager Firewall.
Oct  8 22:53:03 [redacted] systemd[1]: ampfirewall.timer: Succeeded.
Oct  8 22:53:03 [redacted] systemd[1]: Stopped AMP Instance Manager Firewall.
Oct  8 22:53:03 [redacted] systemd[1]: Reloading.
Oct  8 22:53:04 [redacted] ampinstmgr[1979722]: [Info] AMP Instance Manager v2.0.6.6 built 18/09/2020 11:41
Oct  8 22:53:04 [redacted] ampinstmgr[1979722]: [Info] Release spec: Release - built by CUBECODERS/buildbot on CCL-DEV

...

Oct  8 22:53:16 [redacted] systemd[1]: Starting AMP Instance Manager Pending Tasks...

...

Oct  8 22:53:16 [redacted] ampinstmgr[1980052]: [Info] AMP Instance Manager v2.0.6.8 built 08/10/2020 15:04
Oct  8 22:53:16 [redacted] ampinstmgr[1980052]: [Info] Release spec: Release - built by CUBECODERS/buildbot on CCL-DEV

...

Oct  8 22:53:19 [redacted] systemd[1]: amptasks.service: Succeeded.
Oct  8 22:53:19 [redacted] systemd[1]: Finished AMP Instance Manager Pending Tasks.

dkpg log:

2020-10-08 22:53:02 upgrade ampinstmgr:amd64 2.0.6.6 2.0.6.8
2020-10-08 22:53:02 status half-configured ampinstmgr:amd64 2.0.6.6
2020-10-08 22:53:06 status unpacked ampinstmgr:amd64 2.0.6.6
2020-10-08 22:53:06 status half-installed ampinstmgr:amd64 2.0.6.6
2020-10-08 22:53:10 status unpacked ampinstmgr:amd64 2.0.6.8

...

2020-10-08 22:53:10 configure ampinstmgr:amd64 2.0.6.8 <none>
2020-10-08 22:53:10 status unpacked ampinstmgr:amd64 2.0.6.8
2020-10-08 22:53:10 status half-configured ampinstmgr:amd64 2.0.6.8
2020-10-08 22:53:14 status installed ampinstmgr:amd64 2.0.6.8

Steps to reproduce:

  1. Upgrade package (via apt)

Actions taken to resolve so far:

I am not sure which actions I can undertake here. I can easily enable and start the services, which resumes the firewall management. But the upgrade always seems to cause this issue where manual intervention is needed.

Order By: Standard | Newest | Votes
AbhorrentJoel posted this 16 October 2020

The same occurred after 2.0.7.0 update.

AbhorrentJoel posted this 19 November 2020

Still present with 2.0.8.2. Didn't see any failures in the log, but services were not active after the update.

AbhorrentJoel posted this 02 February 2021

I have done a complete reinstall of the Linux server. I will check and see whether the issue persists after an upgrade once a new version of AMP is available.

Mike posted this 02 February 2021

I have actually looked into this, it was indeed disabling it because apt doesn't differentiate between 'upgrade' and 'uninstall'.

AbhorrentJoel posted this 03 February 2021

I have upgraded from 2.1 to 2.1.0.2 and it certainly looks like this particular issue has been resolved.

Using Docker, I am noticing a problem with the panel "forgetting" container settings for instances, despite the instances.json showing values set. I can create a new thread if necessary.

There may be a few other oddities I am experiencing on a fresh install of Ubuntu, AMP and Docker. Will create a new thread as necessary.

Close