I still not have fixed the smbd to fail at boot time.
smbd is working, I can connect to shares from a remote computer in the same workgroup in konsole, but I can’t see the shares using smbtree.
It started the 18th april 2016… since, in the log, nmbd was unable to run.
as I can work it is not very annoying but I WANT to know why nmb was unable to launch… as the parameters are exactly the same as those on my another 13.2 computer which is completely working with samba (smb and nmb are running ok).
I did yet some troubleshooting actions as advised in the samba.org site and different samba books I have plus documentations.
I’m stucked like never before :{
I really can’t understand what is going on but the samba version was updated and then smb4k was unusable, I uninstalled it (smb4k) on my four computers running opensuse (samba server is 12.2).
The samba version on a 13.2 desktop is running very well with exactly the same configuration (but shares are different of course) then the one which nmb could not launch (???)
Here is the output of **nmbd -i -S -d 3
Maximum core file size limits now 16777216(soft) -1(hard)
nmbd version 4.2.4-34.1-3638-SUSE-oS13.2-x86_64 started.
Copyright Andrew Tridgell and the Samba Team 1992-2014
lp_load_ex: refreshing parameters
Initialising global parameters
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
Processing section "[global]"
messaging_dgm_lockfile_create: open failed: Permission denied
messaging_dgm_init: messaging_dgm_create_lockfile failed: Permission denied
messaging_dgm_init failed: Permission denied
**What I’m supposed to do ?As the file system consistency is checked at boot time and never gave any warning or reported any errors I estimated that the file system and the access rights were correct.
I sent a mail to Andrew to ask for more informations about this issue.
My smb.conf was checked by testparm tool and passed with success (only warning concerning the length of some shares).
I can access any shares from RASALGETHI with any of the other computer in the network included the 12.2 samba server (but passing the ip address instead of netbios name) (the one nmb is dead) and any mount.cifs from RASALGETHI succeeded…
The process is launched at boot so it is launched as “root” unless the new version of samba launches the nmb.service with a service account (never heard about that), in this case how come it works in the other 13.2 computer
that launches nmb without any problem with same version of samba ???