Core Update failed. lamp has no active instances

Support
,
1

Hi, as per below.

Where can I find the glitched config/database entries to allow traefik to update.

Thanks

Turbond

<3>Cannot fetch lamp2 attributes: ‘IMAGE_URL’
<3>Cannot fetch lamp3 attributes: ‘IMAGE_URL’
_acontrol_task request attempt failed (Connection closed by server.). Retrying…
_acontrol_task request recovered successfully at attempt 2
<7>run-scriptdir /var/lib/nethserver/cluster/update-core-pre-modules.d/
Running /var/lib/nethserver/cluster/update-core-pre-modules.d/50update_grants…
<3>Cannot fetch lamp2 attributes: ‘IMAGE_URL’
<3>Cannot fetch lamp3 attributes: ‘IMAGE_URL’
<3>Cannot fetch lamp2 attributes: ‘IMAGE_URL’
<3>Cannot fetch lamp3 attributes: ‘IMAGE_URL’
Task cluster/update-module run failed: {‘output’: ‘’, ‘error’: ‘<7>podman-pull-missing Package traefik · GitHub\n<3>Module instance “traefik1” update failed with code 1\nAssertion failed\n File “/var/lib/nethserver/cluster/actions/update-module/50update”, line 154, in \n agent.assert_exp(errors == 0)\n’, ‘exit_code’: 2}
<7>run-scriptdir /var/lib/nethserver/cluster/update-core-post-modules.d/
Running /var/lib/nethserver/cluster/update-core-post-modules.d/70domain_notification…
Running /var/lib/nethserver/cluster/update-core-post-modules.d/70metrics…
Running /var/lib/nethserver/cluster/update-core-post-modules.d/90disable_testing…
update-core failed in some core modules
File “/var/lib/nethserver/cluster/actions/update-core/70update_modules”, line 48, in
agent.assert_exp(update_module_errors == 0, ‘update-core failed in some core modules’)

2

IMAGE_URL is an environment variable pointing to the current app image url that’s also saved in redis, see also Agent | NS8 dev manual

For example the IMAGE_URL for lamp2:

[root@ns8rockytest ~]# runagent -m lamp2 grep IMAGE_URL environment
IMAGE_URL=ghcr.io/stephdl/lamp:1.0.15
PREV_IMAGE_URL=ghcr.io/stephdl/lamp:1.0.14

Get redis entry for lamp2:

[root@ns8rockytest ~]# redis-cli hget module/lamp2/environment IMAGE_URL
"ghcr.io/stephdl/lamp:1.0.15"

Do the directories /home/lamp2 and /home/lamp3 exist?

Does it help to force remove lamp2 and lamp3? Please backup before removing anything or changing something in redis.

remove-module --no-preserve --force lamp2
1 Like
3

Hi,
Sorry for the delay… I was recovering from a bad flu. Interestingly I get the following

root@motueka:/home# runagent -m lamp2 grep IMAGE_URL environment
IMAGE_URL=ghcr.io/stephdl/lamp:1.0.0-dev.4
root@motueka:/home# runagent -m lamp3 grep IMAGE_URL environment
IMAGE_URL=ghcr.io/stephdl/lamp:1.0.12
root@motueka:/home# runagent -m lamp1 grep IMAGE_URL environment
runagent: [FATAL] Cannot find module lamp1 in the local node
root@motueka:/home# redis-cli hget module/lamp2/environment IMAGE_URL
(nil)
root@motueka:/home# redis-cli hget module/lamp1/environment IMAGE_URL
(nil)
root@motueka:/home# redis-cli hget module/lamp3/environment IMAGE_URL
(nil)
root@motueka:/home# ls
collabora1  lamp2  ldapproxy1  mail1     metrics1    samba1    webserver1
 lamp3  loki1       mariadb1  nextcloud1  traefik1  
root@motueka:/home# remove-module --no-preserve --force lamp2
<3>Cannot retrieve the NODE_ID of lamp2

root@motueka:/home# remove-module --no-preserve --force lamp1
<3>Cannot retrieve the NODE_ID of lamp1

root@motueka:/home# remove-module --no-preserve --force lamp3
<3>Cannot retrieve the NODE_ID of lamp3

and looking inside the lamp2/lamp3 folders I have the environment variables set ie

:/home/lamp2/.config/state# cat environment
IMAGE_DIGEST=sha256:56c38c408979cbc4012fb964a88067222b064dfa6f24cb8a8349674375f48ccb
IMAGE_ID=5ca919e36c4dcf62f2706894ded65784de0b33c0d990568ea71005c2224419dd
IMAGE_REOPODIGEST=Package lamp · GitHub
IMAGE_URL=Package lamp · GitHub
LAMP_SERVER_IMAGE=Package lamp-server · GitHub
MODULE_ID=lamp2
MODULE_UUID=1735c52d-5a09-4c53-9cb5-a40a1999c695
NODE_ID=1
TCP_PORT=20019
TCP_PORTS=20019

So although the directories exist, it looks like when I removed using the GUI it hasn’t removed the lamp modules correctly. I know lamp is a module that was being worked on, so it’s probably some sort of bug. So the big question is how do I remove this entry manually so the updates start working again.

Thanks everyone

4

Fixed: I had to run api-cli run get-configuration --agent module/lamp3 which then allowed for the remove-module --no-preserve lamp3 command to run. Now I have an access issue with a proxmox module I installed on nethserver, but that’s something I can deal with :joy:

Thank you Markus for pointing me in the right direction.

1 Like