Greetings,
I've got a samba server that has been serving a 100+ user network for over
a year with no issues, except recently, one XP workstation throws a
sharing violation when saving Excel files, but only intermittently.
It's an older Samba version (3.0.29) - and yes, I know I have to upgrade.
OS is Fedora 9 x64.
The log shows the following when this occurs:
[2009/12/18 09:42:25, 0] lib/util_sec.c:assert_uid(101)
Failed to set uid privileges to (1075,1075) now set to (0,0)
[2009/12/18 09:42:25, 0] lib/util.c:smb_panic(1633)
PANIC (pid 20846): failed to set uid
[2009/12/18 09:42:25, 0] lib/util.c:log_stack_trace(1737)
BACKTRACE: 16 stack frames:
#0 /usr/local/samba/sbin/smbd(log_stack_trace+0x1c) [0x7fa0a799e2a5]
#1 /usr/local/samba/sbin/smbd(smb_panic+0x55) [0x7fa0a799e3a7]
#2 /usr/local/samba/sbin/smbd [0x7fa0a79a2f65]
#3 /usr/local/samba/sbin/smbd(restore_re_uid_fromroot+0x2b)
[0x7fa0a79a2fce]
#4 /usr/local/samba/sbin/smbd [0x7fa0a79a5950]
#5 /usr/local/samba/sbin/smbd [0x7fa0a79a5d57]
#6 /usr/local/samba/sbin/smbd(messaging_send+0x23) [0x7fa0a79a6093]
#7 /usr/local/samba/sbin/smbd(notify_trigger+0x307) [0x7fa0a79d2d75]
#8 /usr/local/samba/sbin/smbd(notify_fname+0x96) [0x7fa0a79d10c8]
#9 /usr/local/samba/sbin/smbd(rename_internals+0x94a) [0x7fa0a782a926]
#10 /usr/local/samba/sbin/smbd(reply_mv+0x2b8) [0x7fa0a7832058]
#11 /usr/local/samba/sbin/smbd [0x7fa0a78639f1]
#12 /usr/local/samba/sbin/smbd(smbd_process+0x392) [0x7fa0a78644df]
#13 /usr/local/samba/sbin/smbd(main+0xa6b) [0x7fa0a7a4ec3d]
#14 /lib64/libc.so.6(__libc_start_main+0xfa) [0x20ea32a]
#15 /usr/local/samba/sbin/smbd [0x7fa0a77f7669]
[2009/12/18 09:42:25, 0] lib/fault.c:dump_core(181)
dumping core in /usr/local/samba/var/cores/smbd
[2009/12/18 09:42:25, 1] smbd/service.c:make_connection_snum(1033)
wks0000 (123.456.789.10) connect to service DATA initially as user
myuser (uid=1075, gid=1000) (pid 21329)
Note above, the error starts when trying to chown the file to uid.gid
1075.1075 - that UID is valid and is the user's UID, but that GID does not
exist. In the last few lines, it reconnects as UID 1075 (again, valid)
and GID 1000 (That *is* the correct GID). Although it says it's dumping
core, it doesn't.
On that share, the GID is forced (config excerpt):
[DATA]
path = /DATA
public = yes
writable = yes
printable = no
write list = @samba
create mask = 0660
force create mode = 0660
security mask = 0660
force security mode = 0660
directory mask = 0770
force directory mode = 0770
directory security mask = 0770
force directory security mode = 0770
force group = samba
nt acl support = no
The samba group is GID 1000, as above.
Any ideas?
TIA
-John
