Re: [Samba] [samba4] crash of winbind after ls -l /usr/local/samba/var/locks/sysvol
till: unset /usr/sbin/smbd: Server exit (failed to receive smb request) Terminating connection - 'wbsrv_call_loop: tstream_read_pdu_blob_recv() - NT_STATUS_CONNECTION_DISCONNECTED' single_terminate: reason[wbsrv_call_loop: tstream_read_pdu_blob_recv() - NT_STATUS_CONNECTION_DISCONNECTED] === INTERNAL ERROR: Signal 11 in pid 14988 (4.0.4-GIT-f77d5d6) Please read the Trouble-Shooting section of the Samba HOWTO === PANIC: internal error Aborted -Original Message- From: Michael Wood [mailto:esiot...@gmail.com] Sent: Monday, April 29, 2013 12:20 PM To: Simonet Philippe, ITS-OUS-OP-IFM-NW-IPE Cc: samba@lists.samba.org Subject: Re: [Samba] [samba4] crash of winbind after ls -l /usr/local/samba/var/locks/sysvol If you have the time to track this down, it might be worth doing a git bisect. It will require compiling samba about 7 times and testing each one. Basically you clone the samba repository (as per the Samba 4 HOWTO on the wiki) and then: 1.) $ git bisect start samba-4.0.5 samba-4.0.4 2.) Compile samba as normal and test the result. 3.) If it fails, run git bisect bad. If it works properly, run git bisect good. 4.) If git tells you it's found the bad commit, report that here. Otherwise it will tell you roughly how many steps are left and what commit you are on now, in which case, go back to step 2. When git bisect tells you the bad commit, you can report that here and it might help the Samba developers to find the problem more easily. To get your git tree back to where it was before starting the bisect, do git bisect reset. On 29 April 2013 10:56, philippe.simo...@swisscom.com wrote: Hi all, just as info, i also have the same crash with debian wheezy and samba 4.0.5, by just doing wbinfo --uid-info 300 and also only when the nssswitch.conf have compat winbind but i didn't have this crash with 4.0.4, in this case NO problem. best regards philippe -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- Michael Wood esiot...@gmail.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] [samba4] crash of winbind after ls -l /usr/local/samba/var/locks/sysvol
Hi all, just as info, i also have the same crash with debian wheezy and samba 4.0.5, by just doing wbinfo --uid-info 300 and also only when the nssswitch.conf have compat winbind but i didn't have this crash with 4.0.4, in this case NO problem. best regards philippe -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] [samba4] crash of winbind after ls -l /usr/local/samba/var/locks/sysvol
If you have the time to track this down, it might be worth doing a git bisect. It will require compiling samba about 7 times and testing each one. Basically you clone the samba repository (as per the Samba 4 HOWTO on the wiki) and then: 1.) $ git bisect start samba-4.0.5 samba-4.0.4 2.) Compile samba as normal and test the result. 3.) If it fails, run git bisect bad. If it works properly, run git bisect good. 4.) If git tells you it's found the bad commit, report that here. Otherwise it will tell you roughly how many steps are left and what commit you are on now, in which case, go back to step 2. When git bisect tells you the bad commit, you can report that here and it might help the Samba developers to find the problem more easily. To get your git tree back to where it was before starting the bisect, do git bisect reset. On 29 April 2013 10:56, philippe.simo...@swisscom.com wrote: Hi all, just as info, i also have the same crash with debian wheezy and samba 4.0.5, by just doing wbinfo --uid-info 300 and also only when the nssswitch.conf have compat winbind but i didn't have this crash with 4.0.4, in this case NO problem. best regards philippe -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- Michael Wood esiot...@gmail.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] [samba4] crash of winbind after ls -l /usr/local/samba/var/locks/sysvol
Hi all, just as info, i can reproduce this crash with debian wheezy with 4.0.5, by just doing wbinfo --uid-info 300 and only when the nssswitch.conf have compat winbind i didn't have this crash with 4.0.4. best regards philippe -- View this message in context: http://samba.2283325.n4.nabble.com/samba4-crash-of-winbind-after-ls-l-usr-local-samba-var-locks-sysvol-tp4646715p4647257.html Sent from the Samba - General mailing list archive at Nabble.com. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] [samba4] crash of winbind after ls -l /usr/local/samba/var/locks/sysvol
On Sun, 2013-04-21 at 14:07 +0200, François Lafont wrote: Hello, Le 20/04/2013 20:00, Michael Wood a écrit : As Andrew suggested it would be good if you could run it under valgrind and reproduce the crash. I don't know valgrind sorry. In spite of all, I have tried this: --- apt-get install valgrind ./configure --enable-debug #--- I add the --enable-debug make make install samba-tool domain provision --realm=CHEZMOI.PRIV --domain=CHEZMOI --server-role=dc --dns-backend=SAMBA_INTERNAL --adminpass='+toto123' echo nameserver 192.168.0.21 /etc/resolv.conf samba ln -s /usr/local/samba/lib/libnss_winbind.so /lib/libnss_winbind.so ln -s /lib/libnss_winbind.so /lib/libnss_winbind.so.2 # I put winbind in the nsswitch.conf file. sed -i -r -e 's/^(passwd:.*)$/\1 winbind/g' -e 's/^(group:.*)$/\1 winbind/g' /etc/nsswitch.conf valgrind --leak-check=full samba -i M single out 21 Can you try that again with: valgrind samba -i -M single out 21 I'm not worried about memory leaks (they don't cause crashes), and missing the '-' in front of -M probably means you didn't get the crash in the log you gave. Either way, it's so large I can't make heads or tails of it. Andrew Bartlett -- Andrew Bartletthttp://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] [samba4] crash of winbind after ls -l /usr/local/samba/var/locks/sysvol
Hi, same problem here: root@leela:~# valgrind samba -i -M single out 21 root@leela:~# cat out ==4450== Memcheck, a memory error detector ==4450== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al. ==4450== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info ==4450== Command: samba -i -M single ==4450== samba version 4.0.5 started. Copyright Andrew Tridgell and the Samba Team 1992-2012 samba: using 'single' process model /opt/samba/sbin/smbd: sh: Zeile 0: test: Zu viele Argumente. /opt/samba/sbin/smbd: sh: Zeile 0: test: Zu viele Argumente. ==4450== Invalid read of size 8 ==4450==at 0xA20F1A0: krb5_cc_store_cred (cache.c:684) ==4450==by 0xA22487A: krb5_get_credentials_with_flags (get_cred.c:1207) ==4450==by 0xA2248C5: krb5_get_credentials (get_cred.c:1220) ==4450==by 0x956E1B7: gsskrb5_get_creds (init_sec_context.c:246) ==4450==by 0x956E73D: init_auth (init_sec_context.c:455) ==4450==by 0x956F52F: _gsskrb5_init_sec_context (init_sec_context.c:942) ==4450==by 0x9587E86: gss_init_sec_context (gss_init_sec_context.c:187) ==4450==by 0x613BB29: gensec_gssapi_update (gensec_gssapi.c:464) ==4450==by 0x61354B5: gensec_update (gensec.c:220) ==4450==by 0x6132E90: gensec_spnego_create_negTokenInit (spnego.c:644) ==4450==by 0x6133891: gensec_spnego_update (spnego.c:842) ==4450==by 0x6134DB1: gensec_spnego_update_wrapper (spnego.c:1311) ==4450== Address 0x26a8ac50 is 0 bytes inside a block of size 24 free'd ==4450==at 0x4C2A82E: free (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==4450==by 0xA20F182: krb5_cc_close (cache.c:666) ==4450==by 0x957E52E: _gsskrb5_release_cred (release_cred.c:65) ==4450==by 0x9586895: gss_release_cred (gss_release_cred.c:65) ==4450==by 0x5492B63: free_gssapi_creds (credentials_krb5.c:443) ==4450==by 0x67A0BA8: _talloc_free_internal (talloc.c:831) ==4450==by 0x67A1BFF: _talloc_free_children_internal (talloc.c:1256) ==4450==by 0x67A0D4B: _talloc_free_internal (talloc.c:851) ==4450==by 0x67A1BFF: _talloc_free_children_internal (talloc.c:1256) ==4450==by 0x67A0D4B: _talloc_free_internal (talloc.c:851) ==4450==by 0x67A1BFF: _talloc_free_children_internal (talloc.c:1256) ==4450==by 0x67A0D4B: _talloc_free_internal (talloc.c:851) ==4450== ==4450== Invalid read of size 8 ==4450==at 0xA236D90: mcc_store_cred (mcache.c:239) ==4450==by 0xA20F1BB: krb5_cc_store_cred (cache.c:684) ==4450==by 0xA22487A: krb5_get_credentials_with_flags (get_cred.c:1207) ==4450==by 0xA2248C5: krb5_get_credentials (get_cred.c:1220) ==4450==by 0x956E1B7: gsskrb5_get_creds (init_sec_context.c:246) ==4450==by 0x956E73D: init_auth (init_sec_context.c:455) ==4450==by 0x956F52F: _gsskrb5_init_sec_context (init_sec_context.c:942) ==4450==by 0x9587E86: gss_init_sec_context (gss_init_sec_context.c:187) ==4450==by 0x613BB29: gensec_gssapi_update (gensec_gssapi.c:464) ==4450==by 0x61354B5: gensec_update (gensec.c:220) ==4450==by 0x6132E90: gensec_spnego_create_negTokenInit (spnego.c:644) ==4450==by 0x6133891: gensec_spnego_update (spnego.c:842) ==4450== Address 0x26a8ac60 is 16 bytes inside a block of size 24 free'd ==4450==at 0x4C2A82E: free (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==4450==by 0xA20F182: krb5_cc_close (cache.c:666) ==4450==by 0x957E52E: _gsskrb5_release_cred (release_cred.c:65) ==4450==by 0x9586895: gss_release_cred (gss_release_cred.c:65) ==4450==by 0x5492B63: free_gssapi_creds (credentials_krb5.c:443) ==4450==by 0x67A0BA8: _talloc_free_internal (talloc.c:831) ==4450==by 0x67A1BFF: _talloc_free_children_internal (talloc.c:1256) ==4450==by 0x67A0D4B: _talloc_free_internal (talloc.c:851) ==4450==by 0x67A1BFF: _talloc_free_children_internal (talloc.c:1256) ==4450==by 0x67A0D4B: _talloc_free_internal (talloc.c:851) ==4450==by 0x67A1BFF: _talloc_free_children_internal (talloc.c:1256) ==4450==by 0x67A0D4B: _talloc_free_internal (talloc.c:851) ==4450== ==4450== Invalid read of size 4 ==4450==at 0xA236D9C: mcc_store_cred (mcache.c:243) ==4450==by 0xA20F1BB: krb5_cc_store_cred (cache.c:684) ==4450==by 0xA22487A: krb5_get_credentials_with_flags (get_cred.c:1207) ==4450==by 0xA2248C5: krb5_get_credentials (get_cred.c:1220) ==4450==by 0x956E1B7: gsskrb5_get_creds (init_sec_context.c:246) ==4450==by 0x956E73D: init_auth (init_sec_context.c:455) ==4450==by 0x956F52F: _gsskrb5_init_sec_context (init_sec_context.c:942) ==4450==by 0x9587E86: gss_init_sec_context (gss_init_sec_context.c:187) ==4450==by 0x613BB29: gensec_gssapi_update (gensec_gssapi.c:464) ==4450==by 0x61354B5: gensec_update (gensec.c:220) ==4450==by 0x6132E90: gensec_spnego_create_negTokenInit (spnego.c:644) ==4450==by 0x6133891: gensec_spnego_update (spnego.c:842) ==4450== Address 0x24f01e1c is 12 bytes inside a block of size 56 free'd ==4450==at 0x4C2A82E: free
Re: [Samba] [samba4] crash of winbind after ls -l /usr/local/samba/var/locks/sysvol
On Fri, 2013-04-26 at 19:47 +0200, sa...@nisx.de wrote: Hi, same problem here: We need to know where that free is coming from, can you add --num-callers=64? eg valgrind --num-callers=64 samba -i -M single out 21 root@leela:~# valgrind samba -i -M single out 21 root@leela:~# cat out ==4450== Memcheck, a memory error detector ==4450== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al. ==4450== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info ==4450== Command: samba -i -M single ==4450== samba version 4.0.5 started. Copyright Andrew Tridgell and the Samba Team 1992-2012 samba: using 'single' process model /opt/samba/sbin/smbd: sh: Zeile 0: test: Zu viele Argumente. /opt/samba/sbin/smbd: sh: Zeile 0: test: Zu viele Argumente. ==4450== Invalid read of size 8 ==4450==at 0xA20F1A0: krb5_cc_store_cred (cache.c:684) ==4450==by 0xA22487A: krb5_get_credentials_with_flags (get_cred.c:1207) ==4450==by 0xA2248C5: krb5_get_credentials (get_cred.c:1220) ==4450==by 0x956E1B7: gsskrb5_get_creds (init_sec_context.c:246) ==4450==by 0x956E73D: init_auth (init_sec_context.c:455) ==4450==by 0x956F52F: _gsskrb5_init_sec_context (init_sec_context.c:942) ==4450==by 0x9587E86: gss_init_sec_context (gss_init_sec_context.c:187) ==4450==by 0x613BB29: gensec_gssapi_update (gensec_gssapi.c:464) ==4450==by 0x61354B5: gensec_update (gensec.c:220) ==4450==by 0x6132E90: gensec_spnego_create_negTokenInit (spnego.c:644) ==4450==by 0x6133891: gensec_spnego_update (spnego.c:842) ==4450==by 0x6134DB1: gensec_spnego_update_wrapper (spnego.c:1311) ==4450== Address 0x26a8ac50 is 0 bytes inside a block of size 24 free'd ==4450==at 0x4C2A82E: free (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==4450==by 0xA20F182: krb5_cc_close (cache.c:666) ==4450==by 0x957E52E: _gsskrb5_release_cred (release_cred.c:65) ==4450==by 0x9586895: gss_release_cred (gss_release_cred.c:65) ==4450==by 0x5492B63: free_gssapi_creds (credentials_krb5.c:443) ==4450==by 0x67A0BA8: _talloc_free_internal (talloc.c:831) ==4450==by 0x67A1BFF: _talloc_free_children_internal (talloc.c:1256) ==4450==by 0x67A0D4B: _talloc_free_internal (talloc.c:851) ==4450==by 0x67A1BFF: _talloc_free_children_internal (talloc.c:1256) ==4450==by 0x67A0D4B: _talloc_free_internal (talloc.c:851) ==4450==by 0x67A1BFF: _talloc_free_children_internal (talloc.c:1256) ==4450==by 0x67A0D4B: _talloc_free_internal (talloc.c:851) ==4450== ==4450== Invalid read of size 8 ==4450==at 0xA236D90: mcc_store_cred (mcache.c:239) ==4450==by 0xA20F1BB: krb5_cc_store_cred (cache.c:684) ==4450==by 0xA22487A: krb5_get_credentials_with_flags (get_cred.c:1207) ==4450==by 0xA2248C5: krb5_get_credentials (get_cred.c:1220) ==4450==by 0x956E1B7: gsskrb5_get_creds (init_sec_context.c:246) ==4450==by 0x956E73D: init_auth (init_sec_context.c:455) ==4450==by 0x956F52F: _gsskrb5_init_sec_context (init_sec_context.c:942) ==4450==by 0x9587E86: gss_init_sec_context (gss_init_sec_context.c:187) ==4450==by 0x613BB29: gensec_gssapi_update (gensec_gssapi.c:464) ==4450==by 0x61354B5: gensec_update (gensec.c:220) ==4450==by 0x6132E90: gensec_spnego_create_negTokenInit (spnego.c:644) ==4450==by 0x6133891: gensec_spnego_update (spnego.c:842) ==4450== Address 0x26a8ac60 is 16 bytes inside a block of size 24 free'd ==4450==at 0x4C2A82E: free (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==4450==by 0xA20F182: krb5_cc_close (cache.c:666) ==4450==by 0x957E52E: _gsskrb5_release_cred (release_cred.c:65) ==4450==by 0x9586895: gss_release_cred (gss_release_cred.c:65) ==4450==by 0x5492B63: free_gssapi_creds (credentials_krb5.c:443) ==4450==by 0x67A0BA8: _talloc_free_internal (talloc.c:831) ==4450==by 0x67A1BFF: _talloc_free_children_internal (talloc.c:1256) ==4450==by 0x67A0D4B: _talloc_free_internal (talloc.c:851) ==4450==by 0x67A1BFF: _talloc_free_children_internal (talloc.c:1256) ==4450==by 0x67A0D4B: _talloc_free_internal (talloc.c:851) ==4450==by 0x67A1BFF: _talloc_free_children_internal (talloc.c:1256) ==4450==by 0x67A0D4B: _talloc_free_internal (talloc.c:851) ==4450== ==4450== Invalid read of size 4 ==4450==at 0xA236D9C: mcc_store_cred (mcache.c:243) ==4450==by 0xA20F1BB: krb5_cc_store_cred (cache.c:684) ==4450==by 0xA22487A: krb5_get_credentials_with_flags (get_cred.c:1207) ==4450==by 0xA2248C5: krb5_get_credentials (get_cred.c:1220) ==4450==by 0x956E1B7: gsskrb5_get_creds (init_sec_context.c:246) ==4450==by 0x956E73D: init_auth (init_sec_context.c:455) ==4450==by 0x956F52F: _gsskrb5_init_sec_context (init_sec_context.c:942) ==4450==by 0x9587E86: gss_init_sec_context (gss_init_sec_context.c:187) ==4450==by 0x613BB29: gensec_gssapi_update (gensec_gssapi.c:464) ==4450==by
Re: [Samba] [samba4] crash of winbind after ls -l /usr/local/samba/var/locks/sysvol
Hi, Le 26/04/2013 11:38, Andrew Bartlett a écrit : Can you try that again with: valgrind samba -i -M single out 21 I'm not worried about memory leaks (they don't cause crashes), and missing the '-' in front of -M probably means you didn't get the crash in the log you gave. Oops, sorry. It's very strange, with your command, there is no problem in the log. I have tried this: ~# valgrind samba -i -M single out 21 During, the execution of samba, I have done this in another shell: - ~# wbinfo -u Administrator Guest krbtgt test1 ~# ls -l /usr/local/samba/var/locks/sysvol/ # 1 minute'wait total 8 drwxrws---+ 4 root 300 4096 Apr 21 13:00 chezmoi.priv ~# wbinfo -u Error looking up domain users - And here my out file: - ==2377== Memcheck, a memory error detector ==2377== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al. ==2377== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info ==2377== Command: samba -i -M single ==2377== samba version 4.0.5 started. Copyright Andrew Tridgell and the Samba Team 1992-2012 samba: using 'single' process model ==2377== ==2377== HEAP SUMMARY: ==2377== in use at exit: 4,601,429 bytes in 36,998 blocks ==2377== total heap usage: 696,172 allocs, 659,174 frees, 113,032,156 bytes allocated ==2377== ==2377== LEAK SUMMARY: ==2377==definitely lost: 0 bytes in 0 blocks ==2377==indirectly lost: 0 bytes in 0 blocks ==2377== possibly lost: 4,283,837 bytes in 35,214 blocks ==2377==still reachable: 317,592 bytes in 1,784 blocks ==2377== suppressed: 0 bytes in 0 blocks ==2377== Rerun with --leak-check=full to see details of leaked memory ==2377== ==2377== For counts of detected and suppressed errors, rerun with: -v ==2377== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 285 from 8) - No problem ! It's very curious. I hope that we would more information with the thomas'log... -- François Lafont -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] [samba4] crash of winbind after ls -l /usr/local/samba/var/locks/sysvol
Hi there, I have done this: useradd -d /tmp -M -s /bin/false -u 300 -g 100 -o -l samba4-workaround0 and also for users from 301 up to 308. groupadd -g 516 -o samba4-workaround-group 516 and also for groups from 517 up to 561. Now all group and user ids are masked, which let winbind crashes: root@leela:~# ll /opt/samba/var/locks/sysvol insgesamt 4 drwxrws---+ 4 root samba4-workaround-group544 35 Mär 18 00:41 futurama.loc Regards Thomas Nolte -- Nolte Infosysteme, Im Sikfeld 8, 38304 Wolfenbuettel Tel 05331-946210, Fax 05331-946211, Handy 0170-5508198 Computer, Netzwerk, Kommunikation www.nisx.de -Ursprüngliche Nachricht- Von: samba-boun...@lists.samba.org [mailto:samba-boun...@lists.samba.org] Im Auftrag von François Lafont Gesendet: Dienstag, 23. April 2013 01:37 An: samba@lists.samba.org Cc: Andrew Bartlett Betreff: Re: [Samba] [samba4] crash of winbind after ls -l /usr/local/samba/var/locks/sysvol [Ooops, sorry Michael for my first message, I have made a mistake with the recipients] Hello, Le 22/04/2013 13:29, Michael Wood a écrit : Did winbind also crash when you ran it under valgrind? Yes, I think so. I have done 2 tests with valgrind --leak-check=full samba -i M single out 21 and for the 2 tests I have the same problem: -- ~# wbinfo -u Administrator Guest krbtgt test1 ~# time ls -l /usr/local/samba/var/locks/sysvol/ total 8 drwxrws---+ 4 root 300 4096 Apr 21 13:00 chezmoi.priv real1m13.350s user0m0.000s sys 0m0.068s ~# wbinfo -u Error looking up domain users -- Perhaps you should attach the two logs directly to the bug instead of just linking to them. Ok, it's done. One of the Samba developers will have to let you know if the information you have provided is enough. Ok, thanks for your help Michael. :) -- François Lafont -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] [samba4] crash of winbind after ls -l /usr/local/samba/var/locks/sysvol
Hi again, sorry only this groups: 517,518,519,520,533,544,545,546,547,548,549,550,551,552,554,555,556,557,558,559,560,561 Mit freundlichen Grüßen Thomas Nolte -- Nolte Infosysteme, Im Sikfeld 8, 38304 Wolfenbuettel Tel 05331-946210, Fax 05331-946211, Handy 0170-5508198 Computer, Netzwerk, Kommunikation www.nisx.de -Ursprüngliche Nachricht- Von: samba-boun...@lists.samba.org [mailto:samba-boun...@lists.samba.org] Im Auftrag von Thomas Nolte Gesendet: Mittwoch, 24. April 2013 12:52 An: samba@lists.samba.org Betreff: Re: [Samba] [samba4] crash of winbind after ls -l /usr/local/samba/var/locks/sysvol Hi there, I have done this: useradd -d /tmp -M -s /bin/false -u 300 -g 100 -o -l samba4-workaround0 and also for users from 301 up to 308. groupadd -g 516 -o samba4-workaround-group 516 and also for groups from 517 up to 561. Now all group and user ids are masked, which let winbind crashes: root@leela:~# ll /opt/samba/var/locks/sysvol insgesamt 4 drwxrws---+ 4 root samba4-workaround-group544 35 Mär 18 00:41 drwxrws---+ futurama.loc Regards Thomas Nolte -- Nolte Infosysteme, Im Sikfeld 8, 38304 Wolfenbuettel Tel 05331-946210, Fax 05331-946211, Handy 0170-5508198 Computer, Netzwerk, Kommunikation www.nisx.de -Ursprüngliche Nachricht- Von: samba-boun...@lists.samba.org [mailto:samba-boun...@lists.samba.org] Im Auftrag von François Lafont Gesendet: Dienstag, 23. April 2013 01:37 An: samba@lists.samba.org Cc: Andrew Bartlett Betreff: Re: [Samba] [samba4] crash of winbind after ls -l /usr/local/samba/var/locks/sysvol [Ooops, sorry Michael for my first message, I have made a mistake with the recipients] Hello, Le 22/04/2013 13:29, Michael Wood a écrit : Did winbind also crash when you ran it under valgrind? Yes, I think so. I have done 2 tests with valgrind --leak-check=full samba -i M single out 21 and for the 2 tests I have the same problem: -- ~# wbinfo -u Administrator Guest krbtgt test1 ~# time ls -l /usr/local/samba/var/locks/sysvol/ total 8 drwxrws---+ 4 root 300 4096 Apr 21 13:00 chezmoi.priv real1m13.350s user0m0.000s sys 0m0.068s ~# wbinfo -u Error looking up domain users -- Perhaps you should attach the two logs directly to the bug instead of just linking to them. Ok, it's done. One of the Samba developers will have to let you know if the information you have provided is enough. Ok, thanks for your help Michael. :) -- François Lafont -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] [samba4] crash of winbind after ls -l /usr/local/samba/var/locks/sysvol
Hi, could you or anyone tell me how to do this? I have never used gdb. Mit freundlichen Grüßen Thomas Nolte -- Nolte Infosysteme, Im Sikfeld 8, 38304 Wolfenbuettel Tel 05331-946210, Fax 05331-946211, Handy 0170-5508198 Computer, Netzwerk, Kommunikation www.nisx.de -Ursprüngliche Nachricht- Von: Volker Lendecke [mailto:volker.lende...@sernet.de] Gesendet: Mittwoch, 24. April 2013 13:35 An: Thomas Nolte Betreff: Re: [Samba] [samba4] crash of winbind after ls -l /usr/local/samba/var/locks/sysvol On Wed, Apr 24, 2013 at 12:51:51PM +0200, sa...@nisx.de wrote: Hi there, I have done this: useradd -d /tmp -M -s /bin/false -u 300 -g 100 -o -l samba4-workaround0 and also for users from 301 up to 308. groupadd -g 516 -o samba4-workaround-group 516 and also for groups from 517 up to 561. Now all group and user ids are masked, which let winbind crashes: root@leela:~# ll /opt/samba/var/locks/sysvol insgesamt 4 drwxrws---+ 4 root samba4-workaround-group544 35 Mär 18 00:41 drwxrws---+ futurama.loc Wenn da irgend ein Prozess stirbt, brauchen wir von diesem Prozess ein bt full backtrace von gdb. Viele Grüße, Volker Lendecke -- SerNet GmbH, Bahnhofsallee 1b, 37081 Göttingen phone: +49-551-37-0, fax: +49-551-37-9 AG Göttingen, HRB 2816, GF: Dr. Johannes Loxen http://www.sernet.de, mailto:kont...@sernet.de -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] [samba4] crash of winbind after ls -l /usr/local/samba/var/locks/sysvol
Hi On 21 April 2013 14:07, François Lafont flafdiv...@free.fr wrote: Hello, Le 20/04/2013 20:00, Michael Wood a écrit : As Andrew suggested it would be good if you could run it under valgrind and reproduce the crash. I don't know valgrind sorry. In spite of all, I have tried this: --- apt-get install valgrind ./configure --enable-debug #--- I add the --enable-debug make make install samba-tool domain provision --realm=CHEZMOI.PRIV --domain=CHEZMOI --server-role=dc --dns-backend=SAMBA_INTERNAL --adminpass='+toto123' echo nameserver 192.168.0.21 /etc/resolv.conf samba ln -s /usr/local/samba/lib/libnss_winbind.so /lib/libnss_winbind.so ln -s /lib/libnss_winbind.so /lib/libnss_winbind.so.2 # I put winbind in the nsswitch.conf file. sed -i -r -e 's/^(passwd:.*)$/\1 winbind/g' -e 's/^(group:.*)$/\1 winbind/g' /etc/nsswitch.conf valgrind --leak-check=full samba -i M single out 21 --- Here is the output during the ls -l /usr/local/samba/var/locks/sysvol/ problem: http://sisco.laf.free.fr/codes/samba4_gid_300_valgrind.log Will that be enough? Also, you should probably log a bug in bugzilla. It's done: https://bugzilla.samba.org/show_bug.cgi?id=9820 Did winbind also crash when you ran it under valgrind? Perhaps you should attach the two logs directly to the bug instead of just linking to them. One of the Samba developers will have to let you know if the information you have provided is enough. Regards, Michael -- Michael Wood esiot...@gmail.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] [samba4] crash of winbind after ls -l /usr/local/samba/var/locks/sysvol
[Ooops, sorry Michael for my first message, I have made a mistake with the recipients] Hello, Le 22/04/2013 13:29, Michael Wood a écrit : Did winbind also crash when you ran it under valgrind? Yes, I think so. I have done 2 tests with valgrind --leak-check=full samba -i M single out 21 and for the 2 tests I have the same problem: -- ~# wbinfo -u Administrator Guest krbtgt test1 ~# time ls -l /usr/local/samba/var/locks/sysvol/ total 8 drwxrws---+ 4 root 300 4096 Apr 21 13:00 chezmoi.priv real1m13.350s user0m0.000s sys 0m0.068s ~# wbinfo -u Error looking up domain users -- Perhaps you should attach the two logs directly to the bug instead of just linking to them. Ok, it's done. One of the Samba developers will have to let you know if the information you have provided is enough. Ok, thanks for your help Michael. :) -- François Lafont -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] [samba4] crash of winbind after ls -l /usr/local/samba/var/locks/sysvol
Hello, Le 20/04/2013 20:00, Michael Wood a écrit : As Andrew suggested it would be good if you could run it under valgrind and reproduce the crash. I don't know valgrind sorry. In spite of all, I have tried this: --- apt-get install valgrind ./configure --enable-debug #--- I add the --enable-debug make make install samba-tool domain provision --realm=CHEZMOI.PRIV --domain=CHEZMOI --server-role=dc --dns-backend=SAMBA_INTERNAL --adminpass='+toto123' echo nameserver 192.168.0.21 /etc/resolv.conf samba ln -s /usr/local/samba/lib/libnss_winbind.so /lib/libnss_winbind.so ln -s /lib/libnss_winbind.so /lib/libnss_winbind.so.2 # I put winbind in the nsswitch.conf file. sed -i -r -e 's/^(passwd:.*)$/\1 winbind/g' -e 's/^(group:.*)$/\1 winbind/g' /etc/nsswitch.conf valgrind --leak-check=full samba -i M single out 21 --- Here is the output during the ls -l /usr/local/samba/var/locks/sysvol/ problem: http://sisco.laf.free.fr/codes/samba4_gid_300_valgrind.log Will that be enough? Also, you should probably log a bug in bugzilla. It's done: https://bugzilla.samba.org/show_bug.cgi?id=9820 -- François Lafont -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] [samba4] crash of winbind after ls -l /usr/local/samba/var/locks/sysvol
Hi, same problem here on all running systems. I would like to help too to get the problem out of the way. Mit freundlichen Grüßen Thomas Nolte -- Nolte Infosysteme, Im Sikfeld 8, 38304 Wolfenbuettel Tel 05331-946210, Fax 05331-946211, Handy 0170-5508198 Computer, Netzwerk, Kommunikation www.nisx.de -Ursprüngliche Nachricht- Von: samba-boun...@lists.samba.org [mailto:samba-boun...@lists.samba.org] Im Auftrag von François Lafont Gesendet: Freitag, 19. April 2013 23:08 An: samba@lists.samba.org Betreff: Re: [Samba] [samba4] crash of winbind after ls -l /usr/local/samba/var/locks/sysvol Hi, I go back to this thread (the title is explicit) just to have news. I have seen in other threads that other people have similar problems. Should we consider this problem as a bug (in Samba 4.0.5) or is it a wrong installation from my part? In the first case, are information that I have given enough or should I provide other things? In the second case, I'm interesting by clues. Thanks. -- François Lafont -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] [samba4] crash of winbind after ls -l /usr/local/samba/var/locks/sysvol
Hi As Andrew suggested it would be good if you could run it under valgrind and reproduce the crash. Also, you should probably log a bug in bugzilla. On 20 April 2013 14:00, sa...@nisx.de wrote: Hi, same problem here on all running systems. I would like to help too to get the problem out of the way. Mit freundlichen Grüßen Thomas Nolte -- Nolte Infosysteme, Im Sikfeld 8, 38304 Wolfenbuettel Tel 05331-946210, Fax 05331-946211, Handy 0170-5508198 Computer, Netzwerk, Kommunikation www.nisx.de -Ursprüngliche Nachricht- Von: samba-boun...@lists.samba.org [mailto:samba-boun...@lists.samba.org] Im Auftrag von François Lafont Gesendet: Freitag, 19. April 2013 23:08 An: samba@lists.samba.org Betreff: Re: [Samba] [samba4] crash of winbind after ls -l /usr/local/samba/var/locks/sysvol Hi, I go back to this thread (the title is explicit) just to have news. I have seen in other threads that other people have similar problems. Should we consider this problem as a bug (in Samba 4.0.5) or is it a wrong installation from my part? In the first case, are information that I have given enough or should I provide other things? In the second case, I'm interesting by clues. Thanks. -- François Lafont -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- Michael Wood esiot...@gmail.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] [samba4] crash of winbind after ls -l /usr/local/samba/var/locks/sysvol
Hi, I go back to this thread (the title is explicit) just to have news. I have seen in other threads that other people have similar problems. Should we consider this problem as a bug (in Samba 4.0.5) or is it a wrong installation from my part? In the first case, are information that I have given enough or should I provide other things? In the second case, I'm interesting by clues. Thanks. -- François Lafont -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] [samba4] crash of winbind after ls -l /usr/local/samba/var/locks/sysvol
Le 14/04/2013 13:51, François Lafont a écrit : I'm going to search, meanwhile, here is the ouput of the samba -i -M single -d 10 command during the ls -l /usr/local/samba/var/locks/sysvol/ problem. Ooups! Sorry I have forgotten the url address: http://sisco.laf.free.fr/codes/samba4_gid_300.log Will that information be enough? Or should I provide other things? -- François Lafont -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] [samba4] crash of winbind after ls -l /usr/local/samba/var/locks/sysvol
On Sun, 2013-04-14 at 02:08 +0200, François Lafont wrote: Hi, I used Samba 4.0.5 in Wheezy. Here is that I have done: But there is something curious with the /usr/local/samba/var/locks/sysvol/ directory: --- # ls -n /usr/local/samba/var/locks/sysvol/ total 8 drwxrws---+ 4 0 300 4096 Apr 14 01:40 chezmoi.priv --- Which group has the gid 300? The files are owned by the domain administrators group. Winbind doesn't know how to make up a 'user' record for that group yet. --- # wbinfo -g | tr '\n' '\0' | xargs -0 -n 1 wbinfo --group-info CHEZMOI\Enterprise Read-Only Domain Controllers:*:318: CHEZMOI\Domain Admins:*:308: CHEZMOI\Domain Users:*:100: CHEZMOI\Domain Guests:*:312: CHEZMOI\Domain Computers:*:319: CHEZMOI\Domain Controllers:*:320: CHEZMOI\Schema Admins:*:307: CHEZMOI\Enterprise Admins:*:306: CHEZMOI\Group Policy Creator Owners:*:304: CHEZMOI\Read-Only Domain Controllers:*:321: CHEZMOI\DnsUpdateProxy:*:322: --- There is no 300 gid. And, a bit more embarrassing, if I use ls -l to resolv the gid to a name, winbind is crashing: Can you please try to get a gdb backtrace, or better still run 'samba' under valgrind? We would very much like to fix that. You could also file these details in a bug, if we don't sort it out quickly. Thanks, Andrew Bartlett -- Andrew Bartletthttp://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] [samba4] crash of winbind after ls -l /usr/local/samba/var/locks/sysvol
On 14/04/13 07:30, Andrew Bartlett wrote: On Sun, 2013-04-14 at 02:08 +0200, François Lafont wrote: Hi, I used Samba 4.0.5 in Wheezy. Here is that I have done: But there is something curious with the /usr/local/samba/var/locks/sysvol/ directory: --- # ls -n /usr/local/samba/var/locks/sysvol/ total 8 drwxrws---+ 4 0 300 4096 Apr 14 01:40 chezmoi.priv --- Which group has the gid 300? The files are owned by the domain administrators group. Winbind doesn't know how to make up a 'user' record for that group yet. In that case, would you like to explain why, if I add a user to Domain Admins and then mount a share as the user from the S4 server via cifs, all the files get saved as user 300? Rowland --- # wbinfo -g | tr '\n' '\0' | xargs -0 -n 1 wbinfo --group-info CHEZMOI\Enterprise Read-Only Domain Controllers:*:318: CHEZMOI\Domain Admins:*:308: CHEZMOI\Domain Users:*:100: CHEZMOI\Domain Guests:*:312: CHEZMOI\Domain Computers:*:319: CHEZMOI\Domain Controllers:*:320: CHEZMOI\Schema Admins:*:307: CHEZMOI\Enterprise Admins:*:306: CHEZMOI\Group Policy Creator Owners:*:304: CHEZMOI\Read-Only Domain Controllers:*:321: CHEZMOI\DnsUpdateProxy:*:322: --- There is no 300 gid. And, a bit more embarrassing, if I use ls -l to resolv the gid to a name, winbind is crashing: Can you please try to get a gdb backtrace, or better still run 'samba' under valgrind? We would very much like to fix that. You could also file these details in a bug, if we don't sort it out quickly. Thanks, Andrew Bartlett -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] [samba4] crash of winbind after ls -l /usr/local/samba/var/locks/sysvol
Le 14/04/2013 08:30, Andrew Bartlett a écrit : --- # ls -n /usr/local/samba/var/locks/sysvol/ total 8 drwxrws---+ 4 0 300 4096 Apr 14 01:40 chezmoi.priv --- Which group has the gid 300? The files are owned by the domain administrators group. Do you mean the CN=Administrators,CN=Builtin,DC=chezmoi,DC=priv group? Why don't this group appear with the wbinfo -g command? --- # wbinfo -g Enterprise Read-Only Domain Controllers Domain Admins Domain Users Domain Guests Domain Computers Domain Controllers Schema Admins Enterprise Admins Group Policy Creator Owners Read-Only Domain Controllers --- Winbind doesn't know how to make up a 'user' record for that group yet. And it's not a normal behavior, isn't it? Can you please try to get a gdb backtrace, or better still run 'samba' under valgrind? We would very much like to fix that. Sorry, I don't know how to do that, I'm a samba beginner. I'm going to search, meanwhile, here is the ouput of the samba -i -M single -d 10 command during the ls -l /usr/local/samba/var/locks/sysvol/ problem. Thanks for your help. -- François Lafont -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] [samba4] crash of winbind after ls -l /usr/local/samba/var/locks/sysvol
Le 14/04/2013 13:49, François Lafont a écrit : I'm going to search, meanwhile, here is the ouput of the samba -i -M single -d 10 command during the ls -l /usr/local/samba/var/locks/sysvol/ problem. Ooups! Sorry I have forgotten the url address: http://sisco.laf.free.fr/codes/samba4_gid_300.log -- François Lafont -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] [samba4] crash of winbind after ls -l /usr/local/samba/var/locks/sysvol
Hi, I used Samba 4.0.5 in Wheezy. Here is that I have done: --- samba-tool domain provision --realm=CHEZMOI.PRIV --domain=CHEZMOI \ --server-role=dc --dns-backend=SAMBA_INTERNAL --adminpass='+toto123' echo nameserver 192.168.0.21 /etc/resolv.conf samba ln -s /usr/local/samba/lib/libnss_winbind.so /lib/libnss_winbind.so ln -s /lib/libnss_winbind.so /lib/libnss_winbind.so.2 # I put winbind in the nsswitch.conf file. sed -i -r -e 's/^(passwd:.*)$/\1 winbind/g' -e 's/^(group:.*)$/\1 winbind/g' /etc/nsswitch.conf samba-tool user add test1 +test123 --- That's all. Here is my smb.conf after this commands: --- # Global parameters [global] workgroup = CHEZMOI realm = CHEZMOI.PRIV netbios name = WHEEZY-1 server role = active directory domain controller dns forwarder = 212.27.40.241 [netlogon] path = /usr/local/samba/var/locks/sysvol/chezmoi.priv/scripts read only = No [sysvol] path = /usr/local/samba/var/locks/sysvol read only = No --- It seems to work well: --- ~# getent passwd [couic...] CHEZMOI\Administrator:*:0:100::/home/CHEZMOI/Administrator:/bin/false CHEZMOI\Guest:*:311:312::/home/CHEZMOI/Guest:/bin/false CHEZMOI\krbtgt:*:316:100::/home/CHEZMOI/krbtgt:/bin/false CHEZMOI\test1:*:317:100::/home/CHEZMOI/test1:/bin/false ~# wbinfo -u Administrator Guest krbtgt test1 # wbinfo -g Enterprise Read-Only Domain Controllers Domain Admins Domain Users Domain Guests Domain Computers Domain Controllers Schema Admins Enterprise Admins Group Policy Creator Owners Read-Only Domain Controllers DnsUpdateProxy --- But there is something curious with the /usr/local/samba/var/locks/sysvol/ directory: --- # ls -n /usr/local/samba/var/locks/sysvol/ total 8 drwxrws---+ 4 0 300 4096 Apr 14 01:40 chezmoi.priv --- Which group has the gid 300? --- # wbinfo -g | tr '\n' '\0' | xargs -0 -n 1 wbinfo --group-info CHEZMOI\Enterprise Read-Only Domain Controllers:*:318: CHEZMOI\Domain Admins:*:308: CHEZMOI\Domain Users:*:100: CHEZMOI\Domain Guests:*:312: CHEZMOI\Domain Computers:*:319: CHEZMOI\Domain Controllers:*:320: CHEZMOI\Schema Admins:*:307: CHEZMOI\Enterprise Admins:*:306: CHEZMOI\Group Policy Creator Owners:*:304: CHEZMOI\Read-Only Domain Controllers:*:321: CHEZMOI\DnsUpdateProxy:*:322: --- There is no 300 gid. And, a bit more embarrassing, if I use ls -l to resolv the gid to a name, winbind is crashing: --- # time ls -l /usr/local/samba/var/locks/sysvol total 8 drwxrws---+ 4 root 300 4096 Apr 14 01:40 chezmoi.priv real0m33.483s # 33 seconds ! user0m0.012s sys 0m0.000s # wbinfo -u Error looking up domain users # wbinfo -g failed to call wbcListGroups: WBC_ERR_WINBIND_NOT_AVAILABLE Error looking up domain groups # wbinfo -i Guest failed to call wbcGetpwnam: WBC_ERR_WINBIND_NOT_AVAILABLE Could not get info for user Guest # wbinfo -p Ping to winbindd failed could not ping winbindd! --- I have to restart samba: --- # killall samba; sleep 2; samba # wbinfo -u Administrator Guest krbtgt test1 # wbinfo -g Enterprise Read-Only Domain Controllers Domain Admins Domain Users Domain Guests Domain Computers Domain Controllers Schema Admins Enterprise Admins Group Policy Creator Owners Read-Only Domain Controllers DnsUpdateProxy # wbinfo -p Ping to winbindd succeeded --- Have I made a mistake? Where is the problem? Thanks in advande. -- François Lafont -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
