samba - May 2019 - Error smb_panic(): calling panic action [/bin/sleep 999999999]

No I can not upgrade now it is a working system with x users.
The master dc with the same config is working without any issues.
So when I upgrade I must do the uprgade on both replicating samba server and the
samba fileservers?
No hint form e to repair:


May 16 14:00:12 s4slave smbd[7141]: [2019/05/16 14:00:12.438121,  0]
../source3/lib/util.c:801(smb_panic_s3)
May 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]
../source3/lib/util.c:900(log_stack_trace)
May 16 14:00:57 s4slave smbd[7173]:   BACKTRACE: 30 stack frames:
May 16 14:00:57 s4slave smbd[7173]:    #0
/usr/local/samba/lib/libsmbconf.so.0(log_stack_trace+0x1f) [0x7fb492c9c65a]
May 16 14:00:57 s4slave smbd[7173]:    #1
/usr/local/samba/lib/libsmbconf.so.0(smb_panic_s3+0x6d) [0x7fb492c9c4c9]
May 16 14:00:57 s4slave smbd[7173]:    #2
/usr/local/samba/lib/libsamba-util.so.0(smb_panic+0x28) [0x7fb4952e86d3]
May 16 14:00:57 s4slave smbd[7173]:    #3
/usr/local/samba/lib/private/libsmbd-base-samba4.so(+0xda7c1) [0x7fb494dc17c1]
May 16 14:00:57 s4slave smbd[7173]:    #4
/usr/local/samba/lib/private/libsmbd-base-samba4.so(is_visible_file+0x2e3)
[0x7fb494dc1bbe]
May 16 14:00:57 s4slave smbd[7173]:    #5
/usr/local/samba/lib/private/libsmbd-base-samba4.so(+0xd8ab7) [0x7fb494dbfab7]
May 16 14:00:57 s4slave smbd[7173]:    #6
/usr/local/samba/lib/private/libsmbd-base-samba4.so(+0xd8bcb) [0x7fb494dbfbcb]
May 16 14:00:57 s4slave smbd[7173]:    #7
/usr/local/samba/lib/private/libsmbd-base-samba4.so(smbd_dirptr_get_entry+0x148)
[0x7fb494dc0a24]
May 16 14:00:57 s4slave smbd[7173]:    #8
/usr/local/samba/lib/private/libsmbd-base-samba4.so(smbd_dirptr_lanman2_entry+0x1d1)
[0x7fb494e102b0]
May 16 14:00:57 s4slave smbd[7173]:    #9
/usr/local/samba/lib/private/libsmbd-base-samba4.so(+0x1b599f) [0x7fb494e9c99f]
May 16 14:00:57 s4slave smbd[7173]:    #10
/usr/local/samba/lib/private/libsmbd-base-samba4.so(smbd_smb2_request_process_query_directory+0x654)
[0x7fb494e9b92c]
May 16 14:00:57 s4slave smbd[7173]:    #11
/usr/local/samba/lib/private/libsmbd-base-samba4.so(smbd_smb2_request_dispatch+0x115b)
[0x7fb494e7e8d4]
May 16 14:00:57 s4slave smbd[7173]:    #12
/usr/local/samba/lib/private/libsmbd-base-samba4.so(+0x19b8bb) [0x7fb494e828bb]
May 16 14:00:57 s4slave smbd[7173]:    #13
/usr/local/samba/lib/private/libsmbd-base-samba4.so(+0x19b9ca) [0x7fb494e829ca]
May 16 14:00:57 s4slave smbd[7173]:    #14
/usr/local/samba/lib/libsmbconf.so.0(run_events_poll+0x544) [0x7fb492cb95cc]
May 16 14:00:57 s4slave smbd[7173]:    #15
/usr/local/samba/lib/libsmbconf.so.0(+0x3e8a2) [0x7fb492cb98a2]
May 16 14:00:57 s4slave smbd[7173]:    #16
/usr/local/samba/lib/private/libtevent.so.0(_tevent_loop_once+0xfc)
[0x7fb4942b6489]
May 16 14:00:57 s4slave smbd[7173]:    #17
/usr/local/samba/lib/private/libtevent.so.0(tevent_common_loop_wait+0x25)
[0x7fb4942b6701]
May 16 14:00:57 s4slave smbd[7173]:    #18
/usr/local/samba/lib/private/libtevent.so.0(_tevent_loop_wait+0x2b)
[0x7fb4942b67cc]
May 16 14:00:57 s4slave smbd[7173]:    #19
/usr/local/samba/lib/private/libsmbd-base-samba4.so(smbd_process+0xbdb)
[0x7fb494e65305]
May 16 14:00:57 s4slave smbd[7173]:    #20 /usr/local/samba/sbin/smbd(+0x8a8e)
[0x7fb49597ca8e]
May 16 14:00:57 s4slave smbd[7173]:    #21
/usr/local/samba/lib/libsmbconf.so.0(run_events_poll+0x544) [0x7fb492cb95cc]
May 16 14:00:57 s4slave smbd[7173]:    #22
/usr/local/samba/lib/libsmbconf.so.0(+0x3e8a2) [0x7fb492cb98a2]
May 16 14:00:57 s4slave smbd[7173]:    #23
/usr/local/samba/lib/private/libtevent.so.0(_tevent_loop_once+0xfc)
[0x7fb4942b6489]
May 16 14:00:57 s4slave smbd[7173]:    #24
/usr/local/samba/lib/private/libtevent.so.0(tevent_common_loop_wait+0x25)
[0x7fb4942b6701]
May 16 14:00:57 s4slave smbd[7173]:    #25
/usr/local/samba/lib/private/libtevent.so.0(_tevent_loop_wait+0x2b)
[0x7fb4942b67cc]
May 16 14:00:57 s4slave smbd[7173]:    #26 /usr/local/samba/sbin/smbd(+0x992b)
[0x7fb49597d92b]
May 16 14:00:57 s4slave smbd[7173]:    #27
/usr/local/samba/sbin/smbd(main+0x15bd) [0x7fb49597f09a]
May 16 14:00:57 s4slave smbd[7173]:    #28
/lib64/libc.so.6(__libc_start_main+0xfd) [0x7fb4915b7cdd]
May 16 14:00:57 s4slave smbd[7173]:    #29 /usr/local/samba/sbin/smbd(+0x6209)
[0x7fb49597a209]
May 16 14:00:57 s4slave smbd[7173]: [2019/05/16 14:00:57.841384,  0]
../source3/lib/util.c:801(smb_panic_s3)
May 16 14:00:57 s4slave smbd[7173]:   smb_panic(): calling panic action
[/bin/sleep 999999999]




