On 2013-06-10 00:29, Cristian Rodríguez wrote:
El 09/06/13 18:25, Carlos E. R. escribió:
1. what exact systemd version are you using in which distribution and arch ?
Distribution is on the signature, and systemd is whatever the distribution has, ie, 12.3 and systemd-195-13.25.1.x86_64 Systemd was restarting continuously rsyslog, and logging it somewhere. Where? No idea (yet). This activity caused cpu to go 100% on one core. I had to halt, wait, boot, to let the engine cool down. Apparently, rsyslog does not like this line in rsyslog config:
if (syslogfacility isequal 10) and ($msg contains 'changing to') and ($msg contains 'hat: Operation not permitted' ) then ~
There is no complain: Telcontar:~ # systemctl restart rsyslog.service # with line active Telcontar:~ # systemctl restart rsyslog.service # with line com.out. Telcontar:~ # but later it fails - it is in the syslog:
<5.6> 2013-06-10 00:46:04 Telcontar rsyslogd - - - [origin software="rsyslogd" swVersion="7.2.7" x-pid="1448" x-info="http://www.rsyslog.com"] exiting on signal 15. <5.6> 2013-06-10 00:46:54 Telcontar rsyslogd - - - [origin software="rsyslogd" swVersion="7.2.7" x-pid="8282" x-info="http://www.rsyslog.com"] start <3.6> 2013-06-10 00:46:54 Telcontar systemd 1 - - Stopping System Logging Service... <3.6> 2013-06-10 00:46:54 Telcontar systemd 1 - - Starting System Logging Service... <3.6> 2013-06-10 00:46:54 Telcontar systemd 1 - - Started System Logging Service. <3.5> 2013-06-10 00:46:54 Telcontar systemd 1 - - rsyslog.service: main process exited, code=exited, status=1/FAILURE <3.5> 2013-06-10 00:46:54 Telcontar systemd 1 - - Unit rsyslog.service entered failed state <3.6> 2013-06-10 00:46:54 Telcontar systemd 1 - - Starting System Logging Service... <3.6> 2013-06-10 00:46:54 Telcontar systemd 1 - - Started System Logging Service. <3.5> 2013-06-10 00:46:54 Telcontar systemd 1 - - rsyslog.service: main process exited, code=exited, status=1/FAILURE <3.5> 2013-06-10 00:46:54 Telcontar systemd 1 - - Unit rsyslog.service entered failed state <3.6> 2013-06-10 00:46:54 Telcontar systemd 1 - - Starting System Logging Service... <3.6> 2013-06-10 00:46:54 Telcontar systemd 1 - - Started System Logging Service. <5.6> 2013-06-10 00:46:57 Telcontar rsyslogd - - - [origin software="rsyslogd" swVersion="7.2.7" x-pid="8282" x-info="http://www.rsyslog.com"] exiting on signal 15. <5.6> 2013-06-10 00:46:57 Telcontar rsyslogd - - - [origin software="rsyslogd" swVersion="7.2.7" x-pid="8295" x-info="http://www.rsyslog.com"] start <3.6> 2013-06-10 00:46:57 Telcontar systemd 1 - - Stopping System Logging Service... <3.6> 2013-06-10 00:46:57 Telcontar systemd 1 - - Starting System Logging Service... <3.6> 2013-06-10 00:46:57 Telcontar systemd 1 - - Started System Logging Service. <3.6> 2013-06-10 00:47:39 Telcontar systemd 1 - - Starting Cleanup of Temporary Directories... <3.3> 2013-06-10 00:47:40 Telcontar systemd-tmpfiles 8313 - - stat(/run/user/1000/gvfs) failed: Permission denied <3.6> 2013-06-10 00:47:40 Telcontar systemd 1 - - Started Cleanup of Temporary Directories. <10.3> 2013-06-10 00:48:01 Telcontar 8320 - - pam_apparmor(crond:session): Unknown error occurred changing to news hat: Operation not permitted <0.5> 2013-06-10 00:48:01 Telcontar kernel - - - [ 921.273824] type=1400 audit(1370818081.268:51): apparmor="DENIED" operation="change_hat" info="unconfined" error=-1 pid=8320 comm="cron"
I commented out that line and restarted the service. CPU is cool again. This is caused by restarting (respawining?) too fast a process that insists in failing, instead of throttling. I have been out of commision quarter of an hour longer than needed because network is not started automatically on boot. I had to restart the service manually (!), and this caused XFCE to burp on session start, too. -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org