search for: valid_stat

...16 14:00:12 s4slave smbd[7141]: smb_panic(): calling panic action [/bin/sleep 999999999] May 16 14:00:57 s4slave smbd[7173]: [2019/05/16 14:00:57.839574, 0] ../source3/smbd/dir.c:1440(user_can_write_file) May 16 14:00:57 s4slave smbd[7173]: PANIC: assert failed at ../source3/smbd/dir.c(1440): VALID_STAT(smb_fname->st) May 16 14:00:57 s4slave smbd[7173]: [2019/05/16 14:00:57.839682, 0] ../source3/lib/util.c:789(smb_panic_s3) May 16 14:00:57 s4slave smbd[7173]: PANIC (pid 7173): assert failed: VALID_STAT(smb_fname->st) May 16 14:00:57 s4slave smbd[7173]: [2019/05/16 14:00:57.840700, 0] ../...

Dear all, since a few days I have a panic error in my logfiles on my second joined DC, Samba version 4.3.4. Can anyone help? PANIC (pid 24120): assert failed: VALID_STAT(smb_fname->st) May 16 10:01:43 s4slave smbd[24120]: [2019/05/16 10:01:43.333006, 0] ../source3/lib/util.c:900(log_stack_trace) May 16 10:01:43 s4slave smbd[24120]: BACKTRACE: 30 stack frames: May 16 10:01:43 s4slave smbd[24120]: #0 /usr/local/samba/lib/libsmbconf.so.0(log_stack_trace+0x1f)...

Hi Even when you are not opening the pipe, but just listing it in cygwin, or trying to see the properties in explorer, you will have this problem: Does anybody know how to disable named pipes in samba? Or how you can kill the connection from the client side? And no, setting "nt pipe support" to no, doesn't fix the problem. /Kaj Symptom: Samba daemon hanging when trying to open

Hello, I tried this week to upgrade my samba 3.2.4 (2 PDCs one trusting the other) to samba 3.3.0 then samba 3.3.1, and apart from the problem with winbindd and trusted domain, my users are not able to modify any ms word document (excel does the same). You can open the file correctly, modify it, and when saving it, it pops up "Access denied" If you try to save the file in the same