[Samba-it] samba 4.1.17 PANIC

[Piviul]

Anch'io ho aggiornato e mi sono anch'io accorto di un panic ma non mi 
sembra abbia nulla a che fare con il tuo:

[2015/04/13 10:24:15.679287,  0] 
../source3/smbd/oplock.c:748(do_break_to_none)
   release_level_2_oplocks_on_change: PANIC. share mode entry 0 is an 
exlusive oplock !
[2015/04/13 10:24:15.693737,  0] ../lib/util/fault.c:72(fault_report)
   ===============================================================
[2015/04/13 10:24:15.693843,  0] ../lib/util/fault.c:73(fault_report)
   INTERNAL ERROR: Signal 6 in pid 17365 (4.1.17-Debian)
   Please read the Trouble-Shooting section of the Samba HOWTO
[2015/04/13 10:24:15.694001,  0] ../lib/util/fault.c:75(fault_report)
   ===============================================================
[2015/04/13 10:24:15.694082,  0] ../source3/lib/util.c:785(smb_panic_s3)
   PANIC (pid 17365): internal error
[2015/04/13 10:24:15.729825,  0] ../source3/lib/util.c:896(log_stack_trace)
   BACKTRACE: 20 stack frames:
    #0 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(log_stack_trace+0x1a) 
[0x7fa2f929ae1a]
    #1 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(smb_panic_s3+0x20) 
[0x7fa2f929aef0]
    #2 /usr/lib/x86_64-linux-gnu/libsamba-util.so.0(smb_panic+0x2f) 
[0x7fa2faa1970f]
    #3 /usr/lib/x86_64-linux-gnu/libsamba-util.so.0(+0x1e906) 
[0x7fa2faa19906]
    #4 /lib/x86_64-linux-gnu/libpthread.so.0(+0xf0a0) [0x7fa2fac400a0]
    #5 /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x35) [0x7fa2f7903165]
    #6 /lib/x86_64-linux-gnu/libc.so.6(abort+0x180) [0x7fa2f79063e0]
    #7 /usr/lib/x86_64-linux-gnu/samba/libsmbd_base.so.0(+0x16cc3c) 
[0x7fa2fa645c3c]
    #8 
/usr/lib/x86_64-linux-gnu/libtevent.so.0(tevent_common_loop_timer_delay+0xd8) 
[0x7fa2f7c646d8]
    #9 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(run_events_poll+0x1dd) 
[0x7fa2f92ba99d]
    #10 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(+0x47b1b) [0x7fa2f92bab1b]
    #11 /usr/lib/x86_64-linux-gnu/libtevent.so.0(_tevent_loop_once+0x9d) 
[0x7fa2f7c603ed]
    #12 
/usr/lib/x86_64-linux-gnu/samba/libsmbd_base.so.0(smbd_process+0xb87) 
[0x7fa2fa60d5e7]
    #13 /usr/sbin/smbd(+0xa974) [0x7fa2fb079974]
    #14 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(run_events_poll+0x187) 
[0x7fa2f92ba947]
    #15 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(+0x47bc9) [0x7fa2f92babc9]
    #16 /usr/lib/x86_64-linux-gnu/libtevent.so.0(_tevent_loop_once+0x9d) 
[0x7fa2f7c603ed]
    #17 /usr/sbin/smbd(main+0x149b) [0x7fa2fb07657b]
    #18 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd) 
[0x7fa2f78efead]
    #19 /usr/sbin/smbd(+0x78a9) [0x7fa2fb0768a9]
[2015/04/13 10:24:15.730694,  0] ../source3/lib/util.c:797(smb_panic_s3)
   smb_panic(): calling panic action [/usr/share/samba/panic-action 17365]
[2015/04/13 10:24:16.097246,  0] ../source3/lib/util.c:805(smb_panic_s3)
   smb_panic(): action returned status 0
[2015/04/13 10:24:16.097606,  0] ../source3/lib/dumpcore.c:317(dump_core)
   dumping core in /var/log/samba/cores/smbd

Per la risoluzione del tuo panic non so proprio aiutarti

Piviul

