opsi client reagiert nicht/wird nicht erkannt

alex411
Beiträge: 28
Registriert: 10 Aug 2009, 17:17

opsi client reagiert nicht/wird nicht erkannt

Beitrag von alex411 »

hallo ich habe auf einem client den preloginloader nachträglich installiert und als client angelegt ..
es wird auch angezeigt das der prelogin loader installiert ist .. also eine verbindung ist irgendwie da aber er startet bei dem preloginloader immer nur windows und keine setups die ich ausgewählt habe

die log datei meldet dabei folgenden fehler :

[4] [Aug 13 18:27:55] Client '10.0.1.44' did not send cookie (opsiconfd|261)
[4] [Aug 13 18:27:55] New session created (opsiconfd|951)
[4] [Aug 13 18:27:55] Authorization request from none@10.0.1.44 (opsiconfd|354)
[2] [Aug 13 18:27:55] Failed to read opsi modules file '/etc/opsi/modules': Signature expired (BackendManager.py|1209)
[2] [Aug 13 18:27:57] Forbidden: PAM authentication failed for user 'none': ('User not known to the underlying authentication module', 10) (opsiconfd|417)
[1] [Aug 13 18:27:57] Traceback (most recent call last):
File "/usr/sbin/opsiconfd", line 118, in http_GET
return worker.process()
File "/usr/sbin/opsiconfd", line 200, in process
self.deferred.callback(None)
File "/usr/lib/python2.5/site-packages/twisted/internet/defer.py", line 243, in callback
self._startRunCallbacks(result)
File "/usr/lib/python2.5/site-packages/twisted/internet/defer.py", line 312, in _startRunCallbacks
self._runCallbacks()
--- <exception caught here> ---
File "/usr/lib/python2.5/site-packages/twisted/internet/defer.py", line 328, in _runCallbacks
self.result = callback(self.result, *args, **kw)
File "/usr/sbin/opsiconfd", line 389, in _authenticate
configFile = backendManagerConf )
File "/var/lib/python-support/python2.5/OPSI/Backend/BackendManager.py", line 167, in __init__
self._authenticate(self.__username, self.__password)
File "/var/lib/python-support/python2.5/OPSI/Backend/BackendManager.py", line 284, in _authenticate
return self._pamAuthenticate(user, password)
File "/var/lib/python-support/python2.5/OPSI/Backend/BackendManager.py", line 378, in _pamAuthenticate
raise BackendAuthenticationError("PAM authentication failed for user '%s': %s" % (user, e))
OPSI.Backend.Backend.BackendAuthenticationError: PAM authentication failed for user 'none': ('User not known to the underlying authentication module', 10)
(opsiconfd|620)
[2] [Aug 13 18:27:57] Failed to process rpc: PAM authentication failed for user 'none': ('User not known to the underlying authentication module', 10) (opsiconfd|624)
[4] [Aug 13 18:28:11] Client '10.0.1.44' did not send cookie (opsiconfd|261)
[4] [Aug 13 18:28:11] New session created (opsiconfd|951)
[4] [Aug 13 18:28:11] Authorization request from root@10.0.1.44 (opsiconfd|354)
[2] [Aug 13 18:28:11] Failed to read opsi modules file '/etc/opsi/modules': Signature expired (BackendManager.py|1209)
[4] [Aug 13 18:28:11] BackendManager created. (opsiconfd|391)
[3] [Aug 13 18:28:17] Host 'opsiapplication.itecra.de' not found (MySQL.py|878)
[4] [Aug 13 18:28:22] Client '10.0.1.44' did not send cookie (opsiconfd|261)
[4] [Aug 13 18:28:22] New session created (opsiconfd|951)
[4] [Aug 13 18:28:22] Authorization request from opsiapplication.itecra.de@10.0.1.44 (opsiconfd|354)
[3] [Aug 13 18:28:22] Failed to resolve hostname 'opsiapplication.itecra.de': (-5, 'No address associated with hostname') (opsiconfd|371)
[4] [Aug 13 18:28:22] Host login attempt with username 'opsiapplication.itecra.de' from ip '10.0.1.44', but name resolves to '[]', ip verification is disabled (access granted) (opsiconfd|384)
[2] [Aug 13 18:28:22] Failed to read opsi modules file '/etc/opsi/modules': Signature expired (BackendManager.py|1209)
[4] [Aug 13 18:28:22] BackendManager created. (opsiconfd|391)
[2] [Aug 13 18:28:55] Failed to read opsi modules file '/etc/opsi/modules': Signature expired (BackendManager.py|1209)
[1] [Aug 13 18:28:55] Traceback (most recent call last):
File "/usr/lib/python2.5/threading.py", line 446, in run
self.__target(*self.__args, **self.__kwargs)
File "/usr/lib/python2.5/site-packages/twisted/python/threadpool.py", line 161, in _worker
context.call(ctx, function, *args, **kwargs)
File "/usr/lib/python2.5/site-packages/twisted/python/context.py", line 59, in callWithContext
return self.currentContext().callWithContext(ctx, func, *args, **kw)
File "/usr/lib/python2.5/site-packages/twisted/python/context.py", line 37, in callWithContext
return func(*args,**kw)
--- <exception caught here> ---
File "/usr/lib/python2.5/site-packages/twisted/internet/threads.py", line 24, in _putResultInDeferred
result = f(*args, **kwargs)
File "/usr/sbin/opsiconfd", line 528, in _realRpc
self.result['result'] = eval( "bm.%s(%s)" % (method, str(params)[1:-1]) )
File "<string>", line 1, in <module>

