Description of problem:
Eclipse doesn't start with this error in the log.
!ENTRY org.eclipse.osgi 4 0 2006-09-21 10:37:19.848
!MESSAGE Error reading configuration: An error occurred while locking file
.manager/.fileTableLock": "No locks available". A common reason is that the file
system or Runtime Environment does not support file locking for that locatio
n. Please choose a different location, or disable file locking passing
"-Dosgi.locking=none" as a VM argument.
the .fileTableLock file is empty.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Remove .eclipse and workspace directories.
2. Start eclipse
Eclipse should start.
Attached is the log file
Created attachment 136861 [details]
I'm sure out this problem but I also see the problem described in bug # 207442.
Can you try the recommended solution there?
That should say "I *not* sure about this problem ..."
Created attachment 136908 [details]
Another log from the workspace/.metadata/.log file
Installing eclipse-sdk did not work for me btw. I thought this comment would be
added when I added the log.
Can you try starting eclipse with a new workspace?
I've been removing my workspace every time I start eclipse.
Also removing the .eclipse directory as well.
Nurdin: is this still broken for you?
nope it was fixed on an update. Or at least I updated and the problem went away.
(In reply to comment #9)
> nope it was fixed on an update. Or at least I updated and the problem went away.
Created attachment 138177 [details]
Log file for October 10, 2006
And it's broken again with this log.
I tried a complete wipeout and reinstall of eclipse, no dice.
[npremji@tow npremji]$ grep eclipse.product
# the identified eclipse.product defines the default application to run.
[npremji@tow npremji]$ rpm -qa | grep eclipse
Remove ~/.eclipse and try running again with a new workspace. Thanks.
Uh I did that as well, sorry I didn't mention.
What architecture are you using?
Also, what version of gcj are you using?
Architecture is i386, dell optiplex gx280.
gcj version is:
gcj (GCC) 4.1.1 20060928 (Red Hat 4.1.1-28)
Copyright (C) 2006 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
I have an i386 box with the same software  and I can't reproduce your problem.
 % rpm -q gcc-java libgcj eclipse-sdk java-1.4.2-gcj-compat
As of this morning's yum update which updated the filesystem package eclipse is
working again. (Not entirely sure if that was the specific package that fixed it
but I think it might be as eclipse used to complain the filesystem couldn't
I guess the thing to do is make sure filesystem guys run eclipse to test locking :)
Ok, let's close the bug for now. Feel free to re-open it if you hit it again.
Created attachment 138577 [details]
Update log for October 16, 2006
So it broke again, I don't think its an eclipse bug but here is the update log
of what I just updated, please help me find which of these packages is messing
with eclipse. Thank you.
Created attachment 138683 [details]
Yet another update log, leads me to believe this is a kernel issue.
So on my update today things have started working again, the only things that
were successfully updated were the kernel, so I assume this is a kernel issue.
I still can't reproduce this bug so I'm closing it again. Please re-open this
bug if this crops up again.
Created attachment 140688 [details]
update log for November 8, 2006
I've installed fc6 official rather than going with devel and as of today
something is broken which gives back the same locking error message. This is
the most recent update I'll post more going back to Nov 2, when I reinstalled.
Created attachment 140689 [details]
update log for November 7, 2006
Created attachment 140690 [details]
update log for November 6, 2006
Created attachment 140691 [details]
update log for November 3, 2006
Created attachment 140692 [details]
update log for November 2, 2006
Since you're the only person that is having this problem and I can't reproduce
it, there's not much I can do to help here. Sorry.
Just archiving more information about this issue that Andrew found:
Starting statd with '/etc/init.d/nfslock start' fixed the problem.
Closing bug since it's not an eclips bug.