Samba smbd service exits after boot on Debian Jessie

Josh Scott · 01-02-2017, 03:42 PM

Hello all,

I'm stumped on a new Debian Jessie simple Samba server setup issue. I setup a new PC with Debian Jessie 8.6, installed all the samba packages and brought over a working smb.conf from another Debian Jessie machine I have. I setup the smb user with smbpasswd and enabled them. Testparm returns no errors.

Problem is, after the system boots, the smbd.service goes into Active (exited) state - effectively not running - so you can't access the shares on the network. If I restart the smbd service, it goes into active (running) status and the samba server works great (I can access the shares across the network no problem). Here is the info from /var/log/samba/log.smbd:

Code:

[2017/01/02 13:46:10,  0] ../source3/smbd/server.c:1241(main)
  smbd version 4.2.14-Debian started.
  Copyright Andrew Tridgell and the Samba Team 1992-2014
[2017/01/02 13:46:10.383069,  0] ../source3/lib/interface.c:543(load_interfaces)
  WARNING: no network interfaces found
[2017/01/02 13:46:10.402720,  0] ../lib/util/become_daemon.c:124(daemon_ready)
  STATUS=daemon 'smbd' finished starting up and ready to serve connections
[2017/01/02 13:46:10.404739,  0] ../source3/smbd/server.c:856(open_sockets_smbd)
  open_sockets_smbd: No sockets available to bind to.
[2017/01/02 13:46:10.404862,  0] ../source3/lib/util.c:788(smb_panic_s3)
  PANIC (pid 1017): open_sockets_smbd() failed
[2017/01/02 13:46:10.405547,  0] ../source3/lib/util.c:899(log_stack_trace)
  BACKTRACE: 9 stack frames:
   #0 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(log_stack_trace+0x1a) [0x7fe63ab28efa]
   #1 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(smb_panic_s3+0x20) [0x7fe63ab28fe0]
   #2 /usr/lib/x86_64-linux-gnu/libsamba-util.so.0(smb_panic+0x2f) [0x7fe63c7e2e5f]
   #3 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0(+0x157f93) [0x7fe63c3e3f93]
   #4 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0(+0x1582c1) [0x7fe63c3e42c1]
   #5 /usr/lib/x86_64-linux-gnu/samba/libsmbd-shim.so.0(exit_server+0x12) [0x7fe63a4ceca2]
   #6 /usr/sbin/smbd(main+0x129b) [0x7fe63ce3c09b]
   #7 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7fe6391bcb45]
   #8 /usr/sbin/smbd(+0x76e4) [0x7fe63ce3c6e4]
[2017/01/02 13:46:10.405593,  0] ../source3/lib/util.c:800(smb_panic_s3)
  smb_panic(): calling panic action [/usr/share/samba/panic-action 1017]
[2017/01/02 13:46:10.416869,  0] ../source3/lib/util.c:808(smb_panic_s3)
  smb_panic(): action returned status 0
[2017/01/02 13:46:10.416895,  0] ../source3/lib/dumpcore.c:318(dump_core)
  dumping core in /var/log/samba/cores/smbd

It seems to panic and fail at "open_sockets_smbd: No sockets available to bind to" ... But Networking is working fine. I have already done:

Code:

systemctl enable smbd.service

and it completes successfully.

Anyone seen this or have any ideas?

Thanks,

Josh Scott
Gigabyte GA-B85M-D3H booting with UEFI
8GB RAM, Core i3, Realtek Onboard NIC

TenTenths · 01-03-2017, 07:50 AM

Code:

[2017/01/02 13:46:10.383069,  0] ../source3/lib/interface.c:543(load_interfaces)
  WARNING: no network interfaces found

is the more interesting error message.

Check that your networking is starting earlier in the startup sequence.

Josh Scott · 01-03-2017, 07:03 PM

Quote:

Originally Posted by TenTenths

Code:

[2017/01/02 13:46:10.383069,  0] ../source3/lib/interface.c:543(load_interfaces)
  WARNING: no network interfaces found

is the more interesting error message.

Check that your networking is starting earlier in the startup sequence.

Thanks for your reply TenTenths. That was my first thought too. I don't know much about systemd but the two scripts I can find for smbd both look good that way.. In /run/systemd/generator.late/smbd.service it does have

Code:

After=network-online.target

and

Code:

Wants=network-online.target

in it. Then there is this script /etc/init/smbd.conf (who knew?) and this one has

Code:

start on (local-filesystems and net-device-up)

in it.

Does anyone know if there is another or a better way to move samba services down the list?

Thanks,
Josh

c0wb0y · 01-04-2017, 02:52 PM

Can you diff the old and new config, paying special attention to 'interfaces' directive as its name can change?

When you

Code:

systemctl enable smbd.service

Did you actually verified if it is indeed serving by checking its systemctl status and network connections? How about checking its unit file

Code:

systemctl cat smb.service

Josh Scott · 01-05-2017, 01:29 PM

Quote:

Originally Posted by c0wb0y

Can you diff the old and new config, paying special attention to 'interfaces' directive as its name can change?

When you

Code:

systemctl enable smbd.service

Did you actually verified if it is indeed serving by checking its systemctl status and network connections? How about checking its unit file

Code:

systemctl cat smb.service

Thanks c0wb0y,

I did check the unit file (see above) .. it looked ok to me.. And after I restart the service, yes it runs and serves.

In any case, I nuked this machine the other night because it was having hardware issues.. so.. I'll be trying again soon and may post again. We can close this thread until then.

Thanks everyone for your responses and ideas.

Josh