updating samba4alpha15 to beta1

Christian Huldt christian at solvare.se
Sat Jun 16 11:10:45 MDT 2012


After first upgrading login2 without any problems (well, not more than before upgrading) I now get (after upgrading LOGIN1):

# /usr/local/samba/bin/samba-tool drs showrepl
ERROR(<class 'samba.drs_utils.drsException'>): DRS connection to login2.arkitekt.msg83 failed - drsException: DRS connection to login2.arkitekt.msg83 failed: (-1073741772, 'NT_STATUS_OBJECT_NAME_NOT_FOUND')
  File "/usr/local/samba/lib/python2.6/site-packages/samba/netcmd/drs.py", line 39, in 
    (ctx.drsuapi, ctx.drsuapi_handle, ctx.bind_supported_extensions) = drs_utils.drsuapi_connect(ctx.server, ctx.lp, ctx.creds)
  File "/usr/local/samba/lib/python2.6/site-packages/samba/drs_utils.py", line 54, in drsuapi_connect
    raise drsException("DRS connection to %s failed: %s" % (server, e))

any clue?

16 jun 2012 kl. 03.58 skrev Andrew Bartlett:

> On Sat, 2012-06-16 at 00:42 +0200, Christian Huldt wrote:
>> 7 jun 2012 kl. 04.33 skrev Andrew Bartlett:
>> 
>>> On Wed, 2012-06-06 at 21:02 +0200, Christian Huldt wrote:
>>>> I have 2 left-alone samba4alpha15 servers as pdc and bdc that I plan to 
>>>> update to beta1
>>>> (and then hopefully keep uptodate...)
>>>> 
>>>> Is that old enough to use upgradeprovision?
>>> 
>>> I think it should be OK without it.  Do run 'dbcheck --cross-ncs'.  
>>> 
>> 
>> This gives a lot of: 
>> ERROR: missing GUID component for objectCategory in object CN=CA006,CN=Computers,DC=arkitekt,DC=msg83 - CN=Computer,CN=Schema,CN=Configuration,DC=arkitekt,DC=msg83
>> Not fixing missing GUID
>> 
>> adding --fix gives:
>> ERROR: missing GUID component for defaultObjectCategory in object CN=Residential-Person,CN=Schema,CN=Configuration,DC=arkitekt,DC=msg83 - CN=Residential-Person,CN=Schema,CN=Configuration,DC=arkitekt,DC=msg83
>> Change DN to <GUID=98716508-375d-4255-9b1c-76a731ab5e0f>;CN=Residential-Person,CN=Schema,CN=Configuration,DC=arkitekt,DC=msg83? [y/N/all/none] y
>> schema_data_add: updates are not allowed: reject request
>> 
>> What would be the best way to proceed?
> 
> Apply this patch.  I've reproduced this locally, and added a test to
> ensure this does not regress. 
> 
> Andrew Bartlett
> 
> -- 
> Andrew Bartlett                                http://samba.org/~abartlet/
> Authentication Developer, Samba Team           http://samba.org
> <0001-s4-dbcheck-Always-specify-the-dhcheck-control.patch>



More information about the samba-technical mailing list