[Bug 581941] Re: statd does not start automatically when needed nor can be forced to start on boot

2010-12-23 Thread Steve Langasek
*** This bug is a duplicate of bug 525154 *** https://bugs.launchpad.net/bugs/525154 ** This bug has been marked a duplicate of bug 525154 mountall for /var races with rpc.statd * You can subscribe to bug 525154 by following this link: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+

[Bug 581941] Re: statd does not start automatically when needed nor can be forced to start on boot

2010-12-23 Thread Clint Byrum
Looks like this one is also a duplicate of an even earlier bug, bug #525154 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/581941 Title: statd does not start automatically when needed nor can be forc

[Bug 581941] Re: statd does not start automatically when needed nor can be forced to start on boot

2010-12-22 Thread Launchpad Bug Tracker
** Branch linked: lp:~clint-fewbar/ubuntu/natty/nfs-utils/wait-for- local-filesystems -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/581941 Title: statd does not start automatically when needed nor c

[Bug 581941] Re: statd does not start automatically when needed nor can be forced to start on boot

2010-12-22 Thread Clint Byrum
Indeed, I've marked 690401 as a duplicate of this bug. I will update the changelog in the merge proposal accordingly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/581941 Title: statd does not start

[Bug 581941] Re: statd does not start automatically when needed nor can be forced to start on boot

2010-12-22 Thread Brian Murray
This seems like a duplicate of bug 690401. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/581941 Title: statd does not start automatically when needed nor can be forced to start on boot -- ubuntu-

[Bug 581941] Re: statd does not start automatically when needed nor can be forced to start on boot

2010-12-22 Thread Brian Murray
** Tags added: regression-release ** Changed in: nfs-utils (Ubuntu Natty) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/581941 Title: statd does not start automaticall

[Bug 581941] Re: statd does not start automatically when needed nor can be forced to start on boot

