FreeBSD version LDB_0.9.10 requiredby/usr/local/samba/sbin/sambanot defined

[tms3 at tms3.com]

>
> --- Original message ---
> Subject: Re: FreeBSD version LDB_0.9.10 
> requiredby/usr/local/samba/sbin/sambanot defined
> From: <tms3 at tms3.com>
> To: Andrew Bartlett <abartlet at samba.org>,  
> <samba-technical at lists.samba.org>
> Date: Saturday, 11/12/2010  8:02 PM
>
>
>
>
>
> On Saturday 11/12/2010 at 7:47 pm, Andrew Bartlett  wrote:
>>
>> On Sat, 2010-12-11 at 18:04 -0800, tms3 at tms3.com wrote:
>>>
>>>
>>>
>>>
>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On Sat, 2010-12-11 at 15:12 -0800, tms3 at tms3.com wrote:
>>>>>
>>>>>
>>>>>
>>>>> This ones got me flipping puzzled.
>>>>>
>>>>> I have three 8.1 amd64 servers and an 8,2-BETA amd64 server.  One of
>>>>> the 8.1's and the 8.2 run Version 4.0.0alpha14-GIT-6bc6c00 no problem.
>>>>>
>>>>> Two of the 8.1 boxes, which were running the last update I did ~2
>>>>> weeks ago perfectly now say:
>>>>>
>>>>> zaphod# /usr/local/samba/sbin/samba
>>>>> /libexec/ld-elf.so.1: /usr/local/samba/lib/libldb-samba4.so.0: version
>>>>> LDB_0.9.10 required by /usr/local/samba/sbin/samba not defined
>>>>>
>>>>> I can't for the life of me figure out what the heck is out of step
>>>>> between the two that work and the two that don't.  Any pointers,
>>>>> ideas, etc would be greatly appreciated.
>>>>
>>>> If you updated recently, ensure you update again and recompile from
>>>> clean.  There have been some small glitches along the way as we
>>>> migrate
>>>> to using symbol versions.
>>>
>>> OK, so after much fiddling around, I take it that the ldb and tdb
>>> files in /usr/local/samba are the issue. Fine. What do I do to
>>> maintain the domain integrity, if I wipe out the samba directories on
>>> the two broken servers? In other words, I have a functional domain
>>> with multiple servers and workstations attached...how do I restore the
>>> ones that have been rendered dead?
>>
>> Just install Samba on top of the previous installation.  It won't wipe
>> the DBs (as long as you don't provision), and it should just work.
>
> Therein lies the problem. The errors occur when install the latest git 
> to the existing install.  When I back up the old install, delete 
> /usr/local/samba and do a clean install, samba functions (as best as I 
> can tell, at least it doesn't kick out the errors.)
>
> On the PDC, which was NOT working with the latest git, I discovered I 
> had a repository from my previous build backed up.  Recompiling and 
> reinstalling from that repository, I was able to start samba on the 
> PDC.
>
> mithrandir# /usr/local/samba/sbin/samba -V
> Version 4.0.0alpha14-GIT-8428311
>
> A member server:
>
> prism# /usr/local/samba/sbin/samba -V
> Version 4.0.0alpha14-GIT-6bc6c00
>
> Is working with that git.
>
> The third server, when using the old repository, samba starts, but it 
> is non-functional--shares don't work (user pass prob, haven't dug the 
> server logs).  As it was a member server, I shall try and do a clean 
> build and rejoin the domain...although I suspect the meta-data will be 
> messy, and the server name may cause issues.  I am really not sure 
> what to do with the PDC at this point however...
>
> In any event, what would be MOST helpful, is if there is a way to 
> clean up orphaned servers, and seize/move the PDC stuff, as that would 
> really reduce the problems of any given servers data getting damaged, 
> made usuable etc, by updates....if there is a rough description of 
> said controls, I would certainly use them...if they exist yet.

Ah...so, samba-tool for that.  OK, well, that's something to play 
with.
>
>
>
> I really appreciate the responses.
>
> Cheers,
>
>>
>>
>>
>>
>> ie, make backups, but don't remove anything.
>>
>> Andrew Bartlett
>>
>> --
>> Andrew Bartlett http://samba.org/~abartlet/
>> Authentication Developer, Samba Team http://samba.org
>> Samba Developer, Cisco Inc.
>>
>