Alessandro Bono ha scrito il 13/04/2015 alle 12:26:
> Ciao
>
> ho aggiornato un samba pdc 3.6 alla versione 4.1.17 di sernet su centos 6
> sembrava tutto funzionante ma gli utenti si lamentano di malfunzionamenti
> nei log vedo questo
>
>  STATUS=daemon 'smbd' finished starting up and ready to serve 
> connectionsPANIC: assert failed at ../source3/smbd/uid.c(317): 
> conn->force_group_gid != (gid_t)-1
> [2015/04/13 08:20:13.455276,  0] ../source3/lib/util.c:785(smb_panic_s3)
>   PANIC (pid 8373): assert failed: conn->force_group_gid != (gid_t)-1
> [2015/04/13 08:20:13.456833,  0] 
> ../source3/lib/util.c:896(log_stack_trace)
>   BACKTRACE: 22 stack frames:
>    #0 /usr/lib64/samba/libsmbconf.so.0(log_stack_trace+0x1c) 
> [0x7f896846e9b7]
>    #1 /usr/lib64/samba/libsmbconf.so.0(smb_panic_s3+0x55) 
> [0x7f896846eab9]
>    #2 /usr/lib64/samba/libsamba-util.so.0(smb_panic+0x2d) 
> [0x7f8969fb6bae]
>    #3 /usr/lib64/samba/libsmbd_base.so(+0xf0ab3) [0x7f8969b96ab3]
>    #4 /usr/lib64/samba/libsmbd_base.so(change_to_user+0x17b) 
> [0x7f8969b96f1b]
>    #5 /usr/lib64/samba/libsmbd_base.so(+0x11a25f) [0x7f8969bc025f]
>    #6 /usr/lib64/samba/libsmbd_base.so(make_connection_smb2+0xb0) 
> [0x7f8969bc12b0]
>    #7 
> /usr/lib64/samba/libsmbd_base.so(smbd_smb2_request_process_tcon+0x5d0) 
> [0x7f8969bd6450]
>    #8 
> /usr/lib64/samba/libsmbd_base.so(smbd_smb2_request_dispatch+0xb8f) 
> [0x7f8969bd098d]
>    #9 /usr/lib64/samba/libsmbd_base.so(+0x12b68a) [0x7f8969bd168a]
>    #10 /usr/lib64/samba/libsmbd_base.so(+0x12c8df) [0x7f8969bd28df]
>    #11 /usr/lib64/samba/libsmbconf.so.0(run_events_poll+0x2c2) 
> [0x7f896848b815]
>    #12 /usr/lib64/samba/libsmbconf.so.0(+0x42c5d) [0x7f896848bc5d]
>    #13 /usr/lib64/samba/libtevent.so.0(_tevent_loop_once+0x92) 
> [0x7f896989d407]
>    #14 /usr/lib64/samba/libsmbd_base.so(smbd_process+0xf76) 
> [0x7f8969bbc378]
>    #15 /usr/sbin/smbd(+0x8860) [0x7f896a619860]
>    #16 /usr/lib64/samba/libsmbconf.so.0(run_events_poll+0x2c2) 
> [0x7f896848b815]
>    #17 /usr/lib64/samba/libsmbconf.so.0(+0x42c5d) [0x7f896848bc5d]
>    #18 /usr/lib64/samba/libtevent.so.0(_tevent_loop_once+0x92) 
> [0x7f896989d407]
>    #19 /usr/sbin/smbd(main+0x17c9) [0x7f896a61b2ee]
>    #20 /lib64/libc.so.6(__libc_start_main+0xfd) [0x7f8966f0bd5d]
>    #21 /usr/sbin/smbd(+0x58b9) [0x7f896a6168b9]
> [2015/04/13 08:20:13.458019,  0] ../source3/lib/util.c:797(smb_panic_s3)
>   smb_panic(): calling panic action [/usr/share/samba/panic-action 8373]
> sh: /usr/share/samba/panic-action: No such file or directory
> [2015/04/13 08:20:13.468288,  0] ../source3/lib/util.c:805(smb_panic_s3)
>   smb_panic(): action returned status 127
> [2015/04/13 08:20:13.468669,  0] ../source3/lib/dumpcore.c:317(dump_core)
>   dumping core in /var/log/samba/cores/smbd
>
>
> le condivisione sono del tipo
>
> [contabilita]
>     path = /home/export/contabilita
>     valid users = @contabilita
>     write list = @contabilita
>     force group = contabilita
>
>
> utenti su openldap + sssd
> se serve posto il file di configurazione completo
>
> qualcuno ha idea come risolvere?
>