…changed case and cable, still using the old SSD.
It’s been a while that the error described (Forbidden You don’t have permission to access this resource.
has come up. It’s difficult to say, but I think after changing the Power Supply to a original PiPowerSupply, it was solved.
But the troubles are not over, the Pi now simply shuts down randomly.
see output:
last -x | grep shutdown | less
shutdown system down 5.10.17-v8+ Tue Mar 30 20:40 - 01:00 (-18716+18:40)
shutdown system down 5.10.17-v8+ Tue Mar 30 17:04 - 01:00 (-18716+15:04)
shutdown system down 5.10.17-v8+ Tue Mar 30 11:05 - 01:00 (-18716+09:05)
shutdown system down 5.10.17-v8+ Mon Mar 29 20:35 - 01:00 (-18715+18:35)
shutdown system down 5.10.17-v8+ Mon Mar 29 15:48 - 01:00 (-18715+13:48)
shutdown system down 5.10.17-v8+ Mon Mar 29 09:21 - 01:00 (-18715+07:21)
shutdown system down 5.10.17-v8+ Thu Mar 25 20:48 - 01:00 (-18711+19:48)
shutdown system down 5.10.17-v8+ Wed Mar 24 21:54 - 01:00 (-18710+20:53)
shutdown system down 5.10.17-v8+ Wed Mar 24 20:29 - 01:00 (-18710+19:29)
shutdown system down 5.10.17-v8+ Mon Mar 22 00:11 - 01:00 (-18707+23:11)
shutdown system down 5.10.17-v8+ Sun Mar 21 23:23 - 01:00 (-18707+22:23)
shutdown system down 5.10.17-v8+ Sun Mar 21 15:36 - 01:00 (-18707+14:36)
shutdown system down 5.10.17-v8+ Fri Mar 19 22:17 - 01:00 (-18705+21:17)
shutdown system down 5.10.17-v8+ Sat Mar 13 20:52 - 01:00 (-18699+19:52)
shutdown system down 5.10.17-v8+ Sat Mar 13 18:08 - 01:00 (-18699+17:08)
shutdown system down 5.10.17-v8+ Thu Mar 11 08:28 - 01:00 (-18697+07:28)
shutdown system down 5.10.17-v8+ Wed Mar 10 22:43 - 01:00 (-18696+21:43)
shutdown system down 5.10.17-v8+ Tue Mar 9 10:52 - 01:00 (-18695+09:52)
shutdown system down 5.10.17-v8+ Tue Mar 9 10:47 - 01:00 (-18695+09:47)
shutdown system down 5.10.17-v8+ Sat Mar 6 23:04 - 01:00 (-18692+22:04)
shutdown system down 5.10.11-v8+ Sat Mar 6 22:48 - 01:00 (-18692+21:48)
shutdown system down 5.10.11-v8+ Tue Mar 2 20:44 - 01:00 (-18688+19:44)
shutdown system down 5.10.11-v8+ Thu Feb 25 22:37 - 01:00 (-18683+21:37)
shutdown system down 5.10.11-v8+ Tue Feb 23 07:09 - 01:00 (-18681+06:09)
shutdown system down 5.10.5-v8+ Wed Feb 10 09:10 - 01:00 (-18668+08:10)
shutdown system down 5.10.5-v8+ Sat Jan 30 22:02 - 01:00 (-18657+21:02)
shutdown system down 5.10.5-v8+ Sat Jan 16 20:54 - 01:00 (-18643+19:54)
shutdown system down 5.10.5-v8+ Fri Jan 15 21:19 - 01:00 (-18642+20:19)
shutdown system down 5.4.51-v8+ Fri Jan 8 21:01 - 01:00 (-18635+20:01)``
– what on earth is causing this?
I found this bash command: (unix.stackexchange.com
grep -iv ': starting\|kernel: .*: Power Button\|watching system buttons\|Stopped Cleaning Up\|Started Crash recovery kernel' \ > /var/log/messages /var/log/syslog /var/log/apcupsd* \ > | grep -iw 'recover[a-z]*\|power[a-z]*\|shut[a-z ]*down\|rsyslogd\|ups'
and this is what I got:
/var/log/messages:Mar 29 00:00:07 nextcloudpi rsyslogd: [origin software="rsyslogd" swVersion="8.1901.0" x-pid="464" x-info="https://www.rsyslog.com"] rsyslogd was HUPed
/var/log/messages:Mar 29 09:21:45 nextcloudpi rsyslogd: imuxsock: Acquired UNIX socket '/run/systemd/journal/syslog' (fd 3) from systemd. [v8.1901.0]
/var/log/messages:Mar 29 09:21:45 nextcloudpi rsyslogd: [origin software="rsyslogd" swVersion="8.1901.0" x-pid="452" x-info="https://www.rsyslog.com"] start
/var/log/messages:Mar 29 09:21:45 nextcloudpi kernel: [ 2.686483] bcm2835-power bcm2835-power: Broadcom BCM2835 power domains driver
/var/log/messages:Mar 29 09:21:45 nextcloudpi kernel: [ 10.232072] raid6: using neon recovery algorithm
/var/log/messages:Mar 29 09:21:45 nextcloudpi udisksd[455]: mountpoint /media/BackupPi is invalid, cannot recover the canonical path
/var/log/messages:Mar 29 15:48:51 nextcloudpi kernel: [ 2.687169] bcm2835-power bcm2835-power: Broadcom BCM2835 power domains driver
/var/log/messages:Mar 29 15:48:51 nextcloudpi kernel: [ 13.500036] raid6: using neon recovery algorithm
/var/log/messages:Mar 29 15:48:51 nextcloudpi rsyslogd: imuxsock: Acquired UNIX socket '/run/systemd/journal/syslog' (fd 3) from systemd. [v8.1901.0]
/var/log/messages:Mar 29 15:48:51 nextcloudpi rsyslogd: [origin software="rsyslogd" swVersion="8.1901.0" x-pid="446" x-info="https://www.rsyslog.com"] start
/var/log/messages:Mar 29 15:48:52 nextcloudpi udisksd[460]: mountpoint /media/BackupPi is invalid, cannot recover the canonical path
/var/log/messages:Mar 29 20:36:11 nextcloudpi kernel: [ 2.680356] bcm2835-power bcm2835-power: Broadcom BCM2835 power domains driver
/var/log/messages:Mar 29 20:36:11 nextcloudpi kernel: [ 10.332148] raid6: using neon recovery algorithm
/var/log/messages:Mar 29 20:36:11 nextcloudpi rsyslogd: imuxsock: Acquired UNIX socket '/run/systemd/journal/syslog' (fd 3) from systemd. [v8.1901.0]
/var/log/messages:Mar 29 20:36:11 nextcloudpi rsyslogd: [origin software="rsyslogd" swVersion="8.1901.0" x-pid="453" x-info="https://www.rsyslog.com"] start
/var/log/messages:Mar 29 20:36:12 nextcloudpi udisksd[450]: mountpoint /media/BackupPi is invalid, cannot recover the canonical path
/var/log/messages:Mar 30 10:58:32 nextcloudpi rsyslogd: [origin software="rsyslogd" swVersion="8.1901.0" x-pid="453" x-info="https://www.rsyslog.com"] rsyslogd was HUPed
/var/log/messages:Mar 30 11:05:56 nextcloudpi kernel: [ 2.680055] bcm2835-power bcm2835-power: Broadcom BCM2835 power domains driver
/var/log/messages:Mar 30 11:05:56 nextcloudpi kernel: [ 10.160012] raid6: using neon recovery algorithm
/var/log/messages:Mar 30 11:05:56 nextcloudpi rsyslogd: imuxsock: Acquired UNIX socket '/run/systemd/journal/syslog' (fd 3) from systemd. [v8.1901.0]
/var/log/messages:Mar 30 11:05:56 nextcloudpi rsyslogd: [origin software="rsyslogd" swVersion="8.1901.0" x-pid="441" x-info="https://www.rsyslog.com"] start
/var/log/messages:Mar 30 11:05:57 nextcloudpi udisksd[465]: mountpoint /media/BackupPi is invalid, cannot recover the canonical path
/var/log/messages:Mar 30 17:05:09 nextcloudpi rsyslogd: imuxsock: Acquired UNIX socket '/run/systemd/journal/syslog' (fd 3) from systemd. [v8.1901.0]
/var/log/messages:Mar 30 17:05:09 nextcloudpi kernel: [ 2.687048] bcm2835-power bcm2835-power: Broadcom BCM2835 power domains driver
/var/log/messages:Mar 30 17:05:09 nextcloudpi rsyslogd: [origin software="rsyslogd" swVersion="8.1901.0" x-pid="444" x-info="https://www.rsyslog.com"] start
/var/log/messages:Mar 30 17:05:09 nextcloudpi kernel: [ 10.228086] raid6: using neon recovery algorithm
/var/log/messages:Mar 30 17:05:10 nextcloudpi udisksd[448]: mountpoint /media/BackupPi is invalid, cannot recover the canonical path
/var/log/messages:Mar 30 20:40:25 nextcloudpi rsyslogd: imuxsock: Acquired UNIX socket '/run/systemd/journal/syslog' (fd 3) from systemd. [v8.1901.0]
/var/log/messages:Mar 30 20:40:25 nextcloudpi rsyslogd: [origin software="rsyslogd" swVersion="8.1901.0" x-pid="456" x-info="https://www.rsyslog.com"] start
/var/log/messages:Mar 30 20:40:25 nextcloudpi kernel: [ 1.902224] bcm2835-power bcm2835-power: Broadcom BCM2835 power domains driver
/var/log/messages:Mar 30 20:40:25 nextcloudpi kernel: [ 9.932078] raid6: using neon recovery algorithm
/var/log/messages:Mar 30 20:40:25 nextcloudpi udisksd[461]: mountpoint /media/BackupPi is invalid, cannot recover the canonical path
/var/log/messages:Mar 30 22:55:18 nextcloudpi rsyslogd: imuxsock: Acquired UNIX socket '/run/systemd/journal/syslog' (fd 3) from systemd. [v8.1901.0]
/var/log/messages:Mar 30 22:55:18 nextcloudpi rsyslogd: [origin software="rsyslogd" swVersion="8.1901.0" x-pid="454" x-info="https://www.rsyslog.com"] start
/var/log/messages:Mar 30 22:55:18 nextcloudpi kernel: [ 2.688416] bcm2835-power bcm2835-power: Broadcom BCM2835 power domains driver
/var/log/messages:Mar 30 22:55:18 nextcloudpi kernel: [ 10.252058] raid6: using neon recovery algorithm
/var/log/messages:Mar 30 22:55:18 nextcloudpi udisksd[448]: mountpoint /media/BackupPi is invalid, cannot recover the canonical path
/var/log/syslog:Mar 30 10:58:32 nextcloudpi rsyslogd: [origin software="rsyslogd" swVersion="8.1901.0" x-pid="453" x-info="https://www.rsyslog.com"] rsyslogd was HUPed
/var/log/syslog:Mar 30 10:58:33 nextcloudpi /etc/mysql/debian-start[1544]: Triggering myisam-recover for all MyISAM tables and aria-recover for all Aria tables
/var/log/syslog:Mar 30 11:05:48 nextcloudpi systemd[1]: Stopping Unattended Upgrades Shutdown...
/var/log/syslog:Mar 30 11:05:56 nextcloudpi kernel: [ 2.680055] bcm2835-power bcm2835-power: Broadcom BCM2835 power domains driver
/var/log/syslog:Mar 30 11:05:56 nextcloudpi systemd[1]: Started Update UTMP about System Boot/Shutdown.
/var/log/syslog:Mar 30 11:05:56 nextcloudpi kernel: [ 10.160012] raid6: using neon recovery algorithm
/var/log/syslog:Mar 30 11:05:56 nextcloudpi systemd[1]: Started listen-for-shutdown.service.
/var/log/syslog:Mar 30 11:05:56 nextcloudpi rsyslogd: imuxsock: Acquired UNIX socket '/run/systemd/journal/syslog' (fd 3) from systemd. [v8.1901.0]
/var/log/syslog:Mar 30 11:05:56 nextcloudpi rsyslogd: [origin software="rsyslogd" swVersion="8.1901.0" x-pid="441" x-info="https://www.rsyslog.com"] start
/var/log/syslog:Mar 30 11:05:57 nextcloudpi listen-for-shutdown.sh[448]: /usr/local/bin/listen-for-shutdown.py:8: RuntimeWarning: A physical pull up resistor is fitted on this channel!
/var/log/syslog:Mar 30 11:05:57 nextcloudpi listen-for-shutdown.sh[448]: GPIO.setup(3, GPIO.IN, pull_up_down=GPIO.PUD_UP)
/var/log/syslog:Mar 30 11:05:57 nextcloudpi udisksd[465]: mountpoint /media/BackupPi is invalid, cannot recover the canonical path
/var/log/syslog:Mar 30 11:06:04 nextcloudpi systemd[1]: Started Unattended Upgrades Shutdown.
/var/log/syslog:Mar 30 11:06:26 nextcloudpi /etc/mysql/debian-start[1250]: Triggering myisam-recover for all MyISAM tables and aria-recover for all Aria tables
/var/log/syslog:Mar 30 11:18:29 nextcloudpi systemd[1410]: Reached target Shutdown.
/var/log/syslog:Mar 30 17:04:56 nextcloudpi systemd[1]: Stopping listen-for-shutdown.service...
/var/log/syslog:Mar 30 17:04:56 nextcloudpi systemd[1]: Stopping Unattended Upgrades Shutdown...
/var/log/syslog:Mar 30 17:04:56 nextcloudpi listen-for-shutdown.sh[4511]: Stopping listen-for-shutdown.py
/var/log/syslog:Mar 30 17:04:56 nextcloudpi systemd[1]: Condition check resulted in Turns off Raspberry Pi display backlight on shutdown/reboot being skipped.
/var/log/syslog:Mar 30 17:05:09 nextcloudpi systemd[1]: Started Update UTMP about System Boot/Shutdown.
/var/log/syslog:Mar 30 17:05:09 nextcloudpi rsyslogd: imuxsock: Acquired UNIX socket '/run/systemd/journal/syslog' (fd 3) from systemd. [v8.1901.0]
/var/log/syslog:Mar 30 17:05:09 nextcloudpi kernel: [ 2.687048] bcm2835-power bcm2835-power: Broadcom BCM2835 power domains driver
/var/log/syslog:Mar 30 17:05:09 nextcloudpi rsyslogd: [origin software="rsyslogd" swVersion="8.1901.0" x-pid="444" x-info="https://www.rsyslog.com"] start
/var/log/syslog:Mar 30 17:05:09 nextcloudpi kernel: [ 10.228086] raid6: using neon recovery algorithm
/var/log/syslog:Mar 30 17:05:10 nextcloudpi systemd[1]: Started listen-for-shutdown.service.
/var/log/syslog:Mar 30 17:05:10 nextcloudpi listen-for-shutdown.sh[446]: /usr/local/bin/listen-for-shutdown.py:8: RuntimeWarning: A physical pull up resistor is fitted on this channel!
/var/log/syslog:Mar 30 17:05:10 nextcloudpi listen-for-shutdown.sh[446]: GPIO.setup(3, GPIO.IN, pull_up_down=GPIO.PUD_UP)
/var/log/syslog:Mar 30 17:05:10 nextcloudpi udisksd[448]: mountpoint /media/BackupPi is invalid, cannot recover the canonical path
/var/log/syslog:Mar 30 17:05:17 nextcloudpi systemd[1]: Started Unattended Upgrades Shutdown.
/var/log/syslog:Mar 30 17:05:39 nextcloudpi /etc/mysql/debian-start[1254]: Triggering myisam-recover for all MyISAM tables and aria-recover for all Aria tables
/var/log/syslog:Mar 30 20:40:09 nextcloudpi systemd[1]: Stopping Unattended Upgrades Shutdown...
/var/log/syslog:Mar 30 20:40:25 nextcloudpi systemd[1]: Started Update UTMP about System Boot/Shutdown.
/var/log/syslog:Mar 30 20:40:25 nextcloudpi systemd[1]: Started listen-for-shutdown.service.
/var/log/syslog:Mar 30 20:40:25 nextcloudpi rsyslogd: imuxsock: Acquired UNIX socket '/run/systemd/journal/syslog' (fd 3) from systemd. [v8.1901.0]
/var/log/syslog:Mar 30 20:40:25 nextcloudpi rsyslogd: [origin software="rsyslogd" swVersion="8.1901.0" x-pid="456" x-info="https://www.rsyslog.com"] start
/var/log/syslog:Mar 30 20:40:25 nextcloudpi kernel: [ 1.902224] bcm2835-power bcm2835-power: Broadcom BCM2835 power domains driver
/var/log/syslog:Mar 30 20:40:25 nextcloudpi kernel: [ 9.932078] raid6: using neon recovery algorithm
/var/log/syslog:Mar 30 20:40:25 nextcloudpi listen-for-shutdown.sh[445]: /usr/local/bin/listen-for-shutdown.py:8: RuntimeWarning: A physical pull up resistor is fitted on this channel!
/var/log/syslog:Mar 30 20:40:25 nextcloudpi listen-for-shutdown.sh[445]: GPIO.setup(3, GPIO.IN, pull_up_down=GPIO.PUD_UP)
/var/log/syslog:Mar 30 20:40:25 nextcloudpi udisksd[461]: mountpoint /media/BackupPi is invalid, cannot recover the canonical path
/var/log/syslog:Mar 30 20:40:32 nextcloudpi systemd[1]: Started Unattended Upgrades Shutdown.
/var/log/syslog:Mar 30 20:40:54 nextcloudpi /etc/mysql/debian-start[1249]: Triggering myisam-recover for all MyISAM tables and aria-recover for all Aria tables
/var/log/syslog:Mar 30 22:52:27 nextcloudpi systemd[1615]: Reached target Shutdown.
/var/log/syslog:Mar 30 22:55:04 nextcloudpi systemd[1]: Condition check resulted in Turns off Raspberry Pi display backlight on shutdown/reboot being skipped.
/var/log/syslog:Mar 30 22:55:18 nextcloudpi systemd[1]: Started Update UTMP about System Boot/Shutdown.
/var/log/syslog:Mar 30 22:55:18 nextcloudpi systemd[1]: Started listen-for-shutdown.service.
grep: /var/log/syslog:Mar 30 22:55:18 nextcloudpi rsyslogd: imuxsock: Acquired UNIX socket '/run/systemd/journal/syslog' (fd 3) from systemd. [v8.1901.0]
/var/log/apcupsd*: No such file or directory
/var/log/syslog:Mar 30 22:55:18 nextcloudpi rsyslogd: [origin software="rsyslogd" swVersion="8.1901.0" x-pid="454" x-info="https://www.rsyslog.com"] start
/var/log/syslog:Mar 30 22:55:18 nextcloudpi kernel: [ 2.688416] bcm2835-power bcm2835-power: Broadcom BCM2835 power domains driver
/var/log/syslog:Mar 30 22:55:18 nextcloudpi kernel: [ 10.252058] raid6: using neon recovery algorithm
/var/log/syslog:Mar 30 22:55:18 nextcloudpi listen-for-shutdown.sh[458]: /usr/local/bin/listen-for-shutdown.py:8: RuntimeWarning: A physical pull up resistor is fitted on this channel!
/var/log/syslog:Mar 30 22:55:18 nextcloudpi listen-for-shutdown.sh[458]: GPIO.setup(3, GPIO.IN, pull_up_down=GPIO.PUD_UP)
/var/log/syslog:Mar 30 22:55:18 nextcloudpi udisksd[448]: mountpoint /media/BackupPi is invalid, cannot recover the canonical path
/var/log/syslog:Mar 30 22:55:24 nextcloudpi systemd[1]: Started Unattended Upgrades Shutdown.
/var/log/syslog:Mar 30 22:55:46 nextcloudpi /etc/mysql/debian-start[1249]: Triggering myisam-recover for all MyISAM tables and aria-recover for all Aria tables```
at 20:40 the Pi shut down unexpected and did nor reboot.
(note: listen-for-shutdown.py is my power button, it was not pressed.)
is anyone seeing something suspicious?
I might soon just make a fresh install of the whole thing… it’s driving me nuts…