Bug#208344: Argh, locking...

[Adam Porter]

severity 208344 important
thanks

Well, I looked at the e-mail logcheck just sent me, and I found this:

gconfd (me-19567): Failed to get lock for daemon, exiting: Failed to 
lock '/tmp/gconfd-me/lock/ior': probably another process has the lock, or 
your operating system has NFS file locking misconfigured (Resource 
temporarily unavailable)

I killall-9'ed gconfd-2 and removed that lock file, and now Newton's working.  
So I'm downgrading it back to important.

The problem is, those crazy CORBA errors gave _no indication_ of the actual 
problem.

The only way I discovered it was by logcheck notifying me of those entries in 
the logs,  I was going to try rebooting today if I couldn't figure it out 
otherwise, and that would most likely have fixed it (the PID in the lockfile 
was the same as the running gconfd-2 process), and then the real problem 
might still not be known.  Remember that I looked for those lock files that 
were listed in the earlier reports, but I'm guessing that the location of the 
gconf lockfile has changed since then.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 191 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/pkg-gnome-maintainers/attachments/20060423/9cf25610/attachment.pgp