Re: [Samba] smbd PANIC at privileges

2011-10-19 Thread Jeremy Allison 
On Wed, Oct 19, 2011 at 03:06:53PM -0400, Matthew Daubenspeck wrote:
> I've had a lprng/samba print server for (literally) years that has just
> worked perfectly. Everything is setup with full guest printing, mainly
> to make our lives here a little easier.
> 
> I had to migrate the machine from one physical server to another and I
> just basically copied the lprng printcap and smb.conf file to the new
> server, restarted the services, and everything seems to be working.
> 
> However, I get a TON of the following messages:
> 
> Oct 19 15:05:23 hal smbd[5216]: [2011/10/19 15:05:23.518393,  0]
> lib/privileges.c:67(get_privileges)
> Oct 19 15:05:23 hal smbd[5216]:   PANIC: assert failed at
> lib/privileges.c(67): data.dsize == sizeof( SE_PRIV )
> Oct 19 15:05:41 hal smbd[5223]: [2011/10/19 15:05:41.347537,  0]
> lib/privileges.c:67(get_privileges)
> Oct 19 15:05:41 hal smbd[5223]:   PANIC: assert failed at
> lib/privileges.c(67): data.dsize == sizeof( SE_PRIV )
> 
> Any ideas? I googled and couldn't really find anything that didn't just
> consist of source code pushes and stuff, nothing that helps
> troubleshoot.

Your priviliges tdb isn't correct for the platform you're running on.

Just delete it and restart.

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

[Samba] smbd PANIC at privileges

2011-10-19 Thread Matthew Daubenspeck 
I've had a lprng/samba print server for (literally) years that has just
worked perfectly. Everything is setup with full guest printing, mainly
to make our lives here a little easier.

I had to migrate the machine from one physical server to another and I
just basically copied the lprng printcap and smb.conf file to the new
server, restarted the services, and everything seems to be working.

However, I get a TON of the following messages:

Oct 19 15:05:23 hal smbd[5216]: [2011/10/19 15:05:23.518393,  0]
lib/privileges.c:67(get_privileges)
Oct 19 15:05:23 hal smbd[5216]:   PANIC: assert failed at
lib/privileges.c(67): data.dsize == sizeof( SE_PRIV )
Oct 19 15:05:41 hal smbd[5223]: [2011/10/19 15:05:41.347537,  0]
lib/privileges.c:67(get_privileges)
Oct 19 15:05:41 hal smbd[5223]:   PANIC: assert failed at
lib/privileges.c(67): data.dsize == sizeof( SE_PRIV )

Any ideas? I googled and couldn't really find anything that didn't just
consist of source code pushes and stuff, nothing that helps
troubleshoot.

I'm using samba 3.5.9, however, an upgrade to samba-3.6.0 didn't make a
difference, other then break some XP printing, etc.

-- 
  Matthew Daubenspeck

Gentoo Linux i686 Intel(R) Xeon(R) CPU 5130 @ 2.00GHz
15:03:40 up 104 days, 2:18, 4 users, load average: 0.23, 0.24, 0.19
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

Re: [Samba] smbd: PANIC (pid xxxxx): internal error -- ? causes?

2011-10-05 Thread Linda W 



This what you looking for?

(gdb) where
#0  0x7faa1b6b126e in waitpid () from /lib64/libc.so.6
#1  0x7faa1b64c491 in do_system () from /lib64/libc.so.6
#2  0x7faa1dba319a in smb_panic ()
#3  0x7faa1db93996 in sig_fault ()
#4  
#5  0x7faa1b654f54 in vfprintf () from /lib64/libc.so.6
#6  0x7faa1b67bea2 in vsnprintf () from /lib64/libc.so.6
#7  0x7faa1b65c3c3 in snprintf () from /lib64/libc.so.6
#8  0x7faa1db92e54 in dbghdrclass ()
#9  0x7faa1a166dcd in recycle_unlink ()
  from /usr/lib64/samba/vfs/recycle.so
#10 0x7faa1d9b9c36 in smb_vfs_call_unlink ()
#11 0x7faa1d9b50ca in close_file ()
#12 0x7faa1d98cfc5 in reply_close ()
#13 0x7faa1d9c94e8 in switch_message ()
#14 0x7faa1d9c970d in process_smb ()
#15 0x7faa1d9c9f02 in smbd_server_connection_handler ()
#16 0x7faa1dbb233b in run_events ()
#17 0x7faa1d9cb0d8 in smbd_process ()
#18 0x7faa1de68d85 in smbd_accept_connection ()
#19 0x7faa1dbb233b in run_events ()
#20 0x7faa1dbb2497 in s3_event_loop_once ()
#21 0x7faa1dbb2e20 in _tevent_loop_once ()
#22 0x7faa1de69fed in main ()

also had a bunch of these in messages log (not samba logs), but despite 
the claim on the
final line -- it wasn't dumping core (at least not where it said it 
was...maybe I'll find

a core stash someday...) ;-)


Oct  3 11:13:01 Ishtar smbd[16169]: [2011/10/03 11:13:01,  0] 
lib/fault.c:46(fault_report)
Oct  3 11:13:01 Ishtar smbd[16169]:   
===
Oct  3 11:13:01 Ishtar smbd[16169]: [2011/10/03 11:13:01,  0] 
lib/fault.c:47(fault_report)
Oct  3 11:13:01 Ishtar smbd[16169]:   INTERNAL ERROR: Signal 11 in pid 16169 
(3.5.11)
Oct  3 11:13:01 Ishtar smbd[16169]:   Please read the Trouble-Shooting section 
of the Samba3-HOWTO
Oct  3 11:13:01 Ishtar smbd[16169]: [2011/10/03 11:13:01,  0] 
lib/fault.c:49(fault_report)
Oct  3 11:13:01 Ishtar smbd[16169]:   
Oct  3 11:13:01 Ishtar smbd[16169]:   From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf

Oct  3 11:13:01 Ishtar smbd[16169]: [2011/10/03 11:13:01,  0] 
lib/fault.c:50(fault_report)
Oct  3 11:13:01 Ishtar smbd[16169]:   
===
Oct  3 11:13:01 Ishtar smbd[16169]: [2011/10/03 11:13:01,  0] 
lib/util.c:1468(smb_panic)
Oct  3 11:13:01 Ishtar smbd[16169]:   PANIC (pid 16169): internal error
Oct  3 11:13:01 Ishtar smbd[16169]: [2011/10/03 11:13:01,  0] 
lib/util.c:1572(log_stack_trace)
Oct  3 11:13:01 Ishtar smbd[16169]:   BACKTRACE: 24 stack frames:
Oct  3 11:13:01 Ishtar smbd[16169]:#0 /usr/sbin/smbd(log_stack_trace+0x1c) 
[0x7f7120093031]
Oct  3 11:13:01 Ishtar smbd[16169]:#1 /usr/sbin/smbd(smb_panic+0x55) 
[0x7f7120093134]
Oct  3 11:13:01 Ishtar smbd[16169]:#2 /usr/sbin/smbd(fault_setup+0) 
[0x7f7120083996]
Oct  3 11:13:01 Ishtar smbd[16169]:#3 /lib64/libc.so.6(+0x32b30) 
[0x7f711db31b30]
Oct  3 11:13:01 Ishtar smbd[16169]:#4 /lib64/libc.so.6(_IO_vfprintf+0x3944) 
[0x7f711db44f54]
Oct  3 11:13:01 Ishtar smbd[16169]:#5 /lib64/libc.so.6(vsnprintf+0xa2) 
[0x7f711db6bea2]
Oct  3 11:13:01 Ishtar smbd[16169]:#6 /lib64/libc.so.6(snprintf+0x83) 
[0x7f711db4c3c3]
Oct  3 11:13:01 Ishtar smbd[16169]:#7 /usr/sbin/smbd(dbghdrclass+0x18c) 
[0x7f7120082e54]
Oct  3 11:13:01 Ishtar smbd[16169]:#8 
/usr/lib64/samba/vfs/recycle.so(+0x2dcd) [0x7f711c3cadcd]
Oct  3 11:13:01 Ishtar smbd[16169]:#9 
/usr/sbin/smbd(smb_vfs_call_unlink+0x29) [0x7f711fea9c36]
Oct  3 11:13:01 Ishtar smbd[16169]:#10 /usr/sbin/smbd(close_file+0x13b4) 
[0x7f711fea50ca]
Oct  3 11:13:01 Ishtar smbd[16169]:#11 /usr/sbin/smbd(reply_close+0x188) 
[0x7f711fe7cfc5]
Oct  3 11:13:01 Ishtar smbd[16169]:#12 /usr/sbin/smbd(+0x16b4e8) 
[0x7f711feb94e8]
Oct  3 11:13:01 Ishtar smbd[16169]:#13 /usr/sbin/smbd(+0x16b70d) 
[0x7f711feb970d]
Oct  3 11:13:01 Ishtar smbd[16169]:#14 /usr/sbin/smbd(+0x16bf02) 
[0x7f711feb9f02]
Oct  3 11:13:01 Ishtar smbd[16169]:#15 /usr/sbin/smbd(run_events+0x25b) 
[0x7f71200a233b]
Oct  3 11:13:01 Ishtar smbd[16169]:#16 /usr/sbin/smbd(smbd_process+0x950) 
[0x7f711febb0d8]
Oct  3 11:13:01 Ishtar smbd[16169]:#17 /usr/sbin/smbd(+0x60ad85) 
[0x7f7120358d85]
Oct  3 11:13:01 Ishtar smbd[16169]:#18 /usr/sbin/smbd(run_events+0x25b) 
[0x7f71200a233b]
Oct  3 11:13:01 Ishtar smbd[16169]:#19 /usr/sbin/smbd(+0x354497) 
[0x7f71200a2497]
Oct  3 11:13:01 Ishtar smbd[16169]:#20 
/usr/sbin/smbd(_tevent_loop_once+0x82) [0x7f71200a2e20]
Oct  3 11:13:01 Ishtar smbd[16169]:#21 /usr/sbin/smbd(main+0x10ec) 
[0x7f7120359fed]
Oct  3 11:13:01 Ishtar smbd[16169]:#22 
/lib64/libc.so.6(__libc_start_main+0xfd) [0x7f711db1dbfd]
Oct  3 11:13:01 Ishtar smbd[16169]:#23 /usr/sbin/smbd(+0xf4ea9) 
[0x7f711fe42ea9]
Oct  3 11:13:01 Ishtar smbd[16169]: [2011/10/03 11:13:01,  0] 
lib/fault.c:326(dump_core)
Oct  3 11:13:01 Ishtar smbd[16169]:   dumping core in /var/log/samba/cores/smbd



