while attempting to update my server to the latest core version.
<3>Cannot fetch erpnext26 attributes: 'IMAGE_URL'
Error: ghcr.io/geniusdynamics/coolify:latest: image not known
<4>_synthesize_module_version: list index out of range
Error: ghcr.io/geniusdynamics/coolify:v4.0.0-beta.390: image not known
<4>_synthesize_module_version: list index out of range
Error: ghcr.io/geniusdynamics/documenso:latest: image not known
<4>_synthesize_module_version: list index out of range
Error: ghcr.io/geniusdynamics/kobotoolbox:latest: image not known
<4>_synthesize_module_version: list index out of range
<6>_fetch_metadata_json/glob: list index out of range
Error: ghcr.io/geniusdynamics/bigcapital:dev: image not known
<4>_synthesize_module_version: list index out of range
<4>Application ghcr.io/geniusdynamics/wallos has no version suitable for the installed Core 3.4.4. Minimum Core requirement is 0.0.0.
<4>Application ghcr.io/geniusdynamics/nocodb has no version suitable for the installed Core 3.4.4. Minimum Core requirement is 0.0.0.
<4>Application ghcr.io/geniusdynamics/2fauth has no version suitable for the installed Core 3.4.4. Minimum Core requirement is 0.0.0.
\'var/lib/nethserver/cluster/ui/js/app~970f9218.99bb654d.js\'\nremoved \'var/lib/nethserver/cluster/ui/js/app~970f9218.99bb654d.js.map\'\nremoved \'var/lib/nethserver/cluster/ui/js/lang-en-translation-json~9b60384d.1eb83036.js\'\nremoved \'var/lib/nethserver/cluster/ui/js/lang-en-translation-json~9b60384d.1eb83036.js.map\'\nremoved \'var/lib/nethserver/cluster/ui/js/settings-system-logs~31ecd969.b7d48df4.js\'\nremoved \'var/lib/nethserver/cluster/ui/js/settings-system-logs~31ecd969.b7d48df4.js.map\'\nremoved \'var/lib/nethserver/cluster/ui/js/software-center-core-apps~4a95bac2.bfd43150.js\'\nremoved \'var/lib/nethserver/cluster/ui/js/software-center-core-apps~4a95bac2.bfd43150.js.map\'\nremoved \'var/lib/nethserver/cluster/ui/js/software-center~software-center-core-apps~31ecd969.85869691.js\'\nremoved \'var/lib/nethserver/cluster/ui/js/software-center~software-center-core-apps~31ecd969.85869691.js.map\'\n<7>systemctl daemon-reload\nTraceback (most recent call last):\n File "/var/lib/nethserver/node/actions/update-core/50update", line 90, in <module>\n agent.set_env(\'PREV_IMAGE_ID\', prev_inspect[0][\'Id\'])\n ~~~~~~~~~~~~^^^\nIndexError: list index out of range\n', 'exit_code': 1}
update-core failed in some nodes
File "/var/lib/nethserver/cluster/actions/update-core/50update_core", line 45, in <module>
agent.assert_exp(update_core_errors == 0, 'update-core failed in some nodes')
as well as
Error: ghcr.io/nethserver/core:3.4.4: image not known
<7>podman-pull-missing ghcr.io/nethserver/core:3.4.5
Trying to pull ghcr.io/nethserver/core:3.4.5...
Getting image source signatures
Copying blob sha256:d36e98ab1ba996b693ba0cc3aeed573e274195c71591c5f68707c3df342f637b
Copying config
removed 'var/lib/nethserver/cluster/ui/js/software-center~software-center-core-apps~31ecd969.85869691.js'
removed 'var/lib/nethserver/cluster/ui/js/software-center~software-center-core-apps~31ecd969.85869691.js.map'
<7>systemctl daemon-reload
Traceback (most recent call last):
File "/var/lib/nethserver/node/actions/update-core/50update", line 90, in <module>
agent.set_env('PREV_IMAGE_ID', prev_inspect[0]['Id'])
~~~~~~~~~~~~^^^
IndexError: list index out of range
subsequent update attempts fails at 23
Above error has been condensed due to limitations in charactors, but i guess should provide enough information
davidep
February 13, 2025, 8:32am
2
Hi Martin, thank you for sharing this issue!
This error indicates that the old core image was not found in the Podman image storage.
The update-core action (step 50update) aborts due to an unhandled condition. The code could be improved to handle cases where the current core image is missing, though this situation is uncommon.
Normally, the current core image is preserved until the next update. Therefore, I’d move this thread to the Support
We can try to recover from this issue—how many nodes are in the cluster? Do all nodes report the same error?
hucky
February 13, 2025, 9:25am
3
for me it is also not possible to update core or the mail and sogo app. starts normal but finish with error.
After a reboot everything is installed and worked
Yeah funny thing after reboot update worked
1 Like
hucky
February 19, 2025, 11:57am
5
and again the updates fails from 3.4.5 to 3.4.6. In this case also a restart dont help.
Aufgabe cluster/update-core fehlgeschlagen
Unteraufgabe cluster/list-actions abgeschlossen
Unteraufgabe cluster/update-core fehlgeschlagen
hucky
February 20, 2025, 5:23pm
7
still no luck with the installation of the core update or the mail app. any suggestions? it is the update from 3.4.5to 3.4.6…
MadPatrick
February 20, 2025, 6:32pm
8
FYI
3 Likes
my update had no issues as well
2 Likes
hucky
February 22, 2025, 1:30pm
10
after rebuilding back the vm from the ns8 i was able to update the core and the mail app. today, i tried to update the samba and get dirtectly ain error after trying installing the update…
|2025-02-22 14:22:53|A|pop.gmx.net|NS8.domain-ns8.de|OK (cache)
|2025-02-22 14:22:53|A|pop.gmx.net|NS8.domain-ns8.de|OK (cache)
|2025-02-22 14:22:53|A|pop.gmx.net|NS8.domain-ns8.de|OK (cache)
mrmarkuz
February 22, 2025, 8:44pm
11
Did you revert to a snapshot? There was an issue with core 3.4.3 IIRC. Maybe you should think about reinstalling just to exclude old issues.
hucky:
insane dns request
There are some DNS checks when a mail is received but that’s really a lot.
It seems pihole caches the queries so it shouldn’t get killed…
hucky
February 23, 2025, 7:36am
12
its not just the mail system it happens always with the ns8 system, like a minute ago:
|2025-02-23 08:32:52|A|repo.mrmarkuz.com|NS8.domain-ns8.de|OK (cache)
hucky
February 23, 2025, 7:38am
13
The Core is the correct one core1 Knoten 1 3.4.6
hucky
February 23, 2025, 7:39am
14
you are right, it is not killing the system but make it very slow when the NS8 is doing the dns request
mrmarkuz
February 23, 2025, 11:13am
15
How did you implement pihole?
Could it be a DNS loop/misconfiguration?
Please share the DNS configuration (DNS servers used, conditional forwarders etc) of NS8 and pihole.
hucky
February 23, 2025, 11:30am
16
pihole is as a lxc on my proxmox
i dont think so… or just at the ns8. all other systems are normal, just the ns8 makes this trouble. Where can i check or get the informations what u need? is there something like a protocoll?
mrmarkuz
February 23, 2025, 12:42pm
17
For example if pihole and NS8 use each other as DNS server there would be a loop.
Which DNS server(s) did you configure for NS8 and pihole? If you use dnsmasq on NS8, which DNS forwarders are configured?
hucky
February 23, 2025, 12:58pm
18
pihole has as dns only the gateway a ipfiresystem
mrmarkuz
February 23, 2025, 2:00pm
19
I assume the ipfire gateway forwards DNS queries to some external DNS server.
To show the used nameservers on NS8 please execute the following:
cat /etc/resolv.conf
Check samba DNS forwarder:
runagent -m samba1 cat dns_forwarder.env
No.
hucky
February 23, 2025, 2:14pm
20
Yes, the ipfire forward to external DNS Servers
nameserver 192.168.100.111 <— is the pi-hole
runagent -m samba1 cat dns_forwarder.env
mrmarkuz
February 23, 2025, 2:28pm
21
Why is the NS8 configured as it’s own DNS server?
After editing /etc/resolv.conf you need to restart samba to apply the changed config to samba:
runagent -m samba1 systemctl --user restart samba-dc
