muliples crashes after 6.06 to 8.04 x64 upgrade

Bug #229654 reported by alessandro
4
Affects Status Importance Assigned to Milestone
samba
Confirmed
Unknown
samba (Ubuntu)
Medium
Unassigned

Bug Description

Binary package hint: samba

1.
Linux host 2.6.24-17-server #1 SMP Thu May 1 14:28:06 UTC 2008 x86_64 GNU/Linux
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=8.04
DISTRIB_CODENAME=hardy
DISTRIB_DESCRIPTION="Ubuntu 8.04"

2.
samba:
  Installed: 3.0.28a-1ubuntu4
  Candidate: 3.0.28a-1ubuntu4
  Version table:
 *** 3.0.28a-1ubuntu4 0
        500 http://archive.ubuntu.com hardy/main Packages
        100 /var/lib/dpkg/status

3.
expected to copy file over the network

4.
[Thread debugging using libthread_db enabled]
[New Thread 0x7f09d68a5700 (LWP 11213)]
0x00007f09d3aa94a5 in waitpid () from /lib/libc.so.6
#0 0x00007f09d3aa94a5 in waitpid () from /lib/libc.so.6
#1 0x00007f09d3a4a461 in ?? () from /lib/libc.so.6
#2 0x00000000006139cb in smb_panic (why=<value optimized out>)
    at lib/util.c:1639
#3 0x0000000000618a71 in assert_uid (ruid=4294967295, euid=1012)
    at lib/util_sec.c:102
#4 0x00000000004ba4fe in become_id (uid=1012, gid=1012) at smbd/sec_ctx.c:57
#5 0x00000000004ba676 in pop_sec_ctx () at smbd/sec_ctx.c:345
#6 0x00000000004afe49 in unbecome_root () at smbd/uid.c:400
#7 0x00000000005d3458 in gid_to_sid (psid=0x7fffde8b8460, gid=1001)
    at passdb/lookup_sid.c:1202
#8 0x00000000004c429a in get_nt_acl (fsp=0xb185e0, security_info=7,
    ppdesc=0x7fffde8b8598) at smbd/posix_acls.c:2809
#9 0x000000000046dfee in is_visible_file (conn=0xac15c0,
    dir_path=0xb690f0 "development/projects/terminal/sagem68k/appli/projects/java/bc/src_java/interfaces",
    name=<value optimized out>, pst=0x7fffde8b8f60, use_veto=1)
    at smbd/dir.c:897
#10 0x000000000046e570 in dptr_normal_ReadDirName (dptr=0xab12c0,
    poffset=0x7fffde8b9028, pst=0x7fffde8b8f60) at smbd/dir.c:562
#11 0x000000000046e5e4 in dptr_ReadDirName (dptr=0xab12c0,
    poffset=0x7fffde8b9028, pst=0x7fffde8b8f60) at smbd/dir.c:642
#12 0x00000000004a5434 in get_lanman2_dir_entry (conn=0xac15c0,
    inbuf=<value optimized out>, outbuf=0xae6fc0 "",
    path_mask=0x7fffde8ba240 "*", dirtype=22, info_level=260,
    requires_resume_key=4, dont_descend=0, ppdata=0x7fffde8ba210,
    base_data=0xb0c490 "`", end_data=0xb1148f "", space_remaining=5936,
    out_of_space=0x7fffde8ba234, got_exact_match=0x7fffde8ba21c,
    last_entry_off=0x7fffde8ba23c, name_list=0x0, ea_ctx=0x0)
    at smbd/trans2.c:1149
#13 0x00000000004a8a63 in call_trans2findfirst (conn=0xac15c0,
    inbuf=0xac6b70 "", outbuf=0xae6fc0 "", bufsize=131072, pparams=0xb14760,
    total_params=<value optimized out>, ppdata=0xb14770, total_data=0,
    max_data_bytes=16384) at smbd/trans2.c:1859
#14 0x00000000004a91fe in handle_trans2 (conn=0xac15c0, state=0xb14610,
    inbuf=0xac6b70 "", outbuf=0xae6fc0 "", size=<value optimized out>,
    bufsize=131072) at smbd/trans2.c:6433
#15 0x00000000004afbba in reply_trans2 (conn=0xac15c0, inbuf=0xac6b70 "",
    outbuf=0xae6fc0 "", size=342, bufsize=131072) at smbd/trans2.c:6703
#16 0x00000000004c870e in switch_message (type=50, inbuf=0xac6b70 "",
    outbuf=0xae6fc0 "", size=342, bufsize=131072) at smbd/process.c:1003
#17 0x00000000004c9af2 in smbd_process () at smbd/process.c:1030
#18 0x00000000006c5c5d in main (argc=<value optimized out>,
    argv=0x7fffde8bc1c8) at smbd/server.c:1120
The program is running. Quit anyway (and detach it)? (y or n) [answered Y; input not from terminal]

Got lot of the same errors on various files

Revision history for this message
Chuck Short (zulcss) wrote :

Can you provide the output of testparm -S /etc/samba/smb.conf and install the samba-dbg package and run the command /usr/lib/debug/usr/sbin/samba -F

Thanks
chuck

Changed in samba:
status: New → Incomplete
Changed in samba:
status: Unknown → Confirmed
Revision history for this message
berni123 (bernd-bernd--zimmermann) wrote :
Download full text (6.5 KiB)

