Samba ошибка error loading services

On Ubuntu 18.04 whenever I do apt upgrade (even if no packages to upgrade):

root@JohnPC:/home/john# apt upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
0 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up samba (2:4.7.6+dfsg~ubuntu-0ubuntu2.2) 

…

Samba is not being run as an AD Domain Controller.
Please ignore the following error about deb-systemd-helper not finding samba-ad-dc.service.
Job for smbd.service failed because the control process exited with error code.
See "systemctl status smbd.service" and "journalctl -xe" for details.
invoke-rc.d: initscript smbd, action "restart" failed.
● smbd.service - Samba SMB Daemon
   Loaded: loaded (/lib/systemd/system/smbd.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Fri 2018-08-17 08:13:54 BST; 27ms ago
     Docs: man:smbd(8)
           man:samba(7)
           man:smb.conf(5)
  Process: 28404 ExecStart=/usr/sbin/smbd --foreground --no-process-group $SMBDOPTIONS (code=exited, status=1/FAILURE)
 Main PID: 28404 (code=exited, status=1/FAILURE)

Aug 17 08:13:54 JohnPC systemd[1]: Starting Samba SMB Daemon...
Aug 17 08:13:54 JohnPC systemd[1]: smbd.service: Main process exited, code=exited, status=1/FAILURE
Aug 17 08:13:54 JohnPC systemd[1]: smbd.service: Failed with result 'exit-code'.
Aug 17 08:13:54 JohnPC systemd[1]: Failed to start Samba SMB Daemon.
dpkg: error processing package samba (--configure):
 installed samba package post-installation script subprocess returned error exit status 1
Processing triggers for libc-bin (2.27-3ubuntu1) ...
Errors were encountered while processing:
 samba
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@JohnPC:/home/john# systemctl status smbd.service
● smbd.service - Samba SMB Daemon
   Loaded: loaded (/lib/systemd/system/smbd.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Fri 2018-08-17 08:13:54 BST; 43s ago
     Docs: man:smbd(8)
           man:samba(7)
           man:smb.conf(5)
  Process: 28404 ExecStart=/usr/sbin/smbd --foreground --no-process-group $SMBDOPTIONS (code=exited, st
 Main PID: 28404 (code=exited, status=1/FAILURE)

Aug 17 08:13:54 JohnPC systemd[1]: Starting Samba SMB Daemon...
Aug 17 08:13:54 JohnPC systemd[1]: smbd.service: Main process exited, code=exited, status=1/FAILURE
Aug 17 08:13:54 JohnPC systemd[1]: smbd.service: Failed with result 'exit-code'.
Aug 17 08:13:54 JohnPC systemd[1]: Failed to start Samba SMB Daemon.

answered Feb 17, 2019 at 18:18

I had the same problem and changed the bound interface in smb.conf from eno0 to eno1 (my actual interface), but the problem was still there.

Then I realised there was a smb.conf.ucf-dist in the same folder /etc/samba which had a wrong interface bound eth0.

I changed it to eno1, saved and then could apt update & upgrade without having the problem any more … Look like some config or all of it is taken from this file if it exists in the folder.

Hi there folks.

As you can tell by the subject line it is all about SAMBA. I am really pulling what little hair I have left out with this. So here is the background:

Very green Linux user. I have had Linux Mint 17,1 & 17.3 on a laptop for a while. They just work and I use them occasionally. (although I’ve never had them sharing files over my LAN with Windows machines etc). I decided to dual boot the shiny new TARA on to my main PC. That went fairly ok, and with some guidance from past posts and a Grub fix it now boots and runs lovely.

I really need this machine to talk to the other machines on the network though and so I went to … https://www.techrepublic.com/blog/five- … ing-samba/ .. looking for a gui to help me. I decided on … «WEBMEIN»
After following the instructions located at ….. http://www.webmin.com/samba-howto.html
My Samba is screwed, and no matter where I look I can’t figure out what to do.

So I figured. I’ll hold my hands up, say that I screws it up, and hope that someone is looking down on the forum kindly and might be willing to help, or at least point my tired eyes in the right direction.

Thanks in advance

Took a quick look at the Webmin Samba Howto and one issue is this:

10.) Change your security to share level then save the changes.

Share level security ( security = share in smb.conf ) is no longer a legitimate option in Samba. Hasn’t been for years. If you force it to that setting today smbd ( the samba daemon ) will refuse to start.

Side note: I would suggest that you get aquatinted with a samba diagnostic tool called testparm. You invoke it in a terminal this way:

If you were to run it with security set to share it would have told you what I just said above:

WARNING: Ignoring invalid value ‘share’ for parameter ‘security’
Error loading services.

The «service» it has an error loading is … well … itself ( smbd ).

Side note2: I also looked at your first link and you should know that system-config-samba has been abandoned, will not run, and designed for version3 of samba. Samba no longer supports SWAT. Gadmin-samba is far far worse — it was written for version2 of samba and will absolutely destroy your smb.conf file to such an extent that it will be inoperable.

First things first, thank you for replying to my post altair4, and thank you for your advice so far.

altair4 wrote: ⤴Sat Oct 13, 2018 6:46 am
Took a quick look at the Webmin Samba Howto and one issue is this:

10.) Change your security to share level then save the changes.

Share level security ( security = share in smb.conf ) is no longer a legitimate option in Samba. Hasn’t been for years. If you force it to that setting today smbd ( the samba daemon ) will refuse to start.

Thanks for that little bit. I have set the «Security» back to default and low and behold the SMB Service has started.

altair4 wrote: ⤴Sat Oct 13, 2018 6:46 am
Side note: I would suggest that you get aquatinted with a samba diagnostic tool called testparm. You invoke it in a terminal this way:

If you were to run it with security set to share it would have told you what I just said above:

WARNING: Ignoring invalid value ‘share’ for parameter ‘security’
Error loading services.

The «service» it has an error loading is … well … itself ( smbd ).

Yep you were right

altair4 wrote: ⤴Sat Oct 13, 2018 6:46 am
Side note2: I also looked at your first link and you should know that system-config-samba has been abandoned, will not run, and designed for version3 of samba. Samba no longer supports SWAT. Gadmin-samba is far far worse — it was written for version2 of samba and will absolutely destroy your smb.conf file to such an extent that it will be inoperable.

Ok, so having followed your brief advice so far I have firstly concluded that I am as green as grass, and that I really like the way Linux Mint just does what you tell it. (When you know what you are doing )

So now that the service is up and running again. Do you fancy, helping me out with getting it to talk to the windows PC’s on my network?

So now that the service is up and running again. Do you fancy, helping me out with getting it to talk to the windows PC’s on my network?

Well, that’s another issue. Linux-to-Linux samba is easy. Linux-to-Windows not so much.

The version of samba that comes with Ubuntu 18.04 ( Mint 19 ) made some changes primarily so that it could converse with Win10. In doing this some things got messed up. So I guess the question is what is the problem?

If you can no longer open your file manager and browse for Windows machines you might want to look at this: Mint 19 and Samba File Sharing Changes

altair4 wrote: ⤴Sat Oct 13, 2018 12:06 pm
Well, that’s another issue. Linux-to-Linux samba is easy. Linux-to-Windows not so much.

…. So I guess the question is what is the problem?

The problem is… Everything…

If I start from the beginning… I followed the doomed instructions as I mentioned before. But that didn’t work. Thanks to you I have now got Samba running.
If I click on «/Files/Network/» then I can see the machine I’m on plus a «windows network folder» if I click on that I can see «Home» (Which takes me to my router) or «Workgroup» if I click on that I get the error message..

Unable to mount location… Failed to retrieve share list from server: Success

There is NO folder with MY actual workgroup. (which I have changed in the smb.conf.

I did that but it hasn’t made any difference.

At this point I’m wondering if it may just be best to start from scratch and get a someone to hold my hand

Please post the output of this command to that we can see how far off from the default you actually are before we start over:

In the mean time if you did this:

There is NO folder with MY actual workgroup. (which I have changed in the smb.conf.

Did you restart samba? You do that in this order:

altair4 wrote: ⤴Sat Oct 13, 2018 1:32 pm
Please post the output of this command to that we can see how far off from the default you actually are before we start over:

No problem output as follows…

testparm -s
Load smb config files from /etc/samba/smb.conf
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
WARNING: The "syslog" option is deprecated
Processing section "[printers]"
Processing section "[print$]"
Loaded services file OK.
Server role: ROLE_STANDALONE

# Global parameters
[global]
	dns proxy = No
	log file = /var/log/samba/log.%m
	map to guest = Bad User
	max log size = 1000
	obey pam restrictions = Yes
	pam password change = Yes
	panic action = /usr/share/samba/panic-action %d
	passwd chat = *Entersnews*spassword:* %nn *Retypesnews*spassword:* %nn *passwordsupdatedssuccessfully* .
	passwd program = /usr/bin/passwd %u
	server role = standalone server
	server string = %h server (Samba, Ubuntu)
	syslog = 0
	unix password sync = Yes
	usershare allow guests = Yes
	workgroup = USLOT65
	idmap config * : backend = tdb


[printers]
	browseable = No
	comment = All Printers
	create mask = 0700
	path = /var/spool/samba
	printable = Yes
	read only = Yes


[print$]
	comment = Printer Drivers
	path = /var/lib/samba/printers
	read only = Yes

Hope that makes sense to you

In the mean time if you did this:

There is NO folder with MY actual workgroup. (which I have changed in the smb.conf.

Did you restart samba? You do that in this order:

Yep done that. Nothing…. So I did a Full PC Restart. Now I can see a folder with my workgroup name but it gives me the «Unable to mount location… Failed to retrieve share list from server: Success» error when I click on it.

So how are we looking?

I don’t know how you are getting to the point where you get «failed to retrieve ..» error. When you go to Network > Windows network you should get a blank screen because netbios browsing is disabled in Mint 19 without the NT1 reference.

Anyhoo what I would do is edit /etc/samba/smb.conf and right below the workgroup = USLOT65 line add these:

client max protocol = NT1
name resolve order = bcast host lmhosts wins

Then restart smbd then nmbd again.

You really should see if Samba itself is working on this box. You do that by trying to access each of your Windows machines by ip address not by name. Open a terminal and run — with the correct ip address of the Windows machine:

altair4 wrote: ⤴Sat Oct 13, 2018 2:25 pm
I don’t know how you are getting to the point where you get «failed to retrieve ..» error. When you go to Network > Windows network you should get a blank screen because netbios browsing is disabled in Mint 19 without the NT1 reference.

As per your other post and suggestion I added the NT1 reference as well as the name resolve order stuff. ( I did that after your second post. You pointed me to one of your other post/tutorials, so I added them in then)

You really should see if Samba itself is working on this box. You do that by trying to access each of your Windows machines by ip address not by name. Open a terminal and run — with the correct ip address of the Windows machine:

Done that and I get the error..

Could not display «smb://192.168/…/…»
error:Failed to retrieve share list from server: Invalid argument. Please select another viewer and try again.

So… I have included here a copy of the «GLOBAL» section from my smb.conf.

[global]

## Browsing/Identification ###

# Change this to the workgroup/NT-domain name your Samba server will part of
workgroup = USLOT65

netbios name = Charles
client max protocol = NT1
security = user
client use spnego = no
name resolve order = bcast host lmhosts wins

# server string is the equivalent of the NT Description field
server string = %h server (Samba, Ubuntu)

# Windows Internet Name Serving Support Section:
# WINS Support — Tells the NMBD component of Samba to enable its WINS Server
# wins support = no

# WINS Server — Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
; wins server = w.x.y.z

# This will prevent nmbd to search for NetBIOS names through DNS.
dns proxy = no

Hope that helps too

altair4 wrote: ⤴Sat Oct 13, 2018 3:00 pm
I don’t think I can help you. The output of testparm doesn’t match what you have in smb.conf and I don’t know how that can happen.

That really is a shame, you have been amazing so far.
Would it be best to just delete the smb.conf I have and start from fresh?

Thanks for everything

altair4 wrote: ⤴Sat Oct 13, 2018 3:17 pm
If you have things in your smb.conf that testparm cannot pick up I don’t know how restarting with a new smb.conf will fix things but there is a recovery default smb.conf located at /usr/share/samba/smb.conf if you want to try.

Perhaps that might have led to my having problems… .. It seems that after following an earlier post it is the /usr/share/samba/smb.conf that i have been altering. I have since put everything as it was. changed everything in the /etc/samba/smb.conf instead, and here follow the testparm -s output

grandad@Charles:~$ testparm -s
Load smb config files from /etc/samba/smb.conf
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
WARNING: The «syslog» option is deprecated
Processing section «[printers]»
Processing section «[print$]»
Loaded services file OK.
Server role: ROLE_STANDALONE

# Global parameters
[global]
client use spnego = No
dns proxy = No
log file = /var/log/samba/log.%m
map to guest = Bad User
max log size = 1000
name resolve order = bcast host lmhosts wins
obey pam restrictions = Yes
pam password change = Yes
panic action = /usr/share/samba/panic-action %d
passwd chat = *Entersnews*spassword:* %nn *Retypesnews*spassword:* %nn *passwordsupdatedssuccessfully* .
passwd program = /usr/bin/passwd %u
security = USER
server role = standalone server
server string = %h server (Samba, Ubuntu)
syslog = 0
unix password sync = Yes
usershare allow guests = Yes
workgroup = USLOT65
idmap config * : backend = tdb

[printers]
browseable = No
comment = All Printers
create mask = 0700
path = /var/spool/samba
printable = Yes
read only = Yes

[print$]
comment = Printer Drivers
path = /var/lib/samba/printers
read only = Yes

Does it look any better now?

altair4 wrote: ⤴Sat Oct 13, 2018 4:28 pm
It does … outside of the client use spnego = No entry. Is there a reason for that?

Actually, the reason for that is after following one of your previous threads…

someone else had a similar problem that apparently needed that line. I figured mine was the same. But that was before I had held my hand up and realised how far down the rabbit hole I was.

EDIT: And client max protocol = NT1 is still missing.

I could have sworn I added it. I am not on that PC now, as it is now 23:29 UK time, and I will be signing off for tonight, but I will double check it in the morning and post back to you then.

Once again altair4 Thank you for everything so far.

ALTAIR4 You are a life saver.

I have been on and commented out the line client use spnego = No so it now reads # client use spnego = No.
Also I have added in the line client max protocol = NT1.

I then did the

But NOTHING… So again I did a PC restart and YES IT WORKS!

I had run testparm -s and was going to post it here but I saved it to the wrong folder… and that one isn’t on my share list… (I’m not on that PC again )

OK so the moral of the story folks is DON’T try and follow some dodgy looking DIY web GUI… Just hold you hand up and say I F.U.B.A.R. and then come here where you should have been all along

So I’m going to mark this as solved, as sharing my Linux files to windows has never been a problem before, but I know who I’m looking up if TARA has any other ideas this time

And for anyone else who has been following this…. here it is in plain English…

using your file manager navigate to the folder /etc/samba (right click on the samba folder and open as root). Then open the file smb.conf (now with elevated privileges), and in the «GLOBAL SETTINGS» section, at the top of the file, under the line workgroup = WORKGROUP add the following lines.

Code: Select all

client max protocol = NT1
name resolve order = bcast host lmhosts wins

Also if you want to you can change the name of the workgroup but it’s not needed.
SAVE THE FILE…

In a terminal, you could then do

Code: Select all

sudo service smbd restart
sudo service nmbd restart

But I found it better to just restart the whole PC.

A Massive thank you to ALTAIR4 for his outstanding help throughout this whole thing. (P.S. I’ll post the testparm -s output in the morning just so you can see it)

And here it is the output of testparm -s

grandad@Charles:~$ testparm -s
Load smb config files from /etc/samba/smb.conf
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
WARNING: The "syslog" option is deprecated
Processing section "[printers]"
Processing section "[print$]"
Loaded services file OK.
Server role: ROLE_STANDALONE

# Global parameters
[global]
	client max protocol = NT1
	dns proxy = No
	log file = /var/log/samba/log.%m
	map to guest = Bad User
	max log size = 1000
	name resolve order = bcast host lmhosts wins
	obey pam restrictions = Yes
	pam password change = Yes
	panic action = /usr/share/samba/panic-action %d
	passwd chat = *Entersnews*spassword:* %nn *Retypesnews*spassword:* %nn *passwordsupdatedssuccessfully* .
	passwd program = /usr/bin/passwd %u
	security = USER
	server role = standalone server
	server string = %h server (Samba, Ubuntu)
	syslog = 0
	unix password sync = Yes
	usershare allow guests = Yes
	workgroup = USLOT65
	idmap config * : backend = tdb


[printers]
	browseable = No
	comment = All Printers
	create mask = 0700
	path = /var/spool/samba
	printable = Yes
	read only = Yes


[print$]
	comment = Printer Drivers
	path = /var/lib/samba/printers
	read only = Yes

Once again a MASSIVE thank you to Altair4

Now to get on with enjoying TARA and all she has to offer