December 31, 20169 yr Since yesterday that I cannot access anymore my machine. I suspect it was some package that I added to the system that might have broken something In my Shield TV I get no WORKGROUP when I browse using SMB and if I try to access the existing share it says "Connection Lost". On my Windows 10 Box it's constantly asking for permissions. Added log level = 3 and enabled log per client IP. It appears that smb daemon is seg faulting. Example: =============================================================== [2016/12/31 10:54:49.366745, 0] ../lib/util/fault.c:79(fault_report) INTERNAL ERROR: Signal 11 in pid 1262 (4.5.1) Please read the Trouble-Shooting section of the Samba HOWTO [2016/12/31 10:54:49.366753, 0] ../lib/util/fault.c:81(fault_report) =============================================================== [2016/12/31 10:54:49.366758, 0] ../source3/lib/util.c:791(smb_panic_s3) PANIC (pid 1262): internal error [2016/12/31 10:54:49.367126, 0] ../source3/lib/util.c:902(log_stack_trace) BACKTRACE: 7 stack frames: #0 /usr/lib64/libsmbconf.so.0(log_stack_trace+0x1a) [0x2b17cc752aea] #1 /usr/lib64/libsmbconf.so.0(smb_panic_s3+0x20) [0x2b17cc752bc0] #2 /usr/lib64/libsamba-util.so.0(smb_panic+0x2f) [0x2b17c9e18aff] #3 /usr/lib64/libsamba-util.so.0(+0x1bd06) [0x2b17c9e18d06] #4 /lib64/libpthread.so.0(+0x115b0) [0x2b17c9bf05b0] #5 /lib64/libc.so.6(+0x21a0d) [0x2b17cdb3aa0d] #6 [0x55e6a8b42ac0] [2016/12/31 10:54:49.367158, 0] ../source3/lib/dumpcore.c:303(dump_core) dumping core in /var/log/samba/cores/smbd Diagnostics and Samba logs in attach. Any help? Thanks! EDIT: I enabled NFS to supress the need to direct media access for the moment. And Plex for Kodi helps with additional magic littlemamba-diagnostics-20161231-1058.zip samba_logs.zip
January 1, 20179 yr Author Solved It was for sure an issue with my Windows 10 presenting itself as a Master Browser... Today tried again and magically worked... Happy New Year!!!
February 1, 20179 yr Sorry to dig up an old thread, but having the exact same issue, minus the Windows 10 machine. unRAID 6.2.4 One day SMB stopped working, digging in deeper and I get the same core. my smb.conf checks out with testparam If I try local: #smbclient -L //Aleph Enter root's password: protocol negotiation failed: NT_STATUS_CONNECTION_DISCONNECTED logs show: Connection allowed from ipv4:127.0.0.1:60424 to ipv4:127.0.0.1:445 lp_file_list_changed() file /etc/samba/smb.conf -> /etc/samba/smb.conf last mod_time: Wed Feb 1 14:42:53 2017 init_oplocks: initializing messages. switch message SMBnegprot (pid 20620) conn 0x0 setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0 Security token: (NULL) UNIX token of user 0 Primary group is 0 and contains 0 supplementary groups change_to_root_user: now uid=(0,0) gid=(0,0) =============================================================== INTERNAL ERROR: Signal 11 in pid 20620 (4.4.5) Please read the Trouble-Shooting section of the Samba HOWTO =============================================================== PANIC (pid 20620): internal error BACKTRACE: 7 stack frames: #0 /usr/lib64/libsmbconf.so.0(log_stack_trace+0x1a) [0x2b04cf4cef2a] #1 /usr/lib64/libsmbconf.so.0(smb_panic_s3+0x20) [0x2b04cf4cf000] #2 /usr/lib64/libsamba-util.so.0(smb_panic+0x2f) [0x2b04ccb9957f] #3 /usr/lib64/libsamba-util.so.0(+0x1b786) [0x2b04ccb99786] #4 /lib64/libpthread.so.0(+0x113b0) [0x2b04cc9723b0] #5 /lib64/libc.so.6(+0x21e6d) [0x2b04d08b4e6d] #6 [0x55a32f4c4df0] dumping core in /var/log/samba/cores/smbd push_sec_ctx(0, 0) : sec_ctx_stack_ndx = 1 push_conn_ctx(0) : conn_ctx_stack_ndx = 0 setting sec ctx (0, 0) - sec_ctx_stack_ndx = 1 Security token: (NULL) UNIX token of user 0 Primary group is 0 and contains 0 supplementary groups messaging_dgm_send: Sending message to 29228 pop_sec_ctx (0, 0) - sec_ctx_stack_ndx = 0 messaging_send_iov returned NT_STATUS_OK ../source3/smbd/server.c:607 Unclean shutdown of pid 20620 Scheduled cleanup of brl and lock database after unclean shutdown messaging_recv_cb: Received message 0x314 len 5 (num_fds:0) from 29226 smbd_cleanupd_process_exited: 20620 exited unclean messaging_dgm_cleanup: Cleaning up : Success
February 1, 20179 yr Sorry to dig up an old thread, but having the exact same issue, minus the Windows 10 machine. One day SMB stopped working, digging in deeper and I get the same core. my smb.conf checks out with testparam If I try local: #smbclient -L //Aleph Enter root's password: protocol negotiation failed: NT_STATUS_CONNECTION_DISCONNECTED logs show: Connection allowed from ipv4:127.0.0.1:60424 to ipv4:127.0.0.1:445 lp_file_list_changed() file /etc/samba/smb.conf -> /etc/samba/smb.conf last mod_time: Wed Feb 1 14:42:53 2017 init_oplocks: initializing messages. switch message SMBnegprot (pid 20620) conn 0x0 setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0 Security token: (NULL) UNIX token of user 0 Primary group is 0 and contains 0 supplementary groups change_to_root_user: now uid=(0,0) gid=(0,0) =============================================================== INTERNAL ERROR: Signal 11 in pid 20620 (4.4.5) Please read the Trouble-Shooting section of the Samba HOWTO =============================================================== PANIC (pid 20620): internal error BACKTRACE: 7 stack frames: #0 /usr/lib64/libsmbconf.so.0(log_stack_trace+0x1a) [0x2b04cf4cef2a] #1 /usr/lib64/libsmbconf.so.0(smb_panic_s3+0x20) [0x2b04cf4cf000] #2 /usr/lib64/libsamba-util.so.0(smb_panic+0x2f) [0x2b04ccb9957f] #3 /usr/lib64/libsamba-util.so.0(+0x1b786) [0x2b04ccb99786] #4 /lib64/libpthread.so.0(+0x113b0) [0x2b04cc9723b0] #5 /lib64/libc.so.6(+0x21e6d) [0x2b04d08b4e6d] #6 [0x55a32f4c4df0] dumping core in /var/log/samba/cores/smbd push_sec_ctx(0, 0) : sec_ctx_stack_ndx = 1 push_conn_ctx(0) : conn_ctx_stack_ndx = 0 setting sec ctx (0, 0) - sec_ctx_stack_ndx = 1 Security token: (NULL) UNIX token of user 0 Primary group is 0 and contains 0 supplementary groups messaging_dgm_send: Sending message to 29228 pop_sec_ctx (0, 0) - sec_ctx_stack_ndx = 0 messaging_send_iov returned NT_STATUS_OK ../source3/smbd/server.c:607 Unclean shutdown of pid 20620 Scheduled cleanup of brl and lock database after unclean shutdown messaging_recv_cb: Received message 0x314 len 5 (num_fds:0) from 29226 smbd_cleanupd_process_exited: 20620 exited unclean messaging_dgm_cleanup: Cleaning up : Success Tools/Diagnostics - post your diags. Are you doing anything non-stock with Samba on your server?
February 1, 20179 yr Haven't messed with the stock samba. it's as is for 6.2.4. The issue persists though restarts. I've turned off all my docker containers just for good measure. I've tried to minimize the numbers of shares I have and test by minimizing my config. I've been stopping the samba services and running smbd-20170201-1733.txt nmbd-20170201-1733.txt smb.conf-test.txt
February 1, 20179 yr Haven't messed with the stock samba. it's as is for 6.2.4. The issue persists though restarts. I've turned off all my docker containers just for good measure. I've tried to minimize the numbers of shares I have and test by minimizing my config. I've been stopping the samba services and running Need to see diagnostics.zip
February 1, 20179 yr sorry, here you go. -- attachment deleted -- Edited February 22, 20179 yr by JPNYC81
Archived
This topic is now archived and is closed to further replies.