I'm not sure I follow the question.
I have a snapshot that I took when the machines would get stuck in portmap, and
i have the currently working configuration. Even after many hours I was unable
to reproduce the failure from the working setup with the same versions of all
packages (i.e. the
Sounds like it was probably that kernel bug, and we can close this
report. Geoffrey, thanks for taking the time to test and try to
reproduce!
** Changed in: portmap (Ubuntu)
Status: In Progress = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
There were some kernel issues with child processes and parents holding
sockets open too long that was fixed very close to the end of the natty
cycle. I wonder if that had something to do with the fact that it
doesn't occur with full updates anymore.
Geoffrey, can you try applying all updates but
since you have a snapshot where the failure is reproducible, probably
best to work from that. Have you tried applying the described changes
to /etc/init/portmap.conf (with or without changing the other jobs)? Do
you get any messages from/about portmap then, besides the 'terminated
with status 1'
I guess I wasn't clear. Everything in my prior post after 'I reverted
to a snapshot...' applies to running on the broken snapshot
So this is the only additional message I get with the requested changes on the
broken snapshot:
portmap[219]: cannot bind udp: Cannot assign requested address
And
oh right - you were probably clear and I was just reading too fast :)
portmap[219]: cannot bind udp: Cannot assign requested address
ok; in this case, at the end of boot, is portmap running or not? what
else could be bound to port 111 - could it be something related to
nfsroot itself (i.e., in
Well, when I get that message, the machine is hung, so there isn't a way for me
to know if portmap is running.
If i hit ctrl-alt-delete (and booted into single-user mode) then I actually can
get passed this, and yes portmap is running (though not as the same address
that is shown in the
On Fri, Feb 18, 2011 at 12:33:42AM -, Geoffrey Hausheer wrote:
Is it possible there are 2 portmap sessions being launched
simultaneously somehow, and this is causing one to hang?
Possible, but something else has to be launching the other session. The
only thing in a default Ubuntu install
Well, I've repeatedly tried to actually recreate this now.
I upgraded from 6.0.0-1ubuntu2 to 6.0.0-1ubuntu2.1
I did a force reconfigure
I purged portmap/nfs-common and re-installed
I tried upgrading just portmap and incrementally nfs-common
In all cases my systems boot fine now.
I reverted to a
On Tue, Feb 15, 2011 at 07:07:59AM -, Geoffrey Hausheer wrote:
As it turns out, I do seem to get the message even with the old portmap,
however, the init sequence continues on.
Right - so fixing the bug that things didn't properly wait for portmap at
boot before exposed a new bug, that
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/719143
Title:
portmap 6.0.0-1ubuntu2.1 makes nfs boot machine unbootable
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
In case it isn't obvious from the versions or logs, this is a 10.04
Lucid install
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/719143
Title:
portmap 6.0.0-1ubuntu2.1 makes nfs boot machine
After disabling plymouth, I could see messages about:
init: portmap main process (358) terminated with status 1 error message.
So if this is what you see when using the new portmap, what is the
status of portmap after boot when using the /old/ package? ('status
portmap')
Do you have any
As it turns out, I do seem to get the message even with the old portmap,
however, the init sequence continues on.
/proc/cmdline:
root=/dev/nfs nfsroot=192.168.1.85:/media/nonraid/nfs
ip=192.168.1.88::192.168.1.1:255.255.255.0:jo:eth0:off rw single
status portmap:
I do not have any
14 matches
Mail list logo
