What should happen?
After upgrading opsi-client-agent from 4.0.7.24 too 4.1.0.0-24 on Opsi Server 4.0.7.69, the agent doesn't launch anymore at startup. After a win7-x64 deployment, the client is properly installed, but the setup_after_install doesn't go on. We have to ask for on_demand from configed to continue.
The problem seems to not occur on win10-x64. (or less frequently)
We can't upgrade the server to 4.1 version at the moment.
What happened? The client does function normally at shutdown, on demand, but not anymore at startup.
Are error messages visible in the log? There is a timeout visible in log, that i can't understand. Here it is.
Code: Alles auswählen
[5] [Mar 08 11:34:47] [ opsiclientd ] rpc getBlockLogin: blockLogin is 'True' (ControlPipe.pyo|426)
[5] [Mar 08 11:34:48] [ control pipe ] -----> Executing: getBlockLogin() (JsonRpc.pyo|134)
[5] [Mar 08 11:34:48] [ opsiclientd ] rpc getBlockLogin: blockLogin is 'True' (ControlPipe.pyo|426)
[5] [Mar 08 11:34:49] [ control pipe ] -----> Executing: getBlockLogin() (JsonRpc.pyo|134)
[5] [Mar 08 11:34:49] [ opsiclientd ] rpc getBlockLogin: blockLogin is 'True' (ControlPipe.pyo|426)
[3] [Mar 08 11:34:49] [ event processing gui_startup{installation_pending}] Failed to connect to config service 'https://opsi:4447/rpc': timed out after 20 seconds (OpsiService.pyo|106)
[5] [Mar 08 11:34:49] [ event processing gui_startup{installation_pending}] Writing log to service (EventProcessing.pyo|257)
[4] [Mar 08 11:34:49] [ event processing gui_startup{installation_pending}] Cannot write log to service: not connected (EventProcessing.pyo|260)
[5] [Mar 08 11:34:49] [ opsiclientd ] Shutdown request in Registry: 0 (Windows.pyo|327)
[5] [Mar 08 11:34:49] [ opsiclientd ] Reboot request in Registry: 0 (Windows.pyo|311)
[5] [Mar 08 11:34:49] [ opsiclientd ] Block login now set to 'False' (Opsiclientd.pyo|109)
[5] [Mar 08 11:34:50] [ control pipe ] -----> Executing: getBlockLogin() (JsonRpc.pyo|134)
[5] [Mar 08 11:34:50] [ opsiclientd ] rpc getBlockLogin: blockLogin is 'False' (ControlPipe.pyo|426)
[3] [Mar 08 11:34:58] [ event processing gui_startup{installation_pending}] Failed to process event <ocdlib.Events.GUIStartupEvent object at 0x029E5390>: Failed to connect to config service 'https://opsi:4447/rpc': timed out after 20 seconds (EventProcessing.pyo|1266)
[2] [Mar 08 11:34:58] [ event processing gui_startup{installation_pending}] Traceback: (Logger.pyo|757)
[2] [Mar 08 11:34:58] [ event processing gui_startup{installation_pending}] File "ocdlib\EventProcessing.pyo", line 1200, in run
(Logger.pyo|757)
[2] [Mar 08 11:34:58] [ event processing gui_startup{installation_pending}] File "ocdlib\OpsiService.pyo", line 188, in connectConfigService
(Logger.pyo|757)
[2] [Mar 08 11:34:58] [ event processing gui_startup{installation_pending}] File "ocdlib\EventProcessing.pyo", line 156, in connectionTimedOut
(Logger.pyo|757)
[2] [Mar 08 11:34:58] [ event processing gui_startup{installation_pending}] File "ocdlib\OpsiService.pyo", line 107, in connectionTimedOut
Server
ii opsi-atftpd 0.7.dfsg-14 amd64 advanced TFTP server - opsi version with pcre, fifo and max-blksize patches
ii opsi-configed 4.0.7.6.34-2 all OPSI config editor
ii opsi-depotserver 4.0.7.3-3 all opsi depotserver configuration package
ii opsi-linux-bootimage 20180813-1 all opsi bootimage for netboot tasks.
ii opsi-utils 4.0.7.20-1 all utilites for working with opsi.
ii opsiconfd 4.0.7.14-2 all opsi configuration service
ii opsipxeconfd 4.0.7.9-4 all opsi pxe configuration daemon
ii python-opsi 4.0.7.69-1 all opsi python library
LocalBoot
opsi-client-agent 4.1.0.0-24
NetBoot
win7-x64 4.1.0.0-14
win10-x64 4.1.0.0-14
Any help would very appreciated !
Greetings,
Nico