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? 

 

I had a similar problem with an olimex a20 board, ended up being the overclock that armbian applies.

Thanks, I see now the cpufreq set of tools, I'll try underclocking to 792 MHz and see if it's stable.

Hi all,

 

how come you're assuming that the cause of the rsyslog message is overheating of CPU ???

 

This is what I find in /var/log/syslog of my Cubietruck [ARMBIAN Debian GNU/Linux 8 (jessie) 4.4.1-sunxi] almost infinitely:

 

Mar 20 10:58:00 localhost rsyslogd-2007: action 'action 17' suspended, next retry is Sun Mar 20 10:58:30 2016 [try http://www.rsyslog.com/e/2007 ]

 

But there's nothing like an overheating of the CPU and all functions seem to be there without any obvious flaws.

And yet, I'd like to find a remedy for the syslog entries as mentioned above.

Is there anyone who can shed a little light on this.

 

Many thanx in advance.