OMV 5 ----> OMV 6 - Upgrade

macom · 20. Mai 2022

Zitat von Danny

fatal: unknown configuration directive 'IdentLookups' on line 22 of '/etc/proftpd/proftpd.conf'

edit that file and make it read

IdentLookups off in line 22

Danny · 20. Mai 2022

journalctl -xe

Code

root@WinklerFiles:~# journalctl -xe
░░ The job identifier is 3.
Mai 20 18:55:07 WinklerFiles systemd[40446]: Reached target Basic System.
░░ Subject: A start job for unit UNIT has finished successfully
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit UNIT has finished successfully.
░░
░░ The job identifier is 2.
Mai 20 18:55:07 WinklerFiles systemd[1]: Started User Manager for UID 0.
░░ Subject: A start job for unit user@0.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit user@0.service has finished successfully.
░░
░░ The job identifier is 1623.
Mai 20 18:55:07 WinklerFiles systemd[1]: Started Session 17 of user root.
░░ Subject: A start job for unit session-17.scope has finished successfully
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit session-17.scope has finished successfully.
░░
░░ The job identifier is 1732.
Mai 20 18:55:07 WinklerFiles systemd[40446]: Reached target Main User Target.
░░ Subject: A start job for unit UNIT has finished successfully
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit UNIT has finished successfully.
░░
░░ The job identifier is 1.
Mai 20 18:55:07 WinklerFiles systemd[40446]: Startup finished in 168ms.
░░ Subject: User manager start-up is now complete
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The user manager instance for user 0 has been started. All services queued
░░ for starting have been started. Note that other services might still be starting
░░ up or be started at any later time.
░░
░░ Startup of the manager took 168548 microseconds.
Mai 20 18:55:18 WinklerFiles autoshutdown[809]: root: INFO: 'main(): ------------------------------------------------------'
Mai 20 18:55:18 WinklerFiles autoshutdown[809]: root: INFO: 'main(): New supervision cycle started, checking system activity'
Mai 20 18:55:18 WinklerFiles autoshutdown[809]: root: DEBUG: '_check_system_active(): Calling: _check_clock()'
Mai 20 18:55:18 WinklerFiles autoshutdown[809]: root: DEBUG: '_check_clock(): Current time: Fr 20. Mai 18:55:18 CEST 2022, Stay up range - start: 09:55, end: 10:30 -> allow shutdown'
Mai 20 18:55:18 WinklerFiles autoshutdown[809]: root: INFO: '_check_clock(): System is in shutdown range -> next check'
Mai 20 18:55:18 WinklerFiles autoshutdown[809]: root: DEBUG: '_check_system_active(): Running on: eth0'
Mai 20 18:55:18 WinklerFiles autoshutdown[809]: root: DEBUG: '_check_system_active(): Calling: _ping_range()'
Mai 20 18:55:18 WinklerFiles autoshutdown[809]: root: DEBUG: '_ping_range(): INTERFACE: eth0'
Mai 20 18:55:18 WinklerFiles autoshutdown[809]: root: DEBUG: '_ping_range(): CLASS: 192.168.178'
Mai 20 18:55:18 WinklerFiles autoshutdown[809]: root: DEBUG: '_ping_range(): PINGLIST: N/A'
Mai 20 18:55:18 WinklerFiles autoshutdown[809]: root: DEBUG: '_ping_range(): RANGE: 25,26,29,32,34,40,41,44,45,201,202,203'
Mai 20 18:55:18 WinklerFiles autoshutdown[809]: root: DEBUG: '_ping_range(): pinglist_array: 192.168.178.25 192.168.178.26 192.168.178.29 192.168.178.32 192.168.178.34 192.168.178.40 192.168.178.41 192.168.178.44 192.168.178.45 192.168.>
Mai 20 18:55:18 WinklerFiles autoshutdown[809]: root: INFO: '_ping_range(): Retrieve list of active IPs for: eth0'
Mai 20 18:55:19 WinklerFiles autoshutdown[809]: root: INFO: '_ping_range(): 192.168.178.26 is active'
Mai 20 18:55:19 WinklerFiles autoshutdown[809]: root: INFO: '_ping_range(): 192.168.178.29 is active'
Mai 20 18:55:19 WinklerFiles autoshutdown[809]: root: INFO: '_ping_range(): Active IPs found in the specified range -> no shutdown'
Mai 20 18:55:19 WinklerFiles autoshutdown[809]: root: INFO: 'main(): Sleep for 30s'
Mai 20 18:55:49 WinklerFiles autoshutdown[809]: root: INFO: 'main(): ------------------------------------------------------'
Mai 20 18:55:49 WinklerFiles autoshutdown[809]: root: INFO: 'main(): New supervision cycle started, checking system activity'
...skipping...
░░ The job identifier is 3.
Mai 20 18:55:07 WinklerFiles systemd[40446]: Reached target Basic System.
░░ Subject: A start job for unit UNIT has finished successfully
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit UNIT has finished successfully.
░░
░░ The job identifier is 2.
Mai 20 18:55:07 WinklerFiles systemd[1]: Started User Manager for UID 0.
░░ Subject: A start job for unit user@0.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit user@0.service has finished successfully.
░░
░░ The job identifier is 1623.
Mai 20 18:55:07 WinklerFiles systemd[1]: Started Session 17 of user root.
░░ Subject: A start job for unit session-17.scope has finished successfully
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit session-17.scope has finished successfully.
░░
░░ The job identifier is 1732.
Mai 20 18:55:07 WinklerFiles systemd[40446]: Reached target Main User Target.
░░ Subject: A start job for unit UNIT has finished successfully
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit UNIT has finished successfully.
░░
░░ The job identifier is 1.
Mai 20 18:55:07 WinklerFiles systemd[40446]: Startup finished in 168ms.
░░ Subject: User manager start-up is now complete
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The user manager instance for user 0 has been started. All services queued
░░ for starting have been started. Note that other services might still be starting
░░ up or be started at any later time.
░░
░░ Startup of the manager took 168548 microseconds.