2010-12-21 Thread Robbie Williamson
** Changed in: nfs-utils (Ubuntu) Status: Incomplete => Triaged ** Changed in: nfs-utils (Ubuntu) Importance: Undecided => Medium ** Changed in: nfs-utils (Ubuntu) Assignee: (unassigned) => Canonical Foundations Team (canonical-foundations) ** Also affects: nfs-utils (Ubuntu Luci

[Bug 581941] Re: statd does not start automatically when needed nor can be forced to start on boot

2010-08-30 Thread ja...@apps4u.com.au
just to add to other post statd has been runnig the whole time ps aux | grep statd root 14801 0.0 0.0 16672 1128 pts/0S+ 14:13 0:00 rpc.statd -Fd root 16282 0.0 0.0 4096 592 ?S14:28 0:00 /bin/sh -c rpc.statd -Fd root 16283 0.0 0.0 16672 1152 ?

[Bug 581941] Re: statd does not start automatically when needed nor can be forced to start on boot

2010-08-30 Thread ja...@apps4u.com.au
I have been having this same issue I have just upgrade from 8.10 to 10.04 over a three week period . When I first upgrade all our mac 10.6 and 10.5 clients stopped auto mounting nfs homes and I used another bug (#540637) report which fixed the issue up untill 3 days ago when I started to have clien

[Bug 581941] Re: statd does not start automatically when needed nor can be forced to start on boot

2010-07-18 Thread Will
So I just type this before mounting an NFS share: /etc/init.d/statd restart and then statd starts and mount will work for me. But that's very manual :( -- statd does not start automatically when needed nor can be forced to start on boot https://bugs.launchpad.net/bugs/581941 You received this

[Bug 581941] Re: statd does not start automatically when needed nor can be forced to start on boot

2010-07-18 Thread Will
Me too! Grrr -- statd does not start automatically when needed nor can be forced to start on boot https://bugs.launchpad.net/bugs/581941 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.ubu

[Bug 581941] Re: statd does not start automatically when needed nor can be forced to start on boot

2010-07-11 Thread Jayen
Hi, I'm having the same problem (statd not starting on boot (after upgrading to lucid)) Should I be using the fix in #5, #7, #10, or #12? Thanks -- statd does not start automatically when needed nor can be forced to start on boot https://bugs.launchpad.net/bugs/581941 You received this bug noti

[Bug 581941] Re: statd does not start automatically when needed nor can be forced to start on boot

2010-06-22 Thread molostoff
I have tryed this as a temporary fix: -start on (started portmap or mounting TYPE=nfs) +start on (started portmap and net-device-up IFACE!=lo) and it works - after desktop logon I can see shares that are in rw-mode. But I think that statd should start before autofs (which I have using). -- stat

[Bug 581941] Re: statd does not start automatically when needed nor can be forced to start on boot

2010-06-22 Thread molostoff
It seems to me that it happens with my desktop too. I have 2 ubuntu servers 10.04 and one desktop 10.04. And statd problem exists only on desktop itself, servers go fine. As a simple comparison I see the difference in network interfaces: servers has a static interface config, while desktop has net

[Bug 581941] Re: statd does not start automatically when needed nor can be forced to start on boot

2010-06-20 Thread AlexAD
I have noticed the a number of daemons do not start in Ubuntu 10.04 - it seems the since version 6 Ubuntu users upstart. So I have created a temporary fix until it gets sorted. as root in /etc/init create a file called temp-fix.conf with the following contents: # Fixes failure to start a number o

[Bug 581941] Re: statd does not start automatically when needed nor can be forced to start on boot

2010-05-21 Thread Dave Martin
I could find where the log messages were going, so I disabled syslog logging in the source and rebuilt sm-notify. apt-get source nfs-utils The find the following lines in utils/statd/sm-notify.c and comment them out: log_syslog = 1; openlog("sm-notify", LOG_PID, LOG_DAEMON); Th

[Bug 581941] Re: statd does not start automatically when needed nor can be forced to start on boot

2010-05-21 Thread Marc Schiffbauer
Hi Steve, sorry, I did not notice that you pass -L to statd. I now removed the -L option from statd as well and it still is running after boot. After reverting back to original state (exec sm-notify in pre-start and statd -L) the log says: init: statd pre-start process (714) terminated with sta

[Bug 581941] Re: statd does not start automatically when needed nor can be forced to start on boot

2010-05-20 Thread Steve Langasek
Marc, when you dropped the 'exec sm-notify' call from the pre-start script, did you also remove the -L from the rpc.statd invocation? (You point out the -L option from the manpage, but don't comment on the fact that we *pass* -L by default.) Can you confirm Dave's comments that /var/lib is read-o

[Bug 581941] Re: statd does not start automatically when needed nor can be forced to start on boot

2010-05-20 Thread Dave Martin
This error bites me too --- here's my boot log Tweaking sm-notify to get more debug, the error appears to be: Cannot create /var/lib/nfs/state.new: Read-only file system Is this problem related to this bug, maybe? https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/525154 (mountall for /v

[Bug 581941] Re: statd does not start automatically when needed nor can be forced to start on boot

2010-05-19 Thread Marc Schiffbauer
Hi Steve, its failing in pre-start: "init: statd pre-start process (712) terminated with status 1" Thats the only line about it in boot.log with --verbose service portmap is running after boot, so I tried to comment out the "exec sm-notify" line. After that statd service is runng after reboot.

[Bug 581941] Re: statd does not start automatically when needed nor can be forced to start on boot

2010-05-18 Thread Steve Langasek
Hmm, it's not clear then why statd is failing to start at boot. Please boot with '--verbose' added to the kernel command line, and attach the resulting /var/log/boot.log. -- statd does not start automatically when needed nor can be forced to start on boot https://bugs.launchpad.net/bugs/581941

[Bug 581941] Re: statd does not start automatically when needed nor can be forced to start on boot

2010-05-18 Thread Marc Schiffbauer
Hi! I started statd like that: r...@ubuntu:~# service statd start statd start/running, process 2145 r...@ubuntu:~# This is the fstab: # /etc/fstab: static file system information. # #

[Bug 581941] Re: statd does not start automatically when needed nor can be forced to start on boot

2010-05-17 Thread Steve Langasek
Thank you for taking the time to report this issue and help to improve Ubuntu. Please post the /etc/fstab for this system. Also, when you started statd manually, how did you do so? ** Changed in: nfs-utils (Ubuntu) Status: New => Incomplete -- statd does not start automatically when nee

[Bug 581941] Re: statd does not start automatically when needed nor can be forced to start on boot

2010-05-17 Thread Marc Schiffbauer
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/48623350/Dependencies.txt -- statd does not start automatically when needed nor can be forced to start on boot https://bugs.launchpad.net/bugs/581941 You received this bug notification because you are a member of Ubuntu Bu