Hi,
After I updated OMV I can no longer apply my changes.
I always get "500 - ok"-Error.
detailed Error:
https://privatebin.net/?b2cedd…GbgdzhNk9F1RBwCoDkve9PbSD
I hope somebody is able to help me.
OMV7 after some update "Pending configuration changes" doesn't work anymore.
-
- resolved
- OMV 7.x
- Sputter1414
-
ryecoaaron
Approved the thread. -
Did you look at the output it told you to look at?
See "systemctl status ssh.service" and "journalctl -xeu ssh.service" for details. -
Did you look at the output it told you to look at?
See "systemctl status ssh.service" and "journalctl -xeu ssh.service" for details.I have unintentionally left something out.
Log:Code
Display Moreroot@nas:~# systemctl status ssh × ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Tue 2025-02-11 16:15:16 CET; 13min ago Docs: man:sshd(8) man:sshd_config(5) Process: 1448356 ExecStartPre=/usr/sbin/sshd -t (code=exited, status=0/SUCCESS) Process: 1448357 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, status=255/EXCEPTION) Main PID: 1448357 (code=exited, status=255/EXCEPTION) CPU: 60ms Feb 11 16:15:16 nas systemd[1]: Starting ssh.service - OpenBSD Secure Shell server... Feb 11 16:15:16 nas sshd[1448357]: error: Bind to port 22 on 0.0.0.0 failed: Address already in use. Feb 11 16:15:16 nas sshd[1448357]: error: Bind to port 22 on :: failed: Address already in use. Feb 11 16:15:16 nas sshd[1448357]: fatal: Cannot bind any address. Feb 11 16:15:16 nas systemd[1]: ssh.service: Main process exited, code=exited, status=255/EXCEPTION Feb 11 16:15:16 nas systemd[1]: ssh.service: Failed with result 'exit-code'. Feb 11 16:15:16 nas systemd[1]: Failed to start ssh.service - OpenBSD Secure Shell server. root@nas:~# systemctl status ssh [...] ░░ The job identifier is 1364440. Feb 11 16:15:16 nas sshd[1448357]: error: Bind to port 22 on 0.0.0.0 failed: Address already in use. Feb 11 16:15:16 nas sshd[1448357]: error: Bind to port 22 on :: failed: Address already in use. Feb 11 16:15:16 nas sshd[1448357]: fatal: Cannot bind any address. Feb 11 16:15:16 nas systemd[1]: ssh.service: Main process exited, code=exited, status=255/EXCEPTION ░░ Subject: Unit process exited ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ An ExecStart= process belonging to unit ssh.service has exited. ░░ ░░ The process' exit code is 'exited' and its exit status is 255. Feb 11 16:15:16 nas systemd[1]: ssh.service: Failed with result 'exit-code'. ░░ Subject: Unit failed ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ The unit ssh.service has entered the 'failed' state with result 'exit-code'. Feb 11 16:15:16 nas systemd[1]: Failed to start ssh.service - OpenBSD Secure Shell server. ░░ Subject: A start job for unit ssh.service has failed ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ A start job for unit ssh.service has finished with a failure. ░░ ░░ The job identifier is 1364440 and the job result is failed.I can connect via. SSH to my NAS and connect from my NAS to other servers without a problem. So it seems that SSH is running?
-
-
So it seems that SSH is running?
Yep. Seems something other than systemd started ssh. Have you rebooted?
-
Yep. Seems something other than systemd started ssh. Have you rebooted?
Yes
-
Do you have ssh running in a docker container or something else?
-
-
Do you have ssh running in a docker container or something else?
Nope
-
You won't be able to do this via ssh but what is the output of:
sudo systemctl stop sshd
sudo killall sshd
sudo ss -tulpn | grep 22
sudo sshd
-
Here is the picture.
But I can login via. SSH without any problems after executing all your comments.(Sorry for the bad quality, I don't have a good camera right now)
-
-
dropbear is listening on port 22. You must have installed dropbear. That is causing your problems. Remove dropbear since it will not work with OMV.
-
But how did it get on the server?
Something you did. Nothing OMV would install it.
-
-
votdev
Added the Label resolved -
votdev
Added the Label OMV 7.x
Participate now!
Don’t have an account yet? Register yourself now and be a part of our community!