[repeated 6 times w/same timest

Re: [Samba] smbd: PANIC (pid xxxxx): internal error -- ? causes?

2011-10-03 Thread Jeremy Allison 
On Mon, Oct 03, 2011 at 05:15:30PM -0700, Linda W wrote:
> Jeremy Allison wrote:
> > On Sun, Oct 02, 2011 at 04:33:12PM -0700, Linda Walsh wrote:
> >   
> >> 
> >> I have a bunch of these in my log...  Was wondering if anyone had seen 
> >> them before
> >> and what the cause might be?  Thanks...
> >>
> >>
> >> Oct  1 03:31:14 Ishtar smbd[24022]:#1 /usr/sbin/smbd(smb_panic+0x55) 
> >> [0x7f7120093134]
> >> Oct  1 03:31:14 Ishtar smbd[24164]: [2011/10/01 03:31:14,  0] 
> >> lib/util.c:1468(smb_panic)
> >> Oct  1 03:31:14 Ishtar smbd[24164]:   PANIC (pid 24164): internal error
> >> Oct  1 03:31:14 Ishtar smbd[24164]:#1 /usr/sbin/smbd(smb_panic+0x55) 
> >> [0x7f7120093134]
> >> Oct  1 03:31:17 Ishtar smbd[24165]: [2011/10/01 03:31:17,  0] 
> >> lib/util.c:1468(smb_panic)
> >> Oct  1 03:31:17 Ishtar smbd[24165]:   PANIC (pid 24165): internal error
> >> Oct  1 03:31:17 Ishtar smbd[24165]:#1 /usr/sbin/smbd(smb_panic+0x55) 
> >> [0x7f7120093134]
> >> 
> >
> > Add the line:
> >
> > panic action = /bin/sleep 999
> >   
> --
> 
> Is it possible to do something like a kill -SIGABRT $$ or $PPID and have
> it gen a core?

Well you don't want to kill -SIGABRT until it's already crashed,
which you don't know until it's already failed.

Adding the "panic action" is definitely the way to go, as the
gdb "bt" on a live (albeit waiting) process captures the entire
callstack showing where (and often why) you got the panic.

As I'm probably going to be the one looking at the backtrace, this is
the way I like to work :-).

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

Re: [Samba] smbd: PANIC (pid xxxxx): internal error -- ? causes?

2011-10-03 Thread Linda W 
Jeremy Allison wrote:
> On Sun, Oct 02, 2011 at 04:33:12PM -0700, Linda Walsh wrote:
>   
>> 
>> I have a bunch of these in my log...  Was wondering if anyone had seen them 
>> before
>> and what the cause might be?  Thanks...
>>
>>
>> Oct  1 03:31:14 Ishtar smbd[24022]:#1 /usr/sbin/smbd(smb_panic+0x55) 
>> [0x7f7120093134]
>> Oct  1 03:31:14 Ishtar smbd[24164]: [2011/10/01 03:31:14,  0] 
>> lib/util.c:1468(smb_panic)
>> Oct  1 03:31:14 Ishtar smbd[24164]:   PANIC (pid 24164): internal error
>> Oct  1 03:31:14 Ishtar smbd[24164]:#1 /usr/sbin/smbd(smb_panic+0x55) 
>> [0x7f7120093134]
>> Oct  1 03:31:17 Ishtar smbd[24165]: [2011/10/01 03:31:17,  0] 
>> lib/util.c:1468(smb_panic)
>> Oct  1 03:31:17 Ishtar smbd[24165]:   PANIC (pid 24165): internal error
>> Oct  1 03:31:17 Ishtar smbd[24165]:#1 /usr/sbin/smbd(smb_panic+0x55) 
>> [0x7f7120093134]
>> 
>
> Add the line:
>
> panic action = /bin/sleep 999
>   
--

Is it possible to do something like a kill -SIGABRT $$ or $PPID and have
it gen a core?



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

Re: [Samba] smbd: PANIC (pid xxxxx): internal error -- ? causes?

2011-10-03 Thread Jeremy Allison 
On Sun, Oct 02, 2011 at 04:33:12PM -0700, Linda Walsh wrote:
> 
> I have a bunch of these in my log...  Was wondering if anyone had seen them 
> before
> and what the cause might be?  Thanks...
> 
> 
> 
> Oct  1 03:25:15 Ishtar smbd[23925]: [2011/10/01 03:25:15,  0] 
> lib/util.c:1468(smb_panic)
> Oct  1 03:25:15 Ishtar smbd[23925]:   PANIC (pid 23925): internal error
> Oct  1 03:25:15 Ishtar smbd[23925]:#1 /usr/sbin/smbd(smb_panic+0x55) 
> [0x7f7120093134]
> Oct  1 03:25:15 Ishtar smbd[23926]: [2011/10/01 03:25:15,  0] 
> lib/util.c:1468(smb_panic)
> Oct  1 03:25:15 Ishtar smbd[23926]:   PANIC (pid 23926): internal error
> Oct  1 03:25:15 Ishtar smbd[23926]:#1 /usr/sbin/smbd(smb_panic+0x55) 
> [0x7f7120093134]
> Oct  1 03:29:49 Ishtar smbd[23927]: [2011/10/01 03:29:49,  0] 
> lib/util.c:1468(smb_panic)
> Oct  1 03:29:49 Ishtar smbd[23927]:   PANIC (pid 23927): internal error
> Oct  1 03:29:49 Ishtar smbd[23927]:#1 /usr/sbin/smbd(smb_panic+0x55) 
> [0x7f7120093134]
> Oct  1 03:29:49 Ishtar smbd[24021]: [2011/10/01 03:29:49,  0] 
> lib/util.c:1468(smb_panic)
> Oct  1 03:29:49 Ishtar smbd[24021]:   PANIC (pid 24021): internal error
> Oct  1 03:29:49 Ishtar smbd[24021]:#1 /usr/sbin/smbd(smb_panic+0x55) 
> [0x7f7120093134]
> Oct  1 03:31:14 Ishtar smbd[24022]: [2011/10/01 03:31:14,  0] 
> lib/util.c:1468(smb_panic)
> Oct  1 03:31:14 Ishtar smbd[24022]:   PANIC (pid 24022): internal error
> Oct  1 03:31:14 Ishtar smbd[24022]:#1 /usr/sbin/smbd(smb_panic+0x55) 
> [0x7f7120093134]
> Oct  1 03:31:14 Ishtar smbd[24164]: [2011/10/01 03:31:14,  0] 
> lib/util.c:1468(smb_panic)
> Oct  1 03:31:14 Ishtar smbd[24164]:   PANIC (pid 24164): internal error
> Oct  1 03:31:14 Ishtar smbd[24164]:#1 /usr/sbin/smbd(smb_panic+0x55) 
> [0x7f7120093134]
> Oct  1 03:31:17 Ishtar smbd[24165]: [2011/10/01 03:31:17,  0] 
> lib/util.c:1468(smb_panic)
> Oct  1 03:31:17 Ishtar smbd[24165]:   PANIC (pid 24165): internal error
> Oct  1 03:31:17 Ishtar smbd[24165]:#1 /usr/sbin/smbd(smb_panic+0x55) 
> [0x7f7120093134]

Add the line:

panic action = /bin/sleep 999

to the [global] section of your smb.conf. Restart Samba. When it
panics again you'll be left with a sleep process whose parent is
the crashed smbd. Attach to this with gdb and get (and post) a
backtrace.

That'll help us track this down and fix it (if it isn't already
fixed).

Thanks,

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

[Samba] smbd: PANIC (pid xxxxx): internal error -- ? causes?

2011-10-02 Thread Linda Walsh 

I have a bunch of these in my log...  Was wondering if anyone had seen them 
before
and what the cause might be?  Thanks...



