OMV 6 Updates failing

tazzz013 · Feb 3rd 2023

I got a notification that there were updates available this morning. Went to install, but updates failed. Prior I have had no issues.

Code

Calculating upgrade...
The following packages will be upgraded:
  docker-ce docker-ce-cli openmediavault
3 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 37.7 MB of archives.
After this operation, 106 MB disk space will be freed.
Err:1 https://download.docker.com/linux/debian bullseye/stable amd64 docker-ce-cli amd64 5:23.0.0-1~debian.11~bullseye
  Could not resolve 'download.docker.com'
Ign:2 http://packages.openmediavault.org/public shaitan/main amd64 openmediavault all 6.2.0-2
Err:3 https://download.docker.com/linux/debian bullseye/stable amd64 docker-ce amd64 5:23.0.0-1~debian.11~bullseye
  Could not resolve 'download.docker.com'
Err:2 https://openmediavault.github.io/packages shaitan/main amd64 openmediavault all 6.2.0-2
  Could not resolve 'packages.openmediavault.org'

** CONNECTION LOST **
█

Display More

macom · Feb 3rd 2023

You have an DNS issue.

tazzz013 · Feb 3rd 2023

Quote from macom

You have an DNS issue.

That is what I checked first, same DNS in OMV as with all my other servers/computers.

macom · Feb 3rd 2023

Post the output of these commands. Each in a separate code box

Code

ping -c 4 8.8.8.8
ping -c 4 google.com
cat /etc/resolv.conf
ls -al /etc/resolv.conf
systemctl status systemd-resolved.service

tazzz013 · Feb 3rd 2023

Quote from macom
Post the output of these commands. Each in a separate code box
Code
ping -c 4 8.8.8.8
ping -c 4 google.com
cat /etc/resolv.conf
ls -al /etc/resolv.conf
systemctl status systemd-resolved.service

Here is the output for each

Code

root@openmediavault:~# ping -c 4 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=115 time=16.9 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=115 time=18.0 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=115 time=16.1 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=115 time=16.6 ms

--- 8.8.8.8 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3003ms

Code

root@openmediavault:~# ping -c 4 google.com
ping: google.com: Name or service not known
root@openmediavault:~#

Code

root@openmediavault:~# cat /etc/resolv.conf
cat: /etc/resolv.conf: No such file or directory
root@openmediavault:~#

Code

root@openmediavault:~# ls -al /etc/resolv.conf
lrwxrwxrwx 1 root root 32 Sep 14  2020 /etc/resolv.conf -> /run/systemd/reslove/resolv.conf
root@openmediavault:~#

Code

root@openmediavault:~# systemctl status systemd-resolved.service
● systemd-resolved.service - Network Name Resolution
     Loaded: loaded (/lib/systemd/system/systemd-resolved.service; disabled; vendor preset: enabled)
     Active: inactive (dead)
       Docs: man:systemd-resolved.service(8)
             man:org.freedesktop.resolve1(5)
             https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
             https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients
root@openmediavault:~#

macom · Feb 3rd 2023

systemctl enable systemd-resolved

systemctl start systemd-resolved

ryecoaaron · Feb 3rd 2023

Quote from tazzz013

/run/systemd/reslove/resolv.conf

Is the /etc/resolv.conf symlink really pointing to this or did you type this instead of copy&paste?

tazzz013 · Feb 3rd 2023

Quote from ryecoaaron

Is the /etc/resolv.conf symlink really pointing to this or did you type this instead of copy&paste?

Copied and pasted

tazzz013 · Feb 3rd 2023

Quote from macom

systemctl enable systemd-resolved
systemctl start systemd-resolved

Stupid question I know, do you want me to run these commands?

macom · Feb 3rd 2023

rm /etc/resolv.conf && ln -s /run/systemd/resolve/resolv.conf /etc/

and then the other two commands I posted

macom · Feb 3rd 2023

Quote from tazzz013

Stupid question I know, do you want me to run these commands?

yep, after the other one, just above

tazzz013 · Feb 3rd 2023

Quote from macom

yep, after the other one, just above

Ok, I ran all 3. Didn't know if you wanted the output. Or if you just want me to try the updates again.

