richard russell
2018-Nov-11 12:09 UTC
[Samba] After reboot the server nmb service is not acitve.
I create multiple server instances for the samba with systemd, everything ok, but after reboot server, the service nmb does not work randomly. selinux disable samba version 4.2.10 config smb [global] workgroup = WORKGROUP3 netbios name = net3 security = user interfaces = enp7s0f3 bind interfaces only = yes server string = %h server log level = 5 max log size = 10000 passdb backend = tdbsam encrypt passwords = true map to guest = Bad User guest account = nobody create mask = 0777 directory mask = 0777 wide links = no unix extensions = yes local master = yes time server = no dns proxy = no wins support = no ntlm auth = no domain logons = no load printers = no printcap name = /dev/null pid directory = /var/run/samba/NAS3 [NAS3-ki-folder] valid users = cuser, buser read list = cuser, buser write list path = /mnt/NAS/myNASFS/ki-folder guest ok = no writable = yes create mask = 0777 directory mask = 0777 browseable = no ----------------------------------------------------------------------------------------------- log nmb.NAS3 add_name_to_subnet: Added netbios name __SAMBA__<00> with first IP 10.10.40.10 ttl=0 nb_flags= 0 to subnet REMOTE_BROADCAST_SUBNET [2018/11/11 19:42:09.029483, 0] ../source3/lib/util_sock.c:1250(create_pipe_sock) bind failed on pipe socket /run/samba/nmbd/unexpected: Address already in use [2018/11/11 19:42:09.029889, 0] ../source3/nmbd/nmbd_packets.c:48(nmbd_init_packet_server) ERROR: nb_packet_server_create failed: NT_STATUS_ADDRESS_ALREADY_ASSOCIATED [2018/11/11 19:42:09.030065, 0] ../lib/util/become_daemon.c:111(exit_daemon) STATUS=daemon failed to start: NMBD failed to setup packet server., error code 13
L A Walsh
2018-Nov-29 19:28 UTC
[Samba] After reboot the server nmb service is not acitve.
On 11/11/2018 4:09 AM, richard russell via samba wrote:> I create multiple server instances for the samba with systemd, everything > ok, but after reboot server, the service nmb does not work randomly. >--- First question, I would have, is what do you mean by you create multiple server instances for samba w/systemd. Then you get nmb not working randommly with, I assume, some of the server instances (on the same machine)? That's my 1st confusion: what do you mean by saying that you create multiple server instances? If you are starting the full "server" for samba multiple times, wouldn't "nmbd" also be started multiple times? If they are on the same machine, wouldn't they conflict with each other if they were all attempting to listen at the same address? Depending on random timing, any given instance of nmbd might fail if another instance had already been started. Is this what you meant? As for the you included, have you checked with 'netstat' to see what is already connected at nmbd's address? I.e. on my machine:> sudo netstat -pul |grep nmbd|sed -r 's/ {8}/ /g'udp 0 0 broadcast.sc:netbios-ns 0.0.0.0:* 1586/nmbd udp 0 0 Ishtar:netbios-ns 0.0.0.0:* 1586/nmbd udp 0 0 0.0.0.0:netbios-ns 0.0.0.0:* 1586/nmbd udp 0 0 broadcast.s:netbios-dgm 0.0.0.0:* 1586/nmbd udp 0 0 Ishtar:netbios-dgm 0.0.0.0:* 1586/nmbd udp 0 0 0.0.0.0:netbios-dgm 0.0.0.0:* 1586/nmbd (re: netstat, -u=udp, -l=include-listening, -p=showprog(requires root)) I see 1 copy of nmbd(pid=1586) listening to services 137(netbios-ns) and 138(netbios-dgm).> ----------------------------------------------------------------------------------------------- > log nmb.NAS3 > add_name_to_subnet: Added netbios name __SAMBA__<00> with first IP > 10.10.40.10 ttl=0 nb_flags= 0 to subnet REMOTE_BROADCAST_SUBNET > [2018/11/11 19:42:09.029483, 0] > ../source3/lib/util_sock.c:1250(create_pipe_sock) > bind failed on pipe socket /run/samba/nmbd/unexpected: Address already in > use > [2018/11/11 19:42:09.029889, 0] > ../source3/nmbd/nmbd_packets.c:48(nmbd_init_packet_server) > ERROR: nb_packet_server_create failed: > NT_STATUS_ADDRESS_ALREADY_ASSOCIATED > [2018/11/11 19:42:09.030065, 0] > ../lib/util/become_daemon.c:111(exit_daemon) > STATUS=daemon failed to start: NMBD failed to setup packet server., error > code 13 >
L.P.H. van Belle
2018-Nov-30 08:25 UTC
[Samba] After reboot the server nmb service is not acitve.
You can run the following. smbd nmbd winbind Or smbd nmbd Or smbd winbind Or winbind Or smbd Or nmbd Or nmbd winbind But not samba-ad-dc nmbd Or not samba-ad-dc smbd And not samba-ad-dc winbind ,, or any other combinatio of samba-ad-dc ... It only samba-ad-dc I suggest start thinging in future not past. Greetz, Louis> -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens L A > Walsh via samba > Verzonden: donderdag 29 november 2018 20:28 > Aan: richard russell > CC: samba at lists.samba.org > Onderwerp: Re: [Samba] After reboot the server nmb service is > not acitve. > > On 11/11/2018 4:09 AM, richard russell via samba wrote: > > I create multiple server instances for the samba with > systemd, everything > > ok, but after reboot server, the service nmb does not work randomly. > > > --- > First question, I would have, is what do you mean by you > create multiple > server instances for samba w/systemd. Then you get nmb not working > randommly > with, I assume, some of the server instances (on the same machine)? > > That's my 1st confusion: what do you mean by saying that > you create > multiple server instances? If you are starting the full > "server" for samba > multiple times, wouldn't "nmbd" also be started multiple > times? If they are > on the same machine, wouldn't they conflict with each other > if they were all > attempting to listen at the same address? > > Depending on random timing, any given instance of nmbd > might fail if > another instance had already been started. > > Is this what you meant? > > As for the you included, have you checked with 'netstat' to see > what is already connected at nmbd's address? > I.e. on my machine: > > > sudo netstat -pul |grep nmbd|sed -r 's/ {8}/ /g' > > udp 0 0 broadcast.sc:netbios-ns 0.0.0.0:* 1586/nmbd > udp 0 0 Ishtar:netbios-ns 0.0.0.0:* 1586/nmbd > udp 0 0 0.0.0.0:netbios-ns 0.0.0.0:* 1586/nmbd > udp 0 0 broadcast.s:netbios-dgm 0.0.0.0:* 1586/nmbd > udp 0 0 Ishtar:netbios-dgm 0.0.0.0:* 1586/nmbd > udp 0 0 0.0.0.0:netbios-dgm 0.0.0.0:* 1586/nmbd > > (re: netstat, -u=udp, -l=include-listening, > -p=showprog(requires root)) > I see 1 copy of nmbd(pid=1586) listening to services 137(netbios-ns) > and 138(netbios-dgm). > > > > > -------------------------------------------------------------- > --------------------------------- > > log nmb.NAS3 > > add_name_to_subnet: Added netbios name __SAMBA__<00> with first IP > > 10.10.40.10 ttl=0 nb_flags= 0 to subnet REMOTE_BROADCAST_SUBNET > > [2018/11/11 19:42:09.029483, 0] > > ../source3/lib/util_sock.c:1250(create_pipe_sock) > > bind failed on pipe socket /run/samba/nmbd/unexpected: > Address already in > > use > > [2018/11/11 19:42:09.029889, 0] > > ../source3/nmbd/nmbd_packets.c:48(nmbd_init_packet_server) > > ERROR: nb_packet_server_create failed: > > NT_STATUS_ADDRESS_ALREADY_ASSOCIATED > > [2018/11/11 19:42:09.030065, 0] > > ../lib/util/become_daemon.c:111(exit_daemon) > > STATUS=daemon failed to start: NMBD failed to setup > packet server., error > > code 13 > > > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba >