[Gelöst] opsi-client-agent Installation bricht mit Fehler ab

Towning
Beiträge: 4
Registriert: 02 Jan 2010, 17:51

[Gelöst] opsi-client-agent Installation bricht mit Fehler ab

Beitragvon Towning » 14 Mai 2019, 14:42

Hallo zusammen,

ich habe ein Problem mit der Client installation.
Bisher sauber funktioniert aber gestern festgestellt das die Installation nicht mehr klappt.
Vorgestern ist das Update gelaufen...

1. Versucht den client-agent über UNC-Pfad zu installieren (RMT "als Administrator ausführen")
Fehlermeldung am Ende: no admin login exiting

2. Versucht über opsi-deploy-client-agent zu installieren
Ausgabe:

Code: Alles auswählen

root@opsi:/var/lib/opsi/depot/opsi-client-agent# ./opsi-deploy-client-agent -vv -u Administrator -p *** confidential *** --use-ip-address 172.24.128.15
Deploying to Windows.
* BackendManager is creating BackendDispatcher
Backend context was set to <BackendManager()>
Loading dispatch config file '/etc/opsi/backendManager/dispatch.conf'
Loading backend config '/etc/opsi/backends/opsipxeconfd.conf'
Backend context was set to <BackendDispatcher(dispatchConfigFile=u'/etc/opsi/backendManager/dispatch.conf', context=<BackendManager()>)>
Loading backend config '/etc/opsi/backends/file.conf'
Backend context was set to <BackendDispatcher(dispatchConfigFile=u'/etc/opsi/backendManager/dispatch.conf', context=<BackendManager()>)>
Loading backend config '/etc/opsi/backends/mysql.conf'
Backend context was set to <BackendDispatcher(dispatchConfigFile=u'/etc/opsi/backendManager/dispatch.conf', context=<BackendManager()>)>
Failed to read opsi modules file '/etc/opsi/modules': [Errno 2] No such file or directory: u'/etc/opsi/modules'
Missing important information about modules. Probably no modules file installed.
* BackendManager is creating ExtendedConfigDataBackend
Setting context to backend <ExtendedConfigDataBackend(configDataBackend=<BackendDispatcher(dispatchConfigFile=u'/etc/opsi/backendManager/dispatch.conf', context=<BackendManager()>)>)>
Executing: /usr/bin/winexe -V
Using encoding 'UTF-8'
Winexe Version: winexe version 4.8This program may be freely redistributed under the terms of the GNU GPLv3
Executing: /usr/bin/winexe -U 'Administrator%*** confidential ***' //172.24.128.15 'cmd.exe /C "echo OMPUTERNAME%"'
Using encoding 'UTF-8'
Deployment to '172.24.128.15' failed: Can't find name for IP 172.24.128.15: Command '/usr/bin/winexe -U 'Administrator%*** confidential ***' //172.24.128.15 'cmd.exe /C "echo OMPUTERNAME%"'' failed (1):

Wobei mir in der letzten Zeile auffällt:
cmd.exe /C "echo OMPUTERNAME%"
müsste m. E. doch %COMPUTERNAME% heissen, oder nicht?

3. Versucht über den opsi-Configed lokal -> Server-Konsole -> opsi - Verteilung opsi-client-agent zu verteilen
Pop-Up Meldung:
Mai 14 13:13:59.396 2019 --Bitte Verbindung/-sdaten überprüfen. Status: (nicht verbunden)

Erst mal Forum besucht und https://forum.uib.de/viewtopic.php?t=319 gefunden
An die %TEMP%\preloginloader.log von beiden Rechnern an denen ich es versucht habe komme ich z. Z. nicht ran.
Die 172.24.128.14.log (die letzten Einträge):

Code: Alles auswählen

