Linux problem on PI

Hardware Server
1

I got a small problem with my Raspbian on Pi2. Yesterday it stucked second time during last quoter. Now I am trying to find a reason, but question is where to find it, where log I have to check ?

Openhab did not report any issues, but something happened:

red - processor usage
green - memory
blue - Openhab process
At 9 I have rebooted PI.

Before I was unable to use putty or Winscp (but ping was ok)

I have checked syslog and found followin items:

Jun 29 02:09:01 raspberrypi /USR/SBIN/CRON[14567]: (root) CMD (  [ -x /usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d /var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 $(/usr/lib/php5/maxlifetime))
Jun 29 02:10:01 raspberrypi /USR/SBIN/CRON[14593]: (root) CMD (/usr/bin/rrd.sh >/dev/null 2>/dev/null)
Jun 29 02:10:01 raspberrypi /USR/SBIN/CRON[14594]: (pi) CMD (/usr/bin/rrd.sh >/dev/null 2>/dev/null)
Jun 29 01:17:10 raspberrypi kernel: imklog 5.8.11, log source = /proc/kmsg started.
Jun 29 01:17:10 raspberrypi rsyslogd: [origin software="rsyslogd" swVersion="5.8.11" x-pid="1890" x-info="http://www.rsyslog.com"] start
Jun 29 01:17:10 raspberrypi kernel: [    0.000000] Booting Linux on physical CPU 0xf00
Jun 29 01:17:10 raspberrypi kernel: [    0.000000] Initializing cgroup subsys cpuset
Jun 29 01:17:10 raspberrypi kernel: [    0.000000] Initializing cgroup subsys cpu
Jun 29 01:17:10 raspberrypi kernel: [    0.000000] Initializing cgroup subsys cpuacct

rrd it is my script, which generate charts, it works every 10minutes.
Is it possible that some system housekeeping process as maxlifetime generate processor overload ?
What does it mean next items ? Was it reseted, but if so why it stucked ?

2

The next Items in your syslog are just standard Linux boot messages. There are no errors and no indications as to why the system crashed.

If you installed openHAB using apt-get, its logs are located in /var/log/openhab. If there was a problem caused by openHAB that is where you will find the errors. If the problem wasn’t caused by openHAB I don’t know if we will be much helps.

3

Openhab’s log is clean for this period :frowning:

any idea where to look for cause ?

4

I’m afraid not.

5

Again similar problem :frowning: , but log says something diff :

Jul  9 09:17:19 raspberrypi watchdog[2637]: starting daemon (5.12):
Jul  9 09:17:19 raspberrypi watchdog[2637]: int=1s realtime=yes sync=no soft=no mla=0 mem=0
Jul  9 09:17:19 raspberrypi watchdog[2637]: ping: no machine to check
Jul  9 09:17:19 raspberrypi watchdog[2637]: file: no file to check
Jul  9 09:17:19 raspberrypi watchdog[2637]: pidfile: no server process to check
Jul  9 09:17:19 raspberrypi watchdog[2637]: interface: no interface to check
Jul  9 09:17:19 raspberrypi watchdog[2637]: test=none(0) repair=none(0) alive=/dev/watchdog heartbeat=none temp=none to=root no_act=no
Jul  9 09:17:19 raspberrypi watchdog[2637]: cannot set timeout 60 (errno = 22 = 'Invalid argument')
Jul  9 09:17:19 raspberrypi watchdog[2637]: hardware wartchdog identity: BCM2708
Jul  9 09:17:19 raspberrypi kernel: [   24.815563] uart-pl011 3f201000.uart: no DMA platform data
Jul 10 16:54:03 raspberrypi ntpdate[2713]: step time server 192.53.103.108 offset 113788.135453 sec

Any ideas what does it mean:
uart-pl011 3f201000.uart: no DMA platform data