RE: [opensuse] mounts not mounting at boot time, etc
Do you have service "nfs" enabled?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~` I do, as is samba and ntp. After the machine is up I can mount manually & run /etc/init.d/ntp and everything will start fine.
It appears the network isn't up, or have an address, when the above commands are called during the boot process.
Then the problem you have to solve is why "dhcp" does not get an IP. /etc/sysconfig/network/{something}: DHCLIENT_WAIT_AT_BOOT="5" change that as appropiate. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Thank you, Carlos. Changed the wait-time to 65 seconds and still the mounts nor ntp were done. Maybe I am barking up the wrong tree. Where in the boot process does mounting take place? Any ideas what else I can look for? Examined the message log and see that ntp can't find (or perhaps resolve?) the server, ntp.example.com; <start> Jul 5 07:18:35 test-ws syslog-ng[2553]: syslog-ng version 1.6.12 going down Jul 5 07:19:45 test-ws syslog-ng[2509]: syslog-ng version 1.6.12 starting Jul 5 07:19:47 test-ws auditd[2603]: Started dispatcher: /sbin/audispd pid: 2605 Jul 5 07:19:47 test-ws audispd[2605]: listening on /var/run/audit_events Jul 5 07:19:47 test-ws auditd[2603]: Init complete, auditd 1.5.5 listening for events (startup state disable) Jul 5 07:19:48 test-ws avahi-daemon[2609]: Found user 'avahi' (UID 105) and group 'avahi' (GID 107). Jul 5 07:19:48 test-ws avahi-daemon[2609]: Successfully dropped root privileges. Jul 5 07:19:48 test-ws avahi-daemon[2609]: avahi-daemon 0.6.20 starting up. Jul 5 07:19:48 test-ws avahi-daemon[2609]: Loading service file /etc/avahi/services/sftp-ssh.service. Jul 5 07:19:48 test-ws avahi-daemon[2609]: Loading service file /etc/avahi/services/ssh.service. Jul 5 07:19:48 test-ws avahi-daemon[2609]: Network interface enumeration completed. Jul 5 07:19:48 test-ws avahi-daemon[2609]: Registering HINFO record with values 'X86_64'/'LINUX'. Jul 5 07:19:48 test-ws avahi-daemon[2609]: Server startup complete. Host name is test-ws.local. Local service cookie is 72422764. Jul 5 07:19:48 test-ws avahi-daemon[2609]: Service "test-ws" (/etc/avahi/services/ssh.service) successfully establis hed. Jul 5 07:19:48 test-ws avahi-daemon[2609]: Service "SFTP File Transfer on test-ws" (/etc/avahi/services/sftp-ssh.ser vice) successfully established. Jul 5 07:19:48 test-ws su: (to postgres) root on /dev/pts/5 Jul 5 07:19:50 test-ws avahi-dnsconfd[2734]: Successfully connected to Avahi daemon. Jul 5 07:19:50 test-ws ntpdate[2686]: can't find host ntp.example.com <<------- "Why?" Jul 5 07:19:50 test-ws webmin[2547]: Webmin starting Jul 5 07:19:50 test-ws ntpdate[2686]: no servers can be used, exiting Jul 5 07:19:50 test-ws kernel: klogd 1.4.1, log source = /proc/kmsg started. <snip> More output from ntpd; <snip> Jul 5 07:19:50 test-ws ntpd[2750]: ntpd 4.2.4p3@1.1502-o Fri Sep 21 21:36:25 UTC 2007 (1) Jul 5 07:19:50 test-ws ntpd[2798]: precision = 1.000 usec Jul 5 07:19:50 test-ws ntpd[2798]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16 Jul 5 07:19:50 test-ws ntpd[2798]: Listening on interface #0 wildcard, 0.0.0.0#123 Disabled <<---"Is this the problem?" Jul 5 07:19:50 test-ws ntpd[2798]: Listening on interface #1 wildcard, ::#123 Disabled Jul 5 07:19:50 test-ws ntpd[2798]: Listening on interface #2 lo, ::1#123 Enabled Jul 5 07:19:50 test-ws ntpd[2798]: bind() fd 19, family 10, port 123, scope 2, addr fe80::203:25ff:fe4f:c682, in6_is_a ddr_multicast=0 flags=0x11 fails: Cannot assign requested address Jul 5 07:19:50 test-ws ntpd[2798]: unable to create socket on eth0 (3) for fe80::203:25ff:fe4f:c682#123 Jul 5 07:19:50 test-ws ntpd[2798]: failed to initialize interface for address fe80::203:25ff:fe4f:c682 Jul 5 07:19:50 test-ws ntpd[2798]: Listening on interface #4 lo, 127.0.0.1#123 Enabled Jul 5 07:19:50 test-ws ntpd[2798]: kernel time sync status 0040 Jul 5 07:19:51 test-ws ntpd[2798]: frequency initialized -124.935 PPM from /var/lib/ntp/drift/ntp.drift <snip> It appears that it is not listening on eth0. Now I see dhcp-discover request in /var/log/messages; <snip> Jul 5 07:19:55 test-ws dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 2 Jul 5 07:19:55 test-ws dhclient: DHCPOFFER from 10.0.0.5 <snip> ...and more; <snip> Jul 5 07:20:00 test-ws dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67 Jul 5 07:20:00 test-ws dhclient: DHCPACK from 10.0.0.5 Jul 5 07:20:00 test-ws dhclient: bound to 10.0.0.127 -- renewal in 1721 seconds. Jul 5 07:20:00 test-ws avahi-daemon[2609]: Withdrawing address record for fe80::203:25ff:fe4f:c682 on eth0. Jul 5 07:20:00 test-ws avahi-daemon[2609]: Joining mDNS multicast group on interface eth0.IPv4 with address 10.0.0.127 . Jul 5 07:20:00 test-ws avahi-daemon[2609]: New relevant interface eth0.IPv4 for mDNS. Jul 5 07:20:00 test-ws avahi-daemon[2609]: Registering new address record for 10.0.0.127 on eth0.IPv4. <snip> How can I ensure that dhcp-discover takes place earlier in the boot cycle? Sorry about the length of this e-mail. Many thanks for your help. ~James -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Saturday 2008-07-05 at 08:03 -0700, James D. Parra wrote:
Then the problem you have to solve is why "dhcp" does not get an IP.
/etc/sysconfig/network/{something}:
DHCLIENT_WAIT_AT_BOOT="5"
change that as appropiate. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Thank you, Carlos. Changed the wait-time to 65 seconds and still the mounts nor ntp were done. Maybe I am barking up the wrong tree.
Where in the boot process does mounting take place? Any ideas what else I can look for?
Local filesystems are mounted very early, from boot.localfs I think. Later, networked filesystem are mounted via the nfs script.
Examined the message log and see that ntp can't find (or perhaps resolve?) the server, ntp.example.com;
Jul 5 07:18:35 test-ws syslog-ng[2553]: syslog-ng version 1.6.12 going down Jul 5 07:19:45 test-ws syslog-ng[2509]: syslog-ng version 1.6.12 starting
Jul 5 07:19:48 test-ws avahi-daemon[2609]: Network interface enumeration completed.
Jul 5 07:19:50 test-ws avahi-dnsconfd[2734]: Successfully connected to Avahi daemon.
Avahi? :-? :-O
Jul 5 07:19:50 test-ws ntpdate[2686]: can't find host ntp.example.com <<------- "Why?"
No network, or no resolving.
Now I see dhcp-discover request in /var/log/messages;
<snip> Jul 5 07:19:55 test-ws dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 2 Jul 5 07:19:55 test-ws dhclient: DHCPOFFER from 10.0.0.5 <snip>
...and more; <snip> Jul 5 07:20:00 test-ws dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67 Jul 5 07:20:00 test-ws dhclient: DHCPACK from 10.0.0.5 Jul 5 07:20:00 test-ws dhclient: bound to 10.0.0.127 -- renewal in 1721 seconds.
So, maybe you have to tell it to wait 3 minutes. O use a fixed IP.
Jul 5 07:20:00 test-ws avahi-daemon[2609]: Withdrawing address record for fe80::203:25ff:fe4f:c682 on eth0.
Avahi again... :-?
How can I ensure that dhcp-discover takes place earlier in the boot cycle?
Search for the problem with a packet sniffer on the same network, and look up the server daemon logs, to see why the IP is not given earlier. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFIb7UMtTMYHG2NR9URAtSxAJ9lazFHJoe2sRl5w9DpFYrARE7YXACZAZhF CG7dkQIjtx48Zsqs+p9ug44= =CA1S -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (2)
-
Carlos E. R.
-
James D. Parra