Robert Steinmetz
2019-Feb-24 00:55 UTC
[Samba] Samba Won't start after upgrading Operating system
I ungraded my Linux Operating system from Ubuntu 16.04 LTS to 8.04 LTS Samba will not start after an upgrade to 18.04. My samba is running as an NT style member server server with smbd nmbd and winbindd all running. None of them will start. It worked this morning. This morning it was running Version 4.3.11-Ubuntu This afternoon after the upgrade it's Version 4.7.6-Ubuntu The logs in /var/spool/samba are empty. root at louise:/var/log/samba# systemctl start smbd Job for smbd.service failed because the control process exited with error code. See "systemctl status smbd.service" and "journalctl -xe" for details. root at louise:/var/log/samba# systemctl status smbd smbd.service - Samba SMB Daemon Loaded: loaded (/lib/systemd/system/smbd.service; enabled; vendor preset: ena Active: failed (Result: exit-code) since Sat 2019-02-23 18:01:35 EST; 20s ago Docs: man:smbd(8) man:samba(7) man:smb.conf(5) Process: 4594 ExecStart=/usr/sbin/smbd --foreground --no-process-group $SMBDOP Main PID: 4594 (code=exited, status=1/FAILURE) Feb 23 18:01:35 louise systemd[1]: Starting Samba SMB Daemon... Feb 23 18:01:35 louise systemd[1]: smbd.service: Main process exited, code=exite Feb 23 18:01:35 louise systemd[1]: smbd.service: Failed with result 'exit-code'. Feb 23 18:01:35 louise systemd[1]: Failed to start Samba SMB Daemon. lines 1-13/13 (END) The information on all three processes is virtually identical. testparm gives a few warnings but it's been doing that for a while with no apparent problem See below. root at louise:/var/log/samba# testparm Load smb config files from /etc/samba/smb.conf rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384) WARNING: The "idmap uid" option is deprecated WARNING: The "idmap gid" option is deprecated handle_name_resolve_order: WARNING: Ignoring invalid list value 'hosts' for parameter 'name resolve order' Error loading services. I've found a number of posts with similar problems but none seem directly on point.
Gregory Sloop
2019-Feb-24 04:05 UTC
[Samba] Samba Won't start after upgrading Operating system
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. nameserver 127.0.0.1 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 127.0.0.1 - until you have Samba up properly, then return to just 127.0.0.1.] --- 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. -Greg 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.
Robert Steinmetz
2019-Feb-24 06:53 UTC
[Samba] Samba Won't start after upgrading Operating system
Thanks for the response. I think found and fixed the problem, but I need to do some more testing tomorrow. It seems that the "handle_name_resolve_order: WARNING: Ignoring invalid list value 'hosts' for parameter 'name resolve order'" is not really a warning and it causes testparm to stop processing the smb.conf. I think that is also what caused the daemons to fail. As soon as I changed that everything started working. I hope someone with more knowledge of samba looks into it to confirm that was what was really happening. If so the error message at least needs to be changed. testparm then generated warning something like "login server=ipaddress" should not be used with "security=domain", but the man pages say while its it's not necessary, it can be used to point at a specific login server. In my case I only have one login server so it shouldn't cause any problems. I can see how it could mess up an AD domain with multiple controllers. On 2/23/19 11:05 PM, Gregory Sloop wrote:> Re: [Samba] Samba Won't start after upgrading Operating system 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. > nameserver 127.0.0.1 > > 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 127.0.0.1 - until you have Samba up properly, > then return to just 127.0.0.1.] > > --- > > 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. > > -Greg > > > *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. > > > *
Rowland Penny
2019-Feb-24 08:33 UTC
[Samba] Samba Won't start after upgrading Operating system
On Sat, 23 Feb 2019 19:55:03 -0500 Robert Steinmetz via samba <samba at lists.samba.org> wrote:> I ungraded my Linux Operating system from Ubuntu 16.04 LTS to 8.04 LTS > > Samba will not start after an upgrade to 18.04. My samba is running > as an NT style member server server with smbd nmbd and winbindd all > running. None of them will start. > > It worked this morning. > > This morning it was running Version 4.3.11-Ubuntu > > This afternoon after the upgrade it's Version 4.7.6-Ubuntu > > The logs in /var/spool/samba are empty. > > > root at louise:/var/log/samba# systemctl start smbd > Job for smbd.service failed because the control process exited with > error code. > See "systemctl status smbd.service" and "journalctl -xe" for details. > root at louise:/var/log/samba# systemctl status smbd > > > smbd.service - Samba SMB Daemon > Loaded: loaded (/lib/systemd/system/smbd.service; enabled; vendor > preset: ena > Active: failed (Result: exit-code) since Sat 2019-02-23 18:01:35 > EST; 20s ago > Docs: man:smbd(8) > man:samba(7) > man:smb.conf(5) > Process: 4594 ExecStart=/usr/sbin/smbd --foreground > --no-process-group $SMBDOP > Main PID: 4594 (code=exited, status=1/FAILURE) > > Feb 23 18:01:35 louise systemd[1]: Starting Samba SMB Daemon... > Feb 23 18:01:35 louise systemd[1]: smbd.service: Main process exited, > code=exite > Feb 23 18:01:35 louise systemd[1]: smbd.service: Failed with result > 'exit-code'. > Feb 23 18:01:35 louise systemd[1]: Failed to start Samba SMB Daemon. > lines 1-13/13 (END) > > The information on all three processes is virtually identical. > > testparm gives a few warnings but it's been doing that for a while > with no apparent problem See below. > > root at louise:/var/log/samba# testparm > Load smb config files from /etc/samba/smb.conf > rlimit_max: increasing rlimit_max (1024) to minimum Windows limit > (16384) WARNING: The "idmap uid" option is deprecated > WARNING: The "idmap gid" option is deprecated > handle_name_resolve_order: WARNING: Ignoring invalid list value > 'hosts' for parameter 'name resolve order' > Error loading services. > > I've found a number of posts with similar problems but none seem > directly on point. > > >The value for 'name resolv order' is 'host' not 'hosts', if this doesn't fix it, please post your smb.conf. You really should start planning to upgrade to AD, Microsoft has already broken NT4-style domains by accident and they have no reason to even consider them whilst writing code, because they dropped them 10 years ago. Rowland
Rowland Penny
2019-Feb-24 19:08 UTC
[Samba] Samba Won't start after upgrading Operating system
On Sun, 24 Feb 2019 13:08:07 -0500 Robert Steinmetz <rob at steinmetznet.com> wrote:> Rowland Penny via samba wrote: > On Sat, 23 Feb 2019 19:55:03 -0500 > Robert Steinmetz via samba <samba at lists.samba.org> wrote: > > I ungraded my Linux Operating system from Ubuntu 16.04 LTS to 8.04 LTS > > Samba will not start after an upgrade to 18.04. My samba is running > as an NT style member server server with smbd nmbd and winbindd all > running. None of them will start. > > It worked this morning. > > This morning it was running Version 4.3.11-Ubuntu > > This afternoon after the upgrade it's Version 4.7.6-Ubuntu > > The logs in /var/spool/samba are empty. > > > root at louise:/var/log/samba# systemctl start smbd > Job for smbd.service failed because the control process exited with > error code. > See "systemctl status smbd.service" and "journalctl -xe" for details. > root at louise:/var/log/samba# systemctl status smbd > > > smbd.service - Samba SMB Daemon > Loaded: loaded (/lib/systemd/system/smbd.service; enabled; vendor > preset: ena > Active: failed (Result: exit-code) since Sat 2019-02-23 18:01:35 > EST; 20s ago > Docs: man:smbd(8) > man:samba(7) > man:smb.conf(5) > Process: 4594 ExecStart=/usr/sbin/smbd --foreground > --no-process-group $SMBDOP > Main PID: 4594 (code=exited, status=1/FAILURE) > > Feb 23 18:01:35 louise systemd[1]: Starting Samba SMB Daemon... > Feb 23 18:01:35 louise systemd[1]: smbd.service: Main process exited, > code=exite > Feb 23 18:01:35 louise systemd[1]: smbd.service: Failed with result > 'exit-code'. > Feb 23 18:01:35 louise systemd[1]: Failed to start Samba SMB Daemon. > lines 1-13/13 (END) > > The information on all three processes is virtually identical. > > testparm gives a few warnings but it's been doing that for a while > with no apparent problem See below. > > root at louise:/var/log/samba# testparm > Load smb config files from /etc/samba/smb.conf > rlimit_max: increasing rlimit_max (1024) to minimum Windows limit > (16384) WARNING: The "idmap uid" option is deprecated > WARNING: The "idmap gid" option is deprecated > handle_name_resolve_order: WARNING: Ignoring invalid list value > 'hosts' for parameter 'name resolve order' > Error loading services. > > I've found a number of posts with similar problems but none seem > directly on point. > > > > > The value for 'name resolv order' is 'host' not 'hosts', if this > doesn't fix it, please post your smb.conf. > > > > I am planning an upgrade but I need to upgrade the OS first. > > Unfortunately while changing the name resolv order did allow testparm > to run I now have another problem. > > I thought I had resolved my problem in the earlier post, However I > have an additional problem. No users can login. Windows reports there > is no path to the shares and that is cannot access the member server, > although it shows up in the lists of servers and can beaccessed by > administrator accounts. > > wbinfo -u works and gives a list of all users > > getent passwd does not show any remote users of the PDCDoes 'getent passwd username' work ?> > I have rejoined the domain with net join -U administrator > > The PDC is running Samba Version Version 4.3.11-Ubuntu > The member server is running 4.7.6-Ubuntu > > #testparm > Load smb config files from /etc/samba/smb.conf > rlimit_max: increasing rlimit_max (1024) to minimum Windows limit > (16384) WARNING: The "idmap uid" option is deprecated > WARNING: The "idmap gid" option is deprecated > Processing section "[printers]" > Processing section "[print$]" > Processing section "[Hamlet]" > Processing section "[Projects]" > Processing section "[Office]" > Processing section "[Sigma]" > Processing section "[Windows]" > Processing section "[Recovered]" > Processing section "[Vault]" > Processing section "[Files]" > Processing section "[Arris]" > Loaded services file OK. > Server role: ROLE_DOMAIN_MEMBER > > Press enter to see a dump of your service definitions > Hers is the global section of the smb.conf file as seen by testparm > > [global] > idmap gid = 10000-20000 > idmap uid = 10000-20000The above have been superseded by 'idmap config' so you can probably remove them.> log file = /var/log/samba/log.%m > max log size = 1000 > name resolve order = wins bcast host > panic action = /usr/share/samba/panic-action %d > security = DOMAINIs winbind running ?> server string = %h file server (Samba, Ubuntu) > template shell = /bin/bash > winbind enum groups = Yes > winbind enum users = Yes > winbind use default domain = Yes > wins proxy = Yes > wins server = 192.168.1.24 > workgroup = ATLANTA > idmap config * : range = 10000-20000 > idmap config * : backend = tdb > admin users = administrator rob > hosts allow = 192.168.1.0/255.255.255.0 >Rowland