Alles anzeigen

Danny · 20. Mai 2022

Code

Mai 20 18:55:18 WinklerFiles autoshutdown[809]: root: INFO: 'main(): ------------------------------------------------------'
Mai 20 18:55:18 WinklerFiles autoshutdown[809]: root: INFO: 'main(): New supervision cycle started, checking system activity'
Mai 20 18:55:18 WinklerFiles autoshutdown[809]: root: DEBUG: '_check_system_active(): Calling: _check_clock()'
Mai 20 18:55:18 WinklerFiles autoshutdown[809]: root: DEBUG: '_check_clock(): Current time: Fr 20. Mai 18:55:18 CEST 2022, Stay up range - start: 09:55, end: 10:30 -> allow shutdown'
Mai 20 18:55:18 WinklerFiles autoshutdown[809]: root: INFO: '_check_clock(): System is in shutdown range -> next check'
Mai 20 18:55:18 WinklerFiles autoshutdown[809]: root: DEBUG: '_check_system_active(): Running on: eth0'
Mai 20 18:55:18 WinklerFiles autoshutdown[809]: root: DEBUG: '_check_system_active(): Calling: _ping_range()'
Mai 20 18:55:18 WinklerFiles autoshutdown[809]: root: DEBUG: '_ping_range(): INTERFACE: eth0'
Mai 20 18:55:18 WinklerFiles autoshutdown[809]: root: DEBUG: '_ping_range(): CLASS: 192.168.178'
Mai 20 18:55:18 WinklerFiles autoshutdown[809]: root: DEBUG: '_ping_range(): PINGLIST: N/A'
Mai 20 18:55:18 WinklerFiles autoshutdown[809]: root: DEBUG: '_ping_range(): RANGE: 25,26,29,32,34,40,41,44,45,201,202,203'
Mai 20 18:55:18 WinklerFiles autoshutdown[809]: root: DEBUG: '_ping_range(): pinglist_array: 192.168.178.25 192.168.178.26 192.168.178.29 192.168.178.32 192.168.178.34 192.168.178.40 192.168.178.41 192.168.178.44 192.168.178.45 192.168.>
Mai 20 18:55:18 WinklerFiles autoshutdown[809]: root: INFO: '_ping_range(): Retrieve list of active IPs for: eth0'
Mai 20 18:55:19 WinklerFiles autoshutdown[809]: root: INFO: '_ping_range(): 192.168.178.26 is active'
Mai 20 18:55:19 WinklerFiles autoshutdown[809]: root: INFO: '_ping_range(): 192.168.178.29 is active'
Mai 20 18:55:19 WinklerFiles autoshutdown[809]: root: INFO: '_ping_range(): Active IPs found in the specified range -> no shutdown'
Mai 20 18:55:19 WinklerFiles autoshutdown[809]: root: INFO: 'main(): Sleep for 30s'
Mai 20 18:55:49 WinklerFiles autoshutdown[809]: root: INFO: 'main(): ------------------------------------------------------'
Mai 20 18:55:49 WinklerFiles autoshutdown[809]: root: INFO: 'main(): New supervision cycle started, checking system activity'
Mai 20 18:55:49 WinklerFiles autoshutdown[809]: root: DEBUG: '_check_system_active(): Calling: _check_clock()'
Mai 20 18:55:49 WinklerFiles autoshutdown[809]: root: DEBUG: '_check_clock(): Current time: Fr 20. Mai 18:55:49 CEST 2022, Stay up range - start: 09:55, end: 10:30 -> allow shutdown'
Mai 20 18:55:50 WinklerFiles autoshutdown[809]: root: INFO: '_check_clock(): System is in shutdown range -> next check'
Mai 20 18:55:50 WinklerFiles autoshutdown[809]: root: DEBUG: '_check_system_active(): Running on: eth0'
Mai 20 18:55:50 WinklerFiles autoshutdown[809]: root: DEBUG: '_check_system_active(): Calling: _ping_range()'
Mai 20 18:55:50 WinklerFiles autoshutdown[809]: root: DEBUG: '_ping_range(): INTERFACE: eth0'
Mai 20 18:55:50 WinklerFiles autoshutdown[809]: root: DEBUG: '_ping_range(): CLASS: 192.168.178'
Mai 20 18:55:50 WinklerFiles autoshutdown[809]: root: DEBUG: '_ping_range(): PINGLIST: N/A'
Mai 20 18:55:50 WinklerFiles autoshutdown[809]: root: DEBUG: '_ping_range(): RANGE: 25,26,29,32,34,40,41,44,45,201,202,203'
Mai 20 18:55:50 WinklerFiles autoshutdown[809]: root: DEBUG: '_ping_range(): pinglist_array: 192.168.178.25 192.168.178.26 192.168.178.29 192.168.178.32 192.168.178.34 192.168.178.40 192.168.178.41 192.168.178.44 192.168.178.45 192.168.>
Mai 20 18:55:50 WinklerFiles autoshutdown[809]: root: INFO: '_ping_range(): Retrieve list of active IPs for: eth0'
Mai 20 18:55:51 WinklerFiles autoshutdown[809]: root: INFO: '_ping_range(): 192.168.178.26 is active'
Mai 20 18:55:51 WinklerFiles autoshutdown[809]: root: INFO: '_ping_range(): 192.168.178.29 is active'
Mai 20 18:55:51 WinklerFiles autoshutdown[809]: root: INFO: '_ping_range(): Active IPs found in the specified range -> no shutdown'
Mai 20 18:55:51 WinklerFiles autoshutdown[809]: root: INFO: 'main(): Sleep for 30s'
Mai 20 18:56:21 WinklerFiles autoshutdown[809]: root: INFO: 'main(): ------------------------------------------------------'
Mai 20 18:56:21 WinklerFiles autoshutdown[809]: root: INFO: 'main(): New supervision cycle started, checking system activity'
Mai 20 18:56:21 WinklerFiles autoshutdown[809]: root: DEBUG: '_check_system_active(): Calling: _check_clock()'
Mai 20 18:56:21 WinklerFiles autoshutdown[809]: root: DEBUG: '_check_clock(): Current time: Fr 20. Mai 18:56:21 CEST 2022, Stay up range - start: 09:55, end: 10:30 -> allow shutdown'
Mai 20 18:56:21 WinklerFiles autoshutdown[809]: root: INFO: '_check_clock(): System is in shutdown range -> next check'
Mai 20 18:56:21 WinklerFiles autoshutdown[809]: root: DEBUG: '_check_system_active(): Running on: eth0'
Mai 20 18:56:21 WinklerFiles autoshutdown[809]: root: DEBUG: '_check_system_active(): Calling: _ping_range()'
Mai 20 18:56:21 WinklerFiles autoshutdown[809]: root: DEBUG: '_ping_range(): INTERFACE: eth0'
Mai 20 18:56:21 WinklerFiles autoshutdown[809]: root: DEBUG: '_ping_range(): CLASS: 192.168.178'
Mai 20 18:56:21 WinklerFiles autoshutdown[809]: root: DEBUG: '_ping_range(): PINGLIST: N/A'
Mai 20 18:56:21 WinklerFiles autoshutdown[809]: root: DEBUG: '_ping_range(): RANGE: 25,26,29,32,34,40,41,44,45,201,202,203'
Mai 20 18:56:21 WinklerFiles autoshutdown[809]: root: DEBUG: '_ping_range(): pinglist_array: 192.168.178.25 192.168.178.26 192.168.178.29 192.168.178.32 192.168.178.34 192.168.178.40 192.168.178.41 192.168.178.44 192.168.178.45 192.168.>
Mai 20 18:56:21 WinklerFiles autoshutdown[809]: root: INFO: '_ping_range(): Retrieve list of active IPs for: eth0'
Mai 20 18:56:23 WinklerFiles autoshutdown[809]: root: INFO: '_ping_range(): 192.168.178.26 is active'
Mai 20 18:56:23 WinklerFiles autoshutdown[809]: root: INFO: '_ping_range(): 192.168.178.29 is active'
Mai 20 18:56:23 WinklerFiles autoshutdown[809]: root: INFO: '_ping_range(): Active IPs found in the specified range -> no shutdown'
Mai 20 18:56:23 WinklerFiles autoshutdown[809]: root: INFO: 'main(): Sleep for 30s'
lines 1346-1407/1407 (END)