Oct  1 03:25:15 Ishtar smbd[23925]: [2011/10/01 03:25:15,  0] 
lib/util.c:1468(smb_panic)
Oct  1 03:25:15 Ishtar smbd[23925]:   PANIC (pid 23925): internal error
Oct  1 03:25:15 Ishtar smbd[23925]:#1 /usr/sbin/smbd(smb_panic+0x55) 
[0x7f7120093134]
Oct  1 03:25:15 Ishtar smbd[23926]: [2011/10/01 03:25:15,  0] 
lib/util.c:1468(smb_panic)
Oct  1 03:25:15 Ishtar smbd[23926]:   PANIC (pid 23926): internal error
Oct  1 03:25:15 Ishtar smbd[23926]:#1 /usr/sbin/smbd(smb_panic+0x55) 
[0x7f7120093134]
Oct  1 03:29:49 Ishtar smbd[23927]: [2011/10/01 03:29:49,  0] 
lib/util.c:1468(smb_panic)
Oct  1 03:29:49 Ishtar smbd[23927]:   PANIC (pid 23927): internal error
Oct  1 03:29:49 Ishtar smbd[23927]:#1 /usr/sbin/smbd(smb_panic+0x55) 
[0x7f7120093134]
Oct  1 03:29:49 Ishtar smbd[24021]: [2011/10/01 03:29:49,  0] 
lib/util.c:1468(smb_panic)
Oct  1 03:29:49 Ishtar smbd[24021]:   PANIC (pid 24021): internal error
Oct  1 03:29:49 Ishtar smbd[24021]:#1 /usr/sbin/smbd(smb_panic+0x55) 
[0x7f7120093134]
Oct  1 03:31:14 Ishtar smbd[24022]: [2011/10/01 03:31:14,  0] 
lib/util.c:1468(smb_panic)
Oct  1 03:31:14 Ishtar smbd[24022]:   PANIC (pid 24022): internal error
Oct  1 03:31:14 Ishtar smbd[24022]:#1 /usr/sbin/smbd(smb_panic+0x55) 
[0x7f7120093134]
Oct  1 03:31:14 Ishtar smbd[24164]: [2011/10/01 03:31:14,  0] 
lib/util.c:1468(smb_panic)
Oct  1 03:31:14 Ishtar smbd[24164]:   PANIC (pid 24164): internal error
Oct  1 03:31:14 Ishtar smbd[24164]:#1 /usr/sbin/smbd(smb_panic+0x55) 
[0x7f7120093134]
Oct  1 03:31:17 Ishtar smbd[24165]: [2011/10/01 03:31:17,  0] 
lib/util.c:1468(smb_panic)
Oct  1 03:31:17 Ishtar smbd[24165]:   PANIC (pid 24165): internal error
Oct  1 03:31:17 Ishtar smbd[24165]:#1 /usr/sbin/smbd(smb_panic+0x55) 
[0x7f7120093134]

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

Re: [Samba] smbd PANIC starting PAM

2010-08-27 Thread Robert W. Smith 
I was not able to get it to reproduce yesterday. I will monitor my logs for
the next several days and perform more testing over the weekend.

Bob
--bs

-Original Message-
From: Volker Lendecke [mailto:volker.lende...@sernet.de] 
Sent: August 26, 2010 03:26
To: Robert W. Smith
Cc: samba@lists.samba.org
Subject: Re: [Samba] smbd PANIC starting PAM

On Wed, Aug 25, 2010 at 10:03:05PM -0400, Robert W. Smith wrote:
> Happened to be tail'ing .log during a login session from XP
> client and notice the PANIC in the output. Login proceeded as usual(?)
> so the following snippet of the log is just informational to the
> developers. Let me know if you need additional info.

Is this repeatable? Can you send me your smb.conf and your
relevant pam.conf, together with the exact Samba and pam
module versions you're using?

Volker

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

Re: [Samba] smbd PANIC starting PAM

2010-08-26 Thread Volker Lendecke 
On Wed, Aug 25, 2010 at 10:03:05PM -0400, Robert W. Smith wrote:
> Happened to be tail'ing .log during a login session from XP
> client and notice the PANIC in the output. Login proceeded as usual(?)
> so the following snippet of the log is just informational to the
> developers. Let me know if you need additional info.

Is this repeatable? Can you send me your smb.conf and your
relevant pam.conf, together with the exact Samba and pam
module versions you're using?

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

[Samba] smbd PANIC starting PAM

2010-08-25 Thread Robert W. Smith 
Happened to be tail'ing .log during a login session from XP
client and notice the PANIC in the output. Login proceeded as usual(?)
so the following snippet of the log is just informational to the
developers. Let me know if you need additional info.
Bob
--bs


[2010/08/25 21:34:21.689597,  4] auth/pampass.c:472(smb_pam_start)
  smb_pam_start: PAM: Init user: rwsmith
[2010/08/25 21:34:21.697488,  4] auth/pampass.c:489(smb_pam_start)
  smb_pam_start: PAM: setting rhost to: :::192.168.1.163
[2010/08/25 21:34:21.697629,  4] auth/pampass.c:498(smb_pam_start)
  smb_pam_start: PAM: setting tty
[2010/08/25 21:34:21.697701,  4] auth/pampass.c:506(smb_pam_start)
  smb_pam_start: PAM: Init passed for user: rwsmith
[2010/08/25 21:34:21.697770,  4]
auth/pampass.c:643(smb_internal_pam_session)
  smb_internal_pam_session: PAM: tty set to: smb/12630/100