File "/etc/opsi/backendManager.d/50_interface.conf", line 1213, in setProductInstallationStatus
return self._execMethod(self.defaultBackend, 'setProductInstallationStatus', productId, objectId, installationStatus)
File "/var/lib/python-support/python2.5/OPSI/Backend/BackendManager.py", line 499, in _execMethod
res = eval( "instance.%s%s" % (method, params) )
File "<string>", line 1, in <module>

File "/var/lib/python-support/python2.5/OPSI/Backend/File31.py", line 2042, in setProductInstallationStatus
self.setProductState(productId, objectId, installationStatus = installationStatus)
File "/var/lib/python-support/python2.5/OPSI/Backend/File31.py", line 1955, in setProductState
productType = self.getProductType(productId = productId, depotId = depotId)
File "/var/lib/python-support/python2.5/OPSI/Backend/Backend.py", line 347, in getProductType
raise Exception("product '%s': is neither localboot nor netboot product" % productId)
exceptions.Exception: product 'preloginvista': is neither localboot nor netboot product
(opsiconfd|620)
[2] [Aug 13 18:28:55] Failed to process rpc: product 'preloginvista': is neither localboot nor netboot product (opsiconfd|624)
[4] [Aug 13 18:30:05] Client '10.0.1.44' did not send cookie (opsiconfd|261)
[4] [Aug 13 18:30:05] New session created (opsiconfd|951)
[2] [Aug 13 18:30:05] Failed to read opsi modules file '/etc/opsi/modules': Signature expired (BackendManager.py|1209)
[4] [Aug 13 18:30:05] Authorization request from opsiapplication.itecra.de@10.0.1.44 (opsiconfd|354)
[3] [Aug 13 18:30:05] Failed to resolve hostname 'opsiapplication.itecra.de': (-5, 'No address associated with hostname') (opsiconfd|371)
[4] [Aug 13 18:30:05] Host login attempt with username 'opsiapplication.itecra.de' from ip '10.0.1.44', but name resolves to '[]', ip verification is disabled (access granted) (opsiconfd|384)
[2] [Aug 13 18:30:05] Failed to read opsi modules file '/etc/opsi/modules': Signature expired (BackendManager.py|1209)
[4] [Aug 13 18:30:05] BackendManager created. (opsiconfd|391)
[2] [Aug 13 18:30:05] Failed to read opsi modules file '/etc/opsi/modules': Signature expired (BackendManager.py|1209)
[4] [Aug 13 18:31:43] Client '10.0.1.44' did not send cookie (opsiconfd|261)
[4] [Aug 13 18:31:43] New session created (opsiconfd|951)
[2] [Aug 13 18:31:43] Failed to read opsi modules file '/etc/opsi/modules': Signature expired (BackendManager.py|1209)
[4] [Aug 13 18:31:43] Authorization request from opsiapplication.itecra.de@10.0.1.44 (opsiconfd|354)
[3] [Aug 13 18:31:43] Failed to resolve hostname 'opsiapplication.itecra.de': (-5, 'No address associated with hostname') (opsiconfd|371)
[4] [Aug 13 18:31:43] Host login attempt with username 'opsiapplication.itecra.de' from ip '10.0.1.44', but name resolves to '[]', ip verification is disabled (access granted) (opsiconfd|384)
[2] [Aug 13 18:31:43] Failed to read opsi modules file '/etc/opsi/modules': Signature expired (BackendManager.py|1209)
[4] [Aug 13 18:31:43] BackendManager created. (opsiconfd|391)
[2] [Aug 13 18:31:44] Failed to read opsi modules file '/etc/opsi/modules': Signature expired (BackendManager.py|1209)
[4] [Aug 13 18:34:15] Client '10.0.1.44' did not send cookie (opsiconfd|261)
[4] [Aug 13 18:34:15] New session created (opsiconfd|951)
[2] [Aug 13 18:34:15] Failed to read opsi modules file '/etc/opsi/modules': Signature expired (BackendManager.py|1209)
[4] [Aug 13 18:34:15] Authorization request from opsiapplication.itecra.de@10.0.1.44 (opsiconfd|354)
[3] [Aug 13 18:34:15] Failed to resolve hostname 'opsiapplication.itecra.de': (-5, 'No address associated with hostname') (opsiconfd|371)
[4] [Aug 13 18:34:15] Host login attempt with username 'opsiapplication.itecra.de' from ip '10.0.1.44', but name resolves to '[]', ip verification is disabled (access granted) (opsiconfd|384)
[2] [Aug 13 18:34:15] Failed to read opsi modules file '/etc/opsi/modules': Signature expired (BackendManager.py|1209)
[4] [Aug 13 18:34:15] BackendManager created. (opsiconfd|391)
[2] [Aug 13 18:34:15] Failed to read opsi modules file '/etc/opsi/modules': Signature expired (BackendManager.py|1209)
[4] [Aug 13 18:39:58] Client '10.0.1.44' did not send cookie (opsiconfd|261)
[4] [Aug 13 18:39:58] New session created (opsiconfd|951)
[2] [Aug 13 18:39:58] Failed to read opsi modules file '/etc/opsi/modules': Signature expired (BackendManager.py|1209)
[4] [Aug 13 18:39:58] Authorization request from opsiapplication.itecra.de@10.0.1.44 (opsiconfd|354)
[3] [Aug 13 18:39:58] Failed to resolve hostname 'opsiapplication.itecra.de': (-5, 'No address associated with hostname') (opsiconfd|371)
[4] [Aug 13 18:39:58] Host login attempt with username 'opsiapplication.itecra.de' from ip '10.0.1.44', but name resolves to '[]', ip verification is disabled (access granted) (opsiconfd|384)
[2] [Aug 13 18:39:58] Failed to read opsi modules file '/etc/opsi/modules': Signature expired (BackendManager.py|1209)
[4] [Aug 13 18:39:58] BackendManager created. (opsiconfd|391)
[2] [Aug 13 18:39:59] Failed to read opsi modules file '/etc/opsi/modules': Signature expired (BackendManager.py|1209)
[4] [Aug 13 18:42:15] Client '10.0.1.44' did not send cookie (opsiconfd|261)
[4] [Aug 13 18:42:15] New session created (opsiconfd|951)
[2] [Aug 13 18:42:15] Failed to read opsi modules file '/etc/opsi/modules': Signature expired (BackendManager.py|1209)
[4] [Aug 13 18:42:15] Authorization request from opsiapplication.itecra.de@10.0.1.44 (opsiconfd|354)
[3] [Aug 13 18:42:15] Failed to resolve hostname 'opsiapplication.itecra.de': (-5, 'No address associated with hostname') (opsiconfd|371)
[4] [Aug 13 18:42:15] Host login attempt with username 'opsiapplication.itecra.de' from ip '10.0.1.44', but name resolves to '[]', ip verification is disabled (access granted) (opsiconfd|384)
[2] [Aug 13 18:42:15] Failed to read opsi modules file '/etc/opsi/modules': Signature expired (BackendManager.py|1209)
[4] [Aug 13 18:42:15] BackendManager created. (opsiconfd|391)
[2] [Aug 13 18:42:16] Failed to read opsi modules file '/etc/opsi/modules': Signature expired (BackendManager.py|1209)
[4] [Aug 13 18:45:14] Client '10.0.1.44' did not send cookie (opsiconfd|261)
[4] [Aug 13 18:45:14] New session created (opsiconfd|951)
[2] [Aug 13 18:45:14] Failed to read opsi modules file '/etc/opsi/modules': Signature expired (BackendManager.py|1209)
[4] [Aug 13 18:45:14] Authorization request from opsiapplication.itecra.de@10.0.1.44 (opsiconfd|354)
[3] [Aug 13 18:45:14] Failed to resolve hostname 'opsiapplication.itecra.de': (-5, 'No address associated with hostname') (opsiconfd|371)
[4] [Aug 13 18:45:14] Host login attempt with username 'opsiapplication.itecra.de' from ip '10.0.1.44', but name resolves to '[]', ip verification is disabled (access granted) (opsiconfd|384)
[2] [Aug 13 18:45:14] Failed to read opsi modules file '/etc/opsi/modules': Signature expired (BackendManager.py|1209)
[4] [Aug 13 18:45:14] BackendManager created. (opsiconfd|391)
[2] [Aug 13 18:45:15] Failed to read opsi modules file '/etc/opsi/modules': Signature expired (BackendManager.py|1209)
[4] [Aug 13 18:50:19] Client '10.0.1.44' did not send cookie (opsiconfd|261)
[4] [Aug 13 18:50:19] New session created (opsiconfd|951)
[2] [Aug 13 18:50:19] Failed to read opsi modules file '/etc/opsi/modules': Signature expired (BackendManager.py|1209)
[4] [Aug 13 18:50:19] Authorization request from opsiapplication.itecra.de@10.0.1.44 (opsiconfd|354)
[3] [Aug 13 18:50:19] Failed to resolve hostname 'opsiapplication.itecra.de': (-5, 'No address associated with hostname') (opsiconfd|371)
[4] [Aug 13 18:50:19] Host login attempt with username 'opsiapplication.itecra.de' from ip '10.0.1.44', but name resolves to '[]', ip verification is disabled (access granted) (opsiconfd|384)
[2] [Aug 13 18:50:19] Failed to read opsi modules file '/etc/opsi/modules': Signature expired (BackendManager.py|1209)
[4] [Aug 13 18:50:19] BackendManager created. (opsiconfd|391)
[2] [Aug 13 18:50:19] Failed to read opsi modules file '/etc/opsi/modules': Signature expired (BackendManager.py|1209)
[4] [Aug 13 18:52:49] Client '10.0.1.44' did not send cookie (opsiconfd|261)
[4] [Aug 13 18:52:49] New session created (opsiconfd|951)
[2] [Aug 13 18:52:49] Failed to read opsi modules file '/etc/opsi/modules': Signature expired (BackendManager.py|1209)
[4] [Aug 13 18:52:49] Authorization request from opsiapplication.itecra.de@10.0.1.44 (opsiconfd|354)
[3] [Aug 13 18:52:49] Failed to resolve hostname 'opsiapplication.itecra.de': (-5, 'No address associated with hostname') (opsiconfd|371)
[4] [Aug 13 18:52:49] Host login attempt with username 'opsiapplication.itecra.de' from ip '10.0.1.44', but name resolves to '[]', ip verification is disabled (access granted) (opsiconfd|384)
[2] [Aug 13 18:52:49] Failed to read opsi modules file '/etc/opsi/modules': Signature expired (BackendManager.py|1209)
[4] [Aug 13 18:52:49] BackendManager created. (opsiconfd|391)
[2] [Aug 13 18:52:50] Failed to read opsi modules file '/etc/opsi/modules': Signature expired (BackendManager.py|1209)
[4] [Aug 13 18:54:21] Client '10.0.1.44' did not send cookie (opsiconfd|261)
[4] [Aug 13 18:54:21] New session created (opsiconfd|951)
[2] [Aug 13 18:54:21] Failed to read opsi modules file '/etc/opsi/modules': Signature expired (BackendManager.py|1209)
[4] [Aug 13 18:54:21] Authorization request from opsiapplication.itecra.de@10.0.1.44 (opsiconfd|354)
[3] [Aug 13 18:54:21] Failed to resolve hostname 'opsiapplication.itecra.de': (-5, 'No address associated with hostname') (opsiconfd|371)
[4] [Aug 13 18:54:21] Host login attempt with username 'opsiapplication.itecra.de' from ip '10.0.1.44', but name resolves to '[]', ip verification is disabled (access granted) (opsiconfd|384)
[2] [Aug 13 18:54:21] Failed to read opsi modules file '/etc/opsi/modules': Signature expired (BackendManager.py|1209)
[4] [Aug 13 18:54:21] BackendManager created. (opsiconfd|391)
[2] [Aug 13 18:54:22] Failed to read opsi modules file '/etc/opsi/modules': Signature expired (BackendManager.py|1209)
[4] [Aug 13 19:00:34] Client '10.0.1.44' did not send cookie (opsiconfd|261)
[4] [Aug 13 19:00:34] New session created (opsiconfd|951)
[2] [Aug 13 19:00:34] Failed to read opsi modules file '/etc/opsi/modules': Signature expired (BackendManager.py|1209)
[4] [Aug 13 19:00:35] Authorization request from opsiapplication.itecra.de@10.0.1.44 (opsiconfd|354)
[3] [Aug 13 19:00:35] Failed to resolve hostname 'opsiapplication.itecra.de': (-5, 'No address associated with hostname') (opsiconfd|371)
[4] [Aug 13 19:00:35] Host login attempt with username 'opsiapplication.itecra.de' from ip '10.0.1.44', but name resolves to '[]', ip verification is disabled (access granted) (opsiconfd|384)
[2] [Aug 13 19:00:35] Failed to read opsi modules file '/etc/opsi/modules': Signature expired (BackendManager.py|1209)
[4] [Aug 13 19:00:35] BackendManager created. (opsiconfd|391)
[2] [Aug 13 19:00:35] Failed to read opsi modules file '/etc/opsi/modules': Signature expired (BackendManager.py|1209)
[4] [Aug 13 19:05:44] Client '10.0.1.44' did not send cookie (opsiconfd|261)
[4] [Aug 13 19:05:44] New session created (opsiconfd|951)
[2] [Aug 13 19:05:44] Failed to read opsi modules file '/etc/opsi/modules': Signature expired (BackendManager.py|1209)
[4] [Aug 13 19:05:44] Authorization request from opsiapplication.itecra.de@10.0.1.44 (opsiconfd|354)
[3] [Aug 13 19:05:44] Failed to resolve hostname 'opsiapplication.itecra.de': (-5, 'No address associated with hostname') (opsiconfd|371)
[4] [Aug 13 19:05:44] Host login attempt with username 'opsiapplication.itecra.de' from ip '10.0.1.44', but name resolves to '[]', ip verification is disabled (access granted) (opsiconfd|384)
[2] [Aug 13 19:05:44] Failed to read opsi modules file '/etc/opsi/modules': Signature expired (BackendManager.py|1209)
[4] [Aug 13 19:05:44] BackendManager created. (opsiconfd|391)
[2] [Aug 13 19:05:44] Failed to read opsi modules file '/etc/opsi/modules': Signature expired (BackendManager.py|1209)
[4] [Aug 13 19:11:34] Client '10.0.1.44' did not send cookie (opsiconfd|261)
[4] [Aug 13 19:11:34] New session created (opsiconfd|951)
[2] [Aug 13 19:11:34] Failed to read opsi modules file '/etc/opsi/modules': Signature expired (BackendManager.py|1209)
[4] [Aug 13 19:11:34] Authorization request from opsiapplication.itecra.de@10.0.1.44 (opsiconfd|354)
[3] [Aug 13 19:11:34] Failed to resolve hostname 'opsiapplication.itecra.de': (-5, 'No address associated with hostname') (opsiconfd|371)
[4] [Aug 13 19:11:34] Host login attempt with username 'opsiapplication.itecra.de' from ip '10.0.1.44', but name resolves to '[]', ip verification is disabled (access granted) (opsiconfd|384)
[2] [Aug 13 19:11:34] Failed to read opsi modules file '/etc/opsi/modules': Signature expired (BackendManager.py|1209)
[4] [Aug 13 19:11:34] BackendManager created. (opsiconfd|391)
[2] [Aug 13 19:11:35] Failed to read opsi modules file '/etc/opsi/modules': Signature expired (BackendManager.py|1209)
[4] [Aug 13 19:18:53] Client '10.0.1.44' did not send cookie (opsiconfd|261)
[4] [Aug 13 19:18:53] New session created (opsiconfd|951)
[2] [Aug 13 19:18:53] Failed to read opsi modules file '/etc/opsi/modules': Signature expired (BackendManager.py|1209)
[4] [Aug 13 19:18:53] Authorization request from opsiapplication.itecra.de@10.0.1.44 (opsiconfd|354)
[3] [Aug 13 19:18:53] Failed to resolve hostname 'opsiapplication.itecra.de': (-5, 'No address associated with hostname') (opsiconfd|371)
[4] [Aug 13 19:18:53] Host login attempt with username 'opsiapplication.itecra.de' from ip '10.0.1.44', but name resolves to '[]', ip verification is disabled (access granted) (opsiconfd|384)
[2] [Aug 13 19:18:53] Failed to read opsi modules file '/etc/opsi/modules': Signature expired (BackendManager.py|1209)
[4] [Aug 13 19:18:53] BackendManager created. (opsiconfd|391)
[2] [Aug 13 19:18:54] Failed to read opsi modules file '/etc/opsi/modules': Signature expired (BackendManager.py|1209)
Benutzeravatar
j.schneider
uib-Team
Beiträge: 2045
Registriert: 29 Mai 2008, 15:14

Re: opsi client reagiert nicht/wird nicht erkannt

Beitrag von j.schneider »

Hallo,

die Modules-Datei ist abgelaufen.
Bitte die folgende Datei:
http://download.uib.de/opsi3.4/modules
in /etc/opsi/ ablegen.

Gruß
Jan Schneider


Vielen Dank für die Nutzung von opsi. Im Forum ist unser Support begrenzt.

Für den professionellen Einsatz und individuelle Beratung empfehlen wir einen Support-Vertrag und eine Schulung.
Gerne informieren wir Sie zu unserem Angebot.

uib GmbH
Telefon: +49 6131 27561 0
E-Mail: sales@uib.de


Rhuen
Beiträge: 9
Registriert: 28 Jul 2009, 14:32

Re: opsi client reagiert nicht/wird nicht erkannt

Beitrag von Rhuen »

Hab es leider jetzt nicht vor mir, sofern das problem mich auch betrifft wie erwähnt.

Welche datei soll wo rein?
Wenn ich den link öffne, seh ich nur den inhalt, oder soll ich den inhalt kopieren?
Aber worein?
Oder muss ich das mitm opsi aufrufen?

mfg
webi
Beiträge: 97
Registriert: 13 Aug 2009, 11:49

Re: opsi client reagiert nicht/wird nicht erkannt

Beitrag von webi »

Die Datei kommt nach /etc/opsi/

Code: Alles auswählen

cd /etc/opsi/
wget http://download.uib.de/opsi3.4/modules
Rhuen
Beiträge: 9
Registriert: 28 Jul 2009, 14:32

Re: opsi client reagiert nicht/wird nicht erkannt

Beitrag von Rhuen »

Hy,
habe ich gemacht, jetzt ist da auch eine modules datei, aber ob sie korrekt ist weiß ich nicht, da es doch irgendwie ziemlich schnell ging....habe dann mein Client neugestartet, da sagt die log:

[4] [Aug 14 10:46:49] Client '192.168.0.106' did not send cookie (opsiconfd|257)
[4] [Aug 14 10:46:49] New session created (opsiconfd|940)
[4] [Aug 14 10:46:49] Authorization request from pcname@192.168.0.106 (opsiconfd|350)
[4] [Aug 14 10:46:49] BackendManager created. (opsiconfd|387)
[2] [Aug 14 10:46:50] Failed to read opsi modules file '/etc/opsi/modules': [Errno 2] No such file or directory: '/etc/opsi/modules' (BackendManager.py|1170)
[4] [Aug 14 11:31:04] Client '192.168.0.106' did not send cookie (opsiconfd|257)
[4] [Aug 14 11:31:04] New session created (opsiconfd|940)
[4] [Aug 14 11:31:04] Authorization request from pcname@192.168.0.106 (opsiconfd|350)
[4] [Aug 14 11:31:04] BackendManager created. (opsiconfd|387)
[2] [Aug 14 11:31:05] Found bad line 'expires = 2009-08-31' in modules file '/etc/opsi/modules' (BackendManager.py|1146)
[2] [Aug 14 11:31:05] /var/lib/python-support/python2.5/OPSI/Backend/BackendManager.py:1157: DeprecationWarning: getPublicKeyObject is deprecated since Twisted Conch 0.9. Use Key.fromString().
publicKey = keys.getPublicKeyObject(data = base64.decodestring('AAAAB3NzaC1yc2EAAAADAQABAAABAQCAD/I79Jd0eKwwfuVwh5B2z+S8aV0C5suItJa18RrYip+d4P0ogzqoCfOoVWtDojY96FDYv+2d73LsoOckHCnuh55GA0mtuVMWdXNZIE8Avt/RzbEoYGo/H0weuga7I8PuQNC/nyS8w3W8TH4pt+ZCjZZoX8S+IizWCYwfqYoYTMLgB0i+6TCAfJj3mNgCrDZkQ24+rOFS4a8RrjamEz/b81noWl9IntllK1hySkR+LbulfTGALHgHkDUlk0OSu+zBPw/hcDSOMiDQvvHfmR4quGyLPbQ2FOVm1TzE0bQPR+Bhx4V8Eo2kNYstG2eJELrz7J1TJI0rCjpB+FQjYPsP'))
(warnings.py|133)
[4] [Aug 14 11:35:06] Client '192.168.0.106' did not send cookie (opsiconfd|257)
[4] [Aug 14 11:35:06] New session created (opsiconfd|940)
[4] [Aug 14 11:35:06] Authorization request from root@192.168.0.106 (opsiconfd|350)
[4] [Aug 14 11:35:06] BackendManager created. (opsiconfd|387)
Benutzeravatar
j.schneider
uib-Team
Beiträge: 2045
Registriert: 29 Mai 2008, 15:14

