unTECH Posted July 6, 2023 Share Posted July 6, 2023 I'm trying to copy files to a share, and getting the following in my syslog: Quote Jul 6 10:52:03 Discovery smbd[4717]: [2023/07/06 10:52:03.610872, 0] ../../source3/modules/vfs_default.c:3554(vfswrap_sys_acl_set_fd) Jul 6 10:52:03 Discovery smbd[4717]: PANIC: assert failed at ../../source3/modules/vfs_default.c(3554): !fsp_is_alternate_stream(fsp) Jul 6 10:52:03 Discovery smbd[4717]: [2023/07/06 10:52:03.610898, 0] ../../lib/util/fault.c:173(smb_panic_log) Jul 6 10:52:03 Discovery smbd[4717]: =============================================================== Jul 6 10:52:03 Discovery smbd[4717]: [2023/07/06 10:52:03.610910, 0] ../../lib/util/fault.c:174(smb_panic_log) Jul 6 10:52:03 Discovery smbd[4717]: INTERNAL ERROR: assert failed: !fsp_is_alternate_stream(fsp) in pid 4717 (4.17.7) Jul 6 10:52:03 Discovery smbd[4717]: [2023/07/06 10:52:03.610919, 0] ../../lib/util/fault.c:178(smb_panic_log) Jul 6 10:52:03 Discovery smbd[4717]: If you are running a recent Samba version, and if you think this problem is not yet fixed in the latest versions, please consider reporting this bug, see https://wiki.samba.org/index.php/Bug_Reporting Jul 6 10:52:03 Discovery smbd[4717]: [2023/07/06 10:52:03.610928, 0] ../../lib/util/fault.c:183(smb_panic_log) Jul 6 10:52:03 Discovery smbd[4717]: =============================================================== Jul 6 10:52:03 Discovery smbd[4717]: [2023/07/06 10:52:03.610936, 0] ../../lib/util/fault.c:184(smb_panic_log) Jul 6 10:52:03 Discovery smbd[4717]: PANIC (pid 4717): assert failed: !fsp_is_alternate_stream(fsp) in 4.17.7 Jul 6 10:52:03 Discovery smbd[4717]: [2023/07/06 10:52:03.611201, 0] ../../lib/util/fault.c:292(log_stack_trace) Jul 6 10:52:03 Discovery smbd[4717]: BACKTRACE: 30 stack frames: Jul 6 10:52:03 Discovery smbd[4717]: #0 /usr/lib64/libgenrand-samba4.so(log_stack_trace+0x2e) [0x14d51239964e] Jul 6 10:52:03 Discovery smbd[4717]: #1 /usr/lib64/libgenrand-samba4.so(smb_panic+0x9) [0x14d5123998a9] Jul 6 10:52:03 Discovery smbd[4717]: #2 /usr/lib64/libsmbd-base-samba4.so(+0x573aa) [0x14d5127853aa] Jul 6 10:52:03 Discovery smbd[4717]: #3 /usr/lib64/vfs/catia.so(+0x56a1) [0x14d50db806a1] Jul 6 10:52:03 Discovery smbd[4717]: #4 /usr/lib64/libsmbd-base-samba4.so(inherit_access_posix_acl+0x21a) [0x14d5127ccdaa] Jul 6 10:52:03 Discovery smbd[4717]: #5 /usr/lib64/libsmbd-base-samba4.so(+0x85991) [0x14d5127b3991] Jul 6 10:52:03 Discovery smbd[4717]: #6 /usr/lib64/libsmbd-base-samba4.so(+0x87cd6) [0x14d5127b5cd6] Jul 6 10:52:03 Discovery smbd[4717]: #7 /usr/lib64/libsmbd-base-samba4.so(create_file_default+0x326) [0x14d5127b7e36] Jul 6 10:52:03 Discovery smbd[4717]: #8 /usr/lib64/vfs/fruit.so(+0xf529) [0x14d50db97529] Jul 6 10:52:03 Discovery smbd[4717]: #9 /usr/lib64/libsmbd-base-samba4.so(smbd_smb2_request_process_create+0xd9a) [0x14d5127ecd9a] Jul 6 10:52:03 Discovery smbd[4717]: #10 /usr/lib64/libsmbd-base-samba4.so(smbd_smb2_request_dispatch+0xe07) [0x14d5127e2b17] Jul 6 10:52:03 Discovery smbd[4717]: #11 /usr/lib64/libsmbd-base-samba4.so(+0xb5ad1) [0x14d5127e3ad1] Jul 6 10:52:03 Discovery smbd[4717]: #12 /usr/lib64/libtevent.so.0(tevent_common_invoke_fd_handler+0x91) [0x14d51235b8c1] Jul 6 10:52:03 Discovery smbd[4717]: #13 /usr/lib64/libtevent.so.0(+0xee07) [0x14d512361e07] Jul 6 10:52:03 Discovery smbd[4717]: #14 /usr/lib64/libtevent.so.0(+0xcef7) [0x14d51235fef7] Jul 6 10:52:03 Discovery smbd[4717]: #15 /usr/lib64/libtevent.so.0(_tevent_loop_once+0x91) [0x14d51235aba1] Jul 6 10:52:03 Discovery smbd[4717]: #16 /usr/lib64/libtevent.so.0(tevent_common_loop_wait+0x1b) [0x14d51235ae7b] Jul 6 10:52:03 Discovery smbd[4717]: #17 /usr/lib64/libtevent.so.0(+0xce97) [0x14d51235fe97] Jul 6 10:52:03 Discovery smbd[4717]: #18 /usr/lib64/libsmbd-base-samba4.so(smbd_process+0x817) [0x14d5127d1a37] Jul 6 10:52:03 Discovery smbd[4717]: #19 /usr/sbin/smbd(+0xb090) [0x55797aa92090] Jul 6 10:52:03 Discovery smbd[4717]: #20 /usr/lib64/libtevent.so.0(tevent_common_invoke_fd_handler+0x91) [0x14d51235b8c1] Jul 6 10:52:03 Discovery smbd[4717]: #21 /usr/lib64/libtevent.so.0(+0xee07) [0x14d512361e07] Jul 6 10:52:03 Discovery smbd[4717]: #22 /usr/lib64/libtevent.so.0(+0xcef7) [0x14d51235fef7] Jul 6 10:52:03 Discovery smbd[4717]: #23 /usr/lib64/libtevent.so.0(_tevent_loop_once+0x91) [0x14d51235aba1] Jul 6 10:52:03 Discovery smbd[4717]: #24 /usr/lib64/libtevent.so.0(tevent_common_loop_wait+0x1b) [0x14d51235ae7b] Jul 6 10:52:03 Discovery smbd[4717]: #25 /usr/lib64/libtevent.so.0(+0xce97) [0x14d51235fe97] Jul 6 10:52:03 Discovery smbd[4717]: #26 /usr/sbin/smbd(main+0x1489) [0x55797aa8f259] Jul 6 10:52:03 Discovery smbd[4717]: #27 /lib64/libc.so.6(+0x236b7) [0x14d5121636b7] Jul 6 10:52:03 Discovery smbd[4717]: #28 /lib64/libc.so.6(__libc_start_main+0x85) [0x14d512163775] Jul 6 10:52:03 Discovery smbd[4717]: #29 /usr/sbin/smbd(_start+0x21) [0x55797aa8fb31] Jul 6 10:52:03 Discovery smbd[4717]: [2023/07/06 10:52:03.611330, 0] ../../source3/lib/dumpcore.c:315(dump_core) Jul 6 10:52:03 Discovery smbd[4717]: dumping core in /var/log/samba/cores/smbd Jul 6 10:52:03 Discovery smbd[4717]: I was able to copy some files fine, and then this started happening. Is this a Samba bug, or something else? Quote Link to comment
JorgeB Posted July 6, 2023 Share Posted July 6, 2023 Is that a specific file that causes that? i.e., if you reboot and copy a different file does it work? Quote Link to comment
unTECH Posted July 6, 2023 Author Share Posted July 6, 2023 22 minutes ago, JorgeB said: Is that a specific file that causes that? i.e., if you reboot and copy a different file does it work? It seems to be all files at this point, at least from a particular machine. Tried rebooting and a different file, same result. Quote Link to comment
JorgeB Posted July 6, 2023 Share Posted July 6, 2023 And from other machine works? Quote Link to comment
unTECH Posted July 7, 2023 Author Share Posted July 7, 2023 Just tried from another machine; a single file will transfer fine, but when it's multiple files, I get it again. Windows copy stops with "An unexpected error occurred". Quote Link to comment
JorgeB Posted July 7, 2023 Share Posted July 7, 2023 Don't know of any similar issues, please post the diagnostics. Quote Link to comment
unTECH Posted July 7, 2023 Author Share Posted July 7, 2023 discovery-diagnostics-20230707-0946.zipHere you go Quote Link to comment
JorgeB Posted July 7, 2023 Share Posted July 7, 2023 I see you're using AD, cannot really help with that, maybe @dlandoncan. Quote Link to comment
dlandon Posted July 7, 2023 Share Posted July 7, 2023 Several suggestions: Disable Multi-channel and see if it makes a difference. I'm not sure it will work with your network configuration. Your network configuration may be an issue. You have two bonds (bond1, and bond2) each with a single NIC, but you've set the backup mode (1). Backup mode won't work with a single NIC. Since you are using AD, I suggest you install this plugin and switch to the 'tdb' database. The 'hash' database is deprecated and has been known to have issues. Caution: You will have to redo all your permissions when you reset the database. I also notice all your shares are set public. Even though you have many set as hidden, it's not really a good idea to share everything as public for security reasons. Why use AD with no permissions being set on any shares? 1 Quote Link to comment
unTECH Posted July 7, 2023 Author Share Posted July 7, 2023 - Disabled Multi-channel; no difference - Fixed network config - disabled bonding - installed the AD Extras plugin and switched to tdb Unfortunately, same results after these changes. Not sure why it's showing all shares set to public for you -- I double checked, and many of my shares are set to private as well as hidden. Only a handful of shares are public. Quote Link to comment
dlandon Posted July 7, 2023 Share Posted July 7, 2023 11 minutes ago, unTECH said: - Disabled Multi-channel; no difference - Fixed network config - disabled bonding - installed the AD Extras plugin and switched to tdb Unfortunately, same results after these changes. Not sure why it's showing all shares set to public for you -- I double checked, and many of my shares are set to private as well as hidden. Only a handful of shares are public. I'm not an expert at AD and the testparm output I looked at did not show any valid users. I think that's how AD works. Please post new diagnostics so I can have another look. Quote Link to comment
unTECH Posted July 7, 2023 Author Share Posted July 7, 2023 6 minutes ago, dlandon said: I'm not an expert at AD and the testparm output I looked at did not show any valid users. I think that's how AD works. Please post new diagnostics so I can have another look. Only user on the tower should be root, right? That was my understanding as well. Here's the fresh diags discovery-diagnostics-20230707-1143.zip Quote Link to comment
dlandon Posted July 7, 2023 Share Posted July 7, 2023 Is your date and time set properly on Unraid? Quote Link to comment
unTECH Posted July 7, 2023 Author Share Posted July 7, 2023 Just now, dlandon said: Is your date and time set properly on Unraid? Just double checked, and yes, it is. Quote Link to comment
dlandon Posted July 7, 2023 Share Posted July 7, 2023 4 minutes ago, unTECH said: Just double checked, and yes, it is. I was searching the Internet for the errors showing in your log and this was just an off the wall shot. A few more things to try: Try the following commands 'net cache flush' and then '/etc/rc.d/rc.samba restart'. Turn off NetBIOS. You don't need it. Turn off macOS interroperability. Turn off mover logging. It's flooding the log with discovery messages. Quote Link to comment
unTECH Posted July 7, 2023 Author Share Posted July 7, 2023 33 minutes ago, dlandon said: I was searching the Internet for the errors showing in your log and this was just an off the wall shot. A few more things to try: Try the following commands 'net cache flush' and then '/etc/rc.d/rc.samba restart'. Turn off NetBIOS. You don't need it. Turn off macOS interroperability. Turn off mover logging. It's flooding the log with discovery messages. Alright, tried all that... Now I'm getting a permissions error. I'd checked before and everything looked fine -- now shares are showing a Unix user as the owner, and it gives me a "permission denied" when I try to change the owner or permissions. Quote Link to comment
dlandon Posted July 7, 2023 Share Posted July 7, 2023 I suspect the net cache flush is what did it after you changed the backend database to tdb. Maybe remove users and re-add them? I guess that the good news is we made things change. Do you still see the SMB panics in the log? Quote Link to comment
unTECH Posted July 7, 2023 Author Share Posted July 7, 2023 1 minute ago, dlandon said: I suspect the net cache flush is what did it after you changed the backend database to tdb. Maybe remove users and re-add them? I guess that the good news is we made things change. Do you still see the SMB panics in the log? I'm not able to remove or add users right now; I'm just told "access denied" when trying to make changes. Not seeing the SMB panics because I can't copy anything due to permissions Quote Link to comment
unTECH Posted July 7, 2023 Author Share Posted July 7, 2023 Rebooted, slightly different error: "This security ID may not be assigned as the owner of this object." -- when trying to change it from "3002 (Unix User\3002)". Quote Link to comment
unTECH Posted July 7, 2023 Author Share Posted July 7, 2023 Ah, wait -- tried copying, it seems to be going now! Altho I have a different error -- "Jul 7 14:52:33 Discovery winbindd[2618]: [2023/07/07 14:52:33.681475, 0] ../../source3/winbindd/winbindd_cache.c:3464(set_global_winbindd_state_offline) Jul 7 14:52:33 Discovery winbindd[2618]: set_global_winbindd_state_offline: Offline requested" flooding the log Quote Link to comment
dlandon Posted July 7, 2023 Share Posted July 7, 2023 7 minutes ago, unTECH said: Ah, wait -- tried copying, it seems to be going now! Altho I have a different error -- "Jul 7 14:52:33 Discovery winbindd[2618]: [2023/07/07 14:52:33.681475, 0] ../../source3/winbindd/winbindd_cache.c:3464(set_global_winbindd_state_offline) Jul 7 14:52:33 Discovery winbindd[2618]: set_global_winbindd_state_offline: Offline requested" flooding the log I saw those in the previous logs. I can't find anything about those errors on the net. Quote Link to comment
unTECH Posted July 7, 2023 Author Share Posted July 7, 2023 7 minutes ago, dlandon said: I saw those in the previous logs. I can't find anything about those errors on the net. I can't find anything either. Well, at least things seem to be working properly aside from that, so thanks for the help with the main issue! Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.