Seite 1 von 2
opsi client agent Windows 7 64Bit
Verfasst: 23 Jan 2012, 14:48
von insideAC
Guten Tag,
ich abe leider bei einem einzigen Windows 7 64 Bit Client das folgende Problem:
Der opsi-Client kann per deployment-Skript erfolgreich installiert werden.
Beim Booten erscheint auch das Schloss, jedoch passiert anschließend nicht. Das übliche osi-Popup erscheint nicht. Es dauert einige Zeit und dann wird der Login freigegeben. Gesetzte Aktionen werden weder beim Booten durchgeführt, noch "on demand".
Ich möchte nicht ausschließen, dass das Problem etwas damit zu tun hat, dass in der Vergangenheit manuelle Instalationsversuche des opsi-Client-Agent durchgeführt wurden.
Im Anhang ist das Logfile "opsiclientd" vom letzten Bootvorgang zu finden.
Ich hoffe jemand kann mir weiterhelfen. Das Problem trit nur bei diesem einen Rechner auf.
Gibt es vielleicht eine Möglichkeit oder Anleitung das Client-System vollständig von opsi-Komponenten zu bereinigen um evtl anschließend eine Neuinstallation des Agents durchführen zu können.
Danke und Grüße!
Re: opsi client agent Windows 7 64Bit
Verfasst: 23 Jan 2012, 14:53
von insideAC
Ich kann leider keine Dateien anhängen, deswegen hier eine Meldung aus dem Logfle diie mir komisch vorkommt:
Code: Alles auswählen
Failed to get current active desktop name for session 1, using 'default' (Opsiclientd.pyo|454)
und
Code: Alles auswählen
[2] [Jan 23 07:08:18] [ action_processor_starter.exe ] Traceback: (Logger.pyo|742)
[2] [Jan 23 07:08:18] [ action_processor_starter.exe ] line 90 in '<module>' in file 'action_processor_starter.py' (Logger.pyo|742)
[2] [Jan 23 07:08:18] [ action_processor_starter.exe ] line 326 in '__init__' in file 'OPSI\Backend\JSONRPC.pyo' (Logger.pyo|742)
[2] [Jan 23 07:08:18] [ action_processor_starter.exe ] line 415 in 'connect' in file 'OPSI\Backend\JSONRPC.pyo' (Logger.pyo|742)
[2] [Jan 23 07:08:18] [ action_processor_starter.exe ] line 603 in '_jsonRPC' in file 'OPSI\Backend\JSONRPC.pyo' (Logger.pyo|742)
[2] [Jan 23 07:08:18] [ action_processor_starter.exe ] line 123 in 'execute' in file 'OPSI\Backend\JSONRPC.pyo' (Logger.pyo|742)
[2] [Jan 23 07:08:18] [ action_processor_starter.exe ] line 134 in 'waitForResult' in file 'OPSI\Backend\Backend.pyo' (Logger.pyo|742)
[2] [Jan 23 07:08:18] [ action_processor_starter.exe ] ==>>> [Errno 10061] Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte (action_processor_starter.py|121)
[3] [Jan 23 07:08:18] [ action_processor_starter.exe ] Failed to process action requests: [Errno 10061] Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte (action_processor_starter.py|128)
Re: opsi client agent Windows 7 64Bit
Verfasst: 23 Jan 2012, 16:13
von ueluekmen
Hi, das was hier geposted wird ist ein Folgefehler, weil der eigentliche opsiclientd-Prozess und damit der Webservice nicht läuft, sorry aber allein mit dieser Log-Meldung kann man nichts anfangen. Steht denn Vorher was mit dem Loglevel 2? ([2])
Re: opsi client agent Windows 7 64Bit
Verfasst: 23 Jan 2012, 16:54
von insideAC
Hallo,
das Log ist sehr lang. Hier der Block der unmittlebar davor kommt:
Code: Alles auswählen
[5] [Jan 23 07:07:50] [ event processing gui_startup ] Event config 'sync_completed{cache_ready}' added to event generator 'sync_completed' (Events.pyo|1107)
[5] [Jan 23 07:07:50] [ event processing gui_startup ] Event config 'gui_startup' added to event generator 'gui_startup' (Events.pyo|1107)
[5] [Jan 23 07:07:50] [ event processing gui_startup ] Event config 'gui_startup{cache_ready}' added to event generator 'gui_startup' (Events.pyo|1107)
[5] [Jan 23 07:07:50] [ event processing gui_startup ] Event config 'on_demand' added to event generator 'on_demand' (Events.pyo|1107)
[5] [Jan 23 07:07:50] [ event processing gui_startup ] Event config 'sync_completed{cache_ready_user_logged_in}' added to event generator 'sync_completed' (Events.pyo|1107)
[5] [Jan 23 07:07:50] [ event processing gui_startup ] Event config 'gui_startup{user_logged_in}' added to event generator 'gui_startup' (Events.pyo|1107)
[5] [Jan 23 07:07:50] [ event processing gui_startup ] Event config 'sync_completed' added to event generator 'sync_completed' (Events.pyo|1107)
[5] [Jan 23 07:07:50] [ event processing gui_startup ] Event config 'software_on_demand' added to event generator 'software_on_demand' (Events.pyo|1107)
[5] [Jan 23 07:07:50] [ event processing gui_startup ] Event config 'on_demand{user_logged_in}' added to event generator 'on_demand' (Events.pyo|1107)
[5] [Jan 23 07:07:50] [ event processing gui_startup ] Updating config file: 'C:\Program Files (x86)\opsi.org\opsi-client-agent\opsiclientd\opsiclientd.conf' (Config.pyo|322)
[5] [Jan 23 07:07:50] [ event processing gui_startup ] No need to write config file 'C:\Program Files (x86)\opsi.org\opsi-client-agent\opsiclientd\opsiclientd.conf', config file is up to date (Config.pyo|353)
[5] [Jan 23 07:07:50] [ event processing gui_startup ] [ 1] product firefox_9.0.1: setup (EventProcessing.pyo|619)
[5] [Jan 23 07:07:50] [ event processing gui_startup ] Start processing action requests (EventProcessing.pyo|630)
[5] [Jan 23 07:07:50] [ event processing gui_startup ] Selecting depot for products [u'firefox_9.0.1'] (Config.pyo|379)
[5] [Jan 23 07:07:50] [ event processing gui_startup ] (fullversion) Selecting depot for products [u'firefox_9.0.1'] (__init__.pyo|38)
[6] [Jan 23 07:07:50] [ event processing gui_startup ] Dynamic depot selection disabled (__init__.pyo|92)
[6] [Jan 23 07:07:51] [ event processing gui_startup ] Master depot for products [u'firefox_9.0.1'] is opsi.inside.de (__init__.pyo|116)
[5] [Jan 23 07:07:51] [ event processing gui_startup ] Selected depot is: <OpsiConfigserver id 'opsi.inside.de'> (__init__.pyo|189)
[6] [Jan 23 07:07:51] [ event processing gui_startup ] Setting config value depot_server.depot_id (Config.pyo|197)
[6] [Jan 23 07:07:51] [ event processing gui_startup ] Setting config value depot_server.url (Config.pyo|197)
[5] [Jan 23 07:07:51] [ event processing gui_startup ] Getting TrustedInstaller service configuration (EventProcessing.pyo|676)
[6] [Jan 23 07:07:51] [ opsiclientd ] Searching pids of process name winlogon.exe (session id: 1) (Windows.pyo|1169)
[6] [Jan 23 07:07:51] [ opsiclientd ] Found process winlogon.exe with matching name (pid 976, session 1) (Windows.pyo|1191)
[5] [Jan 23 07:07:51] [ opsiclientd ] Executing: 'C:\Program Files (x86)\opsi.org\opsi-client-agent\\opsiclientd_rpc.exe "ws15.inside.de" "*** confidential ***" "4441" "setCurrentActiveDesktopName("1", System.getActiveDesktopName())"' in session '1' on desktop 'winsta0\winlogon' (Windows.pyo|1348)
[6] [Jan 23 07:07:51] [ opsiclientd ] Process startet, pid: 3740 (Windows.pyo|1351)
[6] [Jan 23 07:07:51] [ opsiclientd ] Waiting for process ending: 3740 (timeout: 60 seconds) (Windows.pyo|1354)
[5] [Jan 23 07:08:04] [ opsiclientd ] Process 3740 ended with exit code 1 (Windows.pyo|1364)
[5] [Jan 23 07:08:04] [ event processing gui_startup ] Updating action processor (EventProcessing.pyo|395)
[5] [Jan 23 07:08:04] [ event processing gui_startup ] Mounting depot share smb://opsi/opsi_depot (EventProcessing.pyo|363)
[6] [Jan 23 07:08:04] [ event processing gui_startup ] Added depot 'opsi' to trusted domains (EventProcessing.pyo|372)
[5] [Jan 23 07:08:04] [ event processing gui_startup ] Mounting '\\opsi\opsi_depot' to 'p:' (Windows.pyo|664)
[5] [Jan 23 07:08:05] [ event processing gui_startup ] Updating action processor from depot dir 'p:\opsi-winst\\files\\opsi-winst' (EventProcessing.pyo|442)
[5] [Jan 23 07:08:05] [ event processing gui_startup ] Local action processor exists and seems to be up to date (EventProcessing.pyo|453)
[5] [Jan 23 07:08:05] [ event processing gui_startup ] Unmounting depot share (EventProcessing.pyo|388)
[5] [Jan 23 07:08:05] [ event processing gui_startup ] Starting action processor in session '1' on desktop 'default' (EventProcessing.pyo|775)
[6] [Jan 23 07:08:05] [ event processing gui_startup ] Running command C:\Program Files (x86)\opsi.org\opsi-client-agent\action_processor_starter.exe "ws15.inside.de" "*** confidential ***" "4441" "c:\\tmp\\opsiclientd.log" "6" "smb://opsi/opsi_depot" "p:" "pcpatch" "*** confidential ***" "1" "default" "\"C:\Program Files (x86)\opsi.org\opsi-client-agent\\opsi-winst\\winst32.exe\" /opsiservice \"https://192.168.1.75:4447/rpc\" /clientid ws15.inside.de /username ws15.inside.de /password *** confidential *** " 10800 "" "" false in session '1' on desktop 'default' (EventProcessing.pyo|296)
[6] [Jan 23 07:08:05] [ event processing gui_startup ] Searching pids of process name winlogon.exe (session id: 1) (Windows.pyo|1169)
[6] [Jan 23 07:08:05] [ event processing gui_startup ] Found process winlogon.exe with matching name (pid 976, session 1) (Windows.pyo|1191)
[5] [Jan 23 07:08:05] [ event processing gui_startup ] Executing: 'C:\Program Files (x86)\opsi.org\opsi-client-agent\action_processor_starter.exe "ws15.inside.de" "*** confidential ***" "4441" "c:\\tmp\\opsiclientd.log" "6" "smb://opsi/opsi_depot" "p:" "pcpatch" "*** confidential ***" "1" "default" "\"C:\Program Files (x86)\opsi.org\opsi-client-agent\\opsi-winst\\winst32.exe\" /opsiservice \"https://192.168.1.75:4447/rpc\" /clientid ws15.inside.de /username ws15.inside.de /password *** confidential *** " 10800 "" "" false' in session '1' on desktop 'winsta0\default' (Windows.pyo|1348)
[6] [Jan 23 07:08:05] [ event processing gui_startup ] Process startet, pid: 3904 (Windows.pyo|1351)
[6] [Jan 23 07:08:05] [ event processing gui_startup ] Waiting for process ending: 3904 (timeout: 0 seconds) (Windows.pyo|1354)
[6] [Jan 23 07:08:06] [ control pipe ] Creating pipe \\.\pipe\opsiclientd (ControlPipe.pyo|253)
[5] [Jan 23 07:08:06] [ control pipe ] -----> Executing: getBlockLogin() (JsonRpc.pyo|123)
[5] [Jan 23 07:08:06] [ opsiclientd ] rpc getBlockLogin: blockLogin is 'True' (ControlPipe.pyo|428)
[6] [Jan 23 07:08:06] [ control pipe ] Got result (JsonRpc.pyo|131)
[6] [Jan 23 07:08:09] [ control pipe ] Creating pipe \\.\pipe\opsiclientd (ControlPipe.pyo|253)
[5] [Jan 23 07:08:09] [ control pipe ] -----> Executing: getBlockLogin() (JsonRpc.pyo|123)
[5] [Jan 23 07:08:09] [ opsiclientd ] rpc getBlockLogin: blockLogin is 'True' (ControlPipe.pyo|428)
[6] [Jan 23 07:08:09] [ control pipe ] Got result (JsonRpc.pyo|131)
[6] [Jan 23 07:08:11] [ action_processor_starter.exe ] Traceback: (Logger.pyo|742)
[6] [Jan 23 07:08:11] [ action_processor_starter.exe ] line 108 in 'process' in file 'OPSI\Backend\JSONRPC.pyo' (Logger.pyo|742)
[6] [Jan 23 07:08:11] [ action_processor_starter.exe ] line 635 in '_request' in file 'OPSI\Backend\JSONRPC.pyo' (Logger.pyo|742)
[6] [Jan 23 07:08:11] [ action_processor_starter.exe ] line 474 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|742)
[6] [Jan 23 07:08:11] [ action_processor_starter.exe ] line 474 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|742)
[6] [Jan 23 07:08:11] [ action_processor_starter.exe ] line 474 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|742)
[6] [Jan 23 07:08:11] [ action_processor_starter.exe ] line 474 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|742)
[6] [Jan 23 07:08:11] [ action_processor_starter.exe ] line 474 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|742)
[6] [Jan 23 07:08:11] [ action_processor_starter.exe ] line 402 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|742)
[6] [Jan 23 07:08:11] [ action_processor_starter.exe ] line 910 in 'request' in file 'httplib.pyo' (Logger.pyo|742)
[6] [Jan 23 07:08:11] [ action_processor_starter.exe ] line 947 in '_send_request' in file 'httplib.pyo' (Logger.pyo|742)
[6] [Jan 23 07:08:11] [ action_processor_starter.exe ] line 904 in 'endheaders' in file 'httplib.pyo' (Logger.pyo|742)
[6] [Jan 23 07:08:11] [ action_processor_starter.exe ] line 776 in '_send_output' in file 'httplib.pyo' (Logger.pyo|742)
[6] [Jan 23 07:08:11] [ action_processor_starter.exe ] line 735 in 'send' in file 'httplib.pyo' (Logger.pyo|742)
[6] [Jan 23 07:08:11] [ action_processor_starter.exe ] line 1108 in 'connect' in file 'httplib.pyo' (Logger.pyo|742)
[6] [Jan 23 07:08:11] [ action_processor_starter.exe ] line 514 in 'create_connection' in file 'socket.pyo' (Logger.pyo|742)
[6] [Jan 23 07:08:11] [ action_processor_starter.exe ] ==>>> Failed to process method 'backend_getInterface': [Errno 10061] Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte (JSONRPC.pyo|112)
[6] [Jan 23 07:08:12] [ control pipe ] Creating pipe \\.\pipe\opsiclientd (ControlPipe.pyo|253)
[5] [Jan 23 07:08:12] [ control pipe ] -----> Executing: getBlockLogin() (JsonRpc.pyo|123)
[5] [Jan 23 07:08:12] [ opsiclientd ] rpc getBlockLogin: blockLogin is 'True' (ControlPipe.pyo|428)
[6] [Jan 23 07:08:12] [ control pipe ] Got result (JsonRpc.pyo|131)
[6] [Jan 23 07:08:15] [ control pipe ] Creating pipe \\.\pipe\opsiclientd (ControlPipe.pyo|253)
[5] [Jan 23 07:08:15] [ control pipe ] -----> Executing: getBlockLogin() (JsonRpc.pyo|123)
[5] [Jan 23 07:08:15] [ opsiclientd ] rpc getBlockLogin: blockLogin is 'True' (ControlPipe.pyo|428)
[6] [Jan 23 07:08:15] [ control pipe ] Got result (JsonRpc.pyo|131)
[6] [Jan 23 07:08:18] [ control pipe ] Creating pipe \\.\pipe\opsiclientd (ControlPipe.pyo|253)
[5] [Jan 23 07:08:18] [ control pipe ] -----> Executing: getBlockLogin() (JsonRpc.pyo|123)
[5] [Jan 23 07:08:18] [ opsiclientd ] rpc getBlockLogin: blockLogin is 'True' (ControlPipe.pyo|428)
[6] [Jan 23 07:08:18] [ control pipe ] Got result (JsonRpc.pyo|131)
[6] [Jan 23 07:08:18] [ action_processor_starter.exe ] Traceback: (Logger.pyo|742)
[6] [Jan 23 07:08:18] [ action_processor_starter.exe ] line 108 in 'process' in file 'OPSI\Backend\JSONRPC.pyo' (Logger.pyo|742)
[6] [Jan 23 07:08:18] [ action_processor_starter.exe ] line 635 in '_request' in file 'OPSI\Backend\JSONRPC.pyo' (Logger.pyo|742)
[6] [Jan 23 07:08:18] [ action_processor_starter.exe ] line 474 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|742)
[6] [Jan 23 07:08:18] [ action_processor_starter.exe ] line 474 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|742)
[6] [Jan 23 07:08:18] [ action_processor_starter.exe ] line 474 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|742)
[6] [Jan 23 07:08:18] [ action_processor_starter.exe ] line 474 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|742)
[6] [Jan 23 07:08:18] [ action_processor_starter.exe ] line 474 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|742)
[6] [Jan 23 07:08:18] [ action_processor_starter.exe ] line 402 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|742)
[6] [Jan 23 07:08:18] [ action_processor_starter.exe ] line 910 in 'request' in file 'httplib.pyo' (Logger.pyo|742)
[6] [Jan 23 07:08:18] [ action_processor_starter.exe ] line 947 in '_send_request' in file 'httplib.pyo' (Logger.pyo|742)
[6] [Jan 23 07:08:18] [ action_processor_starter.exe ] line 904 in 'endheaders' in file 'httplib.pyo' (Logger.pyo|742)
[6] [Jan 23 07:08:18] [ action_processor_starter.exe ] line 776 in '_send_output' in file 'httplib.pyo' (Logger.pyo|742)
[6] [Jan 23 07:08:18] [ action_processor_starter.exe ] line 735 in 'send' in file 'httplib.pyo' (Logger.pyo|742)
[6] [Jan 23 07:08:18] [ action_processor_starter.exe ] line 1108 in 'connect' in file 'httplib.pyo' (Logger.pyo|742)
[6] [Jan 23 07:08:18] [ action_processor_starter.exe ] line 514 in 'create_connection' in file 'socket.pyo' (Logger.pyo|742)
[6] [Jan 23 07:08:18] [ action_processor_starter.exe ] ==>>> Failed to process method 'getPossibleMethods_listOfHashes': [Errno 10061] Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte (JSONRPC.pyo|112)
Re: opsi client agent Windows 7 64Bit
Verfasst: 26 Jan 2012, 11:39
von insideAC
Hallo,
leider habe ich keine Antworten mehr erhalten.
Hier habe ich nun den Inhalt der Datei "opsi_loginblocker.txt".
Code: Alles auswählen
2012-01-26 11:23:13 [6] Registry value LoginBlockerLogLevel read, result 6
2012-01-26 11:23:13 [5] LoginBlockerLogLevel is: 6
2012-01-26 11:23:13 [6] Registry value LoginBlockerTimeoutConnect read, result 120
2012-01-26 11:23:13 [5] LoginBlockerTimeoutConnect is: 120
2012-01-26 11:23:13 [5] Communicating with service through pipe
2012-01-26 11:23:13 [6] Creating file: \\.\pipe\opsiclientd
2012-01-26 11:23:13 [3] Could not open pipe \\.\pipe\opsiclientd: 2
2012-01-26 11:23:23 [6] Creating file: \\.\pipe\opsiclientd
2012-01-26 11:23:23 [3] Could not open pipe \\.\pipe\opsiclientd: 2
2012-01-26 11:23:33 [6] Creating file: \\.\pipe\opsiclientd
2012-01-26 11:23:33 [3] Could not open pipe \\.\pipe\opsiclientd: 2
2012-01-26 11:23:43 [6] Creating file: \\.\pipe\opsiclientd
2012-01-26 11:23:43 [3] Could not open pipe \\.\pipe\opsiclientd: 2
2012-01-26 11:23:53 [6] Creating file: \\.\pipe\opsiclientd
2012-01-26 11:23:53 [3] Could not open pipe \\.\pipe\opsiclientd: 2
2012-01-26 11:24:03 [6] Creating file: \\.\pipe\opsiclientd
2012-01-26 11:24:03 [3] Could not open pipe \\.\pipe\opsiclientd: 2
2012-01-26 11:24:13 [6] Creating file: \\.\pipe\opsiclientd
2012-01-26 11:24:13 [3] Could not open pipe \\.\pipe\opsiclientd: 2
2012-01-26 11:24:23 [6] Creating file: \\.\pipe\opsiclientd
2012-01-26 11:24:23 [3] Could not open pipe \\.\pipe\opsiclientd: 2
2012-01-26 11:24:33 [6] Creating file: \\.\pipe\opsiclientd
2012-01-26 11:24:33 [3] Could not open pipe \\.\pipe\opsiclientd: 2
2012-01-26 11:24:43 [6] Creating file: \\.\pipe\opsiclientd
2012-01-26 11:24:43 [3] Could not open pipe \\.\pipe\opsiclientd: 2
2012-01-26 11:24:53 [6] Creating file: \\.\pipe\opsiclientd
2012-01-26 11:24:53 [3] Could not open pipe \\.\pipe\opsiclientd: 2
2012-01-26 11:25:03 [6] Creating file: \\.\pipe\opsiclientd
2012-01-26 11:25:03 [3] Could not open pipe \\.\pipe\opsiclientd: 2
2012-01-26 11:25:13 [6] Creating file: \\.\pipe\opsiclientd
2012-01-26 11:25:13 [3] Could not open pipe \\.\pipe\opsiclientd: 2
2012-01-26 11:25:13 [3] Could not open pipe (timed out)
2012-01-26 11:25:13 [3] Service request '{"id": 1, "method": "getBlockLogin", "params": []}' failed
2012-01-26 11:25:23 [5] Filtering credential providers
2012-01-26 11:25:23 [3] Failed to query registry value LoginBlockerStart: 2
2012-01-26 11:25:23 [3] Failed to get LoginBlockerStart value from registry, using default
2012-01-26 11:25:23 [5] LoginBlockerStart is: 1
2012-01-26 11:25:23 [6] Registry value StartOpsiCredentialProvider read, result 0
2012-01-26 11:25:23 [5] StartOpsiCredentialProvider is: 0
2012-01-26 11:25:23 [6] Registry value LoginBlockerLogLevel read, result 6
2012-01-26 11:25:23 [5] LoginBlockerLogLevel is: 6
2012-01-26 11:25:23 [6] Registry value LoginBlockerTimeoutConnect read, result 120
2012-01-26 11:25:23 [5] LoginBlockerTimeoutConnect is: 120
2012-01-26 11:25:23 [5] Communicating with service through pipe
2012-01-26 11:25:23 [6] Creating file: \\.\pipe\opsiclientd
2012-01-26 11:25:23 [3] Could not open pipe \\.\pipe\opsiclientd: 2
2012-01-26 11:25:33 [6] Creating file: \\.\pipe\opsiclientd
2012-01-26 11:25:33 [3] Could not open pipe \\.\pipe\opsiclientd: 2
2012-01-26 11:25:43 [6] Creating file: \\.\pipe\opsiclientd
2012-01-26 11:25:43 [3] Could not open pipe \\.\pipe\opsiclientd: 2
2012-01-26 11:25:53 [6] Creating file: \\.\pipe\opsiclientd
2012-01-26 11:25:53 [3] Could not open pipe \\.\pipe\opsiclientd: 2
2012-01-26 11:26:03 [6] Creating file: \\.\pipe\opsiclientd
2012-01-26 11:26:03 [3] Could not open pipe \\.\pipe\opsiclientd: 2
2012-01-26 11:26:13 [6] Creating file: \\.\pipe\opsiclientd
2012-01-26 11:26:13 [3] Could not open pipe \\.\pipe\opsiclientd: 2
2012-01-26 11:26:23 [6] Creating file: \\.\pipe\opsiclientd
2012-01-26 11:26:23 [3] Could not open pipe \\.\pipe\opsiclientd: 2
2012-01-26 11:26:33 [6] Creating file: \\.\pipe\opsiclientd
2012-01-26 11:26:33 [3] Could not open pipe \\.\pipe\opsiclientd: 2
2012-01-26 11:26:43 [6] Creating file: \\.\pipe\opsiclientd
2012-01-26 11:26:43 [3] Could not open pipe \\.\pipe\opsiclientd: 2
2012-01-26 11:26:53 [6] Creating file: \\.\pipe\opsiclientd
2012-01-26 11:26:53 [3] Could not open pipe \\.\pipe\opsiclientd: 2
2012-01-26 11:27:03 [6] Creating file: \\.\pipe\opsiclientd
2012-01-26 11:27:03 [3] Could not open pipe \\.\pipe\opsiclientd: 2
2012-01-26 11:27:13 [6] Creating file: \\.\pipe\opsiclientd
2012-01-26 11:27:13 [3] Could not open pipe \\.\pipe\opsiclientd: 2
2012-01-26 11:27:23 [6] Creating file: \\.\pipe\opsiclientd
2012-01-26 11:27:23 [3] Could not open pipe \\.\pipe\opsiclientd: 2
2012-01-26 11:27:23 [3] Could not open pipe (timed out)
2012-01-26 11:27:23 [3] Service request '{"id": 1, "method": "getBlockLogin", "params": []}' failed
2012-01-26 11:33:26 [6] Registry value LoginBlockerLogLevel read, result 6
2012-01-26 11:33:26 [5] LoginBlockerLogLevel is: 6
2012-01-26 11:33:26 [6] Registry value LoginBlockerTimeoutConnect read, result 120
2012-01-26 11:33:26 [5] LoginBlockerTimeoutConnect is: 120
2012-01-26 11:33:26 [5] Communicating with service through pipe
2012-01-26 11:33:26 [6] Creating file: \\.\pipe\opsiclientd
2012-01-26 11:33:26 [6] Pipe successfully opened
2012-01-26 11:33:26 [5] Writing '{"id": 1, "method": "getBlockLogin", "params": []}' to pipe
2012-01-26 11:33:26 [6] Reading from pipe
2012-01-26 11:33:26 [5] Read '{"error": null, "result": false, "id": 1}' from pipe
2012-01-26 11:33:26 [6] getJsonValue() value of 'error' is 'null'
2012-01-26 11:33:26 [6] getJsonValue() value of 'result' is 'false'
2012-01-26 11:33:26 [5] Not blocking!
2012-01-26 11:35:31 [6] Registry value LoginBlockerLogLevel read, result 6
2012-01-26 11:35:31 [5] LoginBlockerLogLevel is: 6
2012-01-26 11:35:31 [6] Registry value LoginBlockerTimeoutConnect read, result 120
2012-01-26 11:35:31 [5] LoginBlockerTimeoutConnect is: 120
2012-01-26 11:35:31 [5] Communicating with service through pipe
2012-01-26 11:35:31 [6] Creating file: \\.\pipe\opsiclientd
2012-01-26 11:35:31 [6] Pipe successfully opened
2012-01-26 11:35:31 [5] Writing '{"id": 1, "method": "getBlockLogin", "params": []}' to pipe
2012-01-26 11:35:31 [6] Reading from pipe
2012-01-26 11:35:31 [5] Read '{"error": null, "result": false, "id": 1}' from pipe
2012-01-26 11:35:31 [6] getJsonValue() value of 'error' is 'null'
2012-01-26 11:35:31 [6] getJsonValue() value of 'result' is 'false'
2012-01-26 11:35:31 [5] Not blocking!
Re: opsi client agent Windows 7 64Bit
Verfasst: 26 Jan 2012, 11:40
von insideAC
Und hier noch den Inhalt von "opsi-client-agent.err"
Code: Alles auswählen
[1] [26.01.2012 11:31:45] opsi-winst 4.11.1.6 started at 26.01.2012 11:31:45
[1] [26.01.2012 11:31:45]
[1] [26.01.2012 11:31:45] ============ Version 4.11.1.6 WIN32 script "c:\tmp\opsi\setup.ins"
[1] [26.01.2012 11:31:45] start: 2012-01-26 11:31:45
[1] [26.01.2012 11:31:45] on client named "WS15"
[1] [26.01.2012 11:31:45] loggedin user "Administrator"
[1] [26.01.2012 11:31:45] winst running as "Administrator"
[1] [26.01.2012 11:31:45] winst running with admin privileges
[1] [26.01.2012 11:31:45] [executing: "c:\tmp\opsi\opsi-winst\winst32.exe"]
[1] [26.01.2012 11:31:45] system infos:
[1] [26.01.2012 11:31:45] 00-50-56-C0-00-08 - PC hardware address
[1] [26.01.2012 11:31:45] WS15.inside.de - IP name
[1] [26.01.2012 11:31:45] 192.168.1.74 - IP address
[1] [26.01.2012 11:31:45] DEU - System default locale
[1] [26.01.2012 11:31:45]
[1] [26.01.2012 11:31:45] LogLevel was 6
[1] [26.01.2012 11:31:45] LogLevel set to 7
[1] [26.01.2012 11:31:45] LogLevel was 7
[1] [26.01.2012 11:31:45] LogLevel set to 7
[1] [26.01.2012 11:31:45] LogLevel was 7
[1] [26.01.2012 11:31:45] LogLevel set to 7
[3] [26.01.2012 11:31:45] Error: service not initialized
[3] [26.01.2012 11:31:45] Error: no connection to service
[1] [26.01.2012 11:31:45] LogLevel was 7
[1] [26.01.2012 11:31:45] LogLevel set to 7
[3] [26.01.2012 11:31:50] Error: retrieveJSONObject --- opsi service problem ---{"message":"Opsi authentication error: Forbidden: Backend authentication error: Backend authentication error: PAM authentication failed for user 'adminuser': ('Authentication failure', 7)","class":"OpsiAuthenticationError"}
[3] [26.01.2012 11:31:52] Error: retrieveJSONObject --- opsi service problem ---{"message":"Opsi authentication error: Forbidden: Backend authentication error: Backend authentication error: PAM authentication failed for user 'adminuser': ('Authentication failure', 7)","class":"OpsiAuthenticationError"}
[4] [26.01.2012 11:31:52] opsi service version could not retrieved, perhaps no connection
[3] [26.01.2012 11:31:52] Error: no connection to service
[1] [26.01.2012 11:31:52] LogLevel was 7
[1] [26.01.2012 11:31:52] LogLevel set to 7
[1] [26.01.2012 11:31:52] LogLevel was 7
[1] [26.01.2012 11:31:52] LogLevel set to 7
[1] [26.01.2012 11:32:00] LogLevel was 7
[1] [26.01.2012 11:32:00] LogLevel set to 7
[1] [26.01.2012 11:32:02] LogLevel was 7
[1] [26.01.2012 11:32:02] LogLevel set to 7
[1] [26.01.2012 11:32:02] LogLevel was 7
[1] [26.01.2012 11:32:02] LogLevel set to 7
[1] [26.01.2012 11:32:08] LogLevel was 7
[1] [26.01.2012 11:32:08] LogLevel set to 7
[1] [26.01.2012 11:32:08] LogLevel was 7
[1] [26.01.2012 11:32:08] LogLevel set to 7
[4] [26.01.2012 11:32:12] Warning: Existing value has type ExpandString, we are about to write value of type String
[4] [26.01.2012 11:32:15] Warning: The file could not be deleted
[4] [26.01.2012 11:32:15] Warning: The file could not be deleted
[4] [26.01.2012 11:32:15] Warning: The file could not be deleted
[4] [26.01.2012 11:32:15] Warning: The file could not be deleted
[4] [26.01.2012 11:32:15] Warning: "Directory c:\tmp\opsi\opsi-winst" cannot be deleted, error 145 ("Das Verzeichnis ist nicht leer.
")
[4] [26.01.2012 11:32:15] Warning: "Directory c:\tmp\opsi" cannot be deleted, error 145 ("Das Verzeichnis ist nicht leer.
")
[4] [26.01.2012 11:32:15] Warning: Directory C:\Program Files (x86)\opsi.org\opsi-client-agent\utils\ does not exist, nothing deleted
[1] [26.01.2012 11:32:15] ___________________
[1] [26.01.2012 11:32:15] script finished
[1] [26.01.2012 11:32:15] 4 errors
[1] [26.01.2012 11:32:15] 8 warnings
[1] [26.01.2012 11:32:15]
[1] [26.01.2012 11:32:15]
[1] [26.01.2012 11:32:15] ============ winst Version 4.11.1.6 WIN32 is regularly exiting. Time 2012-01-26 11:32:15 .
Weiß jemand Rat?
Wenn ich nur wüsste wie man den client Agent vollständig aus einem Sysem entfernt, dann würde ich dies einmal versuchen. Leider scheint immer noch etwas hängen zu bleiben.
Re: opsi client agent Windows 7 64Bit
Verfasst: 26 Jan 2012, 16:25
von insideAC
Verwunderlich, dass es nur auf einem Client auftritt.
Kann es am Java JRE liegen?
Ich weiß langsam nicht mehr weiter...
Weiß denn wirklich niemand, was ich noch versuchen kann?
Re: opsi client agent Windows 7 64Bit
Verfasst: 26 Jan 2012, 17:36
von d.oertel
Hi,
empfehlung:
opsi-client-agent auf diesem Rechner per service_setup.cmd neu installieren.
Wenn er nach dem folgenden reboot nicht sofort funktioniert - direkt nochmal per service_setup.cmd.
Wenn es dann immer noch nicht geht ist die opsi-client-agent.log die Datei die auskunft gibt was schief gegangen ist.
gruss
d.oertel
Re: opsi client agent Windows 7 64Bit
Verfasst: 27 Jan 2012, 09:41
von insideAC
Guten Tag,
ich habe die Installation zwei Mal neu durchgeführt.
Leider kann ich das Logfile hier weder anhängen noch in den Beitrag kopieren, da es zu lang ist.
Kann ich Ihnen das Logfile z.B. per Mail zukommen lassen? Ich kann as File leider nicht öffentlich zum Download bereitstellen.
Vielen Dank und freundliche Grüße
Re: opsi client agent Windows 7 64Bit
Verfasst: 27 Jan 2012, 09:45
von wolfbardo
Bitte Logfile opsi-client-agent.log per Mail an
info<at>uib.de
Gruss
Bardo Wolf