Re: opsi client reagiert nicht/wird nicht erkannt

Beitrag von j.schneider »

Hier scheint opsi3.3.1 mit 3.4 vermischt zu sein.
Bitte folgende Ausgaben posten:

Code: Alles auswählen

dpkg -l | grep opsi

Code: Alles auswählen

opsi-package-manager -l


Vielen Dank für die Nutzung von opsi. Im Forum ist unser Support begrenzt.

Für den professionellen Einsatz und individuelle Beratung empfehlen wir einen Support-Vertrag und eine Schulung.
Gerne informieren wir Sie zu unserem Angebot.

uib GmbH
Telefon: +49 6131 27561 0
E-Mail: sales@uib.de


Rhuen
Beiträge: 9
Registriert: 28 Jul 2009, 14:32

Re: opsi client reagiert nicht/wird nicht erkannt

Beitrag von Rhuen »

Da ic hnicht weiß wie ich aus dem Terminal kopieren kann, bin über vnc drauf, schrei bich es per hand:

dpkg..

Code: Alles auswählen

ii opsi-atftpd 0.7.dfsg-1.4
ii opsi-configed 1.3.3-2
ii opsi-depotserver 3.3-10
ii opsi-linux-bootimage 20090414-1
ii opsi-utils 3.3.1.1-1
ii opsiconfd 2.0.0.16-1
ii opsipxeconfd 0.3.6-1
ii python-opsi 3.3.1.7-1
packagemanager

