SuSE-9.2 ACPI powersaved socket ERROR in handleSocketRequest
HI! I am using SuSE-9.2 with ACPI and poersaved-daemon. Occasionally, as far as I can judge it happens after resume (but not allways), I got the following error-message in /var/log/messages: [powersave][6440]: ERROR in Function handleSocketRequest; line 353: User is not allowed to connect to daemon. If this appears, than it appears constantly and without interruption. I think it can not be removed by either restart the powersaved or the kpowersave, nor does a logout/login help. Thanks, Michael -- michael@karbach.org www.karbach.org
Hello everybody! Am Dienstag, 23. November 2004 13:55 schrieb Michael Karbach:
I am using SuSE-9.2 with ACPI and poersaved-daemon. Occasionally, as far as I can judge it happens after resume (but not allways), I got the following error-message in /var/log/messages:
[powersave][6440]: ERROR in Function handleSocketRequest; line 353: User is not allowed to connect to daemon.
If this appears, than it appears constantly and without interruption.
I think there might be a permission problem with the devices (or sockets as Michael suggests) that are monitored/used by kpowersave. Can anyone post a hint or list of those devices, so I could try to add them to /etc/resmgr.conf and see if that helps? Thanks in advance! Jean Pierre
Am Dienstag, 23. November 2004 17:27 schrieb Jean Pierre Wenzel:
Hello everybody!
Am Dienstag, 23. November 2004 13:55 schrieb Michael Karbach:
I am using SuSE-9.2 with ACPI and poersaved-daemon. Occasionally, as far as I can judge it happens after resume (but not allways), I got the following error-message in /var/log/messages:
[powersave][6440]: ERROR in Function handleSocketRequest; line 353: User is not allowed to connect to daemon.
If this appears, than it appears constantly and without interruption.
I think there might be a permission problem with the devices (or sockets as Michael suggests) that are monitored/used by kpowersave.
Hello! I think kpowersave is not really the problem. kpowersave don´t use resmgr. kpowersave monitor only devices/sockets [/proc/acpi/] if powersave isn´t runnig or dead. The message is a errormessage from powersave. Please check if you get the message also if KDE isn´t running. Please change POWERSAVED_DEBUG in /etc/sysconfig/powersave/common to 15 (not wonder, many messages) and send the debugmessages from /var/log/messages if you get this error again. Best regards, Danny
Can anyone post a hint or list of those devices, so I could try to add them to /etc/resmgr.conf and see if that helps?
Thanks in advance!
Jean Pierre
On Tuesday, 23. November 2004 17:51, Danny Kukawka wrote:
Am Dienstag, 23. November 2004 17:27 schrieb Jean Pierre Wenzel:
Hello everybody!
Am Dienstag, 23. November 2004 13:55 schrieb Michael Karbach:
I am using SuSE-9.2 with ACPI and poersaved-daemon. Occasionally, as far as I can judge it happens after resume (but not allways), I got the following error-message in /var/log/messages:
[powersave][6440]: ERROR in Function handleSocketRequest; line 353: User is not allowed to connect to daemon.
If this appears, than it appears constantly and without interruption.
I think there might be a permission problem with the devices (or sockets as Michael suggests) that are monitored/used by kpowersave.
Hello!
I think kpowersave is not really the problem.
May be, but if I stop kpowersave, the error message vanish.
kpowersave donŽt use resmgr. kpowersave monitor only devices/sockets [/proc/acpi/] if powersave isnŽt runnig or dead.
The message is a errormessage from powersave. Please check if you get the message also if KDE isnŽt running.
No, I do not get this message. Michael -- michael@karbach.org www.karbach.org
Am Dienstag, 23. November 2004 18:31 schrieb Michael Karbach:
Hello!
I think kpowersave is not really the problem.
May be, but if I stop kpowersave, the error message vanish.
Then maybe resmgr is the problem. What is the status of resmgr (rcresmgr status and ps aux | grep resmgrd)? Try this if your KDE is running: - rcresmgr restart - logout from KDE - login to KDE Help this? Test also the status of powersaved. Danny
kpowersave don't use resmgr. kpowersave monitor only devices/sockets [/proc/acpi/] if powersave isn't runnig or dead.
The message is a errormessage from powersave. Please check if you get the message also if KDE isn't running.
No, I do not get this message.
Michael
On Tue, Nov 23, 2004 at 01:55:14PM +0100, Michael Karbach wrote:
HI!
I am using SuSE-9.2 with ACPI and poersaved-daemon. Occasionally, as far as I can judge it happens after resume (but not allways), I got the following error-message in /var/log/messages:
[powersave][6440]: ERROR in Function handleSocketRequest; line 353: User is not allowed to connect to daemon.
If this appears, than it appears constantly and without interruption.
I think it can not be removed by either restart the powersaved or the kpowersave, nor does a logout/login help.
I _think_ this may be a nuts-going resmgrd. If this happens again, please check with "top" for a busy-spinning resmgrd. If this is the case, you have to restart resmgr ("rcresmgr restart") and after this, either logout/login to your KDE session or (as root) issue "resmgr login <myusername> :0", replace the <myusername> with your user name. I have seen this, but i have not been able to really reproduce it (which makes bug reporting much harder...) -- Stefan Seyfried
On Tuesday, 23. November 2004 18:52, Stefan Seyfried wrote:
On Tue, Nov 23, 2004 at 01:55:14PM +0100, Michael Karbach wrote:
HI!
I am using SuSE-9.2 with ACPI and poersaved-daemon. Occasionally, as far as I can judge it happens after resume (but not allways), I got the following error-message in /var/log/messages:
[powersave][6440]: ERROR in Function handleSocketRequest; line 353: User is not allowed to connect to daemon.
If this appears, than it appears constantly and without interruption.
I think it can not be removed by either restart the powersaved or the kpowersave, nor does a logout/login help.
I _think_ this may be a nuts-going resmgrd. If this happens again, please check with "top" for a busy-spinning resmgrd.
Yes, at least in one occasion this has happened. This was the case today when I updated resmgr on one of my computers. But sometimes it happened after a resume, and in this case as far as I remember resmgrd was not 'busy-spinning'.
If this is the case, you have to restart resmgr ("rcresmgr restart") and after this, either logout/login to your KDE session or (as root) issue "resmgr login <myusername> :0", replace the <myusername> with your user name.
OK, this works! Thanks!
I have seen this, but i have not been able to really reproduce it (which makes bug reporting much harder...)
As soon as I have some new informations, I will post them. Best regards, Michael -- michael@karbach.org www.karbach.org
Hello,
I am using SuSE-9.2 with ACPI and poersaved-daemon. Occasionally, as far as I can judge it happens after resume (but not allways), I got the following error-message in /var/log/messages:
[powersave][6440]: ERROR in Function handleSocketRequest; line 353: User is not allowed to connect to daemon.
If this appears, than it appears constantly and without interruption.
I think it can not be removed by either restart the powersaved or the kpowersave, nor does a logout/login help.
The problem disappeared when I shut down the laptop when I was leaving the office -- after an new bootup in the train the syslog seems to be clean. Regards, Jean Pierre
On Tue, Nov 23, 2004 at 07:04:30PM +0100, Jean Pierre Wenzel wrote:
The problem disappeared when I shut down the laptop when I was leaving the office -- after an new bootup in the train the syslog seems to be clean.
This is expected, a restart of resmgr and a re-login would have helped also (a reboot is a bit more drastic :-). Unfortunately this is a workaround only and not a fix. -- Stefan Seyfried
participants (4)
-
Danny Kukawka
-
Jean Pierre Wenzel
-
Michael Karbach
-
Stefan Seyfried