Samba/CIFS failures after 8.0.2 to 8.0.3 upgrade

[stmcknig]

Everything was working fine in 8.0.2 but after the upgrade to 8.0.3, can't seem to connect to my shares - here is the tail of the samba log, first after a "restart" by toggling the off.on switch in Freenas services, then trying to connect to the share...looks like something has gone into panic - but what and how ?

[2012/01/09 19:39:51, 0] smbd/server.c:1045(main)
smbd version 3.6.1 started.
Copyright Andrew Tridgell and the Samba Team 1992-2011
[2012/01/09 19:39:51, 1] param/loadparm.c:9666(lp_load_ex)
WARNING: The security=share option is deprecated
[2012/01/09 19:39:51.576657, 0] param/loadparm.c:8004(lp_do_parameter)
Global parameter guest account found in service section!
[2012/01/09 19:39:51.576795, 0] param/loadparm.c:8004(lp_do_parameter)
Global parameter guest account found in service section!
[2012/01/09 19:39:51.576919, 0] param/loadparm.c:8004(lp_do_parameter)
Global parameter guest account found in service section!
[2012/01/09 19:39:51.577057, 0] param/loadparm.c:8004(lp_do_parameter)
Global parameter guest account found in service section!
[2012/01/09 19:39:51.577193, 0] param/loadparm.c:8004(lp_do_parameter)
Global parameter guest account found in service section!
[2012/01/09 19:39:51.577329, 0] param/loadparm.c:8004(lp_do_parameter)
Global parameter guest account found in service section!
[2012/01/09 19:39:51.577450, 1] param/loadparm.c:9666(lp_load_ex)
WARNING: The security=share option is deprecated
[2012/01/09 19:39:51.582218, 1] smbd/files.c:204(file_init)
file_init: Information only: requested 16384 open files, 11075 are available.
[2012/01/09 19:40:35.290028, 1] smbd/process.c:456(receive_smb_talloc)
read_smb_length_return_keepalive failed for client 10.0.0.200 read error = NT_STATUS_END_OF_FILE.
[2012/01/09 19:40:35.290632, 1] smbd/process.c:456(receive_smb_talloc)
read_smb_length_return_keepalive failed for client 10.0.0.200 read error = NT_STATUS_END_OF_FILE.
[2012/01/09 19:40:38.301796, 0] lib/fault.c:51(fault_report)
===============================================================
[2012/01/09 19:40:38.301836, 0] lib/fault.c:52(fault_report)
INTERNAL ERROR: Signal 11 in pid 5507 (3.6.1)
Please read the Trouble-Shooting section of the Samba3-HOWTO
[2012/01/09 19:40:38.301852, 0] lib/fault.c:54(fault_report)

From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
[2012/01/09 19:40:38.301877, 0] lib/fault.c:55(fault_report)
===============================================================
[2012/01/09 19:40:38.301887, 0] lib/util.c:1117(smb_panic)
PANIC (pid 5507): internal error
[2012/01/09 19:40:38.301957, 0] lib/util.c:1221(log_stack_trace)
BACKTRACE: 0 stack frames:
[2012/01/09 19:40:38.302010, 0] lib/fault.c:416(dump_core)
dumping core in /var/log/samba/cores/smbd
[2012/01/09 19:40:38.302542, 1] smbd/server.c:294(remove_child_pid)
Scheduled cleanup of brl and lock database after unclean shutdown
[2012/01/09 19:40:38.305312, 0] lib/fault.c:51(fault_report)
===============================================================
[2012/01/09 19:40:38.305343, 0] lib/fault.c:52(fault_report)
INTERNAL ERROR: Signal 11 in pid 5508 (3.6.1)
Please read the Trouble-Shooting section of the Samba3-HOWTO
[2012/01/09 19:40:38.305359, 0] lib/fault.c:54(fault_report)

From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
[2012/01/09 19:40:38.305374, 0] lib/fault.c:55(fault_report)
===============================================================
[2012/01/09 19:40:38.305389, 0] lib/util.c:1117(smb_panic)
PANIC (pid 5508): internal error
[2012/01/09 19:40:38.305440, 0] lib/util.c:1221(log_stack_trace)
BACKTRACE: 0 stack frames:
[2012/01/09 19:40:38.305478, 0] lib/fault.c:416(dump_core)
dumping core in /var/log/samba/cores/smbd
[2012/01/09 19:40:58.302605, 1] smbd/server.c:266(cleanup_timeout_fn)
Cleaning up brl and lock database after unclean shutdown

I'm guessing the INTERNAL ERROR is not good....

 

[stmcknig]

Here's my smb.conf

[global]
encrypt passwords = yes
dns proxy = no
strict locking = no
read raw = yes
write raw = yes
oplocks = yes
max xmit = 65535
deadtime = 15
display charset = LOCALE
max log size = 10
syslog only = yes
syslog = yes
load printers = no
printing = bsd
printcap name = /dev/null
disable spoolss = yes
smb passwd file = /var/etc/private/smbpasswd
private dir = /var/etc/private
getwd cache = yes
guest account = BigDisk
map to guest = Bad Password
guest ok = yes
netbios name = NAS
workgroup = FREENAS
server string = FreeNAS Server
use sendfile = yes
store dos attributes = yes
local master = yes
time server = yes
security = share
force user = BigDisk
force group = BigDisk
passdb backend = tdbsam:/var/etc/private/passdb.tdb
create mask = 0666
create mask = 0666
directory mask = 0777
client ntlmv2 auth = yes
dos charset = CP437
unix charset = UTF-8
log level = 10
aio read size = 1
aio write size = 1

 

[heupink]

I had problems updating to 8.0.3 too. I reverted back to 8.0.2, and things started to work again.

 

[heupink]

While in 8.0.3: LDAP authentication still worked, getent passwd gave me all my users, and logging on via ssh worked as expected.

However, using cifs (configured with local users) since 8.0.3 I'm getting: "a device attached to the system is not functioning"

[2012/01/12 18:21:36.994887, 5] ../libcli/security/security_token.c:53(security_token_debug) Security token: (NULL)
[2012/01/12 18:21:36.994902, 5] auth/token_util.c:527(debug_unix_user_token) UNIX token of user 0 Primary group is 0 and contains 0 supplementary groups

Is what looked unusual in the logs. No internal errors or such, here.

Now I'm back on 8.0.2, and life is good again.

 

[stmcknig]

Did you have to do anything to roll back to 8.0.2 besides deploy the old firmware ? I didn't want to make things worse....

 

[heupink]

No. When you boot, it boots either F1 or F2. Just press the other one, to select the previous image. See: http://doc.freenas.org/index.php/Upgrading_FreeNAS

 

[heupink]

Are you running with ldap backend as well? Because at home (withOUT) ldap, 8.0.3 runs just fine..!

 

[stmcknig]

Thanks - F2 saved me and restored my SMB/CIFS service; I'd overlooked that new rollback capability...

No, I was not using LDAP - I found other posts and hoped that would fix it but it was never enabled....

 

[heupink]

Hmm. So it's not ldap / cifs specific.

 

[stmcknig]

No, in my case to the best of my research the problem was that the SMB/CIFS daemon kept getting kill 6 ; all other share protocols AFP and NFS seemed unaffected.

It may have been due to the samba upgrade - I did try and look outside the FreeNAS forums for a clue but didn’t come up with anything useful/relevant.

Guess I'll I wait for the .4 release....