[3] [May 13 14:14:07] 6 authentication failures from '172.24.128.14' in a row, waiting 60 seconds to prevent flooding (workers.py|94)
[5] [May 13 14:17:06] Application 'opsi-script 4.12.0.21' on client '172.24.128.14' did not send cookie (workers.py|185)
[5] [May 13 14:17:06] New session created (session.py|77)
[5] [May 13 14:17:06] Authorization request from towning@172.24.128.14 (application: opsi-script 4.12.0.21) (workers.py|217)
[5] [May 13 14:17:07] Session '43KNYEjtnB51TtvvRl9HbucXpiVxoT97' from ip '172.24.128.14', application 'opsi-script 4.12.0.21' deleted (Session.py|234)
[2] [May 13 14:17:07] Traceback: (Logger.py|798)
[2] [May 13 14:17:07]   File "/usr/lib/python2.7/dist-packages/OPSI/Service/Worker.py", line 289, in _errback failure.raiseException() (Logger.py|798)
[2] [May 13 14:17:07]   File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 651, in _runCallbacks current.result = callback(current.result, *args, **kw) (Logger.py|798)
[2] [May 13 14:17:07]   File "/usr/lib/python2.7/dist-packages/opsiconfd/workers.py", line 294, in _authenticate raise OpsiAuthenticationError(errorMessage) (Logger.py|798)
[2] [May 13 14:17:07]      ==>>> Opsi authentication error: Authentication failure for 'towning' from '172.24.128.14': Backend authentication error: Backend authentication error: PAM authentication failed for user 'towning': ('Authentication failure', 7) (Worker.py|291)
[5] [May 13 14:17:07] New session created (session.py|77)
[5] [May 13 14:17:07] Application 'opsi-script 4.12.0.21' on client '172.24.128.14' supplied non existing session id: 43KNYEjtnB51TtvvRl9HbucXpiVxoT97 (Worker.py|396)
[5] [May 13 14:17:07] Authorization request from towning@172.24.128.14 (application: opsi-script 4.12.0.21) (workers.py|217)
[5] [May 13 14:17:09] Session '8mwdXRe1FoCnYp3qvplQLlAecVSAP2n6' from ip '172.24.128.14', application 'opsi-script 4.12.0.21' deleted (Session.py|234)
[2] [May 13 14:17:09] Traceback: (Logger.py|798)
[2] [May 13 14:17:09]   File "/usr/lib/python2.7/dist-packages/OPSI/Service/Worker.py", line 289, in _errback failure.raiseException() (Logger.py|798)
[2] [May 13 14:17:09]   File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 651, in _runCallbacks current.result = callback(current.result, *args, **kw) (Logger.py|798)
[2] [May 13 14:17:09]   File "/usr/lib/python2.7/dist-packages/opsiconfd/workers.py", line 294, in _authenticate raise OpsiAuthenticationError(errorMessage) (Logger.py|798)
[2] [May 13 14:17:09]      ==>>> Opsi authentication error: Authentication failure for 'towning' from '172.24.128.14': Backend authentication error: Backend authentication error: PAM authentication failed for user 'towning': ('Authentication failure', 7) (Worker.py|291)
[5] [May 13 14:17:09] Application 'opsi-script 4.12.0.21' on client '172.24.128.14' did not send cookie (workers.py|185)
[5] [May 13 14:17:09] New session created (session.py|77)
[5] [May 13 14:17:09] Authorization request from towning@172.24.128.14 (application: opsi-script 4.12.0.21) (workers.py|217)
[5] [May 13 14:17:11] Session 'isBVNLJcKdsCqzeJwNxwz2KoROhP0EHH' from ip '172.24.128.14', application 'opsi-script 4.12.0.21' deleted (Session.py|234)
[2] [May 13 14:17:11] Traceback: (Logger.py|798)
[2] [May 13 14:17:11]   File "/usr/lib/python2.7/dist-packages/OPSI/Service/Worker.py", line 289, in _errback failure.raiseException() (Logger.py|798)
[2] [May 13 14:17:11]   File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 651, in _runCallbacks current.result = callback(current.result, *args, **kw) (Logger.py|798)
[2] [May 13 14:17:11]   File "/usr/lib/python2.7/dist-packages/opsiconfd/workers.py", line 294, in _authenticate raise OpsiAuthenticationError(errorMessage)  (Logger.py|798)
[2] [May 13 14:17:11]      ==>>> Opsi authentication error: Authentication failure for 'towning' from '172.24.128.14': Backend authentication error: Backend authentication error: PAM authentication failed for user 'towning': ('Authentication failure', 7) (Worker.py|291)
[5] [May 13 14:17:11] New session created (session.py|77)
[5] [May 13 14:17:11] Application 'opsi-script 4.12.0.21' on client '172.24.128.14' supplied non existing session id: isBVNLJcKdsCqzeJwNxwz2KoROhP0EHH (Worker.py|396)
[5] [May 13 14:17:11] Authorization request from towning@172.24.128.14 (application: opsi-script 4.12.0.21) (workers.py|217)
[5] [May 13 14:17:13] Session 'uvhBR5BsibkNBRsC95aKogH2eR8p4qeu' from ip '172.24.128.14', application 'opsi-script 4.12.0.21' deleted (Session.py|234)
[2] [May 13 14:17:13] Traceback: (Logger.py|798)
[2] [May 13 14:17:13]   File "/usr/lib/python2.7/dist-packages/OPSI/Service/Worker.py", line 289, in _errback failure.raiseException() (Logger.py|798)
[2] [May 13 14:17:13]   File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 651, in _runCallbacks current.result = callback(current.result, *args, **kw) (Logger.py|798)
[2] [May 13 14:17:13]   File "/usr/lib/python2.7/dist-packages/opsiconfd/workers.py", line 294, in _authenticate raise OpsiAuthenticationError(errorMessage) (Logger.py|798)
[2] [May 13 14:17:13]      ==>>> Opsi authentication error: Authentication failure for 'towning' from '172.24.128.14': Backend authentication error: Backend authentication error: PAM authentication failed for user 'towning': ('Authentication failure', 7) (Worker.py|291)
[5] [May 13 14:17:13] New session created (session.py|77)
[5] [May 13 14:17:13] Application 'opsi-script 4.12.0.21' on client '172.24.128.14' supplied non existing session id: uvhBR5BsibkNBRsC95aKogH2eR8p4qeu (Worker.py|396)
[5] [May 13 14:17:13] Authorization request from towning@172.24.128.14 (application: opsi-script 4.12.0.21) (workers.py|217)
[5] [May 13 14:17:15] Session 'FbwLogmVrWjKTp8cISp4ij8hMly33sRF' from ip '172.24.128.14', application 'opsi-script 4.12.0.21' deleted (Session.py|234)
[2] [May 13 14:17:15] Traceback: (Logger.py|798)
[2] [May 13 14:17:15]   File "/usr/lib/python2.7/dist-packages/OPSI/Service/Worker.py", line 289, in _errback failure.raiseException() (Logger.py|798)
[2] [May 13 14:17:15]   File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 651, in _runCallbacks current.result = callback(current.result, *args, **kw) (Logger.py|798)
[2] [May 13 14:17:15]   File "/usr/lib/python2.7/dist-packages/opsiconfd/workers.py", line 294, in _authenticate raise OpsiAuthenticationError(errorMessage) (Logger.py|798)
[2] [May 13 14:17:15]      ==>>> Opsi authentication error: Authentication failure for 'towning' from '172.24.128.14': Backend authentication error: Backend authentication error: PAM authentication failed for user 'towning': ('Authentication failure', 7) (Worker.py|291)
[5] [May 13 14:17:15] New session created (session.py|77)
[5] [May 13 14:17:15] Application 'opsi-script 4.12.0.21' on client '172.24.128.14' supplied non existing session id: FbwLogmVrWjKTp8cISp4ij8hMly33sRF (Worker.py|396)
[5] [May 13 14:17:15] Authorization request from towning@172.24.128.14 (application: opsi-script 4.12.0.21) (workers.py|217)
[5] [May 13 14:17:18] Session 'sm9tUOBJYvIHoRZXzhpXnYDxtBmqgyjl' from ip '172.24.128.14', application 'opsi-script 4.12.0.21' deleted (Session.py|234)
[2] [May 13 14:17:18] Traceback: (Logger.py|798)
[2] [May 13 14:17:18]   File "/usr/lib/python2.7/dist-packages/OPSI/Service/Worker.py", line 289, in _errback failure.raiseException() (Logger.py|798)
[2] [May 13 14:17:18]   File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 651, in _runCallbacks current.result = callback(current.result, *args, **kw) (Logger.py|798)
[2] [May 13 14:17:18]   File "/usr/lib/python2.7/dist-packages/opsiconfd/workers.py", line 294, in _authenticate raise OpsiAuthenticationError(errorMessage) (Logger.py|798)
[2] [May 13 14:17:18]      ==>>> Opsi authentication error: Authentication failure for 'towning' from '172.24.128.14': Backend authentication error: Backend authentication error: PAM authentication failed for user 'towning': ('Authentication failure', 7) (Worker.py|291)
[3] [May 13 14:17:18] 6 authentication failures from '172.24.128.14' in a row, waiting 60 seconds to prevent flooding (workers.py|94)


