[Samba] Samba Won't start after upgrading Operating system

Gregory Sloop gregs at sloop.net
Sun Feb 24 04:05:16 UTC 2019

Top posting...

While I don't really see any details that indicate this is the problem, systemd-resolved causes the packaged 18.04 samba to fail to start [at least in a full AD setup.]
That's because system has a full DNS resolver, and Samba also has it's own DNS resolver. When they both try to start on the same port, the first running wins [systemd] and Samba exits.

Since you're running in NT not AD mode, it's possible that's different.
Here's how I handle systemd-resolved in my AD servers

systemctl mask systemd-resolved.service
systemctl stop systemd-resolved.service

Remove the linked file
[it's a link to: ../run/systemd/resolve/stub-resolv.conf
# rm /etc/resolv.conf

# nano /etc/resolv.conf

[Edit your resolv.conf as appropriate - in AD servers, pointing at itself.

And in the Samba config - setup the forwarder to point to another DNS server that will handle records outside the AD domain.

[You won't have *ANY* DNS until Samba starts properly. If you need DNS for more setup, change the resolv.conf to point at something additionally/other than - until you have Samba up properly, then return to just]


Now, as noted, this is for an AD setup - which I have no familiarity with, in regards to current Samba, so the above might not apply.
But it's worth a try - easy to roll-back if it doesn't fix anything etc.


RSvs> I ungraded my Linux Operating system from Ubuntu 16.04 LTS to 8.04 LTS

RSvs> Samba will not start after an upgrade to 18.04. My samba is running as
RSvs> an NT style member server server with smbd nmbd and winbindd all 
RSvs> running. None of them will start.

RSvs> It worked this morning.

RSvs> This morning it was running Version 4.3.11-Ubuntu

RSvs> This afternoon after the upgrade it's Version 4.7.6-Ubuntu

RSvs> The logs in /var/spool/samba are empty.

RSvs> root at louise:/var/log/samba# systemctl start smbd
RSvs> Job for smbd.service failed because the control process exited with 
RSvs> error code.
RSvs> See "systemctl status smbd.service" and "journalctl -xe" for details.
RSvs> root at louise:/var/log/samba# systemctl status smbd

RSvs>   smbd.service - Samba SMB Daemon
RSvs>     Loaded: loaded (/lib/systemd/system/smbd.service; enabled; vendor 
RSvs> preset: ena
RSvs>     Active: failed (Result: exit-code) since Sat 2019-02-23 18:01:35 
RSvs> EST; 20s ago
RSvs>       Docs: man:smbd(8)
RSvs>             man:samba(7)
RSvs>             man:smb.conf(5)
RSvs>    Process: 4594 ExecStart=/usr/sbin/smbd --foreground 
RSvs> --no-process-group $SMBDOP
RSvs>   Main PID: 4594 (code=exited, status=1/FAILURE)

RSvs> Feb 23 18:01:35 louise systemd[1]: Starting Samba SMB Daemon...
RSvs> Feb 23 18:01:35 louise systemd[1]: smbd.service: Main process exited, 
RSvs> code=exite
RSvs> Feb 23 18:01:35 louise systemd[1]: smbd.service: Failed with result 
RSvs> 'exit-code'.
RSvs> Feb 23 18:01:35 louise systemd[1]: Failed to start Samba SMB Daemon.
RSvs> lines 1-13/13 (END)

RSvs> The information on all three processes is virtually identical.

RSvs> testparm gives a few warnings but it's been doing that for a while with
RSvs> no apparent problem See below.

RSvs> root at louise:/var/log/samba# testparm
RSvs> Load smb config files from /etc/samba/smb.conf
RSvs> rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
RSvs> WARNING: The "idmap uid" option is deprecated
RSvs> WARNING: The "idmap gid" option is deprecated
RSvs> handle_name_resolve_order: WARNING: Ignoring invalid list value 'hosts'
RSvs> for parameter 'name resolve order'
RSvs> Error loading services.

RSvs> I've found a number of posts with similar problems but none seem 
RSvs> directly on point.

More information about the samba mailing list