The way we're dealing with it at my site is as follows:
blacklist autofs4 module
# echo "blacklist autofs4" > /etc/modprobe.d/autofs.conf
# chmod 644 /etc/modprobe.d/autofs.conf
# chown root:root /etc/modprobe.d/autofs.conf
load autofs module
# echo "autofs" >> /etc/modules
# reboot
This is fo
autofs does not need and should not have a strong require for ypbind
(or, even statd)
However, when configured to autostart NFS mounts or to use NIS (!) then
of course it depends on those services.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Yury, I'm sorry this bug is affecting you. It is blocked on bug #569757
, which has made slow progress, but may be close to landing in precise.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/573919
Tit
Latest Lucid and I'm having this issue. Can't be true it's still borked
:-(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/573919
Title:
autofs doesn't work with lucid
To manage notifications about
Oh and to another point, statd's start on has changed and now always
starts before NFS mounts are attempted. So the patch provided isn't
really valid.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/5739
Hello to all reporters of this issue. It seems to me that the upstream
encoded requirements for autofs:
# Required-Start: $network $ypbind
# Required-Stop: $network $ypbind
Have not been properly captured in the upstart job:
start on (filesystem
and net-device-up IFACE!=lo)
stop on runlevel
Further investigation revealed that in my case autofs was not racing
with statd, but rather with nis (client daemon): bug 569757 and bug
570513. The workaround #15 appeared to work in some cases, because it
introduced a small delay into autofs init script, which gave time for
the nis daemon to star
Our 10 machine system (all lucid 64-bit) also suffers from this diffuse
bug. Workaround #23 did not work, some of the machines start autofs
anyway even with "start on never" in /etc/init/autofs.conf . Putting
"service autofs restart" in /etc/rc.local works only for about half of
the machines and no
Someone have an idea on how start autofs on boot with upstart???
I have a server with 9.10 and 10.04, the first is ok, the second no.
The solution with the "start on never" and adding "service autofs start" in the
file
/etc/rc.local works, but is very very worst under the sysadmin's point of
vi
On yet another machine autofs would not start correctly neither with the
workaround from comment #15, nor without it. My efforts to convince
Upstart to run startup scripts in a correct sequence ended in an utter
failure. What I did instead is to modify /etc/init/autofs.conf so that
Upstart doesn't
#15 worked for me as well. I also set NEED_STATD=yes in /etc/default
/nfs-common.
But autofs should only depend on statd if it is mounting NFS volumes.
autofs can be used with other filesystems besides NFS.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
For me workaround given in comment #8 in bug 525154 worked on four
systems, but on the fifth it was not enough, and I had to combine it
with #15 from this bug report. I have to admit that number of problems
caused by Upstart is astoundingly high, and they crop up unexpectedly in
a random fashion. I
13 in bug 525154 and #15 of this solved my problems.
--
autofs doesn't work with lucid
https://bugs.launchpad.net/bugs/573919
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
Post 13 in bug 525154 above has solved the issue with statd, but now
autofs is failing to start. I tried to something similar with
/etc/init/autofs.conf but to no avail. Still no joy here.
k3nt-1 are you seeing the error messages in your /var/logs/boot.log file
that I posted above?
--
autofs doe
Strange, because /var is mounted as part of / in my configuration
(though I faced the problem...)
--
autofs doesn't work with lucid
https://bugs.launchpad.net/bugs/573919
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs ma
This is the same bug as 590570, but this one has been around longer.
I think the real issue underlying this bug is in bug 525154 which
relates to a race condition while starting portmap which in turn starts
statd. This only seems to be an issue if you have /var as a separate
mount point where /var
If you look in /etc/init/portmap.conf you will see that its prerequisite
for starting is statd which is done in /etc/init/portmap.conf. However,
there are numerous errors in my /var/log/boot.log file.
I upgraded two machines and both have the same issue as mentioned above.
A new install I did does
Autofs doesn't work because it startup script has incorrect dependency
to statd (doesn't have). Can submit workaround: in /etc/init/autofs.conf
add line
status statd | grep -q start/running || start statd
after "pre-start script" line
--
autofs doesn't work with lucid
https://bugs.launchpad.net
I'm not sure if my problem is exactly the same as others are having
here. but it definitely matches the description of "autofs doesn't work
with lucid". I've tried the workarounds listed here without success,
though.
My original problem is described here:
http://ubuntuforums.org/showthread.php?t=
Finally managed to successfully connect to my NFS server.
Steps to solve the problem:
* Add the following line to /etc/nsswitch.conf:
automount: nis files
* Change my /etc/auto.nfs config file by removing the options and leaving only
the local folder and the target
--
autofs doesn't work with
I can't also use autofs5 to automount server's home directory for my users.
The workaround to get it work was to remove autofs5 autofs-ldap autofs5-ldap,
then download karmic version of autofs and autofs-ldap
wget
http://fr.archive.ubuntu.com/ubuntu/pool/main/a/autofs/autofs_4.1.4+debian-2.1ubunt
** Tags added: patch
--
autofs doesn't work with lucid
https://bugs.launchpad.net/bugs/573919
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/list
Same problem here, autofs doesn't work because statd is not started.
Some more debugging revealed that:
if some NFS3 mount is used in /etc/fstab, anything work, statd ist
started automatic, but if there is no NFS3 mount inside fstab statd is
not started even with autof. So some of the upstart rul
Hi,
After upgrading from 9.10 to 10.04, I had a short bit of trouble getting
autofs working until I figured out that I needed to re-add the line
automount: files nis
to /etc/nsswitch.conf . Now things are working OK for me.
--
autofs doesn't work with lucid
https://bugs.launchpad.net/bugs/
I also have this problem under Ubuntu 10.04LTS.
Running the automounter manually (thanks onkara), on attempting to change to an
NFS-mounted directory, I noticed:
>> mount.nfs: rpc.statd is not running but is required for remote locking.
>> mount.nfs: Either use '-o nolock' to keep locks local, o
It seems autofs is completely broken for me not only does the service
not start automatically it doesn't mount NFS shares on manual start.
Here is what I have tried
$ sudo service autofs restart
autofs start/running, process 4590
in syslog I see
May 14 12:44:17 sky-ubuntu automount[4590]: synta
This bug started out as 'autofs does not work with lucid'
but the more recent comments indicate 'autofs works with lucid but does not
start on boot in lucid'
Can we nail down which it is and fix the notes and/or the title?
I'm running Ubuntu 10.04 LTS; autofs is working fine for me but does not
k3nt-1 :
I've got the same message. Doing
sudo start autofs
worked.
But I still was unable to make autofs start at boot where other dameon
depending on filesystem or on net-device-up where started as expected.
Any direction on how to debug the problem ?
--
autofs doesn't work with lucid
https
autofs should depend on statd in upstart
Run:
start statd
to verify
It looks like this is a bug in statd... which is just plain wrong :)
With upstart do you have to teach other services about your service?
eg autofs needs statd. statd says "start on (started portmap or mounting
TYPE=nfs)" whi
** Changed in: autofs (Ubuntu)
Status: Incomplete => New
--
autofs doesn't work with lucid
https://bugs.launchpad.net/bugs/573919
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.ubunt
Same problem here: NFS disk mounted via autofs does not mount since
upgrade to lucid.
Besides, when trying to stop/restart the service, I encounter the following
result:
$ service autofs restart
restart: Rejected send message, 1 matched rules; type="method_call",
sender=":1.64" (uid=1000 pid=32
I can confirm this. I got the same problem with network-mounted directories.
When I switch on autofs, the directories that should be mounted, are empty and
not accessable. Once I uninstall autofs, the directories reappear.
In Karmic everything works fine, not so in Lucid.
Does anyone know what to
here are more information about this issue :
The hardware I used for this test and I witnessed this problem with :
SAMSUNG N150 Laptop
What I wanted to do :
I have Installed Ubuntu with the 10.04 BETA1, then I did daily updates.
Today I decided to install autofs (cause I forgot to do it), I use t
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Unfortunately, we can't fix it because your description didn't include
enough information. You may find it helpful to read "How to report bugs
effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html.
34 matches
Mail list logo