smbd: pam_mount.c:417: modify_pm_count: Assertion `user != ((void *)0)'
failed.
[2010/08/25 21:34:21.698897,  0] lib/fault.c:46(fault_report)
  ===
[2010/08/25 21:34:21.699240,  0] lib/fault.c:47(fault_report)
  INTERNAL ERROR: Signal 6 in pid 12630 (3.5.4-63.fc13)
  Please read the Trouble-Shooting section of the Samba3-HOWTO
[2010/08/25 21:34:21.699508,  0] lib/fault.c:49(fault_report)
  
  From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
[2010/08/25 21:34:21.699766,  0] lib/fault.c:50(fault_report)
  ===
[2010/08/25 21:34:21.699928,  0] lib/util.c:1465(smb_panic)
  PANIC (pid 12630): internal error
[2010/08/25 21:34:21.705390,  0] lib/util.c:1569(log_stack_trace)
  BACKTRACE: 29 stack frames:
   #0 smbd(log_stack_trace+0x2e) [0x8e4b4e]
   #1 smbd(smb_panic+0x2e) [0x8e4c6e]
   #2 smbd(+0x36f2cf) [0x8d22cf]
   #3 [0x130400]
   #4 [0x130424]
   #5 /lib/libc.so.6(gsignal+0x51) [0xf7fd11]
   #6 /lib/libc.so.6(abort+0x17a) [0xf815ea]
   #7 /lib/libc.so.6(__assert_fail+0xf8) [0xf78d98]
   #8 /lib/security/pam_mount.so(+0x7a8e) [0x10e8a8e]
   #9 /lib/security/pam_mount.so(pam_sm_close_session+0xf2) [0x10e8fe2]
   #10 /lib/libpam.so.0(+0x241f) [0x2ef41f]
   #11 /lib/libpam.so.0(pam_close_session+0x44) [0x2f39f4]
   #12 smbd(+0x3e6a68) [0x949a68]
   #13 smbd(smb_pam_close_session+0xb0) [0x949bd0]
   #14 smbd(session_yield+0xf7) [0x616157]
   #15 smbd(invalidate_vuid+0x41) [0x61cc41]
   #16 smbd(reply_ulogoffX+0x64) [0x643a24]
   #17 smbd(+0x12ac46) [0x68dc46]
   #18 smbd(+0x12b023) [0x68e023]
   #19 smbd(+0x12b5f4) [0x68e5f4]
   #20 smbd(run_events+0x1c1) [0x8f63c1]
   #21 smbd(smbd_process+0xabb) [0x68d07b]
   #22 smbd(+0x6df605) [0xc42605]
   #23 smbd(run_events+0x1c1) [0x8f63c1]
   #24 smbd(+0x39369f) [0x8f669f]
   #25 smbd(_tevent_loop_once+0x98) [0x8f6ce8]
   #26 smbd(main+0xdaa) [0xc4361a]
   #27 /lib/libc.so.6(__libc_start_main+0xe6) [0xf6bcc6]
   #28 smbd(+0x9d3a1) [0x6003a1]
[2010/08/25 21:34:21.708222,  0] lib/fault.c:326(dump_core)
  dumping core in /var/log/samba/cores/smbd
[2010/08/25 21:34:25.081070,  3] smbd/process.c:1485(process_smb)
  Transaction 0 of length 137 (0 toread)
[2010/08/25 21:34:25.081239,  3] smbd/process.c:1294(switch_message)
  switch message SMBnegprot (pid 12634) conn 0x0
[2010/08/25 21:34:25.081319,  3] smbd/sec_ctx.c:310(set_sec_ctx)
  setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
[2010/08/25 21:34:25.081433,  3] smbd/negprot.c:586(reply_negprot)
  Requested protocol [PC NETWORK PROGRAM 1.0]
[2010/08/25 21:34:25.081508,  3] smbd/negprot.c:586(reply_negprot)
  Requested protocol [LANMAN1.0]
[2010/08/25 21:34:25.081579,  3] smbd/negprot.c:586(reply_negprot)
  Requested protocol [Windows for Workgroups 3.1a]
[2010/08/25 21:34:25.081649,  3] smbd/negprot.c:586(reply_negprot)
  Requested protocol [LM1.2X002]
[2010/08/25 21:34:25.081719,  3] smbd/negprot.c:586(reply_negprot)
  Requested protocol [LANMAN2.1]
[2010/08/25 21:34:25.081788,  3] smbd/negprot.c:586(reply_negprot)
  Requested protocol [NT LM 0.12]
[2010/08/25 21:34:25.082252,  3] smbd/negprot.c:404(reply_nt1)
  using SPNEGO
[2010/08/25 21:34:25.082344,  3] smbd/negprot.c:691(reply_negprot)
  Selected protocol NT LM 0.12

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

Re: [Samba] smbd panic - tdb_reopen: file dev/inode has changed!

2010-05-11 Thread Volker Lendecke 
On Tue, May 11, 2010 at 03:25:21PM -0700, Rob Moser wrote:
> # uname -srvo
> Linux 2.6.18-194.el5xen #1 SMP Tue Mar 16 22:01:26 EDT 2010 GNU/Linux
> 
> # cat /etc/redhat-release
> Red Hat Enterprise Linux Server release 5.5 (Tikanga)
> 
> # smbd --version
> Version 3.3.8-0.51.el5
> 
> I'm trying to run a backup samba server using some custom in-house
> scripts which I inherited and am stuck with.  Essentially the primary
> server periodically rsyncs a bunch of files over to the backup,
> including a collection of the tdb files.  When I try to connect to the
> backup server, I get the following smbd panics in the logs:
> 
> -
> [2010/05/11 14:34:32,  0] lib/util_tdb.c:tdb_log(682)
>   tdb(/var/lib/samba/ntforms.tdb): tdb_reopen: file dev/inode has changed!
> [2010/05/11 14:34:32,  0] lib/util.c:reinit_after_fork(1054)
>   tdb_reopen_all failed.

If you are rsync'ing files to a different server, the inode
on the target *does* change. Samba can not cope with that,
you should never just overwrite tdb files in-flight. Please
restart Samba on the backup host after the rsync.

Volker


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

[Samba] smbd panic - tdb_reopen: file dev/inode has changed!

2010-05-11 Thread Rob Moser 
Hi folks,

# uname -srvo
Linux 2.6.18-194.el5xen #1 SMP Tue Mar 16 22:01:26 EDT 2010 GNU/Linux

# cat /etc/redhat-release
Red Hat Enterprise Linux Server release 5.5 (Tikanga)

# smbd --version
Version 3.3.8-0.51.el5

I'm trying to run a backup samba server using some custom in-house
scripts which I inherited and am stuck with.  Essentially the primary
server periodically rsyncs a bunch of files over to the backup,
including a collection of the tdb files.  When I try to connect to the
backup server, I get the following smbd panics in the logs:

-
[2010/05/11 14:34:32,  0] lib/util_tdb.c:tdb_log(682)
  tdb(/var/lib/samba/ntforms.tdb): tdb_reopen: file dev/inode has changed!
[2010/05/11 14:34:32,  0] lib/util.c:reinit_after_fork(1054)
  tdb_reopen_all failed.
[2010/05/11 14:34:32,  0] printing/print_cups.c:cups_pcap_load_async(432)
  cups_pcap_load_async: reinit_after_fork() failed
[2010/05/11 14:34:32,  0] lib/util.c:smb_panic(1673)
  PANIC (pid 28994): cups_pcap_load_async: reinit_after_fork() failed
[2010/05/11 14:34:32,  0] lib/util_tdb.c:tdb_log(682)
  tdb(/var/lib/samba/ntforms.tdb): tdb_reopen: file dev/inode has changed!
[2010/05/11 14:34:32,  0] lib/util.c:reinit_after_fork(1054)
  tdb_reopen_all failed.
[2010/05/11 14:34:32,  0] smbd/server.c:open_sockets_smbd(774)
  reinit_after_fork() failed
[2010/05/11 14:34:32,  0] lib/util.c:smb_panic(1673)
  PANIC (pid 28995): reinit_after_fork() failed
[2010/05/11 14:34:32,  0] lib/util.c:log_stack_trace(1777)
  BACKTRACE: 9 stack frames:
   #0 smbd(log_stack_trace+0x1c) [0x2b49e45a126c]
   #1 smbd(smb_panic+0x2b) [0x2b49e45a134b]
   #2 smbd(cups_cache_reload+0x1b1) [0x2b49e4571d11]
   #3 smbd(pcap_cache_reload+0xb8) [0x2b49e456e6f8]
[2010/05/11 14:34:32,  0] lib/util.c:log_stack_trace(1777)
  BACKTRACE: 5 stack frames:
   #4 smbd(reload_printers+0x25) [0x2b49e47ab3c5]
   #0 smbd(log_stack_trace+0x1c) [0x2b49e45a126c]
   #5 smbd(check_reload+0xe8) [0x2b49e43e7378]
   #1 smbd(smb_panic+0x2b) [0x2b49e45a134b]
   #6 smbd(main+0x1422) [0x2b49e47acee2]
   #2 smbd(main+0x19bf) [0x2b49e47ad47f]
   #7 /lib64/libc.so.6(__libc_start_main+0xf4) [0x2b49e7c3e994]
   #3 /lib64/libc.so.6(__libc_start_main+0xf4) [0x2b49e7c3e994]
   #8 smbd [0x2b49e43717c9]
   #4 smbd [0x2b49e43717c9]
[2010/05/11 14:34:32,  0] lib/fault.c:dump_core(231)
[2010/05/11 14:34:32,  0] lib/fault.c:dump_core(231)
  dumping core in /var/log/samba/cores/smbd
  dumping core in /var/log/samba/cores/smbd
[2010/05/11 14:34:32,  2] printing/print_cups.c:cups_async_callback(544)
  cups_async_callback: failed to read a new printer list
[2010/05/11 14:34:33,  0] lib/util_tdb.c:tdb_log(682)
  tdb(/var/lib/samba/ntforms.tdb): tdb_reopen: file dev/inode has changed!
[2010/05/11 14:34:33,  0] lib/util.c:reinit_after_fork(1054)
  tdb_reopen_all failed.
[2010/05/11 14:34:33,  0] smbd/server.c:open_sockets_smbd(774)
  reinit_after_fork() failed
[2010/05/11 14:34:33,  0] lib/util.c:smb_panic(1673)
  PANIC (pid 28996): reinit_after_fork() failed
[2010/05/11 14:34:33,  0] lib/util.c:log_stack_trace(1777)
  BACKTRACE: 5 stack frames:
   #0 smbd(log_stack_trace+0x1c) [0x2b49e45a126c]
   #1 smbd(smb_panic+0x2b) [0x2b49e45a134b]
   #2 smbd(main+0x19bf) [0x2b49e47ad47f]
   #3 /lib64/libc.so.6(__libc_start_main+0xf4) [0x2b49e7c3e994]
   #4 smbd [0x2b49e43717c9]
[2010/05/11 14:34:33,  0] lib/fault.c:dump_core(231)
  dumping core in /var/log/samba/cores/smbd
-

Uhm... no kidding the inode has changed?  Its on a different machine!
>From scrounging around the web, this looks remarkably similar to https://bugzilla.samba.org/show_bug.cgi?id=5976";>bug 5976, but
a fix for that supposedly went into 3.3.0.  And a reference to a
different patch for it going into 3.3.0 in http://www.mail-archive.com/samba@lists.samba.org/msg98122.html";>the
list archives for this list.  I installed from a non-source package,
so I can't check to see if either patch is there or not.  Still, rather
than re-open a two-year-old bug on the presumption that I am the only
person that its broken for since, I thought I should check and see if
anyone had any insight into it first... any thoughts?  Is it just broken
of these scripts to be trying to move tdb files across machines in the
first place?  If I wipe them clean and just copy the configuration
files, will I keep all of my configuration?

Thanks for any advice,

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

[Samba] smbd panic due to negative exclusive oplock count

2010-02-13 Thread Georges Brom 
Hi,

I'm facing an issue with at least two Samba servers in production both
showing important number of log entries like:

smbd[27355]:   PANIC: assert failed at smbd/oplock.c(149):
exclusive_oplocks_open>=0


Looking at the source code, this panic is triggered when the number of
exclusive oplocks for a given file becomes negative.


Once triggered for one smbd process, this process can generate more than a
million log entries per day, causing both perf and space issues on server
end, and poor perf on client end.

When dying, the smbd process will log this final entry:
smbd[27355]:   respond_to_all_remaining_local_messages: PANIC : we have -1
exclusive oplocks.


This issue has been reproduced on both servers with versions 3.3.9 and
3.3.10 on RHEL 5.4 64bits, not tested with older ones.


A level 10 log extract around a PANIC is like that:

...
[2010/02/08 17:18:14,  5] smbd/uid.c:change_to_user(355)
  change_to_user uid=(0,6195) gid=(0,101)
[2010/02/08 17:18:14,  3] smbd/reply.c:reply_close(4385)
  close fd=61 fnum=8800 (numopen=3)
[2010/02/08 17:18:14,  6] smbd/close.c:set_close_write_time(450)
  close_write_time: Sun Feb  7 07:28:15 2106
[2010/02/08 17:18:14, 10] lib/dbwrap_tdb.c:db_tdb_fetch_locked(100)
  Locking key 0BFD3E85
[2010/02/08 17:18:14, 10] lib/dbwrap_tdb.c:db_tdb_fetch_locked(129)
  Allocated locked data 0x0x2b62c70b6450
[2010/02/08 17:18:14, 10] locking/locking.c:parse_share_modes(519)
  parse_share_modes: delete_on_close: 0, owrt: Sun Jan 10 18:14:29 2010 CET,
cwrt: Thu Jan  1 01:00:00 1970 CET, tok: 0, num_share_modes: 1
[2010/02/08 17:18:14, 10] locking/locking.c:parse_share_modes(616)
  parse_share_modes: share_mode_entry[0]:  pid = 5575, share_access = 0x3,
private_options = 0x40, access_mask = 0x20089, mid = 0x0, type= 0x10, gen_id
= 23508270, uid = 6195, flags = 0, file_id fd0b:5e853e
[2010/02/08 17:18:14, 10] lib/dbwrap_tdb.c:db_tdb_record_destr(42)
  Unlocking key 0BFD3E85
[2010/02/08 17:18:14,  0] smbd/oplock.c:release_file_oplock(149)
  PANIC: assert failed at smbd/oplock.c(149): exclusive_oplocks_open>=0
[2010/02/08 17:18:14, 10] locking/posix.c:get_windows_lock_ref_count(495)
  get_windows_lock_count for file XXX = 0
[2010/02/08 17:18:14, 10] locking/posix.c:delete_windows_lock_ref_count(521)
  delete_windows_lock_ref_count for file 
[2010/02/08 17:18:14,  2] smbd/close.c:close_normal_file(606)
  padcube closed file  (numopen=2) NT_STATUS_OK
[2010/02/08 17:18:14,  5] smbd/files.c:file_free(476)
  freed files structure 8800 (33 used)
[2010/02/08 17:18:14,  5] lib/util.c:show_msg(645)
...

This pattern looks the same for all PANICs, whatever the 'XXX' file
the client is using.


Any help would be greatly appreciated in order to better diagnose this issue
and find a solution to it.


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

Re: [Samba] smbd panic due to negative exclusive oplock count

2010-02-13 Thread Volker Lendecke 
On Sat, Feb 13, 2010 at 12:19:41PM +0100, Georges Brom wrote:
> This issue has been reproduced on both servers with versions 3.3.9 and
> 3.3.10 on RHEL 5.4 64bits, not tested with older ones.
> 
> 
> A level 10 log extract around a PANIC is like that:

We need a *lot* more context to find this. Please open a bug
at bugzilla.samba.org and upload a full debug level 10 log
of smbd leading to this bug.

Please note that the default max log size is far too small
for this kind of debugging, please set it to 0 for this
test. And also note that smbd logfiles due to their
repetitive nature shrink a lot with bzip2 -9 :-)

If you have privacy concerns, feel free to close this bug to
be readable by the Samba-Team only, or alternatively send
the logfile to me directly. If that is not enough, we need
information how to reproduce the bug ourselves.

Thanks,

Volker


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

[Samba] smbd panic due to negative exclusive oplock count

2010-02-13 Thread Georges Brom 
Hi,

I'm facing an issue with at least two Samba servers both showing important
number of log entries like:

smbd[27355]:   PANIC: assert failed at smbd/oplock.c(149):
exclusive_oplocks_open>=0


Looking at the source code, this panic is triggered when the number of
exclusive oplocks for a given file becomes negative.


Once triggered for one smbd process, this process can generate more than a
million log entries per day, causing both perf and space issues on server
end, and poor perf on client end.

When dying, the smbd process will log this final entry:
smbd[27355]:   respond_to_all_remaining_
local_messages: PANIC : we have -1 exclusive oplocks.


This issue has been reproduced on both servers with versions 3.3.9 and
3.3.10 on RHEL 5.4 64bits, not tested with older ones.


A level 10 log extract around a PANIC is like that:

...
[2010/02/08 17:18:14,  5] smbd/uid.c:change_to_user(355)
  change_to_user uid=(0,6195) gid=(0,101)
[2010/02/08 17:18:14,  3] smbd/reply.c:reply_close(4385)
  close fd=61 fnum=8800 (numopen=3)
[2010/02/08 17:18:14,  6] smbd/close.c:set_close_write_time(450)
  close_write_time: Sun Feb  7 07:28:15 2106
[2010/02/08 17:18:14, 10] lib/dbwrap_tdb.c:db_tdb_fetch_locked(100)
  Locking key 0BFD3E85
[2010/02/08 17:18:14, 10] lib/dbwrap_tdb.c:db_tdb_fetch_locked(129)
  Allocated locked data 0x0x2b62c70b6450
[2010/02/08 17:18:14, 10] locking/locking.c:parse_share_modes(519)
  parse_share_modes: delete_on_close: 0, owrt: Sun Jan 10 18:14:29 2010 CET,
cwrt: Thu Jan  1 01:00:00 1970 CET, tok: 0, num_share_modes: 1
[2010/02/08 17:18:14, 10] locking/locking.c:parse_share_modes(616)
  parse_share_modes: share_mode_entry[0]:  pid = 5575, share_access = 0x3,
private_options = 0x40, access_mask = 0x20089, mid = 0x0, type= 0x10, gen_id
= 23508270, uid = 6195, flags = 0, file_id fd0b:5e853e
[2010/02/08 17:18:14, 10] lib/dbwrap_tdb.c:db_tdb_record_destr(42)
  Unlocking key 0BFD3E85
[2010/02/08 17:18:14,  0] smbd/oplock.c:release_file_oplock(149)
  PANIC: assert failed at smbd/oplock.c(149): exclusive_oplocks_open>=0
[2010/02/08 17:18:14, 10] locking/posix.c:get_windows_lock_ref_count(495)
  get_windows_lock_count for file XXX = 0
[2010/02/08 17:18:14, 10] locking/posix.c:delete_windows_lock_ref_count(521)
  delete_windows_lock_ref_count for file 
[2010/02/08 17:18:14,  2] smbd/close.c:close_normal_file(606)
  padcube closed file  (numopen=2) NT_STATUS_OK
[2010/02/08 17:18:14,  5] smbd/files.c:file_free(476)
  freed files structure 8800 (33 used)
[2010/02/08 17:18:14,  5] lib/util.c:show_msg(645)
...

This pattern looks the same for all PANICs, whatever the 'XXX' file
the client is using.


Any help would be greatly appreciated in order to better diagnose this issue
and find a solution to it.


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

Re: [Samba] SMBD panic with INTERNAL ERROR: Signal 6 for ARM 922T

2008-10-17 Thread Jeremy Allison 
On Fri, Oct 17, 2008 at 05:52:48PM -0400, James Ronald wrote:
> On Wed, Oct 15, 2008 at 3:41 PM, Jeremy Allison <[EMAIL PROTECTED]> wrote:
> > On Wed, Oct 15, 2008 at 03:36:06PM -0400, James Ronald wrote:
> >> I am trying to get SAMBA to run on a custom ARM 922T compatible micro
> >> controller.   It does not matter how I try to start smbd (smbd -D -d10
> >> or smbd i -d10) smbd keeps panicking at the same point with an
> >> INTERNAL ERROR: Signal 6.  I have spent over a day trying to figure
> >> out what could be wrong but I am having no success.  If someone could
> >> at least give me a clue as to what smbd is trying to do at this point
> >> it would be greatly appreciated.
> >
> > Can you get a gdb backtrace with symbols on this platform ?
> >
> > Jeremy.
> >
> Jeremy,
> 
> Here are the results from the backtrace.
> 
> # ./gdb-arm
> GNU gdb 6.6
> Copyright (C) 2006 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you are
> welcome to change it and/or distribute copies of it under certain conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB.  Type "show warranty" for details.
> This GDB was configured as "arm-linux-uclibcgnueabi".
> (gdb) file /tmp/sda1/smbd
> Reading symbols from /tmp/sda1/smbd...done.
> Using host libthread_db library "/lib/libthread_db.so.1".
> (gdb)
> (gdb)
> (gdb) attach 374
> Attaching to program: /tmp/sda1/smbd, process 374
> Reading symbols from /lib/libcrypt.so.0...done.
> Loaded symbols for /lib/libcrypt.so.0
> Reading symbols from /lib/libresolv.so.0...done.
> Loaded symbols for /lib/libresolv.so.0
> Reading symbols from /lib/libdl.so.0...done.
> Loaded symbols for /lib/libdl.so.0
> Reading symbols from /lib/libgcc_s.so.1...done.
> Loaded symbols for /lib/libgcc_s.so.1
> Reading symbols from /lib/libc.so.0...done.
> Loaded symbols for /lib/libc.so.0
> Reading symbols from /lib/ld-uClibc.so.0...done.
> Loaded symbols for /lib/ld-uClibc.so.0
> 0x4005ddd4 in wait4 () from /lib/libc.so.0
> (gdb) tb
> Breakpoint 1 at 0x4005ddd4
> (gdb) bt
> #0  0x4005ddd4 in wait4 () from /lib/libc.so.0
> #1  0x40084964 in system () from /lib/libc.so.0
> #2  0x001e5d20 in smb_panic (why=0x2d7930 "internal error") at lib/util.c:1639
> Backtrace stopped: frame did not save the PC
> (gdb)

Oh, that's really not helping much - looks like the
stack frame is broken, so no way to tell why or where
it crashed.

Run with debug level 10 under gdb so at least we see
the last debug statement was. Then maybe you can
set breakpoints to catch the crashing function.

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

Re: [Samba] SMBD panic with INTERNAL ERROR: Signal 6 for ARM 922T

2008-10-17 Thread James Ronald 
On Wed, Oct 15, 2008 at 3:41 PM, Jeremy Allison <[EMAIL PROTECTED]> wrote:
> On Wed, Oct 15, 2008 at 03:36:06PM -0400, James Ronald wrote:
>> I am trying to get SAMBA to run on a custom ARM 922T compatible micro
>> controller.   It does not matter how I try to start smbd (smbd -D -d10
>> or smbd i -d10) smbd keeps panicking at the same point with an
>> INTERNAL ERROR: Signal 6.  I have spent over a day trying to figure
>> out what could be wrong but I am having no success.  If someone could
>> at least give me a clue as to what smbd is trying to do at this point
>> it would be greatly appreciated.
>
> Can you get a gdb backtrace with symbols on this platform ?
>
> Jeremy.
>
Jeremy,

Here are the results from the backtrace.

# ./gdb-arm
GNU gdb 6.6
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "arm-linux-uclibcgnueabi".
(gdb) file /tmp/sda1/smbd
Reading symbols from /tmp/sda1/smbd...done.
Using host libthread_db library "/lib/libthread_db.so.1".
(gdb)
(gdb)
(gdb) attach 374
Attaching to program: /tmp/sda1/smbd, process 374
Reading symbols from /lib/libcrypt.so.0...done.
Loaded symbols for /lib/libcrypt.so.0
Reading symbols from /lib/libresolv.so.0...done.
Loaded symbols for /lib/libresolv.so.0
Reading symbols from /lib/libdl.so.0...done.
Loaded symbols for /lib/libdl.so.0
Reading symbols from /lib/libgcc_s.so.1...done.
Loaded symbols for /lib/libgcc_s.so.1
Reading symbols from /lib/libc.so.0...done.
Loaded symbols for /lib/libc.so.0
Reading symbols from /lib/ld-uClibc.so.0...done.
Loaded symbols for /lib/ld-uClibc.so.0
0x4005ddd4 in wait4 () from /lib/libc.so.0
(gdb) tb
Breakpoint 1 at 0x4005ddd4
(gdb) bt
#0  0x4005ddd4 in wait4 () from /lib/libc.so.0
#1  0x40084964 in system () from /lib/libc.so.0
#2  0x001e5d20 in smb_panic (why=0x2d7930 "internal error") at lib/util.c:1639
Backtrace stopped: frame did not save the PC
(gdb)
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

Re: [Samba] SMBD panic with INTERNAL ERROR: Signal 6 for ARM 922T

2008-10-15 Thread Jeremy Allison 
On Wed, Oct 15, 2008 at 03:36:06PM -0400, James Ronald wrote:
> I am trying to get SAMBA to run on a custom ARM 922T compatible micro
> controller.   It does not matter how I try to start smbd (smbd -D -d10
> or smbd i -d10) smbd keeps panicking at the same point with an
> INTERNAL ERROR: Signal 6.  I have spent over a day trying to figure
> out what could be wrong but I am having no success.  If someone could
> at least give me a clue as to what smbd is trying to do at this point
> it would be greatly appreciated.

Can you get a gdb backtrace with symbols on this platform ?

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

[Samba] SMBD panic with INTERNAL ERROR: Signal 6 for ARM 922T

2008-10-15 Thread James Ronald 
I am trying to get SAMBA to run on a custom ARM 922T compatible micro
controller.   It does not matter how I try to start smbd (smbd -D -d10
or smbd i -d10) smbd keeps panicking at the same point with an
INTERNAL ERROR: Signal 6.  I have spent over a day trying to figure
out what could be wrong but I am having no success.  If someone could
at least give me a clue as to what smbd is trying to do at this point
it would be greatly appreciated.

Thanks,
Jim Ronald


=
# testparm
Load smb config files from /etc/samba/smb.conf
Processing section "[Share]"
Loaded services file OK.
Server role: ROLE_STANDALONE
Press enter to see a dump of your service definitions

[global]
netbios name = Server
netbios aliases = Server0
server string = Server
interfaces = 192.168.0.200/255.255.255.0
security = SHARE
null passwords = Yes
smb passwd file = /etc/smbpasswd
guest account = root
log level = 10
log file = /var/log/samba.log
max log size = 100
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
load printers = No
os level = 0
preferred master = No
fake oplocks = Yes
magic script = automagic.run

[Share]
comment = File Share
path = /tmp
username = root
read only = No
create mask = 0776
directory mask = 0770
===
# smbd -i -d10
Maximum core file size limits now 16777216(soft) -1(hard)
get_current_groups: user is in 2 groups: 0, 10
smbd version 3.0.28a started.
Copyright Andrew Tridgell and the Samba Team 1992-2008
uid=0 gid=0 euid=0 egid=0
Build environment:
   Built by:[EMAIL PROTECTED]
   Built on:Wed Oct 15 13:37:49 EDT 2008
   Built using:
/home/jronald/phoenix/trunk/buildroot-21758/build_arm/staging_dir/usr/bin/arm-linux-uclibcgnueabi-gcc
   Build host:  Linux jronald-desktop 2.6.24-21-generic #1 SMP Mon Aug
25 17:32:09 UTC 2008 i686 GNU/Linux
   SRCDIR:
/home/jronald/phoenix/trunk/buildroot-21758/build_arm/samba-3.0.28a/source
   BUILDDIR:
/home/jronald/phoenix/trunk/buildroot-21758/build_arm/samba-3.0.28a/source

Paths:
   SBINDIR: /usr/local/samba/sbin
   BINDIR: /usr/local/samba/bin
   SWATDIR: /usr/local/samba/swat
   CONFIGFILE: /etc/samba/smb.conf
   LOGFILEBASE: /var/log/samba
   LMHOSTSFILE: /etc/samba/lmhosts
   LIBDIR: /usr/local/samba/lib
   SHLIBEXT: so
   LOCKDIR: /var/cache/samba
   PIDDIR: /var/run
   SMB_PASSWD_FILE: /etc/samba/smbpasswd
   PRIVATE_DIR: /etc/samba

 System Headers:
   HAVE_SYS_CDEFS_H
   HAVE_SYS_FCNTL_H
   HAVE_SYS_IOCTL_H
   HAVE_SYS_IPC_H
   HAVE_SYS_MMAN_H
   HAVE_SYS_MOUNT_H
   HAVE_SYS_PARAM_H
   HAVE_SYS_PRCTL_H
   HAVE_SYS_QUOTA_H
   HAVE_SYS_RESOURCE_H
   HAVE_SYS_SELECT_H
   HAVE_SYS_SHM_H
   HAVE_SYS_SOCKET_H
   HAVE_SYS_STATFS_H
   HAVE_SYS_STATVFS_H
   HAVE_SYS_STAT_H
   HAVE_SYS_SYSCALL_H
   HAVE_SYS_SYSLOG_H
   HAVE_SYS_SYSMACROS_H
   HAVE_SYS_TIME_H
   HAVE_SYS_TYPES_H
   HAVE_SYS_UIO_H
   HAVE_SYS_UNISTD_H
   HAVE_SYS_UN_H
   HAVE_SYS_VFS_H
   HAVE_SYS_WAIT_H
   HAVE_SYS_XATTR_H

 Headers:
   HAVE_ALLOCA_H
   HAVE_ARPA_INET_H
   HAVE_ASM_TYPES_H
   HAVE_ASM_UNISTD_H
   HAVE_CTYPE_H
   HAVE_DIRENT_H
   HAVE_DLFCN_H
   HAVE_FCNTL_H
   HAVE_FLOAT_H
   HAVE_FNMATCH_H
   HAVE_GLOB_H
   HAVE_GRP_H
   HAVE_LANGINFO_H
   HAVE_LASTLOG_H
   HAVE_LIMITS_H
   HAVE_LINUX_INOTIFY_H
   HAVE_LOCALE_H
   HAVE_MEMORY_H
   HAVE_MNTENT_H
   HAVE_NETDB_H
   HAVE_NETINET_IN_H
   HAVE_NETINET_IN_SYSTM_H
   HAVE_NETINET_IP_H
   HAVE_NETINET_TCP_H
   HAVE_NET_IF_H
   HAVE_PWD_H
   HAVE_RPC_RPC_H
   HAVE_SETJMP_H
   HAVE_SHADOW_H
   HAVE_STDARG_H
   HAVE_STDBOOL_H
   HAVE_STDINT_H
   HAVE_STDIO_H
   HAVE_STDLIB_H
   HAVE_STRINGS_H
   HAVE_STRING_H
   HAVE_SYSCALL_H
   HAVE_SYSLOG_H
   HAVE_TERMIOS_H
   HAVE_TERMIO_H
   HAVE_TIME_H
   HAVE_UNISTD_H
   HAVE_UTIME_H

 UTMP Options:
   HAVE_UTMP_H
   HAVE_UT_UT_ADDR
   HAVE_UT_UT_EXIT
   HAVE_UT_UT_HOST
   HAVE_UT_UT_ID
   HAVE_UT_UT_NAME
   HAVE_UT_UT_PID
   HAVE_UT_UT_TIME
   HAVE_UT_UT_TV
   HAVE_UT_UT_TYPE
   HAVE_UT_UT_USER
   PUTUTLINE_RETURNS_UTMP
   WITH_UTMP

 HAVE_* Defines:
   HAVE_ASPRINTF
   HAVE_ASPRINTF_DECL
   HAVE_ATEXIT
   HAVE_BOOL
   HAVE_CHMOD
   HAVE_CHOWN
   HAVE_CHROOT
   HAVE_COMPARISON_FN_T
   HAVE_COMPILER_WILL_OPTIMIZE_OUT_FNS
   HAVE_CONNECT
   HAVE_CREAT64
   HAVE_CRYPT
   HAVE_DECL_ASPRINTF
   HAVE_DECL_RL_EVENT_HOOK
   HAVE_DECL_SNPRINTF
   HAVE_DECL_VASPRINTF
   HAVE_DECL_VSNPRINTF
   HAVE_DIRENT_D_OFF
   HAVE_DLCLOSE
   HAVE_DLERROR
   HAVE_DLOPEN
   HAVE_DLSYM
   HAVE_DUP2
   HAVE_ENDMNTENT
   HAVE_ERRNO_DECL
   HAVE_EXECL
   HAVE_FCHMOD
   HAVE_FCHOWN
   HAVE_FCNTL_LOCK
   HAVE_FGETXATTR
   HAVE_FLISTXATTR
   HAVE_FOPEN64
   HAVE_FREMOVEXATTR
   HAVE_FSEEKO64
   HAVE_FSETXATTR
   HAVE_FSID_INT
   HAVE_FSTAT
   HAVE_FSTAT64
   HAVE_FSYNC
   HAVE_FTELLO64
   HAVE_FTRUNCATE
   HAVE_FTRUNCATE64
   HAVE_FUNCTION_MACRO
   HAVE_GET

Re: [Samba] smbd panic

2007-08-01 Thread Volker Lendecke 
On Wed, Aug 01, 2007 at 02:35:12PM -0300, Walmiro Muzzi wrote:
> Hi Volker.
> 
> Red Hat Enterprise Linux 4
> 
> Samba version 3.0.10-1.4E.12.2

Can you reproduce this with 3.0.25b?

Volker


pgpSiMX1xMKVa.pgp
Description: PGP signature
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

Re: [Samba] smbd panic

2007-08-01 Thread Walmiro Muzzi 

Hi Volker.

Red Hat Enterprise Linux 4

Samba version 3.0.10-1.4E.12.2

My smb.conf:

# Samba config file created using SWAT
# from 0.0.0.0 (0.0.0.0)
# Date: 2007/08/01 10:54:32

# Global parameters
[global]
workgroup = HIDRAUTRONICA
server string = cronos
security = DOMAIN
log file = /var/log/samba/%m.log
max log size = 50
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
printcap name = /etc/printcap
preferred master = No
dns proxy = No
idmap uid = 16777216-33554431
idmap gid = 16777216-33554431
cups options = raw

[printers]
comment = All Printers
path = /var/spool/samba
printable = Yes
browseable = No

[BACKUP]
comment = Compartilhamento para Backup
path = /backup
read only = No
create mask = 0777
directory mask = 0777
guest ok = Yes

[HIDRAUTRONICA]
comment = Compartilhamento
path = /hidrautronica
read only = No
create mask = 0770
directory mask = 0770
guest ok = Yes

[homes]


Thanks.


Sincerely
Walmiro Muzzi

Volker Lendecke escreveu:

On Wed, Aug 01, 2007 at 10:47:35AM -0300, Walmiro Muzzi wrote:

Can somebody explain to me what's goin on with samba???


What's your Unix, what's your Samba version etc. Can you
also please provide your smb.conf and a debug level 10 log
of smbd up to this fault? Please open a bug at
bugzilla.samba.org with that info.

Volker



___ 
Yahoo! Mail - Sempre a melhor opção para você! 
Experimente já e veja as novidades. 
http://br.yahoo.com/mailbeta/tudonovo/

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

Re: [Samba] smbd panic

2007-08-01 Thread Volker Lendecke 
On Wed, Aug 01, 2007 at 10:47:35AM -0300, Walmiro Muzzi wrote:
> Can somebody explain to me what's goin on with samba???

What's your Unix, what's your Samba version etc. Can you
also please provide your smb.conf and a debug level 10 log
of smbd up to this fault? Please open a bug at
bugzilla.samba.org with that info.

Volker


pgpMMIOoVrH1Z.pgp
Description: PGP signature
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

[Samba] smbd panic

2007-08-01 Thread Walmiro Muzzi 

Hi all.


Please.

Can somebody explain to me what's goin on with samba???


Thanks in advance!


Aug  1 10:37:03 cronos smbd[28462]: [2007/08/01 10:37:03, 0] 
lib/substitute.c:alloc_sub_basic(521)
Aug  1 10:37:03 cronos smbd[28462]:   alloc_sub_basic: NULL source 
string!  This should not happen
Aug  1 10:37:03 cronos smbd[28462]: [2007/08/01 10:37:03, 0] 
lib/fault.c:fault_report(36)
Aug  1 10:37:03 cronos smbd[28462]: 
===
Aug  1 10:37:03 cronos smbd[28462]: [2007/08/01 10:37:03, 0] 
lib/fault.c:fault_report(37)
Aug  1 10:37:03 cronos smbd[28462]:   INTERNAL ERROR: Signal 11 in pid 
28462 (3.0.10-1.4E.12.2)
Aug  1 10:37:03 cronos smbd[28462]:   Please read the appendix Bugs of 
the Samba HOWTO collection
Aug  1 10:37:03 cronos smbd[28462]: [2007/08/01 10:37:03, 0] 
lib/fault.c:fault_report(39)
Aug  1 10:37:03 cronos smbd[28462]: 
===
Aug  1 10:37:03 cronos smbd[28462]: [2007/08/01 10:37:03, 0] 
lib/util.c:smb_panic2(1504)

Aug  1 10:37:03 cronos smbd[28462]:   PANIC: internal error
Aug  1 10:37:03 cronos smbd[28462]: [2007/08/01 10:37:03, 0] 
lib/util.c:smb_panic2(1512)

Aug  1 10:37:03 cronos smbd[28462]:   BACKTRACE: 14 stack frames:
Aug  1 10:37:03 cronos smbd[28462]:#0 smbd(smb_panic2+0x8a) [0x4a2640]
Aug  1 10:37:03 cronos smbd[28462]:#1 smbd(smb_panic+0x19) [0x4a286c]
Aug  1 10:37:03 cronos smbd[28462]:#2 smbd [0x48ed8f]
Aug  1 10:37:03 cronos smbd[28462]:#3 /lib/tls/libc.so.6 [0x8cb898]
Aug  1 10:37:03 cronos smbd[28462]:#4 smbd(push_ascii_fstring+0x28) 
[0x48cec1]

Aug  1 10:37:03 cronos smbd[28462]:#5 smbd [0x344e89]
Aug  1 10:37:03 cronos smbd[28462]:#6 smbd(api_reply+0x25e) [0x349f5a]
Aug  1 10:37:03 cronos smbd[28462]:#7 smbd(reply_trans+0x64f) 
[0x3406a1]

Aug  1 10:37:03 cronos smbd[28462]:#8 smbd [0x38b5e2]
Aug  1 10:37:04 cronos smbd[28462]:#9 smbd(process_smb+0x19b) 
[0x38ba1c]
Aug  1 10:37:04 cronos smbd[28462]:#10 smbd(smbd_process+0x15f) 
[0x38c744]

Aug  1 10:37:04 cronos smbd[28462]:#11 smbd(main+0x875) [0x51f057]
Aug  1 10:37:04 cronos smbd[28462]:#12 
/lib/tls/libc.so.6(__libc_start_main+0xd3) [0x8b8de3]

Aug  1 10:37:04 cronos smbd[28462]:#13 smbd [0x32b2d1]
Aug  1 10:37:04 cronos smbd[28462]:
Aug  1 10:37:04 cronos smbd[28463]: [2007/08/01 10:37:04, 0] 
lib/substitute.c:alloc_sub_basic(521)
Aug  1 10:37:04 cronos smbd[28463]:   alloc_sub_basic: NULL source 
string!  This should not happen
Aug  1 10:37:04 cronos smbd[28463]: [2007/08/01 10:37:04, 0] 
lib/fault.c:fault_report(36)
Aug  1 10:37:04 cronos smbd[28463]: 
===
Aug  1 10:37:04 cronos smbd[28463]: [2007/08/01 10:37:04, 0] 
lib/fault.c:fault_report(37)
Aug  1 10:37:04 cronos smbd[28463]:   INTERNAL ERROR: Signal 11 in pid 
28463 (3.0.10-1.4E.12.2)
Aug  1 10:37:04 cronos smbd[28463]:   Please read the appendix Bugs of 
the Samba HOWTO collection
Aug  1 10:37:04 cronos smbd[28463]: [2007/08/01 10:37:04, 0] 
lib/fault.c:fault_report(39)
Aug  1 10:37:04 cronos smbd[28463]: 
===
Aug  1 10:37:04 cronos smbd[28463]: [2007/08/01 10:37:04, 0] 
lib/util.c:smb_panic2(1504)

Aug  1 10:37:04 cronos smbd[28463]:   PANIC: internal error
Aug  1 10:37:04 cronos smbd[28463]: [2007/08/01 10:37:04, 0] 
lib/util.c:smb_panic2(1512)

Aug  1 10:37:04 cronos smbd[28463]:   BACKTRACE: 14 stack frames:
Aug  1 10:37:04 cronos smbd[28463]:#0 smbd(smb_panic2+0x8a) [0x4a2640]
Aug  1 10:37:04 cronos smbd[28463]:#1 smbd(smb_panic+0x19) [0x4a286c]
Aug  1 10:37:04 cronos smbd[28463]:#2 smbd [0x48ed8f]
Aug  1 10:37:04 cronos smbd[28463]:#3 /lib/tls/libc.so.6 [0x8cb898]
Aug  1 10:37:04 cronos smbd[28463]:#4 smbd(push_ascii_fstring+0x28) 
[0x48cec1]

Aug  1 10:37:04 cronos smbd[28463]:#5 smbd [0x344e89]
Aug  1 10:37:04 cronos smbd[28463]:#6 smbd(api_reply+0x25e) [0x349f5a]
Aug  1 10:37:04 cronos smbd[28463]:#7 smbd(reply_trans+0x64f) 
[0x3406a1]

Aug  1 10:37:04 cronos smbd[28463]:#8 smbd [0x38b5e2]
Aug  1 10:37:04 cronos smbd[28463]:#9 smbd(process_smb+0x19b) 
[0x38ba1c]
Aug  1 10:37:04 cronos smbd[28463]:#10 smbd(smbd_process+0x15f) 
[0x38c744]

Aug  1 10:37:04 cronos smbd[28463]:#11 smbd(main+0x875) [0x51f057]
Aug  1 10:37:04 cronos smbd[28463]:#12 
/lib/tls/libc.so.6(__libc_start_main+0xd3) [0x8b8de3]

Aug  1 10:37:04 cronos smbd[28463]:#13 smbd [0x32b2d1]
Aug  1 10:37:04 cronos smbd[28463]:


[]s
Walmiro Muzzi


___ 
Yahoo! Mail - Sempre a melhor opção para você! 
Experimente já e veja as novidades. 
http://br.yahoo.com/mailbeta/tudonovo/



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

Re: [Samba] smbd panic on security = ADS

2006-07-18 Thread Gerald (Jerry) Carter 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Brian Milco wrote:

> I've tried to down grade back to 3.0.14a with no luck, 
> It looks like it might be samba's interaction with libldap
> and or libnss_mdns, both of which I've tried to downgrade
> as well.

This is not our bug. You'll have to contact the
/lib/libnss_mdns.so.2 maintainers.





cheers, jerry
=
Samba--- http://www.samba.org
Centeris ---  http://www.centeris.com
"What man is a man who does not make the world better?"  --Balian
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iD8DBQFEvXfjIR7qMdg1EfYRAt30AKCe2od4W+YCXmBijfdu5efT1FVE3gCgqG2e
WKFpgSs4yMvM7zb8AttsbEs=
=9MgN
-END PGP SIGNATURE-
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

[Samba] smbd panic on security = ADS

2006-07-18 Thread Brian Milco 

I have a samba server that was updated to samba v3.0.22 and is not working.

It is a fileserver for the network, it's a member of the ADS and it was 
working perfectly up until saturday.


It doesn't panic when I change security = ADS to security = server, 
unfortunately I need ADS auth.


I've tried to down grade back to 3.0.14a with no luck, It looks like it 
might be samba's interaction with libldap and or libnss_mdns, both of which 
I've tried to downgrade as well.


Thanks for any help,

Brian

smbd.log:
[2006/07/18 09:22:53, 0] lib/fault.c:fault_report(36)
 ===
[2006/07/18 09:22:53, 0] lib/fault.c:fault_report(37)
 INTERNAL ERROR: Signal 11 in pid 15071 (3.0.22)
 Please read the Trouble-Shooting section of the Samba3-HOWTO
[2006/07/18 09:22:53, 0] lib/fault.c:fault_report(39)

 From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
[2006/07/18 09:22:53, 0] lib/fault.c:fault_report(40)
 ===
[2006/07/18 09:22:53, 0] lib/util.c:smb_panic2(1554)
 PANIC: internal error
[2006/07/18 09:22:53, 0] lib/util.c:smb_panic2(1562)
 BACKTRACE: 25 stack frames:
  #0 /usr/sbin/smbd(smb_panic2+0x78) [0x81ffea8]
  #1 /usr/sbin/smbd(smb_panic+0x19) [0x82000a5]
  #2 /usr/sbin/smbd [0x81ee1b5]
  #3 [0xe420]
  #4 /lib/libnss_mdns.so.2 [0xb77826d3]
  #5 /lib/libnss_mdns.so.2 [0xb7782941]
  #6 /lib/libnss_mdns.so.2(mdns_query_ipv4+0xa7) [0xb7782a24]
  #7 /lib/libnss_mdns.so.2(_nss_mdns_gethostbyaddr_r+0x134) [0xb77840c0]
  #8 /lib/tls/i686/cmov/libc.so.6(gethostbyaddr_r+0x156) [0xb7cdb1f6]
  #9 /lib/tls/i686/cmov/libc.so.6(getnameinfo+0x41c) [0xb7ce328c]
  #10 /usr/lib/libldap_r.so.2(ldap_pvt_get_hname+0x5a) [0xb7f3af24]
  #11 /usr/lib/libldap_r.so.2(ldap_host_connected_to+0x132) [0xb7f36bc9]
  #12 /usr/lib/libldap_r.so.2(ldap_int_open_connection+0x1bb) [0xb7f232a5]
  #13 /usr/lib/libldap_r.so.2(ldap_new_connection+0x7d) [0xb7f34544]
  #14 /usr/lib/libldap_r.so.2(ldap_open_defconn+0x3d) [0xb7f22c71]
  #15 /usr/lib/libldap_r.so.2(ldap_open+0x43) [0xb7f22fa0]
  #16 /usr/sbin/smbd(ldap_open_with_timeout+0x42) [0x8267e51]
  #17 /usr/sbin/smbd(ads_try_connect+0x44) [0x8267f8a]
  #18 /usr/sbin/smbd(ads_connect+0x53d) [0x826dbdf]
  #19 /usr/sbin/smbd(check_published_printers+0xb2) [0x822918c]
  #20 /usr/sbin/smbd(nt_printing_init+0x2e0) [0x822960b]
  #21 /usr/sbin/smbd(print_backend_init+0x148) [0x8218821]
  #22 /usr/sbin/smbd(main+0x3b4) [0x828afc7]
  #23 /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xd2) [0xb7c11ea2]
  #24 /usr/sbin/smbd [0x807ebb1]


(I've sanitized the smb.conf file but it worked perfectly for the last 6 
months to a year as-is.)


[global]
   workgroup = DOMAINGROUP
   realm = DOMAIN.LOCAL
   server string =
   security = ADS
   password server = 192.168.1.10
   log file = /var/log/samba/%m.log
   max log size = 50
   server signing = auto
   socket options = TCP_NODELAY SO_SNDBUF=8192 SO_RCVBUF=8192
   printcap name = /etc/printcap
   preferred master = No
   domain master = No
   dns proxy = No
   ldap ssl = no
   idmap uid = 16777216-33554431
   idmap gid = 16777216-33554431
   cups options = raw

[Documents]
   comment = Documents
   path = /home/Documents
   valid users = "@DOMAIN\domain users", "@DOMAIN\domain admins"
   admin users = "@DOMAIN\domain admins"
   write list = "@DOMAIN\domain users", "@DOMAIN\domain admins"
   read only = No
   create mask = 0770
   directory mask = 0770
   case sensitive = No
   msdfs proxy = no


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

[Samba] smbd panic

2005-09-19 Thread Martin Philipp 
Hello,

 

we installed samba on SUSE SLE9. (Samba version 3.0.9-2.1.5-SUSE)

The log level in smb.conf must be 1 or 255. With other values the smbd crash
with panic. Can you help me?

 

Here the fragment of /var/log/messages with the error:

 

Sep 16 08:52:05 speyer sudo: mphilipp : TTY=pts/0 ; PWD=/home/mphilipp ;
USER=root ; COMMAND=/usr/sbin/rcsmb start

Sep 16 08:52:05 speyer smbd[19437]: [2005/09/16 08:52:05, 0]
lib/fault.c:fault_report(36) 

Sep 16 08:52:05 speyer smbd[19437]:
=== 

Sep 16 08:52:05 speyer smbd[19437]: [2005/09/16 08:52:05, 0]
lib/fault.c:fault_report(37) 

Sep 16 08:52:05 speyer smbd[19437]:   INTERNAL ERROR: Signal 11 in pid 19437
(3.0.9-2.1.5-SUSE) 

Sep 16 08:52:05 speyer smbd[19437]:   Please read the appendix Bugs of the
Samba HOWTO collection 

Sep 16 08:52:05 speyer smbd[19437]: [2005/09/16 08:52:05, 0]
lib/fault.c:fault_report(39) 

Sep 16 08:52:05 speyer smbd[19437]:
=== 

Sep 16 08:52:05 speyer smbd[19437]: [2005/09/16 08:52:05, 0]
lib/util.c:smb_panic2(1488) 

Sep 16 08:52:05 speyer smbd[19437]:   PANIC: internal error 

Sep 16 08:52:05 speyer smbd[19437]: [2005/09/16 08:52:05, 0]
lib/util.c:smb_panic2(1496) 

Sep 16 08:52:05 speyer smbd[19437]:   BACKTRACE: 12 stack frames: 

Sep 16 08:52:05 speyer smbd[19437]:#0 /usr/sbin/smbd(smb_panic2+0x1ec)
[0x81f7065] 

Sep 16 08:52:05 speyer smbd[19437]:#1 /usr/sbin/smbd(smb_panic+0x25)
[0x81f6e73] 

Sep 16 08:52:05 speyer smbd[19437]:#2 /usr/sbin/smbd [0x81e24d7] 

Sep 16 08:52:05 speyer smbd[19437]:#3 /usr/sbin/smbd [0x81e254d] 

Sep 16 08:52:05 speyer smbd[19437]:#4 [0xe420] 

Sep 16 08:52:05 speyer smbd[19437]:#5 /lib/tls/libc.so.6(malloc+0x94)
[0x402f9f84] 

Sep 16 08:52:05 speyer smbd[19437]:#6
/usr/sbin/smbd(bitmap_allocate+0x29) [0x81eb329] 

Sep 16 08:52:05 speyer smbd[19437]:#7
/usr/sbin/smbd(init_rpc_pipe_hnd+0x1e) [0x815f9f7] 

Sep 16 08:52:05 speyer smbd[19437]:#8 /usr/sbin/smbd [0x8276735] 

Sep 16 08:52:05 speyer smbd[19437]:#9 /usr/sbin/smbd(main+0x38e)
[0x8276ada] 

Sep 16 08:52:05 speyer smbd[19437]:#10
/lib/tls/libc.so.6(__libc_start_main+0xe0) [0x402ab260] 

Sep 16 08:52:05 speyer smbd[19437]:#11 /usr/sbin/smbd [0x80796d1] 

Sep 16 08:52:05 speyer smbd[19437]:

 

The smb.conf

 

# Martin Philipp

# Global parameters

 

[global]

 workgroup = CBB

 netbios name = orleons

 server string = Samba orleons

 interfaces =  172.21.211.119/255.255.255.0

 bind interfaces only = yes

 guest account = mfax

 #log level = 255

 log level = 1

 log file = /var/log/samba/log_cbb.%m

 max log size = 50

 max open files = 400

 wins server = 172.16.44.183

 name resolve order = host wins dns

 #dns proxy = No

 #mangled names = No

 security = share

 local master = no

 hosts allow = localhost 172.

 socket options = TCP_NODELAY

 deadtime = 30

 keepalive = 200

 kernel oplocks = no

 #message command = /bin/csh -c 'mailx -s %f root < %s; rm %s' &

 #max xmit = 32768

#

[Massenfax]

   comment = MASSENFAX Austauschverzeichnis

   path = /app/mfax/Massenfax

   public = yes

   case sensitive = no

   writable = yes

   printable = no

   create mode = 755

   guest only = yes

   Max connections = 400

   oplocks = no

   level 2 oplocks = no

##

 

With kind regards

 

Martin Philipp

 

 

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