[Bug 484209] Re: /etc/init/statd.conf: race with portmap startup
karmic has seen the end of its life and is no longer receiving any updates. Marking the karmic task for this ticket as "Won't Fix". ** Changed in: nfs-utils (Ubuntu Karmic) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/484209 Title: /etc/init/statd.conf: race with portmap startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/484209/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 484209] Re: /etc/init/statd.conf: race with portmap startup
I couldn't reproduce what I said on comment #15. Maybe it was using an old version of upstart. Now I'm getting errors on sm-notify. Probebly I'm seeing bug #690401 or #525154. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/484209 Title: /etc/init/statd.conf: race with portmap startup -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 484209] Re: /etc/init/statd.conf: race with portmap startup
** Branch linked: lp:~ken-vandine/ubuntu/natty/nfs-utils/1.2.2-4ubuntu1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/484209 Title: /etc/init/statd.conf: race with portmap startup -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 484209] Re: /etc/init/statd.conf: race with portmap startup
> I have a workstation that the fix dosn't worked too. > I'm not gettting errors on "start portmap" but on "status portmap | grep -q > start/running" > because status portmap is returning "start/spawned". That would indicate a separate bug in upstart itself. The upstart author has repeatedly assured us that 'start $foo' is not supposed to return until service $foo is running. If you are seeing this is not the case, please file a new bug report against upstart. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/484209 Title: /etc/init/statd.conf: race with portmap startup -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 484209] Re: /etc/init/statd.conf: race with portmap startup
In the problematic workstation I'm using Ubuntu 10.04.1 LTS, fully updated. -- /etc/init/statd.conf: race with portmap startup https://bugs.launchpad.net/bugs/484209 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 484209] Re: /etc/init/statd.conf: race with portmap startup
I have a workstation that the fix dosn't worked too. I'm not gettting errors on "start portmap" but on "status portmap | grep -q start/running" because status portmap is returning "start/spawned". Puting "sleep 1" afeter "start portmap || true" worked, probably because it gave portmap time to start up before "status portmap | grep -q start/running" test if portmap is runing. Probably a real solution is to put a loop to wait portmap start up, like: start portmap || true while status portmap | grep -v -q start/running do # if isn't running because a error ocurred, give up ... sleep 1 done exec sm-notify -- /etc/init/statd.conf: race with portmap startup https://bugs.launchpad.net/bugs/484209 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 484209] Re: /etc/init/statd.conf: race with portmap startup
Needless to say that the bug fix doesn't work for me... Why /etc/init/statd.conf says: start on (started portmap or mounting TYPE=nfs) (requiring portmap to be started before starting the statd job) and later it tries to run portmap manually in the pre-start script? I can't see the point. I probably am wrong, but I think pre-start script is executed AFTER the "start on" event is activated, right? -- /etc/init/statd.conf: race with portmap startup https://bugs.launchpad.net/bugs/484209 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 484209] Re: /etc/init/statd.conf: race with portmap startup
I have the same problem using Ubuntu Server 10.04.1 LTS, fully updated. Sometimes statd starts during system boot and sometimes don't. I resolve it replacing the "start on ..." line with: start on runlevel [2] -- /etc/init/statd.conf: race with portmap startup https://bugs.launchpad.net/bugs/484209 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 484209] Re: /etc/init/statd.conf: race with portmap startup
On Thu, May 20, 2010 at 07:00:20PM -, Atti wrote: > Same problem with Lucid, I actually solved it by adding > "exec rpc.statd -L $STATDOPTS" > before > "status portmap | grep -q start/ || start portmap" Utterly broken. If you do that, 'status statd' will correctly report that the job is *not* running. And the problem you're seeing isn't the same as this bug, either. You're probably seeing bug #525154. -- 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 -- /etc/init/statd.conf: race with portmap startup https://bugs.launchpad.net/bugs/484209 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 484209] Re: /etc/init/statd.conf: race with portmap startup
Same problem with Lucid, I actually solved it by adding
"exec rpc.statd -L $STATDOPTS"
before
"status portmap | grep -q start/ || start portmap"
my statd.conf file actually is:
[...]
[ "x$NEED_STATD" != xno ] || { stop; exit 0; }
start portmap || true
exec rpc.statd -L $STATDOPTS
status portmap | grep -q start/ || start portmap
exec sm-notify
end script
[...]
--
/etc/init/statd.conf: race with portmap startup
https://bugs.launchpad.net/bugs/484209
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 484209] Re: /etc/init/statd.conf: race with portmap startup
I am also seeing this in Karmic, I'm also in Xen here. Please update the script. It took me quite some time to find this bug report via Google. -- /etc/init/statd.conf: race with portmap startup https://bugs.launchpad.net/bugs/484209 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 484209] Re: /etc/init/statd.conf: race with portmap startup
Sorry, my above comment got posted before I was done writing. Before applying Malcolm's patch, I got: start: Job failed to start when I tried to start statd. This problem was preventing me from using NFS shares mounted by autofs. Needless to say, it was a critical problem for me that users could not access their files! I really think that this fix needs to be applied to Karmic most urgently. I can't be the only one affected. If you try to reproduce this bug, please keep in mind that it doesn't fail every time. Being a race condition it succeeds sometimes and fails sometimes. And finally: Thank you THANK YOU to Malcolm for providing the explanation as well as a solution. I had been tearing my hair out over this one! It took me hours of work to track down this solution. I will post some of the symptoms I had of the NFS failures here so that other googlers may find this solution more easily: /var/log/syslog: automount[1812]: attempting to mount entry /mnt/fileserver/home automount[5556]: >> mount.nfs: rpc.statd is not running but is required for remote locking. init: statd pre-start process (6242) terminated with status 1 -- /etc/init/statd.conf: race with portmap startup https://bugs.launchpad.net/bugs/484209 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 484209] Re: /etc/init/statd.conf: race with portmap startup
I can confirm that this issue exists in Karmic! I applied Malcolm's fix to /etc/init/statd.conf, and I was able to start statd with: sudo start statd -- /etc/init/statd.conf: race with portmap startup https://bugs.launchpad.net/bugs/484209 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 484209] Re: /etc/init/statd.conf: race with portmap startup
Any kernel panics you're seeing in the reiserfs kernel module are bugs in that driver and have nothing to do with this bug report. -- /etc/init/statd.conf: race with portmap startup https://bugs.launchpad.net/bugs/484209 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 484209] Re: /etc/init/statd.conf: race with portmap startup
Yes, I can confirm this race condition exists in Karmic, experiencing it every time I shutdown our file server. To add insult to injury, the race also causes random crashes in reiserfs kernel module here (NULL pointer, kernel BUG) forcing full filesystem scan on next boot. Which takes ca. 4 hours on my 6 TB RAID volume, pretty annoying. I will try the suggested fix and report back. -- /etc/init/statd.conf: race with portmap startup https://bugs.launchpad.net/bugs/484209 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 484209] Re: /etc/init/statd.conf: race with portmap startup
** Also affects: nfs-utils (Ubuntu Karmic) Importance: Undecided Status: New ** Also affects: nfs-utils (Ubuntu Lucid) Importance: Medium Assignee: Steve Langasek (vorlon) Status: Fix Released ** Changed in: nfs-utils (Ubuntu Karmic) Status: New => Triaged -- /etc/init/statd.conf: race with portmap startup https://bugs.launchpad.net/bugs/484209 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 484209] Re: /etc/init/statd.conf: race with portmap startup
I have tried to confirm this fix in karmic (bug #504776) in my setup, but I have not been successful to prove that this is the case. -- /etc/init/statd.conf: race with portmap startup https://bugs.launchpad.net/bugs/484209 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 484209] Re: /etc/init/statd.conf: race with portmap startup
I second C Snover's remark. I was bitten by this bug in Karmic. The proposed fix works for me. -- /etc/init/statd.conf: race with portmap startup https://bugs.launchpad.net/bugs/484209 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 484209] Re: /etc/init/statd.conf: race with portmap startup
This bug exists in karmic, unfixed; is there a reason that nfs-utils 1.2.0-2ubuntu9 was packaged and released for lucid only? -- /etc/init/statd.conf: race with portmap startup https://bugs.launchpad.net/bugs/484209 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 484209] Re: /etc/init/statd.conf: race with portmap startup
This bug was fixed in the package nfs-utils - 1:1.2.0-2ubuntu9 --- nfs-utils (1:1.2.0-2ubuntu9) lucid; urgency=low * debian/nfs-common.statd.upstart: check for a started portmap in a non-racy manner. LP: #484209. -- Steve LangasekTue, 17 Nov 2009 11:27:37 -0600 ** Changed in: nfs-utils (Ubuntu) Status: Triaged => Fix Released -- /etc/init/statd.conf: race with portmap startup https://bugs.launchpad.net/bugs/484209 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 484209] Re: /etc/init/statd.conf: race with portmap startup
Confirmed, there's a race condition here. The race-free fix would be: start portmap || true status portmap | grep -q start/running ** Changed in: nfs-utils (Ubuntu) Importance: Undecided => Medium ** Changed in: nfs-utils (Ubuntu) Status: New => Triaged ** Changed in: nfs-utils (Ubuntu) Assignee: (unassigned) => Steve Langasek (vorlon) -- /etc/init/statd.conf: race with portmap startup https://bugs.launchpad.net/bugs/484209 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
