FS#54323 - [samba] 4.5.10 issues on 4.9.30-1-lts x86_64 with w10 in workgroup mode
Attached to Project:
Arch Linux
Opened by Richard PALO (risto3) - Tuesday, 06 June 2017, 12:50 GMT
Last edited by Tobias Powalowski (tpowa) - Tuesday, 29 March 2022, 19:40 GMT
Opened by Richard PALO (risto3) - Tuesday, 06 June 2017, 12:50 GMT
Last edited by Tobias Powalowski (tpowa) - Tuesday, 29 March 2022, 19:40 GMT
|
Details
Summary and Info:
We've noticed for a couple of weeks issues with w10 laptops in accessing our samba server. # smbstatus -p Samba version 4.5.10 PID Username Group Machine Protocol Version Encryption Signing ---------------------------------------------------------------------------------------------------------------------------------------- 14624 nobody nobody 192.168.1.105 (ipv4:192.168.1.105:52807) SMB3_11 - - 15440 nobody nobody 192.168.1.103 (ipv4:192.168.1.103:51498) SMB3_11 - - 14624 nobody nobody 192.168.1.105 (ipv4:192.168.1.105:52807) SMB3_11 - - 14624 nobody nobody 192.168.1.105 (ipv4:192.168.1.105:52807) SMB3_11 - - 12396 nobody nobody 192.168.1.109 (ipv4:192.168.1.109:59825) SMB3_11 - - 12396 nobody nobody 192.168.1.109 (ipv4:192.168.1.109:59825) SMB3_11 - - 15440 nobody nobody 192.168.1.103 (ipv4:192.168.1.103:51498) SMB3_11 - - 14624 nobody nobody 192.168.1.105 (ipv4:192.168.1.105:52807) SMB3_11 - - 12396 nobody nobody 192.168.1.109 (ipv4:192.168.1.109:59825) SMB3_11 - - 12396 nobody nobody 192.168.1.109 (ipv4:192.168.1.109:59825) SMB3_11 - - 12396 nobody nobody 192.168.1.109 (ipv4:192.168.1.109:59825) SMB3_11 - - 14624 nobody nobody 192.168.1.105 (ipv4:192.168.1.105:52807) SMB3_11 - - 14624 nobody nobody 192.168.1.105 (ipv4:192.168.1.105:52807) SMB3_11 - - 14624 nobody nobody 192.168.1.105 (ipv4:192.168.1.105:52807) SMB3_11 - - 14624 xxxx users 192.168.1.105 (ipv4:192.168.1.105:52807) SMB3_11 - partial(AES-128-CMAC) 12396 nobody nobody 192.168.1.109 (ipv4:192.168.1.109:59825) SMB3_11 - - 15440 nobody nobody 192.168.1.103 (ipv4:192.168.1.103:51498) SMB3_11 - - 12396 nobody nobody 192.168.1.109 (ipv4:192.168.1.109:59825) SMB3_11 - - 15440 yyyyyy users 192.168.1.103 (ipv4:192.168.1.103:51498) SMB3_11 - partial(AES-128-CMAC) 12396 zzzzzzzz users 192.168.1.109 (ipv4:192.168.1.109:59825) SMB3_11 - partial(AES-128-CMAC) notice, for example, all users here have many 'nobody' processes. There is one w10 that isn't really up to date which connects with protoco SMB3_02 and doesn't have this problem. I have the following in smb.conf just to get this far: client ntlmv2 auth = yes ntlm auth = no lanman auth = no Now I notice very recently coredumps such as: # coredumpctl -1 info PID: 15430 (smbd) UID: 0 (root) GID: 0 (root) Signal: 6 (ABRT) Timestamp: Tue 2017-06-06 13:31:20 CEST (1h 9min ago) Command Line: /usr/bin/smbd -D Executable: /usr/bin/smbd Control Group: /system.slice/smbd.service Unit: smbd.service Slice: system.slice Boot ID: 3f4b592aaab74c3e9995576d77e652d8 Machine ID: 9cf1e58d4cf1457a8bacc25d13e969a3 Hostname: smicro Storage: /var/lib/systemd/coredump/core.smbd.0.3f4b592aaab74c3e9995576d77e652d8.15430.1496748680000000000000.lz4 Message: Process 15430 (smbd) of user 0 dumped core. Stack trace of thread 15430: #0 0x00007f801cd97670 raise (libc.so.6) #1 0x00007f801cd98d00 abort (libc.so.6) #2 0x00007f801e6d40ea dump_core (libsmbconf.so.0) #3 0x00007f801e6c58eb smb_panic_s3 (libsmbconf.so.0) #4 0x00007f8020bab91f smb_panic (libsamba-util.so.0) #5 0x00007f80207a711d update_num_read_oplocks (libsmbd-base-samba4.so) #6 0x00007f802075073f n/a (libsmbd-base-samba4.so) #7 0x00007f80207521b1 n/a (libsmbd-base-samba4.so) #8 0x00007f8020753cbc create_file_default (libsmbd-base-samba4.so) #9 0x00007f80208142d9 n/a (libsmbd-base-samba4.so) #10 0x00007f802075a657 smb_vfs_call_create_file (libsmbd-base-samba4.so) #11 0x00007f8020789418 smbd_smb2_request_process_create (libsmbd-base-samba4.so) #12 0x00007f80207807ca smbd_smb2_request_dispatch (libsmbd-base-samba4.so) #13 0x00007f802078149b n/a (libsmbd-base-samba4.so) #14 0x00007f801d1140d3 n/a (libtevent.so.0) #15 0x00007f801d1124a7 n/a (libtevent.so.0) #16 0x00007f801d10e27d _tevent_loop_once (libtevent.so.0) #17 0x00007f801d10e4ab tevent_common_loop_wait (libtevent.so.0) #18 0x00007f801d112447 n/a (libtevent.so.0) #19 0x00007f802076fbc9 smbd_process (libsmbd-base-samba4.so) #20 0x000055a6fe6f6844 n/a (smbd) #21 0x00007f801d1140d3 n/a (libtevent.so.0) #22 0x00007f801d1124a7 n/a (libtevent.so.0) #23 0x00007f801d10e27d _tevent_loop_once (libtevent.so.0) #24 0x00007f801d10e4ab tevent_common_loop_wait (libtevent.so.0) #25 0x00007f801d112447 n/a (libtevent.so.0) #26 0x000055a6fe6f35c2 main (smbd) #27 0x00007f801cd8443a __libc_start_main (libc.so.6) #28 0x000055a6fe6f376a _start (smbd) Not sure if related, though. smbd.log and nmbd.log are empty server is using ZFS: Loaded module v0.6.5.9-1, ZFS pool version 5000, ZFS filesystem version 5 Any pointers on how to debug further? |
This task depends upon
Closed by Tobias Powalowski (tpowa)
Tuesday, 29 March 2022, 19:40 GMT
Reason for closing: Won't fix
Additional comments about closing: SMB1 is not part of samba anymore
Tuesday, 29 March 2022, 19:40 GMT
Reason for closing: Won't fix
Additional comments about closing: SMB1 is not part of samba anymore
I noticed that I had no 'nobody' processes until, by chance, a new core dump was encountered.
Then all three users started having them show up.
Perhaps indeed related or aggravated by the smbd core dump after all.
the primary problem, though since two days I have noticed the coredump any longer.
and notably https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1392647
seems to get over the multiple 'nobody' accesses. Now, instead, the login protocol is NT1.