dpkg -l | grep opsi ergibt:

Code: Alles auswählen

ii  opsi-configed                           4.0.7.6.34-2
ii  opsi-linux-bootimage                    20180208-1
ii  opsi-server                             4.1.1.7-1
ii  opsi-tftpd-hpa                          5.2.8-49
ii  opsi-utils                              4.1.1.31-1
ii  opsi-windows-support                    4.1.1-8
ii  opsiconfd                               4.1.1.18-4
ii  opsipxeconfd                            4.1.1.14-1
ii  python-opsi                             4.1.1.62-1 


Habe dann manuell alle Pakete (ausser opsi-tftpd-hpa & opsi-linux-bootimage) einem reinstall unterzogen.
Keine Besserung
Somit bin ich mit meiner Weisheit am Ende und hoffe das jemand eine Idee hat...
Ach ja Debian 9.9 laut /etc/debian_version

Gruß
Frank
Zuletzt geändert von Towning am 03 Jun 2019, 10:23, insgesamt 1-mal geändert.

Benutzeravatar
n.wenselowski
uib-Team
Beiträge: 3175
Registriert: 04 Apr 2013, 12:15

Re: opsi-client-agent Installation bricht mit Fehler ab

Beitragvon n.wenselowski » 20 Mai 2019, 16:00

