In samba 4 log I get the following message: [2013/04/29 00:44:30,? 0] ../source4/smbd/server.c:369(binary_smbd_main) ? samba version 4.1.0pre1-GIT-5727bfa started. ? Copyright Andrew Tridgell and the Samba Team 1992-2013 [2013/04/29 00:44:31,? 0] ../source4/smbd/server.c:475(binary_smbd_main) ? samba: using 'standard' process model [2013/04/29 00:44:32,? 1] ../source4/auth/gensec/gensec_gssapi.c:339(gensec_gssapi_client_start) ? Could not determine hostname for target computer, cannot use kerberos [2013/04/29 00:44:32,? 1] ../source4/auth/gensec/gensec_gssapi.c:339(gensec_gssapi_client_start) ? Could not determine hostname for target computer, cannot use kerberos and in another log I have: [2013/04/29 00:44:32.534527,? 0] ../source3/lib/util_sock.c:423(open_socket_in) ? open_socket_in(): socket() call failed: Address family not supported by protocol [2013/04/29 00:44:32.541347,? 0] ../source3/smbd/server.c:684(smbd_open_one_socket) ? smbd_open_once_socket: open_socket_in: Address family not supported by protocol [2013/04/29 00:44:32.542740,? 0] ../source3/lib/util_sock.c:423(open_socket_in) ? open_socket_in(): socket() call failed: Address family not supported by protocol [2013/04/29 00:44:32.542874,? 0] ../source3/smbd/server.c:684(smbd_open_one_socket) ? smbd_open_once_socket: open_socket_in: Address family not supported by protocol I changed the hostname in /etc/sysconfig/network to name of realm, but it didn't help. I use samba 4, centos 6.3. Please help me. Pavel ?
On Mon, 2013-04-29 at 00:51 +0400, ????????? ???????? wrote:> In samba 4 log I get the following message: > > [2013/04/29 00:44:30, 0] ../source4/smbd/server.c:369(binary_smbd_main) > samba version 4.1.0pre1-GIT-5727bfa started. > Copyright Andrew Tridgell and the Samba Team 1992-2013 > [2013/04/29 00:44:31, 0] ../source4/smbd/server.c:475(binary_smbd_main) > samba: using 'standard' process model > [2013/04/29 00:44:32, 1] ../source4/auth/gensec/gensec_gssapi.c:339(gensec_gssapi_client_start) > Could not determine hostname for target computer, cannot use kerberos > [2013/04/29 00:44:32, 1] ../source4/auth/gensec/gensec_gssapi.c:339(gensec_gssapi_client_start) > Could not determine hostname for target computer, cannot use kerberosDon't worry about this. I'll need to change the log level of the message, it isn't important, just a status message.> and in another log I have: > [2013/04/29 00:44:32.534527, 0] ../source3/lib/util_sock.c:423(open_socket_in) > open_socket_in(): socket() call failed: Address family not supported by protocol > [2013/04/29 00:44:32.541347, 0] ../source3/smbd/server.c:684(smbd_open_one_socket) > smbd_open_once_socket: open_socket_in: Address family not supported by protocol > [2013/04/29 00:44:32.542740, 0] ../source3/lib/util_sock.c:423(open_socket_in) > open_socket_in(): socket() call failed: Address family not supported by protocol > [2013/04/29 00:44:32.542874, 0] ../source3/smbd/server.c:684(smbd_open_one_socket) > smbd_open_once_socket: open_socket_in: Address family not supported by protocolThis is more odd, but is anything actually wrong? Perhaps you have IPv6 half-enabled in some way? Andrew Bartlett -- Andrew Bartlett http://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org
Jeremy, This backtrace looks like it might be something to do with your recent struct DIR work. The revision 5727bfa is from master after the work you did for Ceph in the VFS. On Mon, 2013-04-29 at 10:54 +0400, ????????? ???????? wrote:> Andrew, please help me with this problem. I searched the solution in > internet but couldn't find it. Here is log of certain user.????????? ????????, This is the first time we have seen this particular crash. Essentially all such INTERNAL ERROR messages are bugs in Samba that we fix as soon as we can. If you can give more details of your specific OS and configuration, Jeremy will be able to help you.> [2013/04/29 09:40:49.557876, 0] ../lib/util/fault.c:72(fault_report) > ==============================================================> [2013/04/29 09:40:49.558716, 0] ../lib/util/fault.c:73(fault_report) > INTERNAL ERROR: Signal 11 in pid 7068 (4.1.0pre1-GIT-5727bfa) > Please read the Trouble-Shooting section of the Samba HOWTO > [2013/04/29 09:40:49.558886, 0] ../lib/util/fault.c:75(fault_report) > ==============================================================> [2013/04/29 09:40:49.559004, > 0] ../source3/lib/util.c:810(smb_panic_s3) > PANIC (pid 7068): internal error > [2013/04/29 09:40:49.560313, > 0] ../source3/lib/util.c:921(log_stack_trace) > BACKTRACE: 47 stack frames: > #0 /usr/local/samba/lib/libsmbconf.so.0(log_stack_trace+0x1f) > [0x7ffd5d8f6baf] > #1 /usr/local/samba/lib/libsmbconf.so.0(smb_panic_s3+0x6d) > [0x7ffd5d8f6a1e] > #2 /usr/local/samba/lib/libsamba-util.so.0(smb_panic+0x28) > [0x7ffd5f763a65] > #3 /usr/local/samba/lib/libsamba-util.so.0(+0x1c767) > [0x7ffd5f763767] > #4 /usr/local/samba/lib/libsamba-util.so.0(+0x1c77c) > [0x7ffd5f76377c] > #5 /lib64/libpthread.so.0() [0x345820f500] > #6 /usr/local/samba/lib/private/libsmbd_base.so(TellDir+0xc) > [0x7ffd5ee60f32] > #7 /usr/local/samba/lib/private/libsmbd_base.so(dptr_TellDir+0x1c) > [0x7ffd5ee5eb16] > > #8 /usr/local/samba/lib/private/libsmbd_base.so(smbd_dirptr_get_entry > +0xc7) [0x7ffd5ee5f663] > > #9 /usr/local/samba/lib/private/libsmbd_base.so(smbd_dirptr_lanman2_entry+0x1b4) [0x7ffd5eeadb47] > #10 /usr/local/samba/lib/private/libsmbd_base.so(+0x193f20) > [0x7ffd5ef32f20] > > #11 /usr/local/samba/lib/private/libsmbd_base.so(smbd_smb2_request_process_find+0x654) [0x7ffd5ef321a4] > > #12 /usr/local/samba/lib/private/libsmbd_base.so(smbd_smb2_request_dispatch+0x108f) [0x7ffd5ef19804] > #13 /usr/local/samba/lib/private/libsmbd_base.so(+0x17d944) > [0x7ffd5ef1c944] > > #14 /usr/local/samba/lib/private/libtevent.so.0(_tevent_req_notify_callback+0x6a) [0x7ffd5e98b9d7] > #15 /usr/local/samba/lib/private/libtevent.so.0(+0x5a09) > [0x7ffd5e98ba09] > #16 /usr/local/samba/lib/private/libtevent.so.0(_tevent_req_done > +0x25) [0x7ffd5e98ba30] > #17 /usr/local/samba/lib/private/libsmbd_base.so(+0x17d370) > [0x7ffd5ef1c370] > > #18 /usr/local/samba/lib/private/libtevent.so.0(_tevent_req_notify_callback+0x6a) [0x7ffd5e98b9d7] > #19 /usr/local/samba/lib/private/libtevent.so.0(+0x5a09) > [0x7ffd5e98ba09] > #20 /usr/local/samba/lib/private/libtevent.so.0(_tevent_req_done > +0x25) [0x7ffd5e98ba30] > #21 /usr/local/samba/lib/private/libsamba-sockets.so(+0xc5b8) > [0x7ffd5d6c35b8] > > #22 /usr/local/samba/lib/private/libtevent.so.0(_tevent_req_notify_callback+0x6a) [0x7ffd5e98b9d7] > #23 /usr/local/samba/lib/private/libtevent.so.0(+0x5a09) > [0x7ffd5e98ba09] > #24 /usr/local/samba/lib/private/libtevent.so.0(_tevent_req_done > +0x25) [0x7ffd5e98ba30] > #25 /usr/local/samba/lib/private/libsamba-sockets.so(+0xc086) > [0x7ffd5d6c3086] > #26 /usr/local/samba/lib/private/libsamba-sockets.so(+0xc2b8) > [0x7ffd5d6c32b8] > > #27 /usr/local/samba/lib/private/libtevent.so.0(_tevent_req_notify_callback+0x6a) [0x7ffd5e98b9d7] > #28 /usr/local/samba/lib/private/libtevent.so.0(+0x5a09) > [0x7ffd5e98ba09] > #29 /usr/local/samba/lib/private/libtevent.so.0(_tevent_req_done > +0x25) [0x7ffd5e98ba30] > #30 /usr/local/samba/lib/private/libsamba-sockets.so(+0xb5a1) > [0x7ffd5d6c25a1] > > #31 /usr/local/samba/lib/private/libtevent.so.0(_tevent_req_notify_callback+0x6a) [0x7ffd5e98b9d7] > #32 /usr/local/samba/lib/private/libtevent.so.0(+0x5a09) > [0x7ffd5e98ba09] > #33 /usr/local/samba/lib/private/libtevent.so.0(+0x5b27) > [0x7ffd5e98bb27] > > #34 /usr/local/samba/lib/private/libtevent.so.0(tevent_common_loop_immediate+0x1f9) [0x7ffd5e98aef4] > #35 /usr/local/samba/lib/libsmbconf.so.0(run_events_poll+0x57) > [0x7ffd5d9131ef] > #36 /usr/local/samba/lib/libsmbconf.so.0(+0x4289c) [0x7ffd5d91389c] > #37 /usr/local/samba/lib/private/libtevent.so.0(_tevent_loop_once > +0xfc) [0x7ffd5e989fb9] > #38 /usr/local/samba/lib/private/libsmbd_base.so(smbd_process > +0x1321) [0x7ffd5eefda9c] > #39 /usr/local/samba/sbin/smbd() [0x4098ba] > #40 /usr/local/samba/lib/libsmbconf.so.0(run_events_poll+0x544) > [0x7ffd5d9136dc] > #41 /usr/local/samba/lib/libsmbconf.so.0(+0x429b2) [0x7ffd5d9139b2] > #42 /usr/local/samba/lib/private/libtevent.so.0(_tevent_loop_once > +0xfc) [0x7ffd5e989fb9] > #43 /usr/local/samba/sbin/smbd() [0x40a539] > #44 /usr/local/samba/sbin/smbd(main+0x1587) [0x40bc11] > #45 /lib64/libc.so.6(__libc_start_main+0xfd) [0x3457a1ecdd] > #46 /usr/local/samba/sbin/smbd() [0x4055b9] > [2013/04/29 09:40:49.562765, > 0] ../source3/lib/util.c:822(smb_panic_s3) > smb_panic(): calling panic action [/var/log/samba/panic 7068] > sh: /var/log/samba/panic: Permission denied > [2013/04/29 09:40:49.572649, > 0] ../source3/lib/util.c:830(smb_panic_s3) > smb_panic(): action returned status 126 > [2013/04/29 09:40:49.572871, > 0] ../source3/lib/dumpcore.c:317(dump_core) > dumping core in /usr/local/samba/var/cores/smbd-- Andrew Bartlett http://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org
On Mon, 29 Apr 2013 19:09:16 +1000 Andrew Bartlett <abartlet at samba.org> wrote:> This backtrace looks like it might be something to do with your recent > struct DIR work. The revision 5727bfa is from master after the work you > did for Ceph in the VFS.Could be: https://bugzilla.samba.org/show_bug.cgi?id=9822 Pavel, please retest with 251767cde9a146d8122d76e257ab232c05ad452a. Cheers, David
On Mon, Apr 29, 2013 at 07:09:16PM +1000, Andrew Bartlett wrote:> Jeremy, > > This backtrace looks like it might be something to do with your recent > struct DIR work. The revision 5727bfa is from master after the work you > did for Ceph in the VFS.I think David nailed it. I think this is likely to be the bug I just fixed with the earlier patch. Cheers, Jeremy.
Александр Свиридов
2013-Apr-29 19:26 UTC
[Samba] segfault Re: Errors, errors, errors in log
Thank you all! But can you say, what? I should do? We have samba 4 on our server and people use it. It already has some data (users,group etc). Please, can you explain what I should do now step by step? ???????????, 29 ?????? 2013, 12:21 -07:00 ?? Jeremy Allison <jra at samba.org>:>On Mon, Apr 29, 2013 at 07:09:16PM +1000, Andrew Bartlett wrote: >> Jeremy, >> >> This backtrace looks like it might be something to do with your recent >> struct DIR work. The revision 5727bfa is from master after the work you >> did for Ceph in the VFS. > >I think David nailed it. I think this is likely to be >the bug I just fixed with the earlier patch. > >Cheers, > >Jeremy.
On Mon, 29 Apr 2013 22:39:05 +0400 ????????? ???????? <ooo_saturn7 at mail.ru> wrote:> Yes, I compiled it from source. So, as far as I uderstand you, you suggest me to delete samba and install it again from source. > > If I am right, than I have three questions. > 1) How can I save current AD settings, to upload them into new samba?Running make install should not overwrite any runtime state. That said, backups are always encouraged.> 2) As I understand I have revision: 5727bfa. It has a meaning to install new revision only if new revision has the necessary fix. But how can I check it?After updating your source tree, you can check to see whether the proposed fix is included by running git log. Please see: https://wiki.samba.org/index.php/Build_Samba#Updating_via_git Cheers, David