[Samba] Samba AD/DC crashed again, third time in as many months

[IT Admin]

pytalloc:

/usr/lib/x86_64-linux-gnu/libpytalloc-util.so.2
/usr/lib/x86_64-linux-gnu/libpytalloc-util.so.2.1.2
/usr/local/samba/include/pytalloc.h
/usr/local/samba/lib/private/libpytalloc-util.so.2
/usr/local/samba/lib/private/libpytalloc-util.so.2.1.3

libtalloc:

/usr/lib/x86_64-linux-gnu/libtalloc.so.2
/usr/lib/x86_64-linux-gnu/libtalloc.so.2.1.2
/usr/local/samba/lib/private/libtalloc-report-samba4.so
/usr/local/samba/lib/private/libtalloc.so.2
/usr/local/samba/lib/private/libtalloc.so.2.1.3


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


I also noticed that I've got a log.smbd in /usr/local/samba/var:
http://www.anonpaste.net/?p=bdfa3

JS



On Wed, Mar 2, 2016 at 9:00 PM, Sketch <smblist at rednsx.org> wrote:

> Also check for pytalloc|libtalloc and libtdb.
>
>
> On Wed, 2 Mar 2016, IT Admin wrote:
>
> I poked around the system using locate, I don't think there are any
>> packages installed on this system other than those associated with the
>> 4.3.3 build I compiled.
>>
>> smbd
>>
>> /usr/lib/python2.7/dist-packages/samba/samba3/smbd.so
>> /usr/lib/x86_64-linux-gnu/samba/libsmbd_base.so.0
>> /usr/lib/x86_64-linux-gnu/samba/libsmbd_conn.so.0
>> /usr/lib/x86_64-linux-gnu/samba/libsmbd_shim.so.0
>> /usr/local/samba/lib/private/libsmbd-base-samba4.so
>> /usr/local/samba/lib/private/libsmbd-conn-samba4.so
>> /usr/local/samba/lib/private/libsmbd-shim-samba4.so
>> /usr/local/samba/lib/python2.7/site-packages/samba/samba3/smbd.so
>> /usr/local/samba/private/smbd.tmp
>> /usr/local/samba/sbin/smbd
>> /usr/local/samba/share/man/man8/smbd.8
>> /usr/local/samba/var/log.smbd
>> /usr/local/samba/var/log.smbd.old
>> /usr/local/samba/var/run/smbd.pid
>> /var/log/upstart/smbd.log.1.gz
>>
>> nmbd
>>
>> /usr/local/samba/sbin/nmbd
>> /usr/local/samba/share/man/man8/nmbd.8
>> /var/log/upstart/nmbd.log.1.gz
>>
>> samba
>>
>> /usr/local/samba/sbin/nmbd
>> /usr/local/samba/sbin/samba
>> /usr/local/samba/sbin/samba_dnsupdate
>> /usr/local/samba/sbin/samba_kcc
>> /usr/local/samba/sbin/samba_spnupdate
>> /usr/local/samba/sbin/samba_upgradedns
>> /usr/local/samba/sbin/smbd
>> /usr/local/samba/sbin/winbind
>>
>>
>> If I'm overlooking something obvious please let me know.
>>
>> JS
>>
>> On Wed, Mar 2, 2016 at 5:42 PM, Marc Muehlfeld <mmuehlfeld at samba.org>
>> wrote:
>>
>> Am 02.03.2016 um 18:52 schrieb IT Admin:
>>>
>>>> Samba is compiled from source.
>>>> Samba DB is stored on local RAID array.
>>>> Changes to AD are done using ADUC from a Windows 7 box.
>>>> AD is used for authentication, user shares (folder redirection), and
>>>>
>>> shared
>>>
>>>> folders.
>>>>
>>>
>>> Can you add
>>>   log level = 10
>>> to your smb.conf, empty your log directory and start Samba. It should
>>> generate a new log, that captures all output. Then put it to cpaste.org
>>> or some other paste service and share the link with us. Maybe we see
>>> something interesting.
>>>
>>>
>>> Does something changed when the problem occured the first time? Some
>>> package updates, crashes, etc.?
>>>
>>>
>>> Can you make sure that no kind of Samba package (daemon, libs, etc.) is
>>> installed on the system? Maybe your selfcompiled version overwrites some
>>> stuff and your OS installed an update, that mixes now with the self
>>> compiled version. Just a guess.
>>>
>>> Regards,
>>> Marc
>>>
>>> --
>> To unsubscribe from this list go to the following URL and read the
>> instructions:  https://lists.samba.org/mailman/options/samba
>>
>>
>>