systemctl status proftpd
Is there a guide to in place upgrade?
-
- OMV 5.x
- Upgrade 5.x -> 6.x
- Adrian E
-
-
-
-
-
Code
Alles anzeigenroot@openmediavault:~# systemctl start proftpd Job for proftpd.service failed because the control process exited with error code. See "systemctl status proftpd.service" and "journalctl -xe" for details. root@openmediavault:~# systemctl status proftpd ● proftpd.service - ProFTPD FTP Server Loaded: loaded (/lib/systemd/system/proftpd.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sat 2023-04-01 17:04:29 EDT; 17s ago Process: 59394 ExecStartPre=/usr/sbin/proftpd --configtest -c $CONFIG_FILE (code=exited, status=1/FAILURE) CPU: 21ms root@openmediavault:~# journalctl -xe ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ A start job for unit avahi-daemon.socket has finished successfully. ░░ ░░ The job identifier is 78. Apr 01 13:47:39 openmediavault systemd[1]: Listening on D-Bus System Message Bus Socket. ░░ Subject: A start job for unit dbus.socket has finished successfully ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ A start job for unit dbus.socket has finished successfully. ░░ ░░ The job identifier is 75. Apr 01 13:47:39 openmediavault systemd[1]: Starting Docker Socket for the API. ░░ Subject: A start job for unit docker.socket has begun execution ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ A start job for unit docker.socket has begun execution. ░░ ░░ The job identifier is 79. Apr 01 13:47:39 openmediavault systemd[1]: Mounted /srv/dev-disk-by-label-Photos. ░░ Subject: A start job for unit srv-dev\x2ddisk\x2dby\x2dlabel\x2dPhotos.mount has finished successfully ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ A start job for unit srv-dev\x2ddisk\x2dby\x2dlabel\x2dPhotos.mount has finished successfully. ░░ ░░ The job identifier is 39. Apr 01 13:47:39 openmediavault systemd[1]: Listening on Docker Socket for the API. ░░ Subject: A start job for unit docker.socket has finished successfully ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ A start job for unit docker.socket has finished successfully. ░░ ░░ The job identifier is 79. Apr 01 13:47:39 openmediavault systemd[1]: Reached target Sockets. ░░ Subject: A start job for unit sockets.target has finished successfully ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ A start job for unit sockets.target has finished successfully. ░░ ░░ The job identifier is 74. Apr 01 13:47:39 openmediavault kernel: EXT4-fs (md0): mounted filesystem without journal. Opts: user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl Apr 01 13:47:39 openmediavault folder2ram[1207]: start /var/log Apr 01 13:47:39 openmediavault systemd[1]: Finished Raise network interfaces. ░░ Subject: A start job for unit networking.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ A start job for unit networking.service has finished successfully. ░░ ░░ The job identifier is 107. Apr 01 13:47:40 openmediavault systemd[1]: Found device TOSHIBA_DT01ACA100 Movies. ░░ Subject: A start job for unit dev-disk-by\x2dlabel-Movies.device has finished successfully ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ A start job for unit dev-disk-by\x2dlabel-Movies.device has finished successfully. ░░ ░░ The job identifier is 34. Apr 01 13:47:40 openmediavault systemd[1]: Starting File System Check on /dev/disk/by-label/Movies... ░░ Subject: A start job for unit systemd-fsck@dev-disk-by\x2dlabel-Movies.service has begun execution ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ A start job for unit systemd-fsck@dev-disk-by\x2dlabel-Movies.service has begun execution. ░░ ░░ The job identifier is 32.
-
Let's check the status of OMV installation
dpkg -l | grep openmediav
-
Code
root@openmediavault:~# dpkg -l | grep openmediav ii openmediavault 6.3.7-1 all openmediavault - The open network attached storage solution ii openmediavault-flashmemory 6.2 all folder2ram plugin for openmediavault ii openmediavault-keyring 1.0 all GnuPG archive keys of the OpenMediaVault archive ii openmediavault-omvextrasorg 6.1.1 all OMV-Extras.org Package Repositories for OpenMediaVault ii openmediavault-resetperms 6.0.2 all Reset Permissions
-
-
ok, 6.3.7-1 had a bug, but had already proftp removed and replaced by a plugin
try
apt remove proftpd-core
check it will not remove openmediavault. If it wants to remove openmediavault press "n" and post the output here.
If it goes well run a omv-upgrade
-
Hi Guys,
Trying to upgrade to OMV6 and loaded sudo omv-salt stage run deploy.
It failed , see attachment
Any thoughts before I move to next step safely?
Thanks!!
-
Hola chicos,
Intentando actualizar a OMV6 y cargando sudo omv-salt stage run deployment.
Falló, ver adjunto
¿Alguna idea antes de pasar al siguiente paso de forma segura?
¡¡Gracias!!
sudo omv-salt stage ejecutar deployment.txt
Try to fix the hostname in the GUI in Network>General. Delete a .local
Or post the result to CLI of
hostname
-
-
I have done a reboot and my OMV interface is no longer working...
I am getting 403 Forbidden nginx
Loaded sudo omv-salt stage run deploy on Putty and getting : sudo: omv-salt: command not found
I think OMV6 and OMV5 got mixed...
Docker and Portainer are working though
What do you recommend?
Thanks!
-
Or post the result to CLI of
hostname
give me this
-
-
-
Did you follow all the steps in post No. 2? RE: Is there a guide to in place upgrade?
At what point did it fail?
-
I did follow all the steps and got a message that upgrade was successful. I noticed the upgrade went very fast....
However when rebooting, I figured out that I was still on OMV5.
Then I saw lots of upgrades to do, which I did, then when I rebooted I got the 403 Forbidden nginx
Am I able to recover this?
Thanks
-
See below :
Code
Alles anzeigenroot@openmediavault:~# apt-get install --reinstall openmediavault Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: libpam-modules : PreDepends: libpam-modules-bin (= 1.3.1-5) but 1.4.0-9+deb11u1 is to be installed openmediavault : Depends: acl but it is not going to be installed Depends: ifenslave but it is not going to be installed Depends: resolvconf Depends: acpid but it is not going to be installed Depends: libjavascript-minifier-xs-perl but it is not going to be installed Depends: pm-utils but it is not going to be installed Depends: ntp but it is not going to be installed openmediavault-flashmemory : Depends: openmediavault (>= 5.0) but 4.1.36-1 is to be installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).
Code
Alles anzeigenroot@openmediavault:~# apt --fix-broken install Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following package was automatically installed and is no longer required: fdisk Use 'apt autoremove' to remove it. The following additional packages will be installed: libpam-modules The following packages will be REMOVED: openmediavault-flashmemory openmediavault-omvextrasorg The following packages will be upgraded: libpam-modules 1 upgraded, 0 newly installed, 2 to remove and 333 not upgraded. 2 not fully installed or removed. Need to get 0 B/326 kB of archives. After this operation, 800 kB disk space will be freed. Do you want to continue? [Y/n] y Preconfiguring packages ... (Reading database ... 63742 files and directories currently installed.) Removing openmediavault-flashmemory (5.0.9) ... /var/lib/dpkg/info/openmediavault-flashmemory.prerm: 6: .: Can't open /usr/share/openmediavault/scripts/helper-functions dpkg: error processing package openmediavault-flashmemory (--remove): installed openmediavault-flashmemory package pre-removal script subprocess returned error exit status 127 /var/lib/dpkg/info/openmediavault-flashmemory.postinst: 6: .: Can't open /usr/share/openmediavault/scripts/helper-functions dpkg: error while cleaning up: installed openmediavault-flashmemory package post-installation script subprocess returned error exit status 127 Removing openmediavault-omvextrasorg (5.6.6) ... /var/lib/dpkg/info/openmediavault-omvextrasorg.postrm: 22: .: Can't open /usr/share/openmediavault/scripts/helper-functions dpkg: error processing package openmediavault-omvextrasorg (--remove): installed openmediavault-omvextrasorg package post-removal script subprocess returned error exit status 127 Errors were encountered while processing: openmediavault-flashmemory openmediavault-omvextrasorg E: Sub-process /usr/bin/dpkg returned an error code (1)
-
-
Code
root@openmediavault:~# dpkg -l | grep openm rc openmediavault 5.6.26-1 all openmediavault - The open network attached storage solution rF openmediavault-flashmemory 5.0.9 all folder2ram plugin for OpenMediaVault ii openmediavault-keyring 1.0 all GnuPG archive keys of the OpenMediaVault archive rH openmediavault-omvextrasorg 5.6.6 all OMV-Extras.org Package Repositories for OpenMediaVault rc openmediavault-resetperms 5.0 all Reset Permissions rc openmediavault-shellinabox 3.4 all Web-based SSH client.
-
just run the fix5to6upgrade script. search the forum on it for more details.
-
Thanks!
Could you please elaborate?
Is there a specific command I need to run?
Or could you please provide the link with detailed steps...
Appreciate your support!
-
-
Is there a specific command I need to run?
wget -O - https://github.com/OpenMediaVault-Plugin-Developers/installScript/raw/master/fix5to6upgrade | sudo bash
-
Could you please elaborate?
Is there a specific command I need to run?
Or could you please provide the link with detailed steps...
You have to try... If you literally search the forum (top right hand magnifying glass) for fix5to6upgrade, you will see people posting what to do time and time and time again.
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!