Pi rebooting at 0617 ?? - Raspberry Pi Forums

really odd problem - 1 of pis has started reboot , hang every 4 days @ similar time, ideas start looking @ appreciated ! fwiw it's 1 have running wifi, others have same os version hardwired.

doesn't seem matter how long it's been , running, boot time 17 minutes past 5 or 6 in morning example:

code: select all

messages:mar 28 06:17:26 rfsniffer rsyslogd: [origin software="rsyslogd" swversion="5.8.11" x-pid="2118" x-info="http://www.rsyslog.com"] start ... messages:mar 24 06:17:28 rfsniffer rsyslogd: [origin software="rsyslogd" swversion="5.8.11" x-pid="2124" x-info="http://www.rsyslog.com"] start ... messages:mar 20 05:17:28 rfsniffer rsyslogd: [origin software="rsyslogd" swversion="5.8.11" x-pid="2121" x-info="http://www.rsyslog.com"] start 

there's odd 0 sized file in /tmp same timestamp:

code: select all

$ ls -l /tmp srwxr-xr-x 1 root root    0 mar 28 06:17 wpa_ctrl_1906-1 

, bunch of messages in /var/log/user.log relate last time hung - e.g. today 30/03/2015 file contains:

code: select all

mar 28 06:17:34 rfsniffer wpa_action: creating sendsigs omission pidfile: /run/sendsigs.omit.d/wpasupplicant.wpa_supplicant.wlan0.pid mar 28 06:17:34 rfsniffer wpa_action: bssid=f8:7b:8c:0c:34:73 mar 28 06:17:34 rfsniffer wpa_action: ssid=wlan mar 28 06:17:34 rfsniffer wpa_action: id=0 mar 28 06:17:34 rfsniffer wpa_action: mode=station mar 28 06:17:34 rfsniffer wpa_action: pairwise_cipher=ccmp mar 28 06:17:34 rfsniffer wpa_action: group_cipher=ccmp mar 28 06:17:34 rfsniffer wpa_action: key_mgmt=wpa2-psk mar 28 06:17:34 rfsniffer wpa_action: wpa_state=completed mar 28 06:17:34 rfsniffer wpa_action: ip_address=192.168.0.175 mar 28 06:17:34 rfsniffer wpa_action: address=10:fe:ed:22:cc:66

"clue" can find there's cron script runs @ 17 minutes past every hour:

code: select all

mar 28 06:17:01 rfsniffer /usr/sbin/cron[5481]: (root) cmd (   cd / && run-parts --report /etc/cron.hourly) mar 28 06:17:26 rfsniffer kernel: imklog 5.8.11, log source = /proc/kmsg started. mar 28 06:17:26 rfsniffer rsyslogd: [origin software="rsyslogd" swversion="5.8.11" x-pid="2118" x-info="http://www.rsyslog.com"] start

script in cron.hourly directory 1 called fake-hwclock - maybe i'll stop running , see if helps.

it's more else, running after 06:17.

hwclock stores current time when runs (at 6:17, example), or when pi shutdown/rebooted cleanly. when pi next boots reloads time , uses until can real time internet. so, if pi crashes, boot time show last time hwclock run - if happened later, @ 06:25 when /etc/cron.daily scripts run?

if happening every 7 days (on sunday?), i'd in /etc/cron.weekly (06:52).

raspberrypi