LinuxQuestions.org - Samba not starting properly at boot, because internet not started

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Samba not starting properly at boot, because internet not started (https://www.linuxquestions.org/questions/slackware-14/samba-not-starting-properly-at-boot-because-internet-not-started-4175476633/)

Samba not starting properly at boot, because internet not started

Hi, I have samba in rc.d/rc.d3, rc.d4 ...etc as: S85samba, after S50inetd. Linked to init.d/samba, but when I boot, samba doesn't start properly:

Quote:

Copyright Andrew Tridgell and the Samba Team 1992-2012
[2013/09/11 00:41:07, 0] nmbd/nmbd.c:57(terminate)
Got SIGTERM: going down...
[2013/09/11 00:49:08, 0] nmbd/nmbd.c:883(main)
nmbd version 4.0.0 started.
Copyright Andrew Tridgell and the Samba Team 1992-2012
[2013/09/11 00:49:08, 0] libsmb/nmblib.c:872(send_udp)
Packet send failed to 192.168.1.255(137) ERRNO=Network is unreachable
[2013/09/11 00:49:08, 0] nmbd/nmbd_packets.c:179(send_netbios_packet)
send_netbios_packet: send_packet() to IP 192.168.1.255 port 137 failed
[2013/09/11 00:49:08, 0] nmbd/nmbd_nameregister.c:522(register_name)
register_name: Failed to send packet trying to register name SERVER<20>
[2013/09/11 00:49:08, 0] libsmb/nmblib.c:872(send_udp)
Packet send failed to 192.168.1.255(137) ERRNO=Network is unreachable
[2013/09/11 00:49:08, 0] nmbd/nmbd_packets.c:179(send_netbios_packet)
send_netbios_packet: send_packet() to IP 192.168.1.255 port 137 failed
[2013/09/11 00:49:08, 0] nmbd/nmbd_nameregister.c:522(register_name)
register_name: Failed to send packet trying to register name SERVER<03>
[2013/09/11 00:49:08, 0] libsmb/nmblib.c:872(send_udp)
Packet send failed to 192.168.1.255(137) ERRNO=Network is unreachable
[2013/09/11 00:49:08, 0] nmbd/nmbd_packets.c:179(send_netbios_packet)
send_netbios_packet: send_packet() to IP 192.168.1.255 port 137 failed
[2013/09/11 00:49:08, 0] nmbd/nmbd_nameregister.c:522(register_name)
register_name: Failed to send packet trying to register name SERVER<00>
[2013/09/11 00:49:08, 0] libsmb/nmblib.c:872(send_udp)
Packet send failed to 192.168.1.255(137) ERRNO=Network is unreachable
[2013/09/11 00:49:08, 0] nmbd/nmbd_packets.c:179(send_netbios_packet)
send_netbios_packet: send_packet() to IP 192.168.1.255 port 137 failed
[2013/09/11 00:49:08, 0] nmbd/nmbd_nameregister.c:522(register_name)
register_name: Failed to send packet trying to register name WORKGROUP<00>
[2013/09/11 00:49:08, 0] libsmb/nmblib.c:872(send_udp)
Packet send failed to 192.168.1.255(137) ERRNO=Network is unreachable
[2013/09/11 00:49:08, 0] nmbd/nmbd_packets.c:179(send_netbios_packet)
send_netbios_packet: send_packet() to IP 192.168.1.255 port 137 failed
[2013/09/11 00:49:08, 0] nmbd/nmbd_nameregister.c:522(register_name)
register_name: Failed to send packet trying to register name WORKGROUP<1e>
[2013/09/11 00:49:08, 0] libsmb/nmblib.c:872(send_udp)
Packet send failed to 127.0.0.1(137) ERRNO=Network is unreachable
[2013/09/11 00:49:08, 0] nmbd/nmbd_packets.c:179(send_netbios_packet)
send_netbios_packet: send_packet() to IP 127.0.0.1 port 137 failed
[2013/09/11 00:49:08, 0] nmbd/nmbd_nameregister.c:344(multihomed_register_one)
multihomed_register_one: Failed to send packet trying to register name SERVER<20> IP 192.168.1.12
[2013/09/11 00:49:08, 0] libsmb/nmblib.c:872(send_udp)
Packet send failed to 127.0.0.1(137) ERRNO=Network is unreachable
[2013/09/11 00:49:08, 0] nmbd/nmbd_packets.c:179(send_netbios_packet)
send_netbios_packet: send_packet() to IP 127.0.0.1 port 137 failed
[2013/09/11 00:49:08, 0] nmbd/nmbd_nameregister.c:344(multihomed_register_one)
multihomed_register_one: Failed to send packet trying to register name SERVER<03> IP 192.168.1.12
[2013/09/11 00:49:08, 0] libsmb/nmblib.c:872(send_udp)
Packet send failed to 127.0.0.1(137) ERRNO=Network is unreachable
[2013/09/11 00:49:08, 0] nmbd/nmbd_packets.c:179(send_netbios_packet)
send_netbios_packet: send_packet() to IP 127.0.0.1 port 137 failed
[2013/09/11 00:49:08, 0] nmbd/nmbd_nameregister.c:344(multihomed_register_one)
multihomed_register_one: Failed to send packet trying to register name SERVER<00> IP 192.168.1.12
[2013/09/11 00:49:08, 0] libsmb/nmblib.c:872(send_udp)
Packet send failed to 127.0.0.1(137) ERRNO=Network is unreachable
[2013/09/11 00:49:08, 0] nmbd/nmbd_packets.c:179(send_netbios_packet)
send_netbios_packet: send_packet() to IP 127.0.0.1 port 137 failed
[2013/09/11 00:49:08, 0] nmbd/nmbd_nameregister.c:344(multihomed_register_one)
multihomed_register_one: Failed to send packet trying to register name WORKGROUP<00> IP 192.168.1.12
[2013/09/11 00:49:08, 0] libsmb/nmblib.c:872(send_udp)
Packet send failed to 127.0.0.1(137) ERRNO=Network is unreachable
[2013/09/11 00:49:08, 0] nmbd/nmbd_packets.c:179(send_netbios_packet)
send_netbios_packet: send_packet() to IP 127.0.0.1 port 137 failed
[2013/09/11 00:49:08, 0] nmbd/nmbd_nameregister.c:344(multihomed_register_one)
multihomed_register_one: Failed to send packet trying to register name WORKGROUP<1e> IP 192.168.1.12
[2013/09/11 00:51:02, 0] nmbd/nmbd.c:57(terminate)
Got SIGTERM: going down...
[2013/09/11 00:51:04, 0] nmbd/nmbd.c:883(main)
nmbd version 4.0.0 started.
Copyright Andrew Tridgell and the Samba Team 1992-2012

It only seemed to start properly manually or at rc.local:

Code:

#samba restart

/etc/init.d/samba restart

But I hope it could start perfectly at boot.
Thanks,
Ted

It looks like samba is starting before the network. So what is the XX for SXXnetwork? I would expect it to be a fairly low number.

Hi michael, the rc orders are as below:

Code:

ted:$ ls /etc/rc.d/rc3.d

K40cron@            K6transmission-daemon@  S51sshd@

K45samba@          K76firewall@            S70cron@

K48sshd@            K8gpm@                  S85samba@

K49inetd@          S23firewall@            S91gpm@

K4logmein-hamachi@  S30portmap@            S93transmission-daemon@

K60cups@            S39cups@                S94logmein-hamachi@

K69portmap@        S50inetd@

server:/~

ted:$ ls /etc/rc.d/rc4.d

K40cron@            K6transmission-daemon@  S51sshd@

K45samba@          K76firewall@            S70cron@

K48sshd@            K8gpm@                  S85samba@

K49inetd@          S23firewall@            S91gpm@

K4logmein-hamachi@  S30portmap@            S93transmission-daemon@

K60cups@            S39cups@                S94logmein-hamachi@

K69portmap@        S50inetd@

I believe that network is inetd, so I think there is enough time for network to be up before samba comes in.
Thanks for your reply,
Ted

What distribution/version?

Hi,

Code:



ted:$ uname -a

Linux server 3.0.17 #1 SMP Fri Jan 20 08:54:56 MST 2012 i686 Intel(R) Celeron(R) CPU 2.40GHz GenuineIntel GNU/Linux



ted:$ cat /etc/*version

Slackware 13.37.0

7.0 LIGHT built on March-20-2012

server:/~

The dist is slackware 13.37
Thanks,
Ted

inetd does not start the network. In a netshell it is a daemon that can manage other network services.
http://en.wikipedia.org/wiki/Inetd

Basically, the network is configured by udev.
http://alien.slackbook.org/dokuwiki/...ckware:network

I would take a look at the output of the dmesg command as well as the logs to see what errors if any pop up. Hopefully others have better ideas.

Quote:

Originally Posted by ted_chou12 (Post 5025597)

Hi michael, the rc orders are as below:

Code:

ted:$ ls /etc/rc.d/rc3.d

K40cron@            K6transmission-daemon@  S51sshd@

K45samba@          K76firewall@            S70cron@

K48sshd@            K8gpm@                  S85samba@

K49inetd@          S23firewall@            S91gpm@

K4logmein-hamachi@  S30portmap@            S93transmission-daemon@

K60cups@            S39cups@                S94logmein-hamachi@

K69portmap@        S50inetd@

server:/~

ted:$ ls /etc/rc.d/rc4.d

K40cron@            K6transmission-daemon@  S51sshd@

K45samba@          K76firewall@            S70cron@

K48sshd@            K8gpm@                  S85samba@

K49inetd@          S23firewall@            S91gpm@

K4logmein-hamachi@  S30portmap@            S93transmission-daemon@

K60cups@            S39cups@                S94logmein-hamachi@

K69portmap@        S50inetd@

I believe that network is inetd, so I think there is enough time for network to be up before samba comes in.
Thanks for your reply,
Ted

Does logmein-hamachi create its own virtual (tap or tun) interface? Bridge? If so Samba might need to be restarted afterwards, depending on the interfaces and hosts you allow in smb.conf.

Thanks gezley, I have also tried shifting samba to S95, but samba still fails to start (boot screen). hamachi does have its own ip:

Code:



ted:$ ifconfig

eth0      Link encap:Ethernet  HWaddr 00:01:80:5E:73:04

          inet addr:192.168.1.12  Bcast:192.168.1.255  Mask:255.255.255.0

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:1481992 errors:0 dropped:1 overruns:0 frame:0

          TX packets:914170 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:1929336774 (1839.9 Mb)  TX bytes:298164750 (284.3 Mb)

          Interrupt:22



ham0      Link encap:Ethernet  HWaddr 7A:79:19:86:C5:41

          inet addr:25.134.197.65  Bcast:25.255.255.255  Mask:255.0.0.0

          UP BROADCAST RUNNING MULTICAST  MTU:1404  Metric:1

          RX packets:77 errors:0 dropped:0 overruns:0 frame:0

          TX packets:649 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:500

          RX bytes:10857 (10.6 Kb)  TX bytes:134399 (131.2 Kb)



lo        Link encap:Local Loopback

          inet addr:127.0.0.1  Mask:255.0.0.0

          UP LOOPBACK RUNNING  MTU:16436  Metric:1

          RX packets:661 errors:0 dropped:0 overruns:0 frame:0

          TX packets:661 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:236410 (230.8 Kb)  TX bytes:236410 (230.8 Kb)

Thanks,
Ted

I've got the boot screen recorded, a bit shaky, but its here. Especially attention to the error for both samba:
http://www.youtube.com/watch?v=F67H_jJSYXQ

Quote:

Originally Posted by ted_chou12 (Post 5027456)

I've got the boot screen recorded, a bit shaky, but its here. Especially attention to the error for both samba:
http://www.youtube.com/watch?v=F67H_jJSYXQ

You are not running Slackware.
Your distro is Vector Linux, which will have its own support forum somewhere. Vector may be based on SLackware in some way, but it uses a completly different boot sequence.

Please find a better place to get answers.

Eric