-----Ursprüngliche Nachricht-----
Von: Rowland penny via samba [mailto:samba at lists.samba.org] 
Gesendet: Donnerstag, 16. Mai 2019 10:41
An: samba at lists.samba.org
Betreff: Re: [Samba] Error smb_panic(): calling panic action [/bin/sleep
999999999]

On 16/05/2019 09:12, Mueller via samba wrote:
> 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?
Samba 4.3.x went EOL 2 years ago, so if it is a bug, it might already have been
fixed and you probably have zero chance of getting your version fixed. Is there
any way you can upgrade your version of Samba ?

Rowland




--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba


---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus

On 16/05/2019 13:06, Mueller wrote:
> No I can not upgrade now it is a working system with x users.

If you hadn't left it so long, you probably could (but possibly wouldn't
have to) just upgrade ;-)
> The master dc with the same config is working without any issues.
Check for any differences between the two.
> So when I upgrade I must do the uprgade on both replicating samba server
and the samba fileservers?
Because your Samba version is so old, I would upgrade both DC's, but the 
fileservers should be okay, but I would upgrade them eventually.

Have you run 'samba-tool dbcheck' on the affected DC and 'samba-tool
drs
showrepl' ?

Can you post your smb.conf files from the DC's

Rowland

On 16/05/2019 14:04, Mueller wrote:
> I fear when I do a
> 'samba-tool dbcheck' this will do the rest to kill the affected
samba . Can I do it ?
Just checking AD shouldn't do anything other than tell you if you have a 
problem or not, so yes, check it.
>
>
> Smb.conf on Master only global:
>
> [global]
>          workgroup = TPLK
>          realm = tplk.loc
>          netbios name = S4MASTER
>          server role = active directory domain controller
>          server services = s3fs, rpc, nbt, wrepl, ldap, cldap, kdc, drepl,
winbind, ntp_signd, kcc, dnsupdate
>          idmap_ldb:use rfc2307 = yes
>          follow symlinks = yes
>           wide links = Yes
>          unix extensions= no
>
> smb.conf on Slave only global:
> # Global parameters
> [global]
>          workgroup = TPLK
>          realm = tplk.loc
>          netbios name = S4SLAVE
>          server role = active directory domain controller
>          server services = s3fs, rpc, nbt, wrepl, ldap, cldap, kdc, drepl,
winbind, ntp_signd, kcc, dnsupdate
>          follow symlinks = yes
>          wide links = yes
>          unix extensions = no
>          idmap_ldb:use rfc2307 = yes

Just one comment, you do not have master/slave DC's, you just have two 
DC's, not that this should matter for your problem.
>
>
> SAMBA-TOOL drs showrepl on affected Host /slave)
>
> [root at s4slave ~]# samba-tool drs showrepl
> Default-First-Site-Name\S4SLAVE
> DSA Options: 0x00000001
> DSA object GUID: cce36cb1-5fcd-46f2-a49c-f0d51b72e08b
> DSA invocationId: 47c91612-b1d1-4aa5-ae70-9eb32fb5b6a9
>
Everything looks okay there.

Rowland

On 16/05/2019 14:12, Mueller wrote:
> It tried it:
> [root at s4slave ~]# samba-tool dbcheck
> Checking 723 objects
> Checked 723 objects (0 errors)
>
>
> No errors found?
>
> But every 15 Minutes this errors in my /var/log/messages
>
> May 16 15:00:12 s4slave smbd[28372]: [2019/05/16 15:00:12.439912,  0]
../source3/lib/util.c:801(smb_panic_s3)
> May 16 15:00:12 s4slave smbd[28372]:   smb_panic(): calling panic action
[/bin/sleep 999999999]
> May 16 15:00:57 s4slave smbd[28523]: [2019/05/16 15:00:57.978772,  0]
../source3/smbd/dir.c:1440(user_can_write_file)
> May 16 15:00:57 s4slave smbd[28523]:   PANIC: assert failed at
../source3/smbd/dir.c(1440): VALID_STAT(smb_fname->st)
>
  I seem to remember problems like this a few years ago and as I said, 
you will not get this fixed in 4.3.x (well not unless your OS can 
identify the problem and backport the fix). I strongly urge to find some 
way to upgrade.

Rowland