I am sure I had never touched my nfs-common prior to the bug showing
up. I suspect that an upgrade has introduced code that is less tolerant
of syntax than before.
On 06/01/16 11:55, jmartinz wrote:
> I've been having the same error.
> In my case statd.log gave this message:
> /proc/self/fd/9
I've been having the same error.
In my case statd.log gave this message:
/proc/self/fd/9: 6: /etc/default/nfs-common: no: not found
Checking /etc/default/nfs-common there was this line
NEED_STATD= no
instead of
NEED_STATD=no
(note the space between = an no) and it was giving me that error.
I a
Thanks for following up. Local configuration error, closing as invalid.
** Changed in: nfs-utils (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1523228
T
Hi Again
Found the problem. Checked the /etc/default/nfs-common file and the
entry NEED_GSSD was not followed by an equal sign (=).
Changed to NEED_GSSD= and all is well. upstart log now gives
"UPSTART_EVENTS = virtual-filesystems started"!
Thanks for the pointer. A few minutes Googling and I
Hi Steve
Checked the statd.log s for the last few days. All contain one or more
of the following entries.
/proc/self/fd/9: 16: /etc/default/nfs-common: NEED_GSSD: not found
Regards
Pete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
The error in your log is:
Setting up nfs-common (1:1.2.8-6ubuntu1.2) ...
start: Job failed to start
invoke-rc.d: initscript statd, action "restart" failed.
dpkg: error processing package nfs-common (--configure):
Please attach /var/log/upstart/statd.log from the affected system.
** Changed in: n
