Linux Support FAQ entry 02 Jun 2005, logged in as JanIven
LinuxSupportFAQForm
SupportProblem While logging into an AFS account via X11 (Xterminal/Exceed agaist LXPLUS, or local session on a Linux Desktop), the user observes error messages like

Failed to get a file lock: Failed to lock '~/.gconfd/lock/ior':
 probably another process has the lock, or your operating system has NFS
 file locking misconfigured, or a hard NFS client crash caused a stale
 lock (Resource temporarily unavailable)

This message shows up either in a pop-up window (sometimes with tiny/nearly unreadable fonts), or in ~/.xsession-errors.

SupportAnswer Either

  • the session failed to obtain valid AFS tokens, and a previous session crashed. Solution: manually run klog, remove the offending lock file (rm ~/.gconfd/lock/ior), restart the session, or

  • The AFS volume containing this file is corrupted. Symptoms are that the lock file is "half-visible", it prevents a new file of the same name being created but cannot be accessed or removed. Solution: rename the parent directory (mv ~/.gconfd/lock ~/.gconfd/lock-bad) and restart the session.

OsVersion SLC3
HardwareArchitecture any
ApprovedBySupport SupportApproved
Edit | Attach | Watch | Print version | History: r3 < r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r1 - 2005-06-03 - JanIven
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    LinuxSupport All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright &© 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback