[Bug 719143] Re: portmap 6.0.0-1ubuntu2.1 makes nfs boot machine unbootable
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 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 719143] Re: portmap 6.0.0-1ubuntu2.1 makes nfs boot machine unbootable
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 fix to get the system booting cleared out whatever state that caused it to break in the 1st place), so whatever caused this was likely due to either something special in my setup (there really shouldn't have been anything) or the specific upgrade path I took. Since no-one else has reported this in the past 3 months, it is probably safe to consider it a one-off. I''ll be happy to try additional tests, but to upgrade the packages in the snapshot to a working configuration, I need to fix the issue upgrade then reintroduce it and I'm not sure that will actually be valuable, and I have been unable to reintroduce the problem since fixing it. -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 719143] Re: portmap 6.0.0-1ubuntu2.1 makes nfs boot machine unbootable
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 reverting the kernel version to the exact same version as the one in your broken snapshot? -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 719143] Re: portmap 6.0.0-1ubuntu2.1 makes nfs boot machine unbootable
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 that should be launching portmap is /etc/init/portmap.conf, which will only launch one instance at a time. If portmap is running at the end of the boot, what's the result of 'status portmap'? I.e., is the portmap that's running /supervised by upstart/? You say it's not running on the same address as shown in the message, but the message you cited didn't list an address at all - if you have a message showing the address, can you post that? -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 719143] Re: portmap 6.0.0-1ubuntu2.1 makes nfs boot machine unbootable
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 message) if I remove either of the above conf files, so it boots normally, then ys portmap is running. Is it possible there are 2 portmap sessions being launched simultaneously somehow, and this is causing one to hang? -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 719143] Re: portmap 6.0.0-1ubuntu2.1 makes nfs boot machine unbootable
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 kernel) holding the port? -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 719143] Re: portmap 6.0.0-1ubuntu2.1 makes nfs boot machine unbootable
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 removing portmap-wait.conf or statd-mounting.conf will allow the boot to proceed. -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 719143] Re: portmap 6.0.0-1ubuntu2.1 makes nfs boot machine unbootable
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' message? -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 719143] Re: portmap 6.0.0-1ubuntu2.1 makes nfs boot machine unbootable
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 snapshot of my system which exhibits the problem (which is still there) and made the requested changes, but I still just see the screen stop updating after 'init: portmap main process ended, respawning' The only additional message I see is: portmap[219]: cannot bind udp: Cannot assign requested address I verified I don't get that message with the same changes to portmap.conf on a working system, instead I get this one: portmap-wait: Main process killed by term I then tried to remove portmap-wait.conf, this seemed to prevent the hang, but I got a message about eth1 being busy (which didn't seem to effect anything) Replacing portmap-wait.conf and removing statd-mounting.conf also prevented the hang, and I didn't get the message about eth1 Removing portmap-boot.conf had no effect I diffed the above files (portmap.conf, portmap-boot.conf, portmap- wait.con, statd-mounting.conf) between the working and hanging snapshot and see no differences. I'm not sure any of the above helps, but I found it frustrating taht I couldn't put the machine back in a broken state. As my working configuration has moved forward since I got it functional, it isn't trivial to diff the 2 environments, though if you have ideas where I should look, I can take a more targetted approach -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 719143] Re: portmap 6.0.0-1ubuntu2.1 makes nfs boot machine unbootable
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 portmap isn't starting correctly in your environment. > I can reproduce this problem on a VirtualBox host, so it isn't hard for > me to experiment with different portmap changes if you can give me some > leads. I don't really understand upstart well enough to figure out how > to proceed on my own. Could you try an /etc/init/portmap.conf with the following changes? - add 'console output' - comment out 'expect fork' - change the portmap exec line to read 'exec portmap -d $OPTIONS' This should give debugging output from the portmap command on the console, so turning off plymouth should let us get some idea of why this isn't starting up right. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 719143] Re: portmap 6.0.0-1ubuntu2.1 makes nfs boot machine unbootable
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 customizations in /etc/portmap.conf or /etc/default/portmap portmap start/running, process 556 My systems are setup with a shared root for multiple diskless workstations. The only changes I can recall making from a stock system are: a) initramfs.conf sets BOOT=nfs b) I needed to add 'rw' to the cmdline, otherwise mountall would fail (there should be a bug on that I filed last year) c) I have a custom nfs-bottom script to mount /var/* to a system-specific path which prevents them from clobbering important state data Other than that, I think they are stock 10.04 systems I can reproduce this problem on a VirtualBox host, so it isn't hard for me to experiment with different portmap changes if you can give me some leads. I don't really understand upstart well enough to figure out how to proceed on my own. ** Changed in: portmap (Ubuntu) Status: Incomplete => In Progress -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 719143] Re: portmap 6.0.0-1ubuntu2.1 makes nfs boot machine unbootable
> 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 options set in /etc/portmap.conf or
/etc/default/portmap?
Do you still get this same error at boot time?
Finally, what does /proc/cmdline show on this system?
portmap shouldn't have any dependencies on other services beyond those
specified in /etc/init/portmap-boot.conf, so I don't know why this is
failing for you; and I don't have any nfsroot systems to test against.
I would like us to fix this, but we will need more details about what's
happening to figure out the nature of the bug.
** Changed in: portmap (Ubuntu)
Status: New => Incomplete
--
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
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 719143] Re: portmap 6.0.0-1ubuntu2.1 makes nfs boot machine unbootable
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 unbootable -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 719143] Re: portmap 6.0.0-1ubuntu2.1 makes nfs boot machine unbootable
-- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
