Comment 9 for bug 314657

Paul Dufresne wrote:
> Thanks you, for your comment.
> Happy to see that you are there to answer more questions.
>
> Anyway, in an bug #216358, Steve Langasek say:
> "Hitting this assertion error should also generate log entries. Could you please check /var/log/samba/log.smbd (or the per-host logfile) for entries of the form "Failure to set uid privileges to [...]"? "
>
> I guess, looking the said log file may give a hint.
>

Paul,

there's nothing in log.smbd like this, but I found the following in one
of the client logs (it's my Gutsy machine).

[2009/01/09 08:17:14, 0] lib/util.c:log_stack_trace(1737)
   BACKTRACE: 20 stack frames:
    #0 /usr/sbin/smbd(log_stack_trace+0x1c) [0x613b4c]
    #1 /usr/sbin/smbd(smb_panic+0x43) [0x613c33]
    #2 /usr/sbin/smbd [0x618cf1]
    #3 /usr/sbin/smbd [0x4ba5ae]
    #4 /usr/sbin/smbd(pop_sec_ctx+0x96) [0x4ba726]
    #5 /usr/sbin/smbd(unbecome_root+0x9) [0x4afef9]
    #6 /usr/sbin/smbd(gid_to_sid+0x168) [0x5d36e8]
    #7 /usr/sbin/smbd(get_nt_acl+0x44a) [0x4c435a]
    #8 /usr/sbin/smbd(is_visible_file+0x26e) [0x46e09e]
    #9 /usr/sbin/smbd [0x46e620]
    #10 /usr/sbin/smbd(dptr_ReadDirName+0x54) [0x46e694]
    #11 /usr/sbin/smbd [0x4a54e4]
    #12 /usr/sbin/smbd [0x4a8b13]
    #13 /usr/sbin/smbd(handle_trans2+0x1be) [0x4a92ae]
    #14 /usr/sbin/smbd(reply_trans2+0x6ea) [0x4afc6a]
    #15 /usr/sbin/smbd [0x4c87ce]
    #16 /usr/sbin/smbd(smbd_process+0x7e2) [0x4c9bc2]
    #17 /usr/sbin/smbd(main+0x8cd) [0x6c5fad]
    #18 /lib/libc.so.6(__libc_start_main+0xf4) [0x7f97b2f641c4]
    #19 /usr/sbin/smbd [0x45a899]
[2009/01/09 08:17:14, 0] lib/util.c:smb_panic(1638)
   smb_panic(): calling panic action [/usr/share/samba/panic-action 2141]
[2009/01/09 08:17:14, 0] lib/util.c:smb_panic(1646)
   smb_panic(): action returned status 0
[2009/01/09 08:17:14, 0] lib/fault.c:dump_core(181)
   dumping core in /var/log/samba/cores/smbd
[2009/01/09 08:17:14, 1] smbd/service.c:make_connection_snum(1033)
   10.0.0.203 (10.0.0.203) connect to service webtech initially as user
kmatthews (uid=10009, gid=1009) (pid 2155)
[2009/01/09 08:17:14, 0] lib/util_sec.c:set_effective_uid(205)
   setresuid failed with EAGAIN. uid(10009) might be over its NPROC limit
[2009/01/09 08:17:14, 0] lib/util_sec.c:assert_uid(101)
   Failed to set uid privileges to (-1,10009) now set to (0,0)
[2009/01/09 08:17:14, 0] lib/util.c:smb_panic(1633)
   PANIC (pid 2155): failed to set uid

The line "uid(10009) might be over its NPROC limit"looks interesting.

Keith
--
Theme Group
3 & 4 Grove Park
Waltham Road
White Waltham
MAIDENHEAD
Berkshire
England
SL6 3LW

E: <email address hidden>
T: +44 (0) 1628 829090
F: +44 (0) 1628 828877
I: +44 (0) 1628 828899

http://www.themegroup.com <http://www.themegroup.com/>

----------------------------------------------------------------------------
Theme Group is a wholly owned trading style of This & That '95 Limited.
Registered in England No: 3092394 at 7/8 Eghams Court, Boston Drive, Bourne
End, Buckinghamshire. SL8 5YS.
----------------------------------------------------------------------------
This message and its attached file(s), is strictly confidential and intended
solely for the person whom it is addressed. It may contain personal and
confidential information and as such may be protected by the Data Protection
Act 1998. If you received this message in error, you must not copy,
distribute or take any action in reliance on it. Please notify us as soon
as possible and delete it and any attached files from your system. Any views
expressed in this communication may not necessarily be the views held by
Theme Group. As Internet communications are not secure we do not accept
legal responsibility for the contents of this message nor responsibility for
any change made to this message after the original sender sent it. Although
we have taken steps to ensure that this email and attachments are free from
any virus, we advise that in keeping with good computer practice the
recipient should ensure they are actually virus free. We advise you to
carry out your own virus check before opening any attachment, as Theme Group
is not liable for any loss or damage arising in any way from this message or
its attachments. Thank you for taking the time to read this as it may have
been a complete waste of your time. Very few people bother to read these
things but it proves how special you are 'cause you have, so thanks again.
Please take time to read our terms and conditions at
www.themegroup.co.uk/terms.pdf
<blocked::blocked::">http://www.themegroup.co.uk/terms.pdf>
<http://www.themegroup.co.uk/terms.pdf>

---------------------------------------------------------------------------