I encountered this, after having installed Sun JDK for an esoteric
purpose.
Turns out I had somehow managed to install the "headless" (i.e. non-GUI)
version of OpenJDK.
To fix:
$ sudo apt-get remove openjdk-7-jre-headless
$ sudo apt-get install openjdk-7-jdk
That made everything lovely for me.
I encountered essentially the same problem with a Jaunty (9.04)
installation.
My problem was seemingly caused by having installed and configured
dovecot BEFORE installing the postgres 8.3 server. My snakeoil key had
the following permissions:
r...@kingpin:/etc/postgresql/8.3/main# ls -l
/etc/ss
OK, I have a Sony A616 (8Gb) and a Sony A739F (16Gb). Both exhibit this
problem.
The problem and the fix are both described in the comments above.
However, there's been a bit of too-ing and fro-ing so I thought I would
just summarize and write down the EXACT sequence of commands required to
fix t
Can't agree with you there, Eckart. I upgraded to Hardy and all my
problems with NFS disappeared.
[EMAIL PROTECTED]:~$ uname -a
Linux kirby 2.6.24-19-generic #1 SMP Wed Aug 20 22:56:21 UTC 2008 i686 GNU/Linux
...and hasn't hung once in months. Used to hang at least once a day
under Gibbon.
--
What's an SRU? I'd love to know more about the process for getting
fixes into Ubuntu. Please explain!
--
NFS server: lockd: server not responding
https://bugs.launchpad.net/bugs/181996
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
No,
The failure is very regular. It happens whenever the garbage
collection is performed as a result of a lock request.
J.
--
NFS server: lockd: server not responding
https://bugs.launchpad.net/bugs/181996
You received this bug notification because you are a member of Ubuntu
B
Yeah,
I know how to fix the problem, but I have no idea how to get a patch
into Gutsy. Any ideas who I would contact?
J.
Russel Winder wrote:
> I am running fully up to date Gutsy server and am getting what I think
> is the same problem as is reported here. After an indetermin
Second part is easy. Fix yaird as above, download the .deb files, and
"dpkg install" them both. I had no hassles with that.
J. Bruce Fields suggested the following two patches, but I didn't use
those.
http://git.linux-nfs.org/?p=trondmy/nfs-2.6.git;a=commitdiff;h=255129d1e9ca0ed3d69d5517fae3e03
OK, after four days, this finally crashed again. It gave this message
at the same time as giving the following error:
Feb 1 08:50:45 kirby kernel: [213351.856962] NETDEV WATCHDOG: eth0: transmit
timed out
Feb 1 08:50:45 kirby kernel: [213351.856973] BUG: scheduling while atomic:
swapper/0/0x0
This is fixed in the 2.6.24 kernel series.
I installed:
linux-image-2.6.24-5-generic_2.6.24-5.8_i386.deb
linux-ubuntu-modules-2.6.24-5-generic_2.6.24-5.9_i386.deb
from:
http://packages.ubuntu.com/hardy/base/
(After making the changes to yaird required to install it)
vi /usr/lib/yaird/perl/Inpu
BTW: Most of the problems I've seen related to this are from the RealTek
card. But I have an sis190.
I'm currently trying the following kernel:
linux-image-2.6.24-5-generic_2.6.24-5.8_i386.deb
linux-ubuntu-modules-2.6.24-5-generic_2.6.24-5.9_i386.deb
--
[3c900B] NETDEV WATCHDOG: transmit tim
I was getting this under Gutsy Gibbon, kernel "Ubuntu 7.10, kernel
2.6.22-14-generic".
I grabbed the latest 2.6.24 kernel (rc9) and it's still happening.
--
[3c900B] NETDEV WATCHDOG: transmit timed out/ Resetting the Tx ring pointer
https://bugs.launchpad.net/bugs/107807
You received this bug no
I went with the nlm_gc_hosts_if_needed () approach. Stable so far.
Debug shows completion of GC.
[ 6879.405447] lockd: request from 192.168.1.211, port=729
[ 6879.405454] lockd: LOCK called
[ 6879.405458] lockd: nlm_lookup_host(192.168.1.211, p=6, v=4, my role=server,
name=ditko)
[ 6879
Hmm... one quick-fix approach would seem to be to pass LOCK_RECURSIVE to
mutex_init.
On that note, it's not clear to me yet why we're even using mutexes
here. Isn't there only a single lockd process? And in that case, all
these mutexes are private, no? Or is it possible to start two lockd's
for
OK, let's follow the request and see what is performing a file mutex
lock.
[ 5845.725268] lockd: request from 192.168.1.210, port=860
This is from the main lockd kernel thread function.
static void lockd (...) in svc.c. It invokes svc_process().
[ 5845.725272] lockd: LOCK called
Via some xdr mag
Right, this appears (unsurprisingly) to be a mutex contention issue, on
the file-specific mutex.
See the attached trace: server-kirby-v3.dmsg
Key parts are:
[ 5845.725268] lockd: request from 192.168.1.210, port=860
[ 5845.725272] lockd: LOCK called
[ 5845.725274] lockd: nlm_lookup_host
It's getting lost in nlm_inspect_file ().
[ 693.679373] lockd: mutex acquired, checking 128 file hash entries
[ 693.679375] lockd: got entry in list 58
[ 693.679376] lockd: inspecting file
dprintk("lockd: mutex acquired, checking %d file hash entries\n",
FILE_NRHASH);
for (i =
OK, I added more debug to /usr/src/linux/fs/lockd/host.c and installed a
new lockd module. Seems like it's getting lost somewhere in
nlmsvc_mark_resources(). I'll keep digging.
--
NFS server: lockd: server not responding
https://bugs.launchpad.net/bugs/181996
You received this bug notification
** Attachment added: "Output from client's dmesg."
http://launchpadlibrarian.net/11447299/client-romita.dmsg
--
NFS server: lockd: server not responding
https://bugs.launchpad.net/bugs/181996
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
** Attachment added: "Output from server's dmsg."
http://launchpadlibrarian.net/11447297/server-kirby.dmsg
--
NFS server: lockd: server not responding
https://bugs.launchpad.net/bugs/181996
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact fo
OK, I turned on debug with:
echo "65535" > /proc/sys/sunrpc/nlm_debug
There seems to be a problem when lockd enters garbage collection.
Here's the last of the debug seen from lockd on the server side.
[ 2277.091005] lockd: request from 192.168.1.210, port=864
[ 2277.091018] lockd: LOCK
Feel free to contact me if I can offer help debugging this.
--
NFS server: lockd: server not responding
https://bugs.launchpad.net/bugs/181996
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs
I can confirm the same on a brand new Gutsy install with 2.6.22-14.
Within 24 hours usually, this will occur. When it happens, Skype,
Amarok and other apps will hang first, but eventually all apps will
hang. Client reboot does nothing. nfs-kernel-server doesn't help (it
doesn't clear the broken
23 matches
Mail list logo