Alles anzeigen

macom · 20. Mai 2022

see post #21 and then run the fix script again

Danny · 20. Mai 2022

Wow. The Errors are away! I see the Web-GUI. Thank you! Only Autoshutdown is not Visible, but it works properly. So i can not correct the preferences.

Tank you so much!

macom · 21. Mai 2022

Some plugins might not be upgraded. Post the output of

dpkg -l | grep openmediav

then we need to remove them from CLI and install again from the GUI of OMV.

Danny · 21. Mai 2022

Hello,

the output of "dpkg -l | grep openmediav" is:

Code

root@WinklerFiles:~# dpkg -l | grep openmediav
ii  openmediavault                            6.0.27-1                       all                                                                                                                                                                       openmediavault - The open network attached storage solution
ic  openmediavault-anacron                    5.0.3                          all                                                                                                                                                                       anacron plugin for OpenMediaVault.
ii  openmediavault-autoshutdown               5.1.7                          all                                                                                                                                                                       OpenMediaVault AutoShutdown Plugin
ii  openmediavault-diskstats                  6.0-6                          all                                                                                                                                                                       openmediavault disk monitoring plugin
ii  openmediavault-forkeddaapd                6.0-6                          all                                                                                                                                                                       openmediavault forked-daapd (DAAP server) plugin
ii  openmediavault-keyring                    1.0                            all                                                                                                                                                                       GnuPG archive keys of the OpenMediaVault archive
ic  openmediavault-locate                     3.5                            all                                                                                                                                                                       locate plugin for OpenMediaVault.
ii  openmediavault-omvextrasorg               6.0.9                          all                                                                                                                                                                       OMV-Extras.org Package Repositories for OpenMediaVault
root@WinklerFiles:~#