Code: Alles auswählen

hwaudit 1.2.1-2
hwinvent 1.1-1
opsi-adminutils 3.4-1
opsi-template 1.0-15
opsi-winst 4.8.6-5
preloginloader 3.4-19
softprod 1.0-7
swaudit 1.2.3-3
sachen wie memtest, winxppro xpconfig etc. habe ich mal weg gelassen, hoffe das reicht so.

mfg
Benutzeravatar
j.schneider
uib-Team
Beiträge: 2045
Registriert: 29 Mai 2008, 15:14

Re: opsi client reagiert nicht/wird nicht erkannt

Beitrag von j.schneider »

Ok,

entweder den Server auf opsi3.4 updaten (siehe http://download.uib.de/opsi3.4/doku/ops ... v34-de.pdf) oder den Preloginloader 3.3.1 verwenden (http://download.uib.de/opsi3.3.1/produk ... 3.1-4.opsi).


Vielen Dank für die Nutzung von opsi. Im Forum ist unser Support begrenzt.

Für den professionellen Einsatz und individuelle Beratung empfehlen wir einen Support-Vertrag und eine Schulung.
Gerne informieren wir Sie zu unserem Angebot.

uib GmbH
Telefon: +49 6131 27561 0
E-Mail: sales@uib.de


LION
Beiträge: 13
Registriert: 30 Dez 2009, 11:21

Re: opsi client reagiert nicht/wird nicht erkannt

Beitrag von LION »

Hab bei mir ähnliches Problem.

Wenn ich
cd /etc/opsi/
wget http://download.uib.de/opsi3.4/modules eingebe sagt er mir Fehler 404: Not Found

Auch im Browser kann ich den Pfad nicht finden. Hat sich da was geändert. Finde die module unter den anderen Paketen usw. auch nicht!
webi
Beiträge: 97
Registriert: 13 Aug 2009, 11:49

Re: opsi client reagiert nicht/wird nicht erkannt

Beitrag von webi »

LION hat geschrieben:Hab bei mir ähnliches Problem.

Wenn ich
cd /etc/opsi/
wget http://download.uib.de/opsi3.4/modules eingebe sagt er mir Fehler 404: Not Found

Auch im Browser kann ich den Pfad nicht finden. Hat sich da was geändert. Finde die module unter den anderen Paketen usw. auch nicht!
Die modules Datei wird derzeit nicht benötigt!
Antworten