Samba正在以某种方式工作,但是有些进程崩溃了。只有当一些(或一个) Windows客户端访问GPO推出的网络磁盘时,才会出现这样的接缝。至少有一个w7客户端无法通过网络磁盘访问服务器。当用户尝试smb进程时,/var/log/samba/log.smbd中的以下ocoure崩溃:
[2014/03/10 14:16:47.897568, 0] lib/fault.c:47(fault_report)
===============================================================
[2014/03/10 14:16:47.897702, 0] lib/fault.c:48(fault_report)
INTERNAL ERROR: Signal 11 in pid 9410 (3.6.17-cdc-4.5.6-302)
Please read the Trouble-Shooting section of the Samba3-HOWTO
[2014/03/10 14:16:47.897831, 0] lib/fault.c:50(fault_report)
From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
[2014/03/10 14:16:47.897918, 0] lib/fault.c:51(fault_report)
===============================================================
[2014/03/10 14:16:47.897978, 0] lib/util.c:1117(smb_panic)
PANIC (pid 9410): internal error
[2014/03/10 14:16:47.902326, 0] lib/util.c:1221(log_stack_trace)
BACKTRACE: 21 stack frames:
#0 /opt/centrify/samba/sbin/smbd(log_stack_trace+0x1c) [0x7fd7f834ee8c]
#1 /opt/centrify/samba/sbin/smbd(smb_panic+0x2b) [0x7fd7f834ef5b]
#2 /opt/centrify/samba/sbin/smbd(+0x40af40) [0x7fd7f833ff40]
#3 /lib/x86_64-linux-gnu/libc.so.6(+0x364a0) [0x7fd7f4d764a0]
#4 /lib/x86_64-linux-gnu/libc.so.6(cfree+0x1c) [0x7fd7f4dc359c]
#5 /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2(+0xcf80) [0x7fd7f2a9cf80]
#6 /lib64/ld-linux-x86-64.so.2(+0xf90e) [0x7fd7f7d1f90e]
#7 /lib/x86_64-linux-gnu/libc.so.6(+0x3b901) [0x7fd7f4d7b901]
#8 /lib/x86_64-linux-gnu/libc.so.6(+0x3b985) [0x7fd7f4d7b985]
#9 /opt/centrify/samba/sbin/smbd(+0x675a99) [0x7fd7f85aaa99]
#10 /opt/centrify/samba/sbin/smbd(+0x675bbe) [0x7fd7f85aabbe]
#11 /opt/centrify/samba/sbin/smbd(+0x18936a) [0x7fd7f80be36a]
#12 /opt/centrify/samba/sbin/smbd(run_events_poll+0x320) [0x7fd7f835d2a0]
#13 /opt/centrify/samba/sbin/smbd(smbd_process+0x8ab) [0x7fd7f80bce5b]
#14 /opt/centrify/samba/sbin/smbd(+0x6740a1) [0x7fd7f85a90a1]
#15 /opt/centrify/samba/sbin/smbd(run_events_poll+0x320) [0x7fd7f835d2a0]
#16 /opt/centrify/samba/sbin/smbd(+0x428709) [0x7fd7f835d709]
#17 /opt/centrify/samba/lib/libtevent.so.0(_tevent_loop_once+0x90) [0x7fd7f5737120]
#18 /opt/centrify/samba/sbin/smbd(main+0x12df) [0x7fd7f85aa6bf]
#19 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed) [0x7fd7f4d6176d]
#20 /opt/centrify/samba/sbin/smbd(+0x1085c9) [0x7fd7f803d5c9]
[2014/03/10 14:16:47.902958, 0] lib/fault.c:345(dump_core)
Exiting on internal error (core file administratively disabled)我对DNS有点怀疑,因为windows客户端不能通过dns名称访问samba (但是服务器响应例如。在dns名称上进行ping操作,对于带有dns的mac客户端来说,nettatalk工作得很好。我已经将gpo更改为使用IP从samba服务器挂载网络驱动器,而不是dns,它对大多数客户端都很好。我已经卸载了使samba崩溃的客户机上的所有驱动器,并在/force客户机上运行gpupdate it.The从AD2008R2服务器获得IP,并且我检查了客户机上的DNS是正确的。
注意:域名是"opusark.local“。我收到了一个警告,当安装centrify关于结束“本地”是不擅长的,应该被避免。这有什么关系吗?
有关于如何排除此错误的线索吗?
OS: Ubuntu 12.04 6位Centrify: centrify- Samba -4.5.6-deb5-x86_64.tgz samba版本(centrify使用):# /opt/centrify/samba/sbin/smbd -版本3.6.17-cdc-4.5.6-302
用centrify使能的ssh登录到服务器的速度很慢,并不是所有的计算机都能工作。
全局in /etc/samba/smb.conf:
[global]
security = ADS
realm = OPUSARK.LOCAL
workgroup = OPUSARK
netbios name = sinan
auth methods = guest, sam, winbind, ntdomain
machine password timeout = 0
passdb backend = tdbsam:/etc/samba/private/passdb.tdb
kerberos method = secrets and keytab
client use spnego principal = true
send spnego principal = Yes
server signing = auto
client ntlmv2 auth = yes
client use spnego = yes
template shell = /bin/bash
winbind use default domain = Yes
winbind enum users = No
winbind enum groups = No
winbind nested groups = Yes
idmap cache time = 0
ignore syssetgroups error = No
idmap config * : backend = tdb
idmap config * : range = 1000 - 200000000
idmap config * : base_tdb = 0
enable core files = false
syslog = 0发布于 2014-03-14 09:24:59
坠机报告已经停止了。这可能是因为当客户端试图通过dns名称访问它们时,smbd进程崩溃了(由于某种原因,这不起作用)。
https://serverfault.com/questions/581035
复制相似问题