pgk831 · Feb 3rd 2023

Hi i have a same poroblem... i just push the update bottom and i give this:

Reading package lists... Done

Building dependency tree... Done

Reading state information... Done

0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

2 not fully installed or removed.

After this operation, 0 B of additional disk space will be used.

Setting up openmediavault (6.2.0-2) ...

Creating configuration database ...

Migrating configuration database ...

Setting up Salt environment ...

[ERROR ] 'EntryPoints' object has no attribute 'items'

Traceback (most recent call last):

File "/usr/lib/python3/dist-packages/salt/utils/parsers.py", line 210, in parse_args

mixin_after_parsed_func(self)

File "/usr/lib/python3/dist-packages/salt/utils/parsers.py", line 880, in __setup_extended_logging

log.setup_extended_logging(self.config)

File "/usr/lib/python3/dist-packages/salt/log/setup.py", line 414, in setup_extended_logging

providers = salt.loader.log_handlers(opts)

File "/usr/lib/python3/dist-packages/salt/loader.py", line 663, in log_handlers

_module_dirs(

File "/usr/lib/python3/dist-packages/salt/loader.py", line 138, in _module_dirs

for entry_point in entrypoints.iter_entry_points("salt.loader"):

File "/usr/lib/python3/dist-packages/salt/utils/entrypoints.py", line 62, in iter_entry_points

for entry_point_group, entry_points_list in entry_points.items():

AttributeError: 'EntryPoints' object has no attribute 'items'

[ERROR ] An un-handled exception was caught by salt's global exception handler:

TypeError: '>=' not supported between instances of 'AttributeError' and 'int'

Traceback (most recent call last):

File "/usr/lib/python3/dist-packages/salt/utils/parsers.py", line 210, in parse_args

mixin_after_parsed_func(self)

File "/usr/lib/python3/dist-packages/salt/utils/parsers.py", line 880, in __setup_extended_logging

log.setup_extended_logging(self.config)

File "/usr/lib/python3/dist-packages/salt/log/setup.py", line 414, in setup_extended_logging

providers = salt.loader.log_handlers(opts)

File "/usr/lib/python3/dist-packages/salt/loader.py", line 663, in log_handlers

_module_dirs(

File "/usr/lib/python3/dist-packages/salt/loader.py", line 138, in _module_dirs

for entry_point in entrypoints.iter_entry_points("salt.loader"):

File "/usr/lib/python3/dist-packages/salt/utils/entrypoints.py", line 62, in iter_entry_points

for entry_point_group, entry_points_list in entry_points.items():

AttributeError: 'EntryPoints' object has no attribute 'items'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):

File "/usr/bin/salt-call", line 11, in <module>

load_entry_point('salt==3003', 'console_scripts', 'salt-call')()

File "/usr/lib/python3/dist-packages/salt/scripts.py", line 449, in salt_call

client.run()

File "/usr/lib/python3/dist-packages/salt/cli/call.py", line 22, in run

self.parse_args()

File "/usr/lib/python3/dist-packages/salt/utils/parsers.py", line 215, in parse_args

mixin_after_parsed_func, traceback.format_exc(err)

File "/usr/lib/python3.9/traceback.py", line 167, in format_exc

return "".join(format_exception(*sys.exc_info(), limit=limit, chain=chain))

File "/usr/lib/python3.9/traceback.py", line 120, in format_exception

return list(TracebackException(

File "/usr/lib/python3.9/traceback.py", line 508, in __init__

self.stack = StackSummary.extract(

File "/usr/lib/python3.9/traceback.py", line 340, in extract

if limit >= 0:

TypeError: '>=' not supported between instances of 'AttributeError' and 'int'

Traceback (most recent call last):

File "/usr/lib/python3/dist-packages/salt/utils/parsers.py", line 210, in parse_args

mixin_after_parsed_func(self)

File "/usr/lib/python3/dist-packages/salt/utils/parsers.py", line 880, in __setup_extended_logging

log.setup_extended_logging(self.config)

File "/usr/lib/python3/dist-packages/salt/log/setup.py", line 414, in setup_extended_logging

providers = salt.loader.log_handlers(opts)

File "/usr/lib/python3/dist-packages/salt/loader.py", line 663, in log_handlers

_module_dirs(

File "/usr/lib/python3/dist-packages/salt/loader.py", line 138, in _module_dirs

for entry_point in entrypoints.iter_entry_points("salt.loader"):

File "/usr/lib/python3/dist-packages/salt/utils/entrypoints.py", line 62, in iter_entry_points

for entry_point_group, entry_points_list in entry_points.items():

AttributeError: 'EntryPoints' object has no attribute 'items'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):

File "/usr/bin/salt-call", line 11, in <module>

load_entry_point('salt==3003', 'console_scripts', 'salt-call')()

File "/usr/lib/python3/dist-packages/salt/scripts.py", line 449, in salt_call

client.run()

File "/usr/lib/python3/dist-packages/salt/cli/call.py", line 22, in run

self.parse_args()

File "/usr/lib/python3/dist-packages/salt/utils/parsers.py", line 215, in parse_args

mixin_after_parsed_func, traceback.format_exc(err)

File "/usr/lib/python3.9/traceback.py", line 167, in format_exc

return "".join(format_exception(*sys.exc_info(), limit=limit, chain=chain))

File "/usr/lib/python3.9/traceback.py", line 120, in format_exception

return list(TracebackException(

File "/usr/lib/python3.9/traceback.py", line 508, in __init__

self.stack = StackSummary.extract(

File "/usr/lib/python3.9/traceback.py", line 340, in extract

if limit >= 0:

TypeError: '>=' not supported between instances of 'AttributeError' and 'int'

dpkg: error processing package openmediavault (--configure):

installed openmediavault package post-installation script subprocess returned error exit status 1

dpkg: dependency problems prevent configuration of openmediavault-backup:

openmediavault-backup depends on openmediavault (>= 6); however:

Package openmediavault is not configured yet.

dpkg: error processing package openmediavault-backup (--configure):

dependency problems - leaving unconfigured

Errors were encountered while processing:

openmediavault

openmediavault-backup

E: Sub-process /usr/bin/dpkg returned an error code (1)

macom · Feb 3rd 2023

Quote from tazzz013

Or if you just want me to try the updates again.

Did you see any error?

Try the updates. If it does not work, run the commands again and post the output here.

tazzz013 · Feb 3rd 2023

Quote from macom

Did you see any error?
Try the updates. If it does not work, run the commands again and post the output here.

There were no errors when I ran the last commands I will try the updates again and see what happens.

pgk831 · Feb 3rd 2023

Quote from macom

Did you see any error?
Try the updates. If it does not work, run the commands again and post the output here.

sudo apt install docker-ce-cli=5:20.10.23~3-0~debian-bullseye
sudo apt install docker-ce=5:20.10.23~3-0~debian-bullseye

sudo service docker restart

This commands solve my problem, if anybody looking for a yesturday update error... Docker bin has some problem with the last version.

Wolf2000 · Feb 3rd 2023

I ran apt-get install apparmor-utils and then update.

everything on wonderful

Wolf2000 · Feb 3rd 2023

What have you done?

tazzz013 · Feb 3rd 2023

Quote from macom

Did you see any error?
Try the updates. If it does not work, run the commands again and post the output here.

macom, All updates installed, all is working. Thanks for your help! Now the real question, what was the issue if you don't mind me asking.

ED-209 · Feb 3rd 2023

Applied these however, I cannot access portainer through the web interface.
I can access webtop guacomole client but not portainer.
Refused to connect error, removing portainer and will wait it out.
Switching to the KVM pluggin as all I was using was WEBTOP anyway

OMV 6 Updates failing

Participate now!

Similar Threads

OMV Won't boot after update

Lost access (ssh, webui, samba)

openmediavault-nut 6.0.1-1 failing after update from openmediavault all 6.1.1-1 to openmediavault all 6.1.2-1

OMV 5.x Upgrade 5.x -> 6.x failing with "404 Not Found [IP: 199.232.34.132 443]"

apt failing, normal fixes don't seem to help.

Misteriously rolled back configs after reboot