client agent/loginblocker error

Antworten
inszekt_
Beiträge: 65
Registriert: 15 Sep 2009, 11:06

client agent/loginblocker error

Beitrag von inszekt_ »

Hi

we have a serious problem with the opsi client agent. it affects Windows deployment and application installation too. for example after the agent installed an application the loginblocker stay in 'Stating action processor' status. if we want to login into the operating system, we must to reset the computer. after the restart we are avle to login. the agent writes the following lines infinite (or until we push the power button):

Code: Alles auswählen

2011-01-06 21:26:17 [6] Registry value LoginBlockerLogLevel read, result: 6
2011-01-06 21:26:17 [5] LoginBlockerLogLevel is: 6
2011-01-06 21:26:17 [6] Registry value LoginBlockerTimeoutConnect read, result: 30
2011-01-06 21:26:17 [5] LoginBlockerTimeoutConnect is: 30
2011-01-06 21:26:17 [6] Registry value LoginBlockerStart read, result: 1
2011-01-06 21:26:17 [5] LoginBlockerStart is: 1
2011-01-06 21:26:17 [6] Registry value OpsiServiceType read, result: 2
2011-01-06 21:26:17 [5] OpsiServiceType is: 2
2011-01-06 21:26:17 [6] Registry value NextGina read, result: msgina.dll
2011-01-06 21:26:17 [5] NextGina is: msgina.dll
2011-01-06 21:26:17 [5] Loading chained gina: msgina.dll
2011-01-06 21:26:36 [5] Communicating with service through pipe
2011-01-06 21:26:36 [6] Creating file: \\.\pipe\opsiclientd
2011-01-06 21:26:36 [3] Could not open pipe \\.\pipe\opsiclientd: 2
2011-01-06 21:26:48 [6] Creating file: \\.\pipe\opsiclientd
2011-01-06 21:26:48 [6] Pipe successfully opened
2011-01-06 21:26:48 [5] Writing '{"id": 1, "method": "getBlockLogin", "params": []}' to pipe
2011-01-06 21:26:48 [6] Reading from pipe
2011-01-06 21:26:48 [5] Read '{"error": null, "result": true, "id": 1}' from pipe
2011-01-06 21:26:48 [5] Blocking!
2011-01-06 21:26:48 [5] Communicating with service through pipe
2011-01-06 21:26:48 [6] Creating file: \\.\pipe\opsiclientd
2011-01-06 21:26:48 [6] Pipe successfully opened
2011-01-06 21:26:48 [5] Writing '{"id": 1, "method": "isShutdownRequested", "params": []}' to pipe
2011-01-06 21:26:48 [6] Reading from pipe
2011-01-06 21:26:48 [5] Read '{"error": null, "result": false, "id": 1}' from pipe
2011-01-06 21:26:48 [5] Communicating with service through pipe
2011-01-06 21:26:48 [6] Creating file: \\.\pipe\opsiclientd
2011-01-06 21:26:48 [6] Pipe successfully opened
2011-01-06 21:26:48 [5] Writing '{"id": 1, "method": "isRebootRequested", "params": []}' to pipe
2011-01-06 21:26:48 [6] Reading from pipe
2011-01-06 21:26:48 [5] Read '{"error": null, "result": false, "id": 1}' from pipe
2011-01-06 21:26:49 [5] Communicating with service through pipe
2011-01-06 21:26:49 [6] Creating file: \\.\pipe\opsiclientd
2011-01-06 21:26:49 [6] Pipe successfully opened
2011-01-06 21:26:49 [5] Writing '{"id": 1, "method": "getBlockLogin", "params": []}' to pipe
2011-01-06 21:26:49 [6] Reading from pipe
2011-01-06 21:26:49 [5] Read '{"error": null, "result": true, "id": 1}' from pipe
2011-01-06 21:26:49 [5] Blocking!
[UPDATE #1]

and this is the last lines before shutdown:

Code: Alles auswählen

2011-01-06 21:32:33 [5] Communicating with service through pipe
2011-01-06 21:32:33 [6] Creating file: \\.\pipe\opsiclientd
2011-01-06 21:32:33 [3] Could not open pipe \\.\pipe\opsiclientd: 231
2011-01-06 21:32:34 [6] Creating file: \\.\pipe\opsiclientd
2011-01-06 21:32:34 [6] Pipe successfully opened
2011-01-06 21:32:34 [5] Writing '{"id": 1, "method": "isShutdownRequested", "params": []}' to pipe
2011-01-06 21:32:34 [6] Reading from pipe
2011-01-06 21:32:34 [5] Read '{"error": null, "result": false, "id": 1}' from pipe
2011-01-06 21:32:34 [5] Communicating with service through pipe
2011-01-06 21:32:34 [6] Creating file: \\.\pipe\opsiclientd
2011-01-06 21:32:34 [6] Pipe successfully opened
2011-01-06 21:32:34 [5] Writing '{"id": 1, "method": "isRebootRequested", "params": []}' to pipe
2011-01-06 21:32:34 [6] Reading from pipe
2011-01-06 21:32:34 [5] Read '{"error": null, "result": false, "id": 1}' from pipe
2011-01-06 21:32:35 [5] Communicating with service through pipe
2011-01-06 21:32:35 [6] Creating file: \\.\pipe\opsiclientd
2011-01-06 21:32:35 [6] Pipe successfully opened
2011-01-06 21:32:35 [5] Writing '{"id": 1, "method": "getBlockLogin", "params": []}' to pipe
2011-01-06 21:32:35 [6] Reading from pipe
2011-01-06 21:32:35 [5] Read '{"error": null, "result": false, "id": 1}' from pipe
2011-01-06 21:32:35 [6] Last unblock time now set to: 1294345955
2011-01-06 21:32:35 [5] Not blocking!
2011-01-06 21:32:35 [5] WlxDisplaySASNotice: Not blocking
2011-01-06 21:32:38 [5] Not blocking because time of last unblock is less than 5 seconds ago!
2011-01-06 21:32:38 [5] LWlxLoggedOutSAS: Not blocking
[UPDATE #2]

trying push install I found the following lines in the opsiconfd.log

Code: Alles auswählen

[6] [Jan 06 23:03:15] [ event processing on_demand    ] sending notification 'messageChanged' to clients   (Message.pyo|559)
[6] [Jan 06 23:03:15] [ event processing on_demand    ] User is allowed to cancel connection after 30 seconds   (Opsiclientd.pyo|609)
[6] [Jan 06 23:03:15] [ event processing on_demand    ] Starting ServiceConnectionThread, timeout is 30 seconds   (Opsiclientd.pyo|614)
[5] [Jan 06 23:03:15] [ service connection            ] Connecting to config server 'https://172.18.1.2:4447/rpc' #1   (OpsiService.pyo|82)
[6] [Jan 06 23:03:15] [ service connection            ] sending notification 'messageChanged' to clients   (Message.pyo|559)
[6] [Jan 06 23:03:15] [ opsiclientd                   ] Traceback:   (Logger.pyo|710)
[6] [Jan 06 23:03:15] [ opsiclientd                   ]      line 107 in 'process' in file 'OPSI\Backend\JSONRPC.pyo'   (Logger.pyo|710)
[6] [Jan 06 23:03:15] [ opsiclientd                   ]      line 601 in '_request' in file 'OPSI\Backend\JSONRPC.pyo'   (Logger.pyo|710)
[6] [Jan 06 23:03:15] [ opsiclientd                   ]      line 361 in 'urlopen' in file 'OPSI\Util\HTTP.pyo'   (Logger.pyo|710)
[6] [Jan 06 23:03:15] [ opsiclientd                   ]      ==>>> Failed to process method 'backend_getInterface': 'ascii' codec can't decode byte 0xe9 in position 19: ordinal not in range(128)   (JSONRPC.pyo|111)
we started the OS deployment from the scratch (without drivers, with vanilla setup.py and unattend.txt), but the problem still exists.

regards, np
Benutzeravatar
j.schneider
uib-Team
Beiträge: 1821
Registriert: 29 Mai 2008, 15:14

Re: client agent/loginblocker error

Beitrag von j.schneider »

Hi,

please update to a more recent version of opsi-client-agent.
You could try:
http://download.uib.de/opsi4.0/experime ... .0-10.opsi

Greetings,
Jan Schneider
inszekt_
Beiträge: 65
Registriert: 15 Sep 2009, 11:06

Re: client agent/loginblocker error

Beitrag von inszekt_ »

j.schneider hat geschrieben:Hi,

please update to a more recent version of opsi-client-agent.
You could try:
http://download.uib.de/opsi4.0/experime ... .0-10.opsi

Greetings,
Jan Schneider
Hi Jan

Seems it solved the problem. Can you describe what was the problem?

np
Benutzeravatar
d.oertel
uib-Team
Beiträge: 3319
Registriert: 04 Jun 2008, 14:27

Re: client agent/loginblocker error

Beitrag von d.oertel »

Hi,
Can you describe what was the problem?
As far I know: Encoding problems while logging a handled exception.

regards

d.oertel
opsi support - uib gmbh

For productive opsi installations we recommend support contracts.
http://www.uib.de
http://www.opsi.org
Antworten