[opensuse] Stale NFS lockfile after system crash
Hi, after a system crash, yast2 throws the following on me: ** (y2controlcenter-gnome:7997): WARNING **: error accessing /desktop/gnome/applications/y2cc-gnome/cc_actions_list [Failed to contact configuration server; som e possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)] The "system" menue after clicking on the "computer" button in Gnome has also disappeared. I have read a bunch of articles, but was not able to solve the problem. I did also kill /tmp/* and similar files, and have cleaned ~/.gconfd without any success. Does anybody have an idea where these lockfiles are? Thanks, Heinz. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 10/19/2009 03:37 PM, Heinz Diehl wrote:
Does anybody have an idea where these lockfiles are?
Did you look on /var/lock/? -- Cheers / Saludos, Carlos E. R. (from 11.2-factory "Emerald" RC 1) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 19.10.2009, Carlos E. R. wrote:
Did you look on /var/lock/?
Yes, I couldn't find anything which had to do with this. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Heinz Diehl wrote:
Hi,
after a system crash, yast2 throws the following on me:
** (y2controlcenter-gnome:7997): WARNING **: error accessing /desktop/gnome/applications/y2cc-gnome/cc_actions_list [Failed to contact configuration server; som e possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)]
The "system" menue after clicking on the "computer" button in Gnome has also disappeared.
I have read a bunch of articles, but was not able to solve the problem. I did also kill /tmp/* and similar files, and have cleaned ~/.gconfd without any success.
Does anybody have an idea where these lockfiles are?
The document to which you posted a link says: I'm having a lock file problem. What do I do? Usually a problem here involves either NFS, or a kernel bug. The per-user daemon locks two files in the default configuration: ~/.gconfd/lock/ior ~/.gconf/%gconf-xml-backend.lock/ior You mentioned checking ~/.gconfd but did you also check ~/.gconf ? Also which user is logged in and which user is running yast and did you check both users' directories? Just a wild idea.
Thanks, Heinz.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 19.10.2009, Dave Howorth wrote:
You mentioned checking ~/.gconfd but did you also check ~/.gconf ?
Yes, I did read what is mentioned following the link in the error message. It didn't helt, there's no such lockfiles at all.
Also which user is logged in and which user is running yast and did you check both users' directories? Just a wild idea.
There's only me and root on this machine, I checked the homedir of both. No chance. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 19.10.2009, Heinz Diehl wrote:
** (y2controlcenter-gnome:7997): WARNING **: error accessing /desktop/gnome/applications/y2cc-gnome/cc_actions_list [Failed to contact configuration server; som e possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)]
After all, I realise that this obviously isn't a lockfile problem at all, but an issue with gconf. Since it worked before, there must be a solution to this. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (3)
-
Carlos E. R. -
Dave Howorth -
Heinz Diehl