Ok, thanks. Now I remember during the upgrade I was asked if i wanted to
keep the idmapd config file or not.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927908
Title:
rpc.idmapd refuses to start
Why is /var/lib/nfs/rpc_pipefs missing in package nfs-common of precise?
It is present in oneiric.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927908
Title:
rpc.idmapd refuses to start
To manage
It's not missing. The correct directory is /run/rpc_pipefs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927908
Title:
rpc.idmapd refuses to start
To manage notifications about this bug go to:
I had the same problem and I had to create directory
/var/lib/nfs/rpc_pipefs because it was missing after upgrading from
oneiric to precise. Why was it missing?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
After creating directory /var/lib/nfs/rpc_pipefs, I have to manually
mount rpc_pipefs with
mount -t rpc_pipefs rpc_pipefs /var/lib/nfs/rpc_pipefs/
and then start the idmapd service to make it run.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
You have a wrong /etc/idmapd.conf pointing at a deprecated directory.
The nfs-common package in precise uses /run/rpc_pipefs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927908
Title:
rpc.idmapd
On Thu, 16 Feb 2012 00:35:27 -, Steve Langasek
steve.langa...@canonical.com wrote:
Oh, of course; the stop/pre-start message is precisely because the '|| {
stop; exit 0; }' is being called, and this is the output of the stop
command. So somehow, the job is failing to properly handle the
ok - invalid bug after all. ;) Thanks for following up.
Now the idmapd job can be started with service idmapd start.
However the logfile is empty:
Yes, we should expect an empty logfile here when there are no problems.
** Changed in: nfs-utils (Ubuntu)
Status: New = Invalid
--
You
On Sat, Feb 11, 2012 at 02:42:16PM -, manut wrote:
Instead, please try adding just 'exec /var/log/idmapd.log 21' as the
first line of the pre-start script. This will give you a /var/log/idmapd.log
showing what's going wrong.
Thanks for the hint. I removed the 'exec echo' lines and now
** Attachment added: idmapd.conf
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/927908/+attachment/2743747/+files/idmapd.conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927908
Title:
On Wed, Feb 15, 2012 at 10:40:47PM -, manut wrote:
** Attachment added: idmapd.conf
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/927908/+attachment/2743747/+files/idmapd.conf
Ok, that looks reasonable. Is there any chance that you accidentally ran
this 'exec' command on
Oh, interesting; I've just managed to reproduce exactly this sort of
problem here (with incomprehensible output) with the gssd job. Sorry
for assuming user error there. I'll see if I can puzzle out why we're
getting this useless stop/pre-start message instead of a useful log.
** Changed in:
Oh, of course; the stop/pre-start message is precisely because the '|| {
stop; exit 0; }' is being called, and this is the output of the stop
command. So somehow, the job is failing to properly handle the
NEED_IDMAPD setting in /etc/default/nfs-common. Could you attach this
file as well?
--
exec echo 2
end script
Instead, please try adding just 'exec /var/log/idmapd.log 21' as the
first line of the pre-start script. This will give you a /var/log/idmapd.log
showing what's going wrong.
Thanks for the hint. I removed the 'exec echo' lines and now get the following
On Tue, 07 Feb 2012 23:56:41 -, Steve Langasek
steve.langa...@canonical.com wrote:
On Tue, Feb 07, 2012 at 09:50:27AM -, manut wrote:
Even if i start it via upstart it doesn't work.
local@vogone:~$ sudo service idmapd start
idmapd stop/pre-start, process 5239
local@vogone:~$ ps -A |
On Thu, Feb 09, 2012 at 06:38:57PM -, manut wrote:
Which version of Ubuntu is this? Your report doesn't mention. (Please
use the 'ubuntu-bug' command for filing bugs, when possible.)
it's oneiric with latest updates
Ok. The oneiric upstart doesn't have the same job logging facilities
Even if i start it via upstart it doesn't work.
local@vogone:~$ sudo service idmapd start
idmapd stop/pre-start, process 5239
local@vogone:~$ ps -A | grep 5239
local@vogone:~$
in /etc/default/nfs-common
# Do you want to start the idmapd daemon? It is only needed for NFSv4.
NEED_IDMAPD=y
is
On Tue, Feb 07, 2012 at 09:50:27AM -, manut wrote:
Even if i start it via upstart it doesn't work.
local@vogone:~$ sudo service idmapd start
idmapd stop/pre-start, process 5239
local@vogone:~$ ps -A | grep 5239
local@vogone:~$
Which version of Ubuntu is this? Your report doesn't
rpc.idmapd is meant to be started from the /etc/init/idmapd.conf upstart
job, which takes care of mounting the rpc_pipefs filesystem beforehand.
** Changed in: nfs-utils (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
19 matches
Mail list logo