Hi Frank,

Towning hat geschrieben:1. Versucht den client-agent über UNC-Pfad zu installieren (RMT "als Administrator ausführen")
Fehlermeldung am Ende: no admin login exiting

Bitte versuch es mal ohne elevated rights.
Der opsi-client-agent wurde vor einiger Zeit so umgebaut, dass das nicht mehr notwendig ist.
Voraussetzung ist die Verwendung eines halbwegs aktuellen opsi-client-agent.

Den bekommst du so (und gleich dazu einen neuen opsi-winst):

Code: Alles auswählen

opsi-package-updater -v update opsi-client-agent opsi-winst


Towning hat geschrieben:2. Versucht über opsi-deploy-client-agent zu installieren
Ausgabe:

Code: Alles auswählen

root@opsi:/var/lib/opsi/depot/opsi-client-agent# ./opsi-deploy-client-agent -vv -u Administrator -p *** confidential *** --use-ip-address 172.24.128.15
Deploying to Windows.
* BackendManager is creating BackendDispatcher
Backend context was set to <BackendManager()>
Loading dispatch config file '/etc/opsi/backendManager/dispatch.conf'
Loading backend config '/etc/opsi/backends/opsipxeconfd.conf'
Backend context was set to <BackendDispatcher(dispatchConfigFile=u'/etc/opsi/backendManager/dispatch.conf', context=<BackendManager()>)>
Loading backend config '/etc/opsi/backends/file.conf'
Backend context was set to <BackendDispatcher(dispatchConfigFile=u'/etc/opsi/backendManager/dispatch.conf', context=<BackendManager()>)>
Loading backend config '/etc/opsi/backends/mysql.conf'
Backend context was set to <BackendDispatcher(dispatchConfigFile=u'/etc/opsi/backendManager/dispatch.conf', context=<BackendManager()>)>
Failed to read opsi modules file '/etc/opsi/modules': [Errno 2] No such file or directory: u'/etc/opsi/modules'
Missing important information about modules. Probably no modules file installed.
* BackendManager is creating ExtendedConfigDataBackend
Setting context to backend <ExtendedConfigDataBackend(configDataBackend=<BackendDispatcher(dispatchConfigFile=u'/etc/opsi/backendManager/dispatch.conf', context=<BackendManager()>)>)>
Executing: /usr/bin/winexe -V
Using encoding 'UTF-8'
Winexe Version: winexe version 4.8This program may be freely redistributed under the terms of the GNU GPLv3
Executing: /usr/bin/winexe -U 'Administrator%*** confidential ***' //172.24.128.15 'cmd.exe /C "echo OMPUTERNAME%"'
Using encoding 'UTF-8'
Deployment to '172.24.128.15' failed: Can't find name for IP 172.24.128.15: Command '/usr/bin/winexe -U 'Administrator%*** confidential ***' //172.24.128.15 'cmd.exe /C "echo OMPUTERNAME%"'' failed (1):

Wobei mir in der letzten Zeile auffällt:
cmd.exe /C "echo OMPUTERNAME%"
müsste m. E. doch %COMPUTERNAME% heissen, oder nicht?

Der OMPUTERNAME ist in dem Fall ein Anzeigeproblem.

