On Thu, 21 Aug 2008, Greg Cornell wrote:
> > -----Original Message-----
> > From: [EMAIL PROTECTED] [mailto:rhelv5-list-
> > [EMAIL PROTECTED] On Behalf Of Peter Ruprecht
> > Sent: Thursday, August 21, 2008 12:06 PM
> > To: Red Hat Enterprise Linux 5 (Tikanga) discussion mailing-list
> > Subject: Re: [rhelv5-list] Firefox won't run
> >
> >
> > On Thu, 21 Aug 2008, Greg Cornell wrote:
> >
> > > Hi List,
> > >
> > > I'm having trouble with firefox on a RHEL 5.2 client workstation
> > (fully up to date). It doesn't run as a normal user but runs fine as
> > root. When I run the firefox command as a normal user, there aren't
> > any messages displayed, it just waits for about 4-5 minutes and then
> > gives me the prompt back.
> > >
> > > I've tried Google, Red Hat's knowledgebase and bugzilla, and haven't
> > been able to find anything helpful.
> > >
> > > I ran 'strace firefox' but didn't find anything in the output that
> > looked useful (to me at least, but I'm not an expert there). I
> > attached the strace output for any of you that might what to look
> > through it.
> > >
> > > I also ran 'ltrace firefox' which returned:
> > > ltrace: Can't open ELF file "/usr/bin/firefox"
> > >
> > > but the permissions seem fine to me:
> > > -rwxr-xr-x root root system_u:object_r:bin_t
> > /usr/bin/firefox
> > >
> > > Any help you can give will be appreciated.
> > >
> >
> > Just a guess, but I have seen this kind of thing when the user's home
> > directory (or specifically, .mozilla directory) is not writable.
> > Problems
> > like this can also show up if there's a file locking problem. Maybe
> > if the homedirs are NFS-mounted there's some subtle issue with lockd on
> > the
> > server?
> >
>
> Hi Peter,
>
> Thanks for help me out.
>
> It does indeed seem to be a NFS lock issue. If I mount the home tree using
> the "nolock" option firefox starts up just fine. I've only used NFS a couple
> of times before so I'm not all that familiar with it. Is it bad to not use
> locking?
>
> If it is bad, how do I trace down the problem. The system's log files don't
> have anything useful in them. I've turned off the firewall on the server for
> testing but that didn't help. There is a lockd process running but the only
> thing that's made a difference so far is using "nolock" on the client to
> mount the home directory.
>
I'd definitely recommend using file locking if there's any chance that
two clients will be accessing the same file simultaneously.
If lockd on the server is wonky, you might be able to fix it just by
restarting it: "service nfslock restart". Otherwise completely restarting
all the nfs daemons and portmap on the server may be necessary. The time
this happened to me, it was easiest just to reboot the server ... not
sure if that's feasible for you.
-Peter
_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list
