DietPi v9.6.1
The attempt to update portainer (dietpi-software reinstall 185) failed.
The computer hangs
in the terminal runs endlessly:
Job redis-server.service/stop running: Error trying to save the DB, can't exit.
What can I do?
Sharing some more information on your system like the troubleshooting template that you ignored.
And redis service log
journalctl -u redis-server.service
here is the result for redis journalctl
root@DietPi:~# journalctl -u redis-server.service
Aug 02 16:02:06 DietPi systemd[1]: Starting redis-server.service - Advanced key-value store...
Aug 02 16:02:06 DietPi redis-server[690]: 690:C 02 Aug 2024 16:02:06.597 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
Aug 02 16:02:06 DietPi redis-server[690]: 690:C 02 Aug 2024 16:02:06.597 # Redis version=7.0.15, bits=64, commit=00000000, modified=0, pid=690, just started
Aug 02 16:02:06 DietPi redis-server[690]: 690:C 02 Aug 2024 16:02:06.597 # Configuration loaded
Aug 02 16:02:06 DietPi redis-server[690]: oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
Aug 02 16:02:06 DietPi redis-server[690]: Redis version=7.0.15, bits=64, commit=00000000, modified=0, pid=690, just started
Aug 02 16:02:06 DietPi redis-server[690]: Configuration loaded
Aug 02 16:02:06 DietPi redis-server[690]: 690:M 02 Aug 2024 16:02:06.599 # Warning: Could not create server TCP listening socket ::1:6379: bind: Cannot assign requested address
Aug 02 16:02:06 DietPi redis[690]: Warning: Could not create server TCP listening socket ::1:6379: bind: Cannot assign requested address
Aug 02 16:02:06 DietPi redis-server[690]: 690:M 02 Aug 2024 16:02:06.604 # Server initialized
Aug 02 16:02:06 DietPi redis-server[690]: 690:M 02 Aug 2024 16:02:06.604 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
Aug 02 16:02:06 DietPi redis[690]: Server initialized
Aug 02 16:02:06 DietPi redis[690]: WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
Aug 02 16:02:06 DietPi systemd[1]: Started redis-server.service - Advanced key-value store.
and further system information:
Required Information
DietPi Version:
root@DietPi:~# cat /boot/dietpi/.version
G_DIETPI_VERSION_CORE=9
G_DIETPI_VERSION_SUB=6
G_DIETPI_VERSION_RC=1
G_GITBRANCH=‘master’
G_GITOWNER=‘MichaIng’
Distro Version:
root@DietPi:~# echo $G_DISTRO_NAME $G_RASPBIAN
bookworm
root@DietPi:
Kernel Version:
root@DietPi:~# uname --all
Linux DietPi 6.1.0-23-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.99-1 (2024-07-15) x86_64 GNU/Linux
Architecture:
root@DietPi:~# dpkg --print-architecture
amd64
SBC model:
Virtual Machine (x86_64)
The log is showing a clean start of redis-server only. Has the system been rebooted in between?
reboot does not work - the error message appears
Can you share the log right after the error occure.
The error message is as described above:
Job redis-server.service/stop running: Error trying to save the DB, can’t exit.
then I can only power off
You can connect with a 2nd ssh session to get the log
Yes, I can do that
how do I retrieve the log that you mean?
Going to quote myself
I had already created the protocol and added it to the chat - see above in the history
Yes and it was showing the service start only. You would need to create it right after the issue happens
during the boot process (and the mentioned error) putty is also disconnected (inactive)
the operating system does not let me boot completely - and during the boot I have no possibility to connect
Can you clearly describe the order of events? Because so far you have only described an error for redis not being able to stop during service being stopped. But now there are problems during the boot process?
yes exactly, because the machine hung up when booting, i had to abort by switching it off
when rebooting - the hangup remains
Can you connect a monitor or do you have an UART adapter? Otherwise we will gather no information what happens during booting.
It’s a VM as stated above. Therefore there should be some output on screen 
Means situation changed und system is not booting anymore? Because you started with an issue during software installation?
Can you do a screen print from the hanging system during boot? As well keep it running for a while. Usually, services should time out if not starting correctly.
Can you share more from the screen? I don’t understand why there is a service stopped during boot process. This looks like a system shutdown and not like a startup.