Das eigentliche Problem ist in diesem Fall, dass für 172.24.128.15 kein Name ermittelt werden kann.
Steht der zugehörige Client im DNS und ist ein reverse lookup möglich? (Fehler: Can't find name for IP 172.24.128.15)

Falls nicht, kannst du den Client in die /etc/hosts eintragen und so temporär eine lokale Adressauflösung ermöglichen. Dann würde ich in diesem Fall den FQDN verwenden.


Towning hat geschrieben:3. Versucht über den opsi-Configed lokal -> Server-Konsole -> opsi - Verteilung opsi-client-agent zu verteilen
Pop-Up Meldung:
Mai 14 13:13:59.396 2019 --Bitte Verbindung/-sdaten überprüfen. Status: (nicht verbunden)

Erst mal Forum besucht und https://forum.uib.de/viewtopic.php?t=319 gefunden
An die %TEMP%\preloginloader.log von beiden Rechnern an denen ich es versucht habe komme ich z. Z. nicht ran.
Die 172.24.128.14.log (die letzten Einträge):

Code: Alles auswählen

[3] [May 13 14:14:07] 6 authentication failures from '172.24.128.14' in a row, waiting 60 seconds to prevent flooding (workers.py|94)
[5] [May 13 14:17:06] Application 'opsi-script 4.12.0.21' on client '172.24.128.14' did not send cookie (workers.py|185)
[5] [May 13 14:17:06] New session created (session.py|77)
[5] [May 13 14:17:06] Authorization request from towning@172.24.128.14 (application: opsi-script 4.12.0.21) (workers.py|217)
[5] [May 13 14:17:07] Session '43KNYEjtnB51TtvvRl9HbucXpiVxoT97' from ip '172.24.128.14', application 'opsi-script 4.12.0.21' deleted (Session.py|234)
[2] [May 13 14:17:07] Traceback: (Logger.py|798)
[2] [May 13 14:17:07]   File "/usr/lib/python2.7/dist-packages/OPSI/Service/Worker.py", line 289, in _errback failure.raiseException() (Logger.py|798)
[2] [May 13 14:17:07]   File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 651, in _runCallbacks current.result = callback(current.result, *args, **kw) (Logger.py|798)
[2] [May 13 14:17:07]   File "/usr/lib/python2.7/dist-packages/opsiconfd/workers.py", line 294, in _authenticate raise OpsiAuthenticationError(errorMessage) (Logger.py|798)
[2] [May 13 14:17:07]      ==>>> Opsi authentication error: Authentication failure for 'towning' from '172.24.128.14': Backend authentication error: Backend authentication error: PAM authentication failed for user 'towning': ('Authentication failure', 7) (Worker.py|291)
[5] [May 13 14:17:07] New session created (session.py|77)
[5] [May 13 14:17:07] Application 'opsi-script 4.12.0.21' on client '172.24.128.14' supplied non existing session id: 43KNYEjtnB51TtvvRl9HbucXpiVxoT97 (Worker.py|396)
[5] [May 13 14:17:07] Authorization request from towning@172.24.128.14 (application: opsi-script 4.12.0.21) (workers.py|217)
[5] [May 13 14:17:09] Session '8mwdXRe1FoCnYp3qvplQLlAecVSAP2n6' from ip '172.24.128.14', application 'opsi-script 4.12.0.21' deleted (Session.py|234)
[2] [May 13 14:17:09] Traceback: (Logger.py|798)
[2] [May 13 14:17:09]   File "/usr/lib/python2.7/dist-packages/OPSI/Service/Worker.py", line 289, in _errback failure.raiseException() (Logger.py|798)
[2] [May 13 14:17:09]   File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 651, in _runCallbacks current.result = callback(current.result, *args, **kw) (Logger.py|798)
[2] [May 13 14:17:09]   File "/usr/lib/python2.7/dist-packages/opsiconfd/workers.py", line 294, in _authenticate raise OpsiAuthenticationError(errorMessage) (Logger.py|798)
[2] [May 13 14:17:09]      ==>>> Opsi authentication error: Authentication failure for 'towning' from '172.24.128.14': Backend authentication error: Backend authentication error: PAM authentication failed for user 'towning': ('Authentication failure', 7) (Worker.py|291)
[5] [May 13 14:17:09] Application 'opsi-script 4.12.0.21' on client '172.24.128.14' did not send cookie (workers.py|185)
[5] [May 13 14:17:09] New session created (session.py|77)
[5] [May 13 14:17:09] Authorization request from towning@172.24.128.14 (application: opsi-script 4.12.0.21) (workers.py|217)
[5] [May 13 14:17:11] Session 'isBVNLJcKdsCqzeJwNxwz2KoROhP0EHH' from ip '172.24.128.14', application 'opsi-script 4.12.0.21' deleted (Session.py|234)
[2] [May 13 14:17:11] Traceback: (Logger.py|798)
[2] [May 13 14:17:11]   File "/usr/lib/python2.7/dist-packages/OPSI/Service/Worker.py", line 289, in _errback failure.raiseException() (Logger.py|798)
[2] [May 13 14:17:11]   File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 651, in _runCallbacks current.result = callback(current.result, *args, **kw) (Logger.py|798)
[2] [May 13 14:17:11]   File "/usr/lib/python2.7/dist-packages/opsiconfd/workers.py", line 294, in _authenticate raise OpsiAuthenticationError(errorMessage)  (Logger.py|798)
[2] [May 13 14:17:11]      ==>>> Opsi authentication error: Authentication failure for 'towning' from '172.24.128.14': Backend authentication error: Backend authentication error: PAM authentication failed for user 'towning': ('Authentication failure', 7) (Worker.py|291)
[5] [May 13 14:17:11] New session created (session.py|77)
[5] [May 13 14:17:11] Application 'opsi-script 4.12.0.21' on client '172.24.128.14' supplied non existing session id: isBVNLJcKdsCqzeJwNxwz2KoROhP0EHH (Worker.py|396)
[5] [May 13 14:17:11] Authorization request from towning@172.24.128.14 (application: opsi-script 4.12.0.21) (workers.py|217)
[5] [May 13 14:17:13] Session 'uvhBR5BsibkNBRsC95aKogH2eR8p4qeu' from ip '172.24.128.14', application 'opsi-script 4.12.0.21' deleted (Session.py|234)
[2] [May 13 14:17:13] Traceback: (Logger.py|798)
[2] [May 13 14:17:13]   File "/usr/lib/python2.7/dist-packages/OPSI/Service/Worker.py", line 289, in _errback failure.raiseException() (Logger.py|798)
[2] [May 13 14:17:13]   File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 651, in _runCallbacks current.result = callback(current.result, *args, **kw) (Logger.py|798)
[2] [May 13 14:17:13]   File "/usr/lib/python2.7/dist-packages/opsiconfd/workers.py", line 294, in _authenticate raise OpsiAuthenticationError(errorMessage) (Logger.py|798)
[2] [May 13 14:17:13]      ==>>> Opsi authentication error: Authentication failure for 'towning' from '172.24.128.14': Backend authentication error: Backend authentication error: PAM authentication failed for user 'towning': ('Authentication failure', 7) (Worker.py|291)
[5] [May 13 14:17:13] New session created (session.py|77)
[5] [May 13 14:17:13] Application 'opsi-script 4.12.0.21' on client '172.24.128.14' supplied non existing session id: uvhBR5BsibkNBRsC95aKogH2eR8p4qeu (Worker.py|396)
[5] [May 13 14:17:13] Authorization request from towning@172.24.128.14 (application: opsi-script 4.12.0.21) (workers.py|217)
[5] [May 13 14:17:15] Session 'FbwLogmVrWjKTp8cISp4ij8hMly33sRF' from ip '172.24.128.14', application 'opsi-script 4.12.0.21' deleted (Session.py|234)
[2] [May 13 14:17:15] Traceback: (Logger.py|798)
[2] [May 13 14:17:15]   File "/usr/lib/python2.7/dist-packages/OPSI/Service/Worker.py", line 289, in _errback failure.raiseException() (Logger.py|798)
[2] [May 13 14:17:15]   File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 651, in _runCallbacks current.result = callback(current.result, *args, **kw) (Logger.py|798)
[2] [May 13 14:17:15]   File "/usr/lib/python2.7/dist-packages/opsiconfd/workers.py", line 294, in _authenticate raise OpsiAuthenticationError(errorMessage) (Logger.py|798)
[2] [May 13 14:17:15]      ==>>> Opsi authentication error: Authentication failure for 'towning' from '172.24.128.14': Backend authentication error: Backend authentication error: PAM authentication failed for user 'towning': ('Authentication failure', 7) (Worker.py|291)
[5] [May 13 14:17:15] New session created (session.py|77)
[5] [May 13 14:17:15] Application 'opsi-script 4.12.0.21' on client '172.24.128.14' supplied non existing session id: FbwLogmVrWjKTp8cISp4ij8hMly33sRF (Worker.py|396)
[5] [May 13 14:17:15] Authorization request from towning@172.24.128.14 (application: opsi-script 4.12.0.21) (workers.py|217)
[5] [May 13 14:17:18] Session 'sm9tUOBJYvIHoRZXzhpXnYDxtBmqgyjl' from ip '172.24.128.14', application 'opsi-script 4.12.0.21' deleted (Session.py|234)
[2] [May 13 14:17:18] Traceback: (Logger.py|798)
[2] [May 13 14:17:18]   File "/usr/lib/python2.7/dist-packages/OPSI/Service/Worker.py", line 289, in _errback failure.raiseException() (Logger.py|798)
[2] [May 13 14:17:18]   File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 651, in _runCallbacks current.result = callback(current.result, *args, **kw) (Logger.py|798)
[2] [May 13 14:17:18]   File "/usr/lib/python2.7/dist-packages/opsiconfd/workers.py", line 294, in _authenticate raise OpsiAuthenticationError(errorMessage) (Logger.py|798)
[2] [May 13 14:17:18]      ==>>> Opsi authentication error: Authentication failure for 'towning' from '172.24.128.14': Backend authentication error: Backend authentication error: PAM authentication failed for user 'towning': ('Authentication failure', 7) (Worker.py|291)
[3] [May 13 14:17:18] 6 authentication failures from '172.24.128.14' in a row, waiting 60 seconds to prevent flooding (workers.py|94)


Die Anmeldung scheitert: vielleicht falsche Credentials.
Falls hier zusätzliche PAM-Konfiguration / -Anbindung auf dem opsi-Server gemacht wurde, würde ich das mal checken.



Gruß

Niko
opsi development - uib gmbh
For productive opsi installations we recommend support contracts.

Towning
Beiträge: 4
Registriert: 02 Jan 2010, 17:51

Re: opsi-client-agent Installation bricht mit Fehler ab

Beitragvon Towning » 22 Mai 2019, 17:02

Hallo Niko,

ich hatte gestern (bevor ich die Antwort gelesen hatte) den OPSI neu installiert.
Vorher die Datenbank, pckey und die Client-Dateien gesichert und hinterher in den neu installierten Opsi wieder eingespielt.
Softwarepakete hatte ich ja noch auf dem Server zum einspielen.

n.wenselowski hat geschrieben:Bitte versuch es mal ohne elevated rights.
Der opsi-client-agent wurde vor einiger Zeit so umgebaut, dass das nicht mehr notwendig ist.
Voraussetzung ist die Verwendung eines halbwegs aktuellen opsi-client-agent.

Heute vor Ort gewesen und beide Varianten funktionieren.

n.wenselowski hat geschrieben:Den bekommst du so (und gleich dazu einen neuen opsi-winst):

Code: Alles auswählen

opsi-package-updater -v update opsi-client-agent opsi-winst


Hatte ich gestern vor der Neuinstallation porbiert - hat nicht funktioniert.

Als 2. erneut versucht über opsi-deploy-client-agent zu installieren
Ausgabe (verkürzt):

Code: Alles auswählen

Winexe failure RuntimeError(u'Command \'/usr/bin/winexe -U \'opsi%*** confidential ***\' //pvgen15-53108 \'cmd.exe /C "del /s /q c:\\tmp\\opsi-client-agent_inst && rmdir /s /q c:\\tmp\\opsi-client-agent_inst || echo not found"\'\' failed (1):\n',), retrying
Executing: /usr/bin/winexe -V
Using encoding 'UTF-8'
Winexe Version: winexe version 4.8This program may be freely redistributed under the terms of the GNU GPLv3
Executing: /usr/bin/winexe -U 'opsi%*** confidential ***' //pvgen15-53108 'cmd.exe /C "del /s /q c:\tmp\opsi-client-agent_inst && rmdir /s /q c:\tmp\opsi-client-agent_inst || echo not found"'
Using encoding 'UTF-8'
Deployment to 'PVGEN15-53108.genv.lgh' failed: Failed to execute command on host u'pvgen15-53108': winexe error: Command '/usr/bin/winexe -U 'opsi%*** confidential ***' //pvgen15-53108 'cmd.exe /C "del /s /q c:\tmp\opsi-client-agent_inst && rmdir /s /q c:\tmp\opsi-client-agent_inst || echo not found"'' failed (1):

DNS scheint mittlerweile wieder sauber zu laufen - nichts daran geändert.
In https://forum.opsi.org/viewtopic.php?f=7&t=11088&hilit=mkdir+failed+on+directory+%2Fusr%2Flocal%2Fsamba%2Fvar%2Fcache
unten den Verweis auf Windows UAC gefunden und Registry über GPO geändert.
Der erneute Versuch ging aber ebenfalls mit der gleichen Meldung daneben.
Ich habe aber den Verdacht das ESET Endpoint Protection daran schuld ist. Bei einem Versuch hier im Büro hatte ich die Meldung von ESET das die Winexe von ESET gelöscht wurde. :x
Werde mal einen Rechner aufsetzen und ESET nicht installieren um zu testen ob dann die Installation klappt, da ich vermute das ich mit dem
Virenscanner den Schuldigen für das Versagen vom opsi-deploy-client-agent gefunden habe.

Als 3. ebenfalls erneut versucht über den opsi-Configed lokal -> Server-Konsole -> opsi - Verteilung opsi-client-agent zu verteilen
Pop-Up Meldung bleibt:

Code: Alles auswählen

Mai 14 13:13:59.396 2019 --Bitte Verbindung/-sdaten überprüfen. Status: (nicht verbunden)

habe die mal kopiert..... nur das Datum und die Uhrzeit sind anders

Da ich den Client-Agent aber jetzt zumindest auf eine Weise installieren kann, reicht mir das erst mal.
Waren ja nur 5 vorhandene Rechner neu aufzunehmen.
Fall neue kommen werden die sowieso über den Opsi installiert :D
n.wenselowski hat geschrieben:

Code: Alles auswählen

[2] [May 13 14:17:18]      ==>>> Opsi authentication error: Authentication failure for 'towning' from '172.24.128.14': Backend authentication error: Backend authentication error: PAM authentication failed for user 'towning': ('Authentication failure', 7) (Worker.py|291)
[3] [May 13 14:17:18] 6 authentication failures from '172.24.128.14' in a row, waiting 60 seconds to prevent flooding (workers.py|94)

Die Anmeldung scheitert: vielleicht falsche Credentials.
Falls hier zusätzliche PAM-Konfiguration / -Anbindung auf dem opsi-Server gemacht wurde, würde ich das mal checken.


An PAM nichts gedreht....
Und da ich bei anderen Servern zur gleichen Zeit die gleichen Updates gemacht habe, denke ich (da die anderen Server ohne Probleme laufen)
das irgendetwas bei dem Opsi-Update oder dem Debian-Update daneben gegangen ist was das System vergrützt hat.

Rückmeldung bezüglich opsi-deploy-client-agent und Virenscanner gebe ich dann noch.

Gruß
Frank

Towning
Beiträge: 4
Registriert: 02 Jan 2010, 17:51

Re: opsi-client-agent Installation bricht mit Fehler ab

Beitragvon Towning » 29 Mai 2019, 16:19

Rückmeldung bezüglich opsi-client-agent und Virenscanner.
Ist fast binär ;) mal wird die Winexe vom Virenscanner gelöscht aber meistens klappt es.
Kann nicht sagen woher das kommt und bin nicht in der Lage das ganze zeitlich zu verfolgen :x

