Hallo,
seit einigenTagen bekomme ich alle drei Std. diese Systemmail:
[code]***** Nagios *****
Notification Type: PROBLEM
Service: UNIVENTION_S4CONNECTOR
Host: modsrv.hermandung.lan
Address: 192.168.0.10
State: WARNING
Date/Time: Thu Jan 19 18:36:23 CET 2017
Additional Info:
S4CONNECTOR WARNING: Found 71 reject(s)! Please check output of univention-s4connector-list-rejected.[/code]
univention-s4connector-list-rejected:
Diesen Eintrag gibt es 76mal mit unterschiedlicher Ziffernfolge hinter …/s4/
1: UCS DN: cn=W7X64,cn=Client-PC,cn=Computers,dc=hermandung,dc=lan
S4 DN: <not found>
Filename: /var/lib/univention-connector/s4/1483720373.166554
Das gibt’s einmal:
40: UCS DN: cn=Client-PC,cn=computers,dc=hermandung,dc=lan
S4 DN: cn=client-pc,cn=computers,DC=hermandung,DC=lan
Filename: /var/lib/univention-connector/s4/1483721880.377211
Und am Ende steht:
[code]S4 rejected
1: S4 DN: CN=W7X64,CN=Client-PC,CN=Computers,DC=hermandung,DC=lan
UCS DN: <not found>
last synced USN: 7455[/code]
CN=W7X64 und CN=Client-PC sind Objekte, die ich nach der Installation testhalber angelegt und wieder gelöscht hatte.
Wenn ich mich recht erinnere, hatte ich dabei direkt im LDAP-Modul der UCM rumgefummelt - offensichtlich eine schlechte Idee…
In der connector-s4.log finde ich blockweise erst etliche dieser Einträge:
19.01.2017 19:23:15,629 LDAP (PROCESS): sync from ucs: Resync rejected file: /var/lib/univention-connector/s4/1483720307.632478
19.01.2017 19:23:15,641 LDAP (PROCESS): sync from ucs: [windowscomputer] [ delete] cn=W7X64,cn=Client-PC,cn=Computers,DC=hermandung,DC=lan
19.01.2017 19:23:15,672 LDAP (PROCESS): Unable to sync cn=W7X64,cn=Client-PC,cn=Computers,DC=hermandung,DC=lan (GUID: b516c3a9-8e1c-4526-8194-09eaae2f3c2a). The object is currently locked.
19.01.2017 19:23:15,813 LDAP (PROCESS): sync from ucs: Resync rejected file: /var/lib/univention-connector/s4/1483720372.575060
19.01.2017 19:23:15,826 LDAP (PROCESS): sync from ucs: [windowscomputer] [ add] cn=W7X64,cn=Client-PC,cn=computers,DC=hermandung,DC=lan
19.01.2017 19:23:15,857 LDAP (PROCESS): Unable to sync cn=W7X64,cn=Client-PC,cn=computers,DC=hermandung,DC=lan (GUID: b516c3a9-8e1c-4526-8194-09eaae2f3c2a). The object is currently locked.
dann folgt:
19.01.2017 19:23:15,980 LDAP (PROCESS): sync to ucs: Resync rejected dn: CN=W7X64,CN=Client-PC,CN=Computers,DC=hermandung,DC=lan
19.01.2017 19:23:15,989 LDAP (PROCESS): sync to ucs: [windowscomputer] [ add] cn=W7X64,CN=Client-PC,CN=Computers,dc=hermandung,dc=lan
19.01.2017 19:23:16,977 LDAP (ERROR ): Unknown Exception during sync_to_ucs
19.01.2017 19:23:16,978 LDAP (ERROR ): Traceback (most recent call last):
File "/usr/lib/pymodules/python2.7/univention/s4connector/__init__.py", line 1475, in sync_to_ucs
result = self.add_in_ucs(property_type, object, module, position)
File "/usr/lib/pymodules/python2.7/univention/s4connector/__init__.py", line 1262, in add_in_ucs
return ucs_object.create() and self.__modify_custom_attributes(property_type, object, ucs_object, module, position)
File "/usr/lib/pymodules/python2.7/univention/admin/handlers/__init__.py", line 306, in create
return self._create()
File "/usr/lib/pymodules/python2.7/univention/admin/handlers/__init__.py", line 722, in _create
al = self._ldap_addlist()
File "/usr/lib/pymodules/python2.7/univention/admin/handlers/computers/windows.py", line 456, in _ldap_addlist
self.machineSid = self.getMachineSid(self.lo, self.position, self.uidNum, self.get('sambaRID'))
File "/usr/lib/pymodules/python2.7/univention/admin/handlers/__init__.py", line 1147, in getMachineSid
univention.admin.allocators.request(self.lo, self.position, 'sid', sid)
File "/usr/lib/pymodules/python2.7/univention/admin/allocators.py", line 196, in request
return acquireUnique(lo, position, type, value, _type2attr[type], scope=_type2scope[type])
File "/usr/lib/pymodules/python2.7/univention/admin/allocators.py", line 185, in acquireUnique
univention.admin.locking.lock(lo, position, type, value, scope=scope)
File "/usr/lib/pymodules/python2.7/univention/admin/locking.py", line 98, in lock
raise univention.admin.uexceptions.noLock(_('The attribute %r could not get locked.') % (type,))
noLock: The attribute 'sid' could not get locked.
Und das wiederholt sich dann im Sekundentakt. Die Log-Datei ist inzwischen über 200 MiB groß!
univention-ldapsearch -b “cn=W7X64,cn=Client-PC,cn=Computers,dc=hermandung,dc=lan”:
[code]# extended LDIF
LDAPv3
base <cn=W7X64,cn=Client-PC,cn=Computers,dc=hermandung,dc=lan> with scope subtree
filter: (objectclass=*)
requesting: ALL
search result
search: 3
result: 32 No such object
matchedDN: cn=computers,dc=hermandung,dc=lan
numResponses: 1[/code]
univention-s4search -b “cn=W7X64,cn=Client-PC,cn=Computers,dc=hermandung,dc=lan”
[code]# record 1
dn: CN=W7X64,CN=Client-PC,CN=Computers,DC=hermandung,DC=lan
objectClass: top
objectClass: person
objectClass: organizationalPerson
objectClass: user
objectClass: computer
instanceType: 4
whenCreated: 20170106150228.0Z
uSNCreated: 4101
objectGUID: b516c3a9-8e1c-4526-8194-09eaae2f3c2a
userAccountControl: 4096
badPwdCount: 0
codePage: 0
countryCode: 0
badPasswordTime: 0
lastLogoff: 0
lastLogon: 0
primaryGroupID: 515
objectSid: S-1-5-21-280987424-3587840878-2925083125-1115
accountExpires: 9223372036854775807
logonCount: 0
sAMAccountName: W7X64.hermandung.lan$
sAMAccountType: 805306369
objectCategory: CN=Computer,CN=Schema,CN=Configuration,DC=hermandung,DC=lan
isCriticalSystemObject: FALSE
lockoutTime: 0
cn: W7X64
name: W7X64
whenChanged: 20170106160323.0Z
userPrincipalName: host/W7X64.hermandung.lan@HERMANDUNG.LAN
pwdLastSet: 131281816990000000
uSNChanged: 7246
distinguishedName: CN=W7X64,CN=Client-PC,CN=Computers,DC=hermandung,DC=lan
returned 1 records
1 entries
0 referrals[/code]
Was läuft da falsch, wie kann ich das stoppen?
Bitte um Hilfe, ehe mir die Log-Datei meine Festplatte vollgeschrieben hat 
- gibt es da keine Größenbeschränkung?
TIA und Gruß,
Dirk Hermandung
