NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RN104 Unexpected ReBoot
Hello Community.
I have a RN104 for several years and so far no issues until yesterday. For some unknow reason, it re-booted it's self. I have downloaded the logs and viewed some of the entries, ...
Looking further... in the systemd-journal.log I found the following:
Apr 18 12:09:03 TW CRON[4442]: pam_unix(cron:session): session closed for user root
Apr 18 12:13:44 TW systemd-logind[2157]: Power key pressed.
Apr 18 12:13:48 TW systemd-logind[2157]: Power key pressed.
Apr 18 12:13:55 TW systemd-logind[2157]: Power key pressed.
Apr 18 12:13:59 TW readynasd[2984]: The system is shutting down.
Apr 18 12:14:01 TW systemd-logind[2157]: Power key pressed.
Apr 18 12:14:02 TW systemd-logind[2157]: Power key pressed.
Apr 18 12:14:04 TW systemd-logind[2157]: Power key pressed.
Apr 18 12:14:04 TW msmtpq[4523]: mail for [ -C /etc/msmtprc myemail@email.com --timeout=60 ] : couldn't be sent - host not connected
Apr 18 12:14:04 TW msmtpq[4526]: enqueued mail as : [ 2019-04-18-12.14.00 ] ( -C /etc/msmtprc negative.nancy@comcast.net --timeout=60 ) : successful
Apr 18 12:14:05 TW systemd-logind[2157]: Power key pressed.
Apr 18 12:14:07 TW msmtpq[4533]: mail for [ -C /etc/msmtprc myemail@email.com --timeout=60 ] : send was successful
Apr 18 12:14:07 TW systemd[1]: Started /sbin/poweroff.
Apr 18 12:14:07 TW readynasd[2984]: Running timer as unit: run-r3cc53709fcd14252a89fb719b3b36c36.timer
Apr 18 12:14:07 TW readynasd[2984]: Will run service as unit: run-r3cc53709fcd14252a89fb719b3b36c36.service
Apr 18 12:14:18 TW systemd-logind[2157]: Power key pressed.
Apr 18 12:14:49 TW systemd[1]: Started /sbin/poweroff.
In fact, I found sever of the messages for "Power Key pressed". How or what is causing this? Do I have a bad power button? Some internal OS error causing this issue? There was no one around this day to push any button. The other times are:
Apr 18 00:56:37 TW systemd-logind[2157]: Power key pressed.
Apr 18 11:36:52 TW systemd-logind[2157]: Power key pressed.
Apr 18 11:58:16 TW systemd-logind[2157]: Power key pressed.
Apr 18 12:13:44 TW systemd-logind[2157]: Power key pressed.
Apr 18 12:13:48 TW systemd-logind[2157]: Power key pressed.
Apr 18 12:13:55 TW systemd-logind[2157]: Power key pressed.
Apr 18 12:13:59 TW readynasd[2984]: The system is shutting down.
Apr 18 12:14:01 TW systemd-logind[2157]: Power key pressed.
Apr 18 12:14:02 TW systemd-logind[2157]: Power key pressed.
Apr 18 12:14:04 TW systemd-logind[2157]: Power key pressed.
Apr 18 12:14:05 TW systemd-logind[2157]: Power key pressed.
Apr 18 12:14:18 TW systemd-logind[2157]: Power key pressed.
Apr 18 12:23:55 TW systemd-logind[2157]: Power key pressed.
Apr 18 12:27:08 TW systemd-logind[2157]: Power key pressed.
Apr 18 12:42:20 TW systemd-logind[2157]: Power key pressed.
Anyone know why this might have happened?
Hi BarkingSpider, make sure your external power supply is not directly exposed to sunlight. The time stamps in your excerpts from the logs are all between 12:00 and 15:00 as I can see. Depending on where you are and the sun shining directly on this power supply, that could be a problem, too, even if you are keeping the Nas in the shade.
Kind regards
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