Was ich aber sagen kann, ist das ich den Wald vor lauter Bäumen nicht sehe :oops:
Wenn eine Windows-Domäne vorhanden ist (oder aber ein Windows 10 PC) dann kann das nicht klappen:
./opsi-deploy-client-agent -vv -u Administrator -p *** confidential *** --use-ip-address 172.24.128.15
macht man es richtig dann klappt das in der Regel. Also so:
./opsi-deploy-client-agent -vv -u <HOSTNAME oder DOMAINNAME>\\Administrator -p *** confidential *** --use-ip-address 172.24.128.15

Wenn mir noch jemand verraten kann, ob ich das Thema schliessen kann/muß?
Habe keine Möglichkeit dazu gefunden.

Gruß
Frank

uncle_scrooge
Beiträge: 579
Registriert: 21 Feb 2012, 12:03
Wohnort: Mainz

Re: opsi-client-agent Installation bricht mit Fehler ab

Beitragvon uncle_scrooge » 29 Mai 2019, 18:33

Wenn mir noch jemand verraten kann, ob ich das Thema schliessen kann/muß?
Habe keine Möglichkeit dazu gefunden.

Müssen muß man nix. Aber nett wär's schon.
Und nein, schließen im klassischen Sinn (danach kann keiner kommen) gibt es nicht. Zumindest können wir niedere Chargen das nicht.
Aber Du kannst den Titel von Deinem Eingangspost editieren. Ein geklammertes Gelöst/Solved/Heureka vorangestellt würde sich anbieten.