I have a similar stack trace maybe related to this, happens often a network user tries to access a network device, he got the windows messages that the network share is not available, smbd crashes and after that, the user can access the network share. But from time to time, the crash continues and only a complee restart of samba has to be done.

[Thread debugging using libthread_db enabled]
[New Thread 0x7f02cd972700 (LWP 6430)]
0x00007f02cab804a5 in waitpid () from /lib/libc.so.6
#0 0x00007f02cab804a5 in waitpid () from /lib/libc.so.6
#1 0x00007f02cab21461 in ?? () from /lib/libc.so.6
#2 0x0000000000613c4b in smb_panic (why=<value optimized out>)
    at lib/util.c:1639
#3 0x0000000000618cc1 in assert_uid (ruid=4294967295, euid=1001)
    at lib/util_sec.c:102
#4 0x00000000004ba57e in become_id (uid=1001, gid=100) at smbd/sec_ctx.c:57
#5 0x00000000004ba6f6 in pop_sec_ctx () at smbd/sec_ctx.c:345
#6 0x00000000004afec9 in unbecome_root () at smbd/uid.c:400
#7 0x00000000005d36b8 in gid_to_sid (psid=0x7fffd5990990, gid=100)
    at passdb/lookup_sid.c:1202
#8 0x00000000004c432a in get_nt_acl (fsp=0xb16fb0, security_info=7,
    ppdesc=0x7fffd5990ac8) at smbd/posix_acls.c:2809
#9 0x000000000046e06e in is_visible_file (conn=0xab9240,
    dir_path=0xa85ce0 "./", name=<value optimized out>, pst=0x7fffd5991490,
    use_veto=1) at smbd/dir.c:897
#10 0x000000000046e5f0 in dptr_normal_ReadDirName (dptr=0xa13ff0,
    poffset=0x7fffd5991558, pst=0x7fffd5991490) at smbd/dir.c:562
#11 0x000000000046e664 in dptr_ReadDirName (dptr=0xa13ff0,
    poffset=0x7fffd5991558, pst=0x7fffd5991490) at smbd/dir.c:642
#12 0x00000000004a54b4 in get_lanman2_dir_entry (conn=0xab9240,
    inbuf=<value optimized out>, outbuf=0xadefb0 "",
    path_mask=0x7fffd5992770 "*", dirtype=22, info_level=260,
    requires_resume_key=4, dont_descend=0, ppdata=0x7fffd5992740,
    base_data=0xaff400 "`", end_data=0xb043ff "", space_remaining=10504,
    out_of_space=0x7fffd5992764, got_exact_match=0x7fffd599274c,
    last_entry_off=0x7fffd599276c, name_list=0x0, ea_ctx=0x0)
    at smbd/trans2.c:1149
#13 0x00000000004a8ae3 in call_trans2findfirst (conn=0xab9240,
    inbuf=0xabeb60 "", outbuf=0xadefb0 "", bufsize=131072, pparams=0xabd460,
    total_params=<value optimized out>, ppdata=0xabd470, total_data=0,
    max_data_bytes=16384) at smbd/trans2.c:1859
#14 0x00000000004a927e in handle_trans2 (conn=0xab9240, state=0xabd310,
    inbuf=0xabeb60 "", outbuf=0xadefb0 "", size=<value optimized out>,
    bufsize=131072) at smbd/trans2.c:6433
#15 0x00000000004afc3a in reply_trans2 (conn=0xab9240, inbuf=0xabeb60 "",
    outbuf=0xadefb0 "", size=90, bufsize=131072) at smbd/trans2.c:6703
#16 0x00000000004c879e in switch_message (type=50, inbuf=0xabeb60 "",
    outbuf=0xadefb0 "", size=90, bufsize=131072) at smbd/process.c:1004
#17 0x00000000004c9b92 in smbd_process () at smbd/process.c:1031
#18 0x00000000006c5f6d in main (argc=<value optimized out>,
    argv=0x7fffd59946f8) at smbd/server.c:1120

Hier the host log entry:

[2008/10/06 08:49:27, 0] lib/util_sec.c:set_effective_uid(205)
  setresuid failed with EAGAIN. uid(1001) might be over its NPROC limit
[2008/10/06 08:49:27, 0...

Read more...

Revision history for this message
Pedro Villavicencio (pedro) wrote :

comment from upstream:

"Quick shot -- do you have something like SELinux or so running? If yes, can you
try disabling it?
"
could somebody try that and report back? thanks in advance.

Changed in samba:
importance: Undecided → Medium
Revision history for this message
alessandro (asandini) wrote : Re: [Bug 229654] Re: muliples crashes after 6.06 to 8.04 x64 upgrade

No, no SELinux here.

If it can help, I noticed that the crashes only happens in shares where
"force group" is used (and never in the homes directories)

On Thu, 2009-03-12 at 13:07 +0000, Pedro Villavicencio wrote:
> comment from upstream:
>
> "Quick shot -- do you have something like SELinux or so running? If yes, can you
> try disabling it?
> "
> could somebody try that and report back? thanks in advance.
>
> ** Changed in: samba (Ubuntu)
> Importance: Undecided => Medium
>

Revision history for this message
Paul Dufresne (paulduf) wrote :

Looks like a dup of bug #216358.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.