Hello. I have had my RN104 for several years and it has been working just fine and this may be just a "one-off", so yesterday my RN104 rebooted itself for what I can tell...no reason. I downloaded the logs and will post here some of the findings. I'm hoping someone will spot something and point me to an issue if there is one.
Thanks
The logs
Frontview Logs tab 18 Apr 2019 12:23:57 System: ReadyNASOS background service started. 18 Apr 2019 12:13:59 System: The system is shutting down.
18 Apr 2019 00:53:38 Snapshot: Snapshot prune worker successfully deleted snapshot 2019_03_21__00_00_04 from share or LUN rsyslog.
status.log [19/04/18 12:13:59 PDT] notice:system:LOGMSG_SYSTEM_HALT The system is shutting down.
kernal.log Apr 15 16:24:37 TW kernel: mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=512 Apr 18 12:14:53 TW kernel: nfsd: last server has exited, flushing export cache Apr 18 12:15:02 TW systemd-shutdown[1]: Sending SIGTERM to remaining processes... -- Reboot -- Apr 18 12:22:14 TW kernel: Booting Linux on physical CPU 0x0
readynasd.log Apr 18 00:53:38 TW readynasd[2984]: Snapshot prune worker successfully deleted snapshot 2019_03_21__00_00_04 from share or LUN rsyslog. Apr 18 12:13:59 TW readynasd[2984]: The system is shutting down. Apr 18 12:14:52 TW readynasd[2984]: Exit main thread by SIGTERM. Apr 18 12:14:52 TW readynasd[2984]: readynasd is halted. -- Reboot --
system.log Apr 18 12:09:01 TW CRON[4442]: pam_unix(cron:session): session opened for user root by (uid=0) Apr 18 12:09:01 TW CRON[4446]: (root) CMD ( [ -x /usr/lib/php5/sessionclean ] && /usr/lib/php5/sessionclean) Apr 18 12:09:03 TW CRON[4442]: pam_unix(cron:session): session closed for user root Apr 18 12:14:04 TW msmtpq[4523]: mail for [ -C /etc/msmtprc myemail@email.net --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 myemail@email.net --timeout=60 ) : successful Apr 18 12:14:07 TW msmtpq[4533]: mail for [ -C /etc/msmtprc myemail@email.net --timeout=60 ] : send was successful Apr 18 12:14:50 TW upsmon[3130]: Signal 15: exiting Apr 18 12:14:50 TW wsdd2[2146]: Terminated received. Apr 18 12:14:50 TW wsdd2[2146]: terminating. Apr 18 12:14:51 TW rpc.mountd[3387]: Caught signal 15, un-registering and exiting. Apr 18 12:14:51 TW minissdpd[3229]: quitting... Apr 18 12:14:53 TW mysqld[2681]: 190418 12:14:53 [Note] /usr/sbin/mysqld: Normal shutdown Apr 18 12:14:53 TW mysqld[2681]: Apr 18 12:14:53 TW mysqld[2681]: 190418 12:14:53 [Note] Event Scheduler: Purging the queue. 0 events Apr 18 12:14:53 TW sshd[2208]: Received signal 15; terminating. Apr 18 12:14:54 TW nmbd[2213]: [2019/04/18 12:14:54.062285, 0] ../source3/nmbd/nmbd.c:58(terminate) Apr 18 12:14:54 TW nmbd[2213]: Got SIGTERM: going down... Apr 18 12:14:54 TW avahi-daemon[2171]: Got SIGTERM, quitting. Apr 18 12:14:54 TW avahi-daemon[2171]: Leaving mDNS multicast group on interface eth0.IPv6 with address 2601:600:997f:6324:2ac6:8eff:fe36:755c. Apr 18 12:14:54 TW avahi-daemon[2171]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.1.158. Apr 18 12:14:54 TW avahi-daemon[2171]: avahi-daemon 0.6.32 exiting. Apr 18 12:14:54 TW rsyncd[2159]: sent 0 bytes received 0 bytes total size 0 Apr 18 12:14:55 TW mysqld[2681]: 190418 12:14:55 InnoDB: Starting shutdown... Apr 18 12:14:55 TW mysqld[2681]: 190418 12:14:55 InnoDB: Waiting for 37 pages to be flushed Apr 18 12:14:57 TW mysqld[2681]: 190418 12:14:57 InnoDB: Shutdown completed; log sequence number 748362230 Apr 18 12:14:57 TW mysqld[2681]: 190418 12:14:57 [Note] /usr/sbin/mysqld: Shutdown complete Apr 18 12:14:57 TW mysqld[2681]: Apr 18 12:14:57 TW mysqld_safe[4628]: mysqld from pid file /var/run/mysqld/mysqld.pid ended Apr 18 12:15:00 TW rpcbind[2216]: rpcbind terminating on signal. Restart with "rpcbind -w" Apr 18 12:15:00 TW connmand[2170]: Terminating Apr 18 12:15:00 TW connmand[2170]: Time request for server 192.168.1.1 failed (101/Network is unreachable) Apr 18 12:15:00 TW connmand[2170]: Time request for server 192.168.1.1 failed (101/Network is unreachable) Apr 18 12:15:00 TW connmand[2170]: Remove interface eth0 [ ethernet ] Apr 18 12:15:00 TW connmand[2170]: Remove interface eth1 [ ethernet ] Apr 18 12:15:00 TW connmand[2170]: eth0 {remove} index 2 Apr 18 12:15:00 TW connmand[2170]: eth1 {remove} index 3 Apr 18 12:15:00 TW connmand[2170]: Exit -- Reboot -- Apr 18 12:22:40 TW wsdd2[2148]: starting.
Hi @BarkingSpider, you found in your kernel.log "Apr 15 16:24:37 TW kernel: mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=512".
As the RN104 is more and more overwhelmed by the challenges of the recent OS releases, I would put the blame on its lack of resources regarding CPU and RAM. In case you would like to improve performance and stability of your RN104 in general you might want to have a look at some suggestions behind the following link and apply as suits your needs. You will read my collected experiences with my RN104 throughout the years and your comments would be welcome.
