Crash on the usual server again.
This time I found log entries as well:
Crash (26-Nov-2008 05:33):
[Thread debugging using libthread_db enabled]
[New Thread 0xb7b626d0 (LWP 8280)]
0xb7d628fe in waitpid () from /lib/libc.so.6
#0 0xb7d628fe in waitpid () from
Crashes are also occurring on a different host in a different Windows domain,
but running the same packages.
However the problem is usually rare on this one.
But I've had two recent crashes so I figured I'd send the details through.
Crash 1. (19-Nov-2008 16:00)
[Thread debugging using
Winbind still panics after upgrading to the latest Samba packages.
The panic dump from yesterday is as follows:
[Thread debugging using libthread_db enabled]
[New Thread 0xb7af16d0 (LWP 31075)]
0xb7cf18fe in waitpid () from /lib/libc.so.6
#0 0xb7cf18fe in waitpid
The panic seems to be mostly resolved now.
I used to get this at least once a day, but somewhere along the line, it
changed.
However the panics aren't solved. I've had a couple. They look different though
so could be due to a different bug?
My most recent occurred on 05 Oct 2008 and it looks
Hi again.
As of last night the packages are now as follows:
ii ldap-utils 2.4.10-3OpenLDAP utilities
ii libldap-2.4-2 2.4.10-3OpenLDAP libraries
ii libldap-2.4-2-dbg 2.4.10-3Debugging
Hi again.
Some new and hopefully useful information.
I've upgraded to the latest LDAP libraries in testing and also decided to add
the debug package for LDAP so see if it reveals anything.
Packages are now as follows:
ii ldap-utils 2.4.10-3OpenLDAP
Last night I upgraded to the following packages:
ii ldap-utils 2.4.10-2+lenny1 OpenLDAP utilities
ii libldap-2.4-2 2.4.10-2+lenny1 OpenLDAP libraries
ii libwbclient02:3.2.0-4 client library for
On Tue, Jul 22, 2008 at 10:06:38AM +0800, Jim Barber wrote:
I've now upgraded to the following related packages:
ii samba 2:3.0.31-1 a
LanManager-like file and printer server for Unix
ii samba-common2:3.0.31-1
I've now upgraded to the following related packages:
ii ldap-utils 2.4.10-2+lenny1 OpenLDAP
utilities
ii libldap-2.4-2 2.4.10-2+lenny1 OpenLDAP
libraries
ii samba 2:3.0.31-1
The output from log.winbindd for one of the crashes last night follows.
I grabbed a few lines earlier, although I'm not sure they are relevant.
Do I need to increase the logging level for winbind to be above 4?
[2008/07/15 08:57:06, 3]
nsswitch/winbindd_misc.c:winbindd_interface_version(491)
Steve Langasek wrote:
Aha, well, that handily answers the question of which of the three assert
statements in ldap_parse_result() is being hit.
And essentially, this points to a failure in ldap_search_ext_s(), because
this function isn't returning an error but is returning a NULL res value
Jim Barber wrote:
There seems to be gaps in the timestamps in these files for some reason.
Oh, I've found the problem with the logs.
I had 'max log size = 1000' defined in /etc/samba/smb.conf (the default value).
The log.winbind file is reaching this size every hour with the debug level 4
Hi.
I've upgraded to the new version and also installed the samba-dbg package this
time.
No changes were made to the Samba configuration.
The LDAP libraries were also updated.
I still experience crashes.
The versions of packages that have changed since the previous list are as
follows:
ii
I've got a couple more stack dumps from today as well that look a little
different.
Is it worth sending them through as well?
Once if very similar except for slight variations in a number of the hex values.
But at step #18 a different path down the functions calls happens.
So I'll paste that.
severity 484235 important
thanks
Quoting root ([EMAIL PROTECTED]):
Package: winbind
Version: 1:3.0.28a-3
Severity: critical
Justification: breaks unrelated software
Sorry, that's overestimated.
winbind and samba works for dozens of users all around so that bug
does not deserve that
Christian Perrier wrote:
Severity: critical
Justification: breaks unrelated software
Sorry, that's overestimated.
Okay sorry about the overstated severity.
I was going to put it in as 'normal' but I followed the descriptions from
reportbug which mislead me.
When this breaks, packages like
16 matches
Mail list logo