Danke Sabine heute hat mein RPi wohl mehrfach rebootet. Seitdem startet fhem nicht mehr.
pi@rpi:~ $ systemctl status fhem.service
● fhem.service - FHEM Home Automation
Loaded: loaded (/etc/systemd/system/fhem.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Mon 2020-02-10 15:06:49 CET; 2min 32s ago
Process: 1811 ExecStart=/usr/bin/perl fhem.pl fhem.cfg (code=exited, status=28)
CPU: 348ms
Feb 10 15:06:49 rpi systemd[1]: fhem.service: Unit entered failed state.
Feb 10 15:06:49 rpi systemd[1]: fhem.service: Failed with result 'exit-code'.
Feb 10 15:06:49 rpi systemd[1]: fhem.service: Service hold-off time over, scheduling restart.
Feb 10 15:06:49 rpi systemd[1]: Stopped FHEM Home Automation.
Feb 10 15:06:49 rpi systemd[1]: fhem.service: Start request repeated too quickly.
Feb 10 15:06:49 rpi systemd[1]: Failed to start FHEM Home Automation.
Feb 10 15:06:49 rpi systemd[1]: fhem.service: Unit entered failed state.
Feb 10 15:06:49 rpi systemd[1]: fhem.service: Failed with result 'exit-code'.
und beim versuch es zu re-starten
pi@rpi:~ $ sudo service fhem restart
Job for fhem.service failed because the control process exited with error code.
See "systemctl status fhem.service" and "journalctl -xe" for details.
pi@rpi:~ $ journalctl -xe
Feb 10 15:10:12 rpi systemd[1]: fhem.service: Failed with result 'exit-code'.
Feb 10 15:10:12 rpi systemd[1]: fhem.service: Service hold-off time over, scheduling restart.
Feb 10 15:10:12 rpi systemd[1]: Stopped FHEM Home Automation.
-- Subject: Unit fhem.service has finished shutting down
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit fhem.service has finished shutting down.
Feb 10 15:10:12 rpi systemd[1]: Starting FHEM Home Automation...
-- Subject: Unit fhem.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit fhem.service has begun starting up.
Feb 10 15:10:13 rpi perl[1953]: Can't open ./log/fhem-2020-02.log: No space left on device at fhem.pl line 2767.
Feb 10 15:10:13 rpi systemd[1]: fhem.service: Control process exited, code=exited status=28
Feb 10 15:10:13 rpi systemd[1]: Failed to start FHEM Home Automation.
-- Subject: Unit fhem.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit fhem.service has failed.
--
-- The result is failed.
Feb 10 15:10:13 rpi systemd[1]: fhem.service: Unit entered failed state.
Feb 10 15:10:13 rpi systemd[1]: fhem.service: Failed with result 'exit-code'.
Feb 10 15:10:13 rpi systemd[1]: fhem.service: Service hold-off time over, scheduling restart.
Feb 10 15:10:13 rpi systemd[1]: Stopped FHEM Home Automation.
-- Subject: Unit fhem.service has finished shutting down
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit fhem.service has finished shutting down.
Feb 10 15:10:13 rpi systemd[1]: fhem.service: Start request repeated too quickly.
Feb 10 15:10:13 rpi systemd[1]: Failed to start FHEM Home Automation.
-- Subject: Unit fhem.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit fhem.service has failed.
--
-- The result is failed.
Feb 10 15:10:13 rpi systemd[1]: fhem.service: Unit entered failed state.
Feb 10 15:10:13 rpi systemd[1]: fhem.service: Failed with result 'exit-code'.
Hilfe...
Evtl. kein Platz mehr?
Feb 10 15:10:13 rpi perl[1953]: Can't open ./log/fhem-2020-02.log: No space left on device at fhem.pl line 2767.
Partition korrupt?
Herunterfahren, Karten in anderes Linux Gerät stecken und Dateisystem prüfen.
Gesendet von meinem Doogee S60 mit Tapatalk
Ne .. was dort wortwörtlich steht:
No space left
Also einfach mal aufräumen ...
Zitat von: Wernieman am 10 Februar 2020, 15:37:57
Ne .. was dort wortwörtlich steht:
No space left
Also einfach mal aufräumen ...
wenn Die Partition nicht durch Fehler auf Read Only steht.
Oder kommt da nen anderer Fehler?
Plötzlicher Stromausfall ist ja Partitionskiller #1 bei de RPI...
Wo finde ich den "./log" auf dem RPi?
pi@rpi:/ $ df -h
Dateisystem Größe Benutzt Verf. Verw% Eingehängt auf
/dev/root 3,7G 3,5G 0 100% /
devtmpfs 459M 0 459M 0% /dev
tmpfs 464M 0 464M 0% /dev/shm
tmpfs 464M 13M 451M 3% /run
tmpfs 5,0M 4,0K 5,0M 1% /run/lock
tmpfs 464M 0 464M 0% /sys/fs/cgroup
/dev/mmcblk0p1 44M 23M 21M 52% /boot
tmpfs 93M 0 93M 0% /run/user/1000
Eigentlich zeigt er mir ja noch Rest an, auch wenn total bei 100% steht. Gern lösche ich mal alle FHEM Logs, brauche die nichtm, wenn ich sie nur finde...
Danke!
Selber gefunden :D
/opt/fhem/log
Nach dem Löschen:
pi@rpi:~ $ df -h
Dateisystem Größe Benutzt Verf. Verw% Eingehängt auf
/dev/root 3,7G 2,6G 962M 73% /
devtmpfs 459M 0 459M 0% /dev
tmpfs 464M 0 464M 0% /dev/shm
tmpfs 464M 13M 451M 3% /run
tmpfs 5,0M 4,0K 5,0M 1% /run/lock
tmpfs 464M 0 464M 0% /sys/fs/cgroup
/dev/mmcblk0p1 44M 23M 21M 52% /boot
//server/TempVolume 1,8T 238G 1,5T 14% /home/pi/TempVolume
tmpfs 93M 0 93M 0% /run/user/1000
pi@rpi:~ $ service fhem status
● fhem.service - FHEM Home Automation
Loaded: loaded (/etc/systemd/system/fhem.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2020-02-10 16:11:58 CET; 1min 30s ago
Process: 551 ExecStart=/usr/bin/perl fhem.pl fhem.cfg (code=exited, status=0/SUCCESS)
Main PID: 734 (perl)
Tasks: 12 (limit: 4915)
Memory: 101.6M
CPU: 18.318s
CGroup: /system.slice/fhem.service
├─ 734 /usr/bin/perl fhem.pl fhem.cfg
├─1298 node /usr/local/bin/alexa-fhem -c ./alexa-fhem.cfg
└─1368 /usr/bin/ssh -R 1234:127.0.0.1:44379 -oServerAliveInterval=90 -i /opt/fhem/.ssh/id_rsa -p 58824 fhem-va.fhem.de
Feb 10 16:11:56 rpi systemd[1]: Starting FHEM Home Automation...
Feb 10 16:11:58 rpi systemd[1]: Started FHEM Home Automation.
Alles in Butter! Danke nochmals!