Re: [Samba] segfault Re: Errors, errors, errors in log

2013-04-30 Thread David Disseldorp
On Mon, 29 Apr 2013 22:39:05 +0400
Александр Свиридов ooo_satu...@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
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

[Samba] segfault Re: Errors, errors, errors in log

2013-04-29 Thread Andrew Bartlett
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) 

Re: [Samba] segfault Re: Errors, errors, errors in log

2013-04-29 Thread David Disseldorp
On Mon, 29 Apr 2013 19:09:16 +1000
Andrew Bartlett abart...@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
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba


Re: [Samba] segfault Re: Errors, errors, errors in log

2013-04-29 Thread Александр Свиридов
 Thank you for your help! I send system information and conf file. Users say 
that when they work with open office with documens on samba share and save 
changes to file program hangs. Can I do anything else?

Here is system information:

+ uname -a
Linux example.com 2.6.32-279.el6.x86_64 #1 SMP Fri Jun 22 12:19:21 UTC 2012 
x86_64 x86_64 x86_64 GNU/Linux
+ head -n1 /etc/issue
CentOS release 6.3 (Final)
+ cat /proc/partitions
major minor  #blocks  name

   8   16  976762584 sdb
   8   17  975187968 sdb1
   8   18    1048576 sdb2
   8   19 524288 sdb3
   8    0  976762584 sda
   8    1  975187968 sda1
   8    2    1048576 sda2
   8    3 524288 sda3
   8   32  976762584 sdc
   8   33  976760832 sdc1
   8   48  976762584 sdd
   8   49  976760832 sdd1
   9    2  975186812 md2
   9    1    1048568 md1
 253    0   36220928 dm-0
   9    3  976759676 md3
   9    0 524276 md0
 253    1  976756736 dm-1
 253    2  524288000 dm-2
 253    3   10485760 dm-3
 253    4   10485760 dm-4
 253    5   10485760 dm-5
 253    6  104857600 dm-6
 253    7   10485760 dm-7
 253    8   10485760 dm-8
+ grep MemTotal /proc/meminfo
MemTotal:   16325256 kB
+ grep 'model name' /proc/cpuinfo
model name    : Intel(R) Xeon(R) CPU   E5645  @ 2.40GHz
model name    : Intel(R) Xeon(R) CPU   E5645  @ 2.40GHz
model name    : Intel(R) Xeon(R) CPU   E5645  @ 2.40GHz
model name    : Intel(R) Xeon(R) CPU   E5645  @ 2.40GHz
model name    : Intel(R) Xeon(R) CPU   E5645  @ 2.40GHz
model name    : Intel(R) Xeon(R) CPU   E5645  @ 2.40GHz
model name    : Intel(R) Xeon(R) CPU   E5645  @ 2.40GHz
model name    : Intel(R) Xeon(R) CPU   E5645  @ 2.40GHz
model name    : Intel(R) Xeon(R) CPU   E5645  @ 2.40GHz
model name    : Intel(R) Xeon(R) CPU   E5645  @ 2.40GHz
model name    : Intel(R) Xeon(R) CPU   E5645  @ 2.40GHz
model name    : Intel(R) Xeon(R) CPU   E5645  @ 2.40GHz
model name    : Intel(R) Xeon(R) CPU   E5645  @ 2.40GHz
model name    : Intel(R) Xeon(R) CPU   E5645  @ 2.40GHz
model name    : Intel(R) Xeon(R) CPU   E5645  @ 2.40GHz
model name    : Intel(R) Xeon(R) CPU   E5645  @ 2.40GHz
model name    : Intel(R) Xeon(R) CPU   E5645  @ 2.40GHz
model name    : Intel(R) Xeon(R) CPU   E5645  @ 2.40GHz
model name    : Intel(R) Xeon(R) CPU   E5645  @ 2.40GHz
model name    : Intel(R) Xeon(R) CPU   E5645  @ 2.40GHz
model name    : Intel(R) Xeon(R) CPU   E5645  @ 2.40GHz
model name    : Intel(R) Xeon(R) CPU   E5645  @ 2.40GHz
model name    : Intel(R) Xeon(R) CPU   E5645  @ 2.40GHz
model name    : Intel(R) Xeon(R) CPU   E5645  @ 2.40GHz
+ ps
  PID TTY  TIME CMD
 9939 pts/1    00:00:00 bash
10442 pts/1    00:00:00 getsysteminfo.s
10448 pts/1    00:00:00 ps
+ cat /proc/version
Linux version 2.6.32-279.el6.x86_64 (mockbu...@c6b9.bsys.dev.centos.org) (gcc 
version 4.4.6 20120305 (Red Hat 4.4.6-4) (GCC) ) #1 SMP Fri Jun 22 12:19:21 UTC 
2012
+ cat /proc/filesystems
nodev    sysfs
nodev    rootfs
nodev    bdev
nodev    proc
nodev    cgroup
nodev    cpuset
nodev    tmpfs
nodev    devtmpfs
nodev    binfmt_misc
nodev    debugfs
nodev    securityfs
nodev    sockfs
nodev    usbfs
nodev    pipefs
nodev    anon_inodefs
nodev    inotifyfs
nodev    devpts
nodev    ramfs
nodev    hugetlbfs
    iso9660
nodev    pstore
nodev    mqueue
nodev    selinuxfs
    ext4
nodev    rpc_pipefs
nodev    fuse
    fuseblk
nodev    fusectl
+ echo 
/usr/lib64/qt-3.3/bin:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/Pavel/bin
/usr/lib64/qt-3.3/bin:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/Pavel/bin
+ netstat -tulpn
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address   Foreign Address 
State   PID/Program name   
tcp    0  0 0.0.0.0:3269    0.0.0.0:*   
LISTEN  2821/samba  
tcp    0  0 0.0.0.0:389 0.0.0.0:*   
LISTEN  2821/samba  
tcp    0  0 0.0.0.0:135 0.0.0.0:*   
LISTEN  2817/samba  
tcp    0  0 0.0.0.0:139 0.0.0.0:*   
LISTEN  2819/smbd   
tcp    0  0 0.0.0.0:464 0.0.0.0:*   
LISTEN  2823/samba  
tcp    0  0 0.0.0.0:53  0.0.0.0:*   
LISTEN  2829/samba  
tcp    0  0 0.0.0.0:88  0.0.0.0:*   
LISTEN  2823/samba  
tcp    0  0 0.0.0.0:636 0.0.0.0:*   
LISTEN  2821/samba  
tcp    0  0 0.0.0.0:445 0.0.0.0:*   
LISTEN  2819/smbd   
tcp    0 

Re: [Samba] segfault Re: Errors, errors, errors in log

2013-04-29 Thread Jeremy Allison
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.
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba


Re: [Samba] segfault Re: Errors, errors, errors in log

2013-04-29 Thread Александр Свиридов
 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 j...@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.

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