Bug#469117: sysvinit: Doesn't mount NFS shares at startup
This bug was closed in portmap_6.0-9 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#469117: sysvinit: Doesn't mount NFS shares at startup
I have this bug too on lenny. I think that this is because then script /etc/network/if-up.d/mountnfs start portmap by command: /etc/init.d/portmap start it doesn't start (i found on my console: Starting portmap daemon... Already running..) This is because then /etc/init.d/portmap check it pid by function: pid=$( pidofproc portmap ) it found pid for /bin/sh /etc/init.d/portmap start and does not start /sbin/portmap. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#469117: sysvinit: Doesn't mount NFS shares at startup
I would like to re-open this bug. Here's my interfaces file: auto lo iface lo inet loopback allow-hotplug eth0 iface eth0 inet static address 192.168.40.5 netmask 255.255.255.0 network 192.168.40.0 broadcast 192.168.40.255 gateway 192.168.40.254 dns-nameservers 192.168.40.254 dns-search maglie.it -- After boot nothing is mounted, but if execute manually /etc/network/if-up.d/mountnfs my shares are correctly mounted. I use etch. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#469117: sysvinit: Doesn't mount NFS shares at startup
Package: sysvinit Version: 2.86.ds1-53 Severity: normal Since a while now, the nfs entries in my /etc/fstab are not mounted (they have an auto line). Also /proc/mounts doesn't say they're mounted. After starting up, I have to manually do a 'sudo mount -a' to get my NFS shares mounted. I found this possibly related issue in Ubuntu: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/45842 -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (990, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.22-3-686 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages sysvinit depends on: ii initscripts 2.86.ds1-53 Scripts for initializing and shutt ii libc62.7-6 GNU C Library: Shared libraries ii libselinux1 2.0.15-2+b1 SELinux shared libraries ii libsepol12.0.11-1Security Enhanced Linux policy lib ii sysv-rc 2.86.ds1-53 System-V-like runlevel change mech ii sysvinit-utils 2.86.ds1-53 System-V-like utilities sysvinit recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#469117: [Pkg-sysvinit-devel] Bug#469117: sysvinit: Doesn't mount NFS shares at startup
[Manuel Bilderbeek] Since a while now, the nfs entries in my /etc/fstab are not mounted (they have an auto line). Also /proc/mounts doesn't say they're mounted. After starting up, I have to manually do a 'sudo mount -a' to get my NFS shares mounted. What is the content of your /etc/fstab and /etc/network/interfaces? The current system try to mount the NFS mounts after all the 'auto' interfaces are up during boot. I found this possibly related issue in Ubuntu: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/45842 This is about having / on NFS. It does not work without changes to the boot system at the moment, because ifup does not do its normal things when the IP setup is done by the kernel before ifupdown is executed. Not sure if it is related to your problem. Your fstab will tell, I guess. :) Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#469117: [Pkg-sysvinit-devel] Bug#469117: sysvinit: Doesn't mount NFS shares at startup
Hi, What is the content of your /etc/fstab and /etc/network/interfaces? The current system try to mount the NFS mounts after all the 'auto' interfaces are up during boot. Due to security reasons, I'll have to scratch out some names, but the structure will be the same as the original file: # /etc/fstab: static file system information. # # file system mount point type options dump pass /dev/hda4 / ext3defaults,noatime,errors=remount-ro 0 1 /dev/hda3 noneswapsw 0 0 /dev/fd0/floppy autorw,user,noauto 0 0 /dev/hdc/cdrom autoro,user,noauto 0 0 proc/proc procdefaults0 0 /dev/hda1 /mnt/winxpdisk ntfs defaults,ro,user,noauto,umask=022,uid=0,gid=0 /dev/hda5 /mnt/datadisk vfat defaults,user,noauto,umask=022,uid=N,gid=100 nfsserver.oce.nl:/export/home/NAME /mnt/datashare/ nfs defaults,user,exec,auto,rsize=8192,wsize=8192 0 0 anothernfsserver.oce.nl:/files1/tools /tools nfs defaults,user,exec,auto,rsize=8192,wsize=8192 0 0 //yetanotherserver/data /mnt/scans smbfs credentials=/home/NAME/.scans-credentials,user,auto Here is /etc/network/interfaces: auto lo iface lo inet loopback # This entry was created during the Debian installation auto eth0 iface eth0 inet dhcp auto usb0 iface usb0 inet static address 10.0.0.1 netmask 255.255.255.0 I found this possibly related issue in Ubuntu: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/45842 This is about having / on NFS. It does not work without changes to Not only, AFAICS. the boot system at the moment, because ifup does not do its normal things when the IP setup is done by the kernel before ifupdown is executed. Not sure if it is related to your problem. Your fstab will tell, I guess. :) I hope this is enough to get a grip on this problem. Thanks! -- Kind regards, Manuel Bilderbeek (Apologies for the following stuff that is automatically added beyond my power.) This message and attachment(s) are intended solely for use by the addressee and may contain information that is privileged, confidential or otherwise exempt from disclosure under applicable law. If you are not the intended recipient or agent thereof responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately by telephone and with a 'reply' message. Thank you for your co-operation.
Bug#469117: [Pkg-sysvinit-devel] Bug#469117: sysvinit: Doesn't mount NFS shares at startup
[Manuel Bilderbeek] Due to security reasons, I'll have to scratch out some names, but the structure will be the same as the original file: Thanks. No / on NFS, so that is not the problem here. Here is /etc/network/interfaces: auto lo iface lo inet loopback # This entry was created during the Debian installation auto eth0 iface eth0 inet dhcp auto usb0 iface usb0 inet static address 10.0.0.1 netmask 255.255.255.0 This is the first time I see an usb0 interface. Could it be that ifupdown do not call the scripts in /etc/network/if-up.d/ when this static interface is brought up? Is it brought up during boot? Does it work if you comment out the 'auto usb0' line? What is the content of your /etc/network/run/ifstate file? Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#469117: [Pkg-sysvinit-devel] Bug#469117: sysvinit: Doesn't mount NFS shares at startup
Hi, auto usb0 iface usb0 inet static address 10.0.0.1 netmask 255.255.255.0 This is the first time I see an usb0 interface. Could it be that ifupdown do not call the scripts in /etc/network/if-up.d/ when this static interface is brought up? Is it brought up during boot? Does it work if you comment out the 'auto usb0' line? It isn't brought up most of the time (not for the last few months), because there's nothing connected to it. Also, I don't see anything about it in dmesg or /var/log/messages or /var/log/syslog. I commented out the usb0 interface completely now (as I don't use it anymore) and I'll report back soon to tell you if it helped. What is the content of your /etc/network/run/ifstate file? lo=lo eth0=eth0 -- Kind regards, Manuel Bilderbeek This message and attachment(s) are intended solely for use by the addressee and may contain information that is privileged, confidential or otherwise exempt from disclosure under applicable law. If you are not the intended recipient or agent thereof responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately by telephone and with a 'reply' message. Thank you for your co-operation.
Bug#469117: [Pkg-sysvinit-devel] Bug#469117: sysvinit: Doesn't mount NFS shares at startup
Hi, [Manuel Bilderbeek] It isn't brought up most of the time (not for the last few months), because there's nothing connected to it. Also, I don't see anything about it in dmesg or /var/log/messages or /var/log/syslog. OK. Then this is your problem, because NFS mounting is done after the last of the auto interfaces listed in /etc/network/interfaces is available. Ah! I didn't know this at all! Thanks for clearing that up. I commented it out, so I suppose it will work next time. Consider this solved then. If I still have problems, I'll report back. Petter Reinholdtsen Petter, thanks again for your very quick response and superb support. -- Kind regards, Manuel Bilderbeek This message and attachment(s) are intended solely for use by the addressee and may contain information that is privileged, confidential or otherwise exempt from disclosure under applicable law. If you are not the intended recipient or agent thereof responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately by telephone and with a 'reply' message. Thank you for your co-operation.
Bug#469117: [Pkg-sysvinit-devel] Bug#469117: sysvinit: Doesn't mount NFS shares at startup
[Manuel Bilderbeek] It isn't brought up most of the time (not for the last few months), because there's nothing connected to it. Also, I don't see anything about it in dmesg or /var/log/messages or /var/log/syslog. OK. Then this is your problem, because NFS mounting is done after the last of the auto interfaces listed in /etc/network/interfaces is available. I commented out the usb0 interface completely now (as I don't use it anymore) and I'll report back soon to tell you if it helped. What is the content of your /etc/network/run/ifstate file? lo=lo eth0=eth0 No usb0 - no NFS mount. Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#469117: [Pkg-sysvinit-devel] Bug#469117: Bug#469117: sysvinit: Doesn't mount NFS shares at startup
Hi Petter 2008/3/3, Petter Reinholdtsen [EMAIL PROTECTED]: [Manuel Bilderbeek] It isn't brought up most of the time (not for the last few months), because there's nothing connected to it. Also, I don't see anything about it in dmesg or /var/log/messages or /var/log/syslog. OK. Then this is your problem, because NFS mounting is done after the last of the auto interfaces listed in /etc/network/interfaces is available. What's the reasoning behind this? Why don't you try to mount as soon as one (*not* all) connection is established? Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
