Robert G. (Doc) Savage | 2 Feb 13:19 2012
Picon

rtkit-daemon looping leads to crash

Following a complete re-install, I found (IIRC) the only real user on my
RHEL6 box had uid/gui of 501/502. Somehow the xguest user got assigned
its uid/gid ahead of the real user. To match the underlying uid/gid
assignments for that real user on surrounding machines, I removed the
xguest package and reassigned 501:501 to the real user. Now I'm seeing
some serious thrashing of the rtkit-daemon process that causes the
machine to crash in 2-3 hours. The following lines repeat
in /var/log/messages with a new rtkit-daemon PID every few minutes.

Can someone suggest where to start untying this knot?

Feb  2 05:58:42 lion rtkit-daemon[3061]: Sucessfully made thread 3239 of process 3239
(/usr/bin/pulseaudio) owned by '501' high priority at nice level -11.
Feb  2 05:58:42 lion pulseaudio[3239]: pid.c: Stale PID file, overwriting.
Feb  2 05:58:42 lion rtkit-daemon[3061]: Sucessfully made thread 3241 of process 3239
(/usr/bin/pulseaudio) owned by '501' RT at priority 5.
Feb  2 05:58:42 lion rtkit-daemon[3061]: Sucessfully made thread 3242 of process 3239
(/usr/bin/pulseaudio) owned by '501' RT at priority 5.
Feb  2 05:58:44 lion rtkit-daemon[3061]: Sucessfully made thread 3349 of process 3349
(/usr/bin/pulseaudio) owned by '501' high priority at nice level -11.
Feb  2 05:58:44 lion pulseaudio[3349]: pid.c: Daemon already running.

--Doc Savage
  Fairview Heights, IL


Gmane