Another broken SAMBA ... Failed to start Samba SMB Daemon [SOLVED]
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Another broken SAMBA ... Failed to start Samba SMB Daemon [SOLVED]
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
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
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 3 times in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Re: Another broken SAMBA ... Failed to start Samba SMB Daemon
Took a quick look at the Webmin Samba Howto and one issue is this:
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:
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.
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.10.) Change your security to share level then save the changes.
Side note: I would suggest that you get aquatinted with a samba diagnostic tool called testparm. You invoke it in a terminal this way:
Code: Select all
testparm -s
The "service" it has an error loading is ... well ... itself ( smbd ).WARNING: Ignoring invalid value 'share' for parameter 'security'
Error loading services.
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.
Please add a [SOLVED] at the end of your original subject header if your question has been answered and solved.
Re: Another broken SAMBA ... Failed to start Samba SMB Daemon
First things first, thank you for replying to my post altair4, and thank you for your advice so far.
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?
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 Took a quick look at the Webmin Samba Howto and one issue is this: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.10.) Change your security to share level then save the changes.
Yep you were rightaltair4 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:Code: Select all
testparm -s
The "service" it has an error loading is ... well ... itself ( smbd ).WARNING: Ignoring invalid value 'share' for parameter 'security'
Error loading services.
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 )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.
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?
Re: Another broken SAMBA ... Failed to start Samba SMB Daemon
Well, that's another issue. Linux-to-Linux samba is easy. Linux-to-Windows not so much.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?
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
Please add a [SOLVED] at the end of your original subject header if your question has been answered and solved.
Re: Another broken SAMBA ... Failed to start Samba SMB Daemon
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..
There is NO folder with MY actual workgroup. (which I have changed in the smb.conf.Unable to mount location... Failed to retrieve share list from server: Success
I did that but it hasn't made any difference.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
At this point I'm wondering if it may just be best to start from scratch and get a someone to hold my hand
Re: Another broken SAMBA ... Failed to start Samba SMB Daemon
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:
Code: Select all
testparm -s
Did you restart samba? You do that in this order:There is NO folder with MY actual workgroup. (which I have changed in the smb.conf.
Code: Select all
sudo service smbd restart
Code: Select all
sudo service nmbd restart
Please add a [SOLVED] at the end of your original subject header if your question has been answered and solved.
Re: Another broken SAMBA ... Failed to start Samba SMB Daemon
No problem output as follows...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:Code: Select all
testparm -s
Code: Select all
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 = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
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
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.In the mean time if you did this:Did you restart samba? You do that in this order:There is NO folder with MY actual workgroup. (which I have changed in the smb.conf.Code: Select all
sudo service smbd restart
Code: Select all
sudo service nmbd restart
So how are we looking?
Re: Another broken SAMBA ... Failed to start Samba SMB Daemon
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
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:
Anyhoo what I would do is edit /etc/samba/smb.conf and right below the
workgroup = USLOT65
line add these:
Code: Select all
client max protocol = NT1
name resolve order = bcast host lmhosts wins
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:
Code: Select all
nemo smb://192.168.0.100
Please add a [SOLVED] at the end of your original subject header if your question has been answered and solved.
Re: Another broken SAMBA ... Failed to start Samba SMB Daemon
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)
Done that and I get the error..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:Code: Select all
nemo smb://192.168.0.100
So... I have included here a copy of the "GLOBAL" section from my smb.conf.Could not display "smb://192.168/.../..."
error:Failed to retrieve share list from server: Invalid argument. Please select another viewer and try again.
Hope that helps too[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
Re: Another broken SAMBA ... Failed to start Samba SMB Daemon
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.
Please add a [SOLVED] at the end of your original subject header if your question has been answered and solved.
Re: Another broken SAMBA ... Failed to start Samba SMB Daemon
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
Re: Another broken SAMBA ... Failed to start Samba SMB Daemon
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.Please add a [SOLVED] at the end of your original subject header if your question has been answered and solved.
Re: Another broken SAMBA ... Failed to start Samba SMB Daemon
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
outputDoes it look any better now?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 = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
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
Re: Another broken SAMBA ... Failed to start Samba SMB Daemon
It does ... outside of the
EDIT: And
client use spnego = No
entry. Is there a reason for that?EDIT: And
client max protocol = NT1
is still missing.Please add a [SOLVED] at the end of your original subject header if your question has been answered and solved.
Re: Another broken SAMBA ... Failed to start Samba SMB Daemon
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.
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.EDIT: Andclient max protocol = NT1
is still missing.
Once again altair4 Thank you for everything so far.
Re: Another broken SAMBA ... Failed to start Samba SMB Daemon
ALTAIR4 You are a life saver.
I have been on and commented out the line
Also I have added in the line
I then did the
But NOTHING... So again I did a PC restart and YES IT WORKS!
I had run
And for anyone else who has been following this.... here it is in plain English...
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
Code: Select all
sudo service smbd restart
Code: Select all
sudo service nmbd restart
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 )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 timeOK 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
And for anyone else who has been following this.... here it is in plain English...
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)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 lineworkgroup = WORKGROUP
add the following lines.
Also if you want to you can change the name of the workgroup but it's not needed.Code: Select all
client max protocol = NT1 name resolve order = bcast host lmhosts wins
SAVE THE FILE...
In a terminal, you could then doBut I found it better to just restart the whole PC.Code: Select all
sudo service smbd restart sudo service nmbd restart
Re: Another broken SAMBA ... Failed to start Samba SMB Daemon [SOLVED]
And here it is the output of
Once again a MASSIVE thank you to Altair4
Now to get on with enjoying TARA and all she has to offer
testparm -s
Code: Select all
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 = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
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
Now to get on with enjoying TARA and all she has to offer