samba - Mar 2016 - Samba AD/DC crashed again, third time in as many months

I do have the 4.3.3 sources.  The only configure flag i set was
--enable-debug.  I can execute that install, however the issue of unwanted
libs still lingers.  I'm confused, is it or is it not an issue that i have
libtld, libtalloc and pytalloc libs in /usr/lib?  And if it is an issue
whats the best path forward to resolve it?

JS
On Mar 3, 2016 2:59 PM, "Marc Muehlfeld" <mmuehlfeld at
samba.org> wrote:
> Hello,
>
> Am 03.03.2016 um 01:08 schrieb IT Admin:
> > I added "log level = 10" to my smb.conf, the new log is
here:
> > http://www.anonpaste.net/?p=f1ec8
>
> Do you still have the compiled sources or can re-compile the 4.3.3
> sources with the same ./configure parameters? If yes, do an "make
> install" over your existing installation and see what happens.
>
> Regards,
> Marc
>

On 03/03/16 20:33, IT Admin wrote:
> I do have the 4.3.3 sources.  The only configure flag i set was
> --enable-debug.  I can execute that install, however the issue of unwanted
> libs still lingers.  I'm confused, is it or is it not an issue that i
have
> libtld, libtalloc and pytalloc libs in /usr/lib?  And if it is an issue
> whats the best path forward to resolve it?
>
> JS
>
No, I don't think it is a problem, except for libtld and that is only 
because I have never heard of it :-)     Do you mean libldb ?

My debian server running 4.3.1:

locate libldb
/usr/lib/x86_64-linux-gnu/libldb.so.1
/usr/lib/x86_64-linux-gnu/libldb.so.1.1.17

/usr/local/samba/lib/private/libldb.so.1
/usr/local/samba/lib/private/libldb.so.1.1.21

locate libtalloc
/usr/lib/x86_64-linux-gnu/libtalloc.so.2
/usr/lib/x86_64-linux-gnu/libtalloc.so.2.1.1

/usr/local/samba/lib/private/libtalloc.so.2
/usr/local/samba/lib/private/libtalloc.so.2.1.3

locate pytalloc
/usr/lib/x86_64-linux-gnu/libpytalloc-util.so.2
/usr/lib/x86_64-linux-gnu/libpytalloc-util.so.2.1.1

/usr/local/samba/lib/private/libpytalloc-util.so.2
/usr/local/samba/lib/private/libpytalloc-util.so.2.1.3

Rowland

Ha!  That should be libtdb:

/usr/lib/x86_64-linux-gnu/libtdb.so.1
/usr/lib/x86_64-linux-gnu/libtdb.so.1.3.5
/usr/lib/x86_64-linux-gnu/samba/libtdb-wrap.so.0
/usr/lib/x86_64-linux-gnu/samba/libtdb_compat.so.0
/usr/local/samba/lib/private/libtdb-wrap-samba4.so
/usr/local/samba/lib/private/libtdb.so.1
/usr/local/samba/lib/private/libtdb.so.1.3.7

Sorry for the typo, I compose most of my replies on my phone in the car as
this case pertains to work I do outside the scope of my primary source of
employment.

Ok, if Rowland says they aren't an issue then I'm moving forward. 
I'll
recompile 4.3.3 and overwrite my existing install, then fire up samba and
see what happens.  My guess is it fails all over itself at which point I'll
make sure samba process is stopped and follow the restore guidelines in the
wiki to restore an older copy of the database.  Fingers crossed I can raise
this thing from the dead.

Thanks again everyone, really appreciate the community stepping up to help
out.

JS
On Mar 3, 2016 4:02 PM, "Rowland penny" <rpenny at samba.org>
wrote:
> On 03/03/16 20:33, IT Admin wrote:
>
>> I do have the 4.3.3 sources.  The only configure flag i set was
>> --enable-debug.  I can execute that install, however the issue of
unwanted
>> libs still lingers.  I'm confused, is it or is it not an issue that
i have
>> libtld, libtalloc and pytalloc libs in /usr/lib?  And if it is an issue
>> whats the best path forward to resolve it?
>>
>> JS
>>
>>
> No, I don't think it is a problem, except for libtld and that is only
> because I have never heard of it :-)     Do you mean libldb ?
>
> My debian server running 4.3.1:
>
> locate libldb
> /usr/lib/x86_64-linux-gnu/libldb.so.1
> /usr/lib/x86_64-linux-gnu/libldb.so.1.1.17
>
> /usr/local/samba/lib/private/libldb.so.1
> /usr/local/samba/lib/private/libldb.so.1.1.21
>
> locate libtalloc
> /usr/lib/x86_64-linux-gnu/libtalloc.so.2
> /usr/lib/x86_64-linux-gnu/libtalloc.so.2.1.1
>
> /usr/local/samba/lib/private/libtalloc.so.2
> /usr/local/samba/lib/private/libtalloc.so.2.1.3
>
> locate pytalloc
> /usr/lib/x86_64-linux-gnu/libpytalloc-util.so.2
> /usr/lib/x86_64-linux-gnu/libpytalloc-util.so.2.1.1
>
> /usr/local/samba/lib/private/libpytalloc-util.so.2
> /usr/local/samba/lib/private/libpytalloc-util.so.2.1.3
>
> Rowland
>
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba
>

Could I get some input regarding restoring ACLs?  There's nothing in the
Samba wiki about what to do with the ACL archive.  I've finished all of the
other steps already, what do I need to do to restore this archive?

JS
On Mar 3, 2016 4:02 PM, "Rowland penny" <rpenny at samba.org>
wrote:
> On 03/03/16 20:33, IT Admin wrote:
>
>> I do have the 4.3.3 sources.  The only configure flag i set was
>> --enable-debug.  I can execute that install, however the issue of
unwanted
>> libs still lingers.  I'm confused, is it or is it not an issue that
i have
>> libtld, libtalloc and pytalloc libs in /usr/lib?  And if it is an issue
>> whats the best path forward to resolve it?
>>
>> JS
>>
>>
> No, I don't think it is a problem, except for libtld and that is only
> because I have never heard of it :-)     Do you mean libldb ?
>
> My debian server running 4.3.1:
>
> locate libldb
> /usr/lib/x86_64-linux-gnu/libldb.so.1
> /usr/lib/x86_64-linux-gnu/libldb.so.1.1.17
>
> /usr/local/samba/lib/private/libldb.so.1
> /usr/local/samba/lib/private/libldb.so.1.1.21
>
> locate libtalloc
> /usr/lib/x86_64-linux-gnu/libtalloc.so.2
> /usr/lib/x86_64-linux-gnu/libtalloc.so.2.1.1
>
> /usr/local/samba/lib/private/libtalloc.so.2
> /usr/local/samba/lib/private/libtalloc.so.2.1.3
>
> locate pytalloc
> /usr/lib/x86_64-linux-gnu/libpytalloc-util.so.2
> /usr/lib/x86_64-linux-gnu/libpytalloc-util.so.2.1.1
>
> /usr/local/samba/lib/private/libpytalloc-util.so.2
> /usr/local/samba/lib/private/libpytalloc-util.so.2.1.3
>
> Rowland
>
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba
>