Hi All,
I'm really hoping one of you lovely people will be able to help me out here. I've somehow managed to mess up my samba config so much that I cannot connect to any of my shares any more
I'm a debian and Samba noob so you'll have to bear with me here.....
I started following this post to join OMV to my Windows AD domain: http://phpbb.openmediavault.org/viewtopic.php?f=3&t=1493
So, successfully configured Kerberos, winbind and ldap (with the plugin) etc and managed to join my domain with no problems.
Once I'd joined I suddenly realised I could no longer connect to any of the shares which were working fine previously.
I had saved all of my smb config before I started so reverted all of my changes thinking I'd somehow gone wrong joining the windows domain...... Still can't connect.
The problem I have is that sometimes (not all of the time) smbd just refuses to start and when I try to get the status I get the following:
root@NAS01:~# /etc/init.d/samba restart
Stopping Samba daemons: nmbd smbd.
Starting Samba daemons: nmbd smbd.
root@NAS01:~# /etc/init.d/samba status
nmbd is running.
could not access PID file for smbd ... failed!
A search for the PID file sometimes returns one, sometime not.
When I run a testparm I get the following:
root@NAS01:/var/log/samba# testparm
Load smb config files from /etc/samba/smb.conf
rlimit_max: rlimit_max (1024) below minimum Windows limit (16384)
Processing section "[Acronis_Vault]"
Processing section "[KEVTEST]"
Processing section "[Backup]"
Processing section "[homes]"
Loaded services file OK.
WARNING: You have some share names that are longer than 12 characters.
These may not be accessible to some older clients.
(Eg. Windows9x, WindowsMe, and smbclient prior to Samba 3.0.)
Server role: ROLE_STANDALONE
Alles anzeigen
After a quick google I still don't know how to fix the rlimit_max issue, is this likely to be my problem?
The weird thing is that sometimes Smbd just won't be running at all and there is nothing in either the log.nmbd or the log.smbd files even though debug is maxed out.
When I do get the smbd running I get 2 instances:
root@NAS01:~# ps ax | grep mbd
1299 ? Ss 0:00 /usr/sbin/nmbd -D
1330 ? Ss 0:00 /usr/sbin/smbd -D
1347 ? S 0:00 /usr/sbin/smbd -D
5876 pts/0 S+ 0:00 grep mbd
Here is my current smb.conf file (written by the gui):
#======================= Global Settings =======================
[global]
workgroup = DOMAIN
server string = NAS01
include = /etc/samba/dhcp.conf
dns proxy = no
log level = 10
syslog = 10
log file = /var/log/samba/log.%m
max log size = 1000
syslog only = yes
panic action = /usr/share/samba/panic-action %d
encrypt passwords = true
passdb backend = tdbsam
obey pam restrictions = yes
unix password sync = no
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
pam password change = yes
socket options = TCP_NODELAY IPTOS_LOWDELAY
guest account = nobody
load printers = no
disable spoolss = yes
printing = bsd
printcap name = /dev/null
unix extensions = yes
wide links = no
create mask = 0777
directory mask = 0777
map to guest = Bad User
use sendfile = yes
aio read size = 16384
aio write size = 16384
null passwords = yes
local master = yes
time server = no
wins support = no
#======================= Share Definitions =======================
[KEVTEST]
comment = exchange 2k3 files
path = /media/7f7729c2-4c05-41d3-a535-9bac4e2a6393/Kev/
guest ok = yes
read only = no
browseable = yes
inherit acls = yes
inherit permissions = no
ea support = no
store dos attributes = no
printable = no
create mask = 0755
force create mode = 0644
directory mask = 0755
force directory mode = 0755
hide dot files = yes
invalid users =
read list =
[Backup]
path = /media/7f7729c2-4c05-41d3-a535-9bac4e2a6393/Backup/
guest ok = yes
read only = no
browseable = yes
inherit acls = no
inherit permissions = no
ea support = no
store dos attributes = no
printable = no
create mask = 0755
Alles anzeigen
As far as I can see my config is OK.
Any suggestions will be greatly appreciated.
Cheers,
Kev