Anacron, autoshutdown, locate and omvextras are not visible in the menu.

I am excited

Danny

macom · 21. Mai 2022

Remove the plugins and install them fresh from the GUI of OMV.

apt purge openmediavault-locate openmediavault-autoshutdown openmediavault-anacron

Danny · 22. Mai 2022

It does not help. In "System/Einstellungen" is autoshutdown and omvextras visible, but not removeable. After remove it is still "green" and available.

Code

root@WinklerFiles:~# apt purge openmediavault-locate openmediavault-autoshutdown openmediavault-anacron openmediavault-omvextrasorg
Paketlisten werden gelesen… Fertig
Abhängigkeitsbaum wird aufgebaut… Fertig
Statusinformationen werden eingelesen… Fertig
E: Paket openmediavault-locate kann nicht gefunden werden.
E: Paket openmediavault-autoshutdown kann nicht gefunden werden.
E: Paket openmediavault-anacron kann nicht gefunden werden.
E: Paket openmediavault-omvextrasorg kann nicht gefunden werden.
root@WinklerFiles:~#

But in the OMV Plugin List is it available. Even after F5.

Greeting Danny

Zoki · 25. Mai 2022

Did you try this: RE: Error when updating packet lists or doing an upgrade

metRo_ · 15. August 2022

Now that omv is stable is a guide on how to upgrade from 5 to 6 on rpi4?

macom · 15. August 2022

Beitrag

RE: Is there a guide to in place upgrade?

Contributions wanted:

Backup the OS drive (this is allways a good idea, not only for upgrades)
Make sure, you have enough free space on your os drive
Check any installed plugins if they have been ported to OMV6
If you are using plugins which have not been / will not be ported, get rid of the plugins except unionfs / mergefolderfs. These two will automatically be be converted to the newer mergerfs plugin
(Many plugins can be replaced by docker containers. Do this before upgrading)
If you installed

…

Zoki

8. März 2022

OMV 5 ----> OMV 6 - Upgrade

Jetzt mitmachen!

Ähnliche Themen

omv 6.x on rpi

Upgrade fails

Is OMV6 stable enough to upgrade a production environment