I have a Cubox-i (older 2GB version) running Armbian_5.00_Cubox-i_Debian_jessie_4.4.1.zip. It's using a SATA drive as root. I've installed some services that take up a lot of CPU. After a couple of days, it still responds to pings, but I can no longer log into the box with SSH. I'm forced to power cycle it to log back in.
Looking at it, there's nothing in the logs to point to the problem, the only weird thing in /var/log/messages is:
Feb 22 12:34:47 localhost rsyslogd-2007: action 'action 17' suspended, next retry is Mon Feb 22 12:36:17 2016 [try http://www.rsyslog.com/e/2007 ]
I do wonder if it's overheating due to the CPU use. Is there anything I can do to track down this issue, and try to prevent it from freezing?
Question
lazerdye
I have a Cubox-i (older 2GB version) running Armbian_5.00_Cubox-i_Debian_jessie_4.4.1.zip. It's using a SATA drive as root. I've installed some services that take up a lot of CPU. After a couple of days, it still responds to pings, but I can no longer log into the box with SSH. I'm forced to power cycle it to log back in.
Looking at it, there's nothing in the logs to point to the problem, the only weird thing in /var/log/messages is:
Feb 22 12:34:47 localhost rsyslogd-2007: action 'action 17' suspended, next retry is Mon Feb 22 12:36:17 2016 [try http://www.rsyslog.com/e/2007 ]
I do wonder if it's overheating due to the CPU use. Is there anything I can do to track down this issue, and try to prevent it from freezing?
Link to comment
Share on other sites
3 answers to this question
Recommended Posts