18188 2008-12-11 07:10:23 +0300 ConsoleKit флудит в /var/log/messages после перезапуска messagebus 2009-03-03 13:04:45 +0300 1 1 3 Distributions Branch 4.1 ConsoleKit unspecified all Linux CLOSED WONTFIX P2 normal --- 1 ilis.krou shrek qa-4.1 oldest_to_newest 82617 0 ilis.krou 2008-12-11 07:10:23 +0300 [root@altus ~]# service messagebus restart Stopping system message bus service: [ DONE ] Starting system message bus service: [ DONE ] Dec 11 09:00:39 altus console-kit-daemon[32586]: GLib-CRITICAL: g_async_queue_unref: assertion `queue->waiting_threads == 0' failed Dec 11 09:00:40 altus messagebus: dbus-daemon shutdown succeeded Dec 11 09:00:40 altus messagebus: dbus-daemon startup succeeded Dec 11 09:00:42 altus console-kit-daemon[32586]: WARNING: Failed to acquire org.freedesktop.ConsoleKit Dec 11 09:00:42 altus console-kit-daemon[32586]: WARNING: Could not acquire name; will retry Dec 11 09:00:45 altus console-kit-daemon[32586]: WARNING: Failed to acquire org.freedesktop.ConsoleKit Dec 11 09:00:45 altus console-kit-daemon[32586]: WARNING: Could not acquire name; will retry и далее каждые 3 сек бесконечно [root@altus ~]# kill -15 32586 останавливает флуд. 82817 1 ilis.krou 2008-12-16 20:44:44 +0300 https://bugs.launchpad.net/ubuntu/+source/consolekit/+bug/231180 В частности: https://bugs.launchpad.net/ubuntu/+source/consolekit/+bug/231180/comments/5 ===8<====== I am seeing this bug, too. Here is a summary: - because of dbus buggyness I have to restart it sometimes: # /etc/init.d/dbus restart (I know how to fix the mess afterward and how to get networkmanager working again :>) - one of the consequences is that two console-kit-daemon processes are running: $ ps aux | grep console root 6102 0.0 0.1 13140 2892 ? Ssl May26 0:14 /usr/sbin/console-kit-daemon root 24182 0.0 0.0 8868 1956 ? Ssl 09:24 0:00 /usr/sbin/console-kit-daemon (/etc/init.d/dbus starts the second one but fails to kill the first one) - the new console-kit-daemon process spams my syslog with the following messages (one message every 3 seconds !): May 29 09:45:03 vougeot console-kit-daemon[24182]: WARNING: Failed to acquire org.freedesktop.ConsoleKit May 29 09:45:03 vougeot console-kit-daemon[24182]: WARNING: Could not acquire name; will retry There are at least 3 things to fix to improve the situation: 1. fix the original dbus problem (I will report another bug for this...) 2. have /etc/init.d/dbus kill old console-kit-daemon processes 3. reduce the number of console-kit-daemon warning messages to one ===8<====== 85718 2 ilis.krou 2009-02-10 21:48:27 +0300 Пока всё то же самое... Feb 10 23:27:20 altus apt-get: dbus-1.2.12-alt0.M41.1 installed Feb 10 23:27:22 altus console-kit-daemon[8254]: GLib-CRITICAL: g_async_queue_unref: assertion `queue->waiting_threads == 0' failed Feb 10 23:27:24 altus messagebus: dbus-daemon shutdown succeeded Feb 10 23:27:24 altus messagebus: dbus-daemon startup succeeded Feb 10 23:27:25 altus console-kit-daemon[8254]: WARNING: Failed to acquire org.freedesktop.ConsoleKit Feb 10 23:27:25 altus console-kit-daemon[8254]: WARNING: Could not acquire name; will retry [ilis@altus ~]$ rpm -qa | grep -i consolekit ConsoleKit-0.2.10-alt1 libConsoleKit-0.2.10-alt1 После перезапуска dbus-daemon, console-kit-daemon становится в двух экземплярах 85719 3 shrek 2009-02-10 21:53:58 +0300 reboot. исправлений для 4.1 не будет 85724 4 ilis.krou 2009-02-11 08:58:35 +0300 (В ответ на комментарий №3) > reboot. исправлений для 4.1 не будет Почему ребут-то? Отстреливание старого помогает...