OPSIclientd install problem (?)

[d.oertel]

Hi,

have a look at the opsiclientd.conf. There are the events defined. Set 'active= true' to enable the event.

regards

d.oertel

[inszekt_]

Hi

i found the following config lines:

[event_daemon_startup]
active = false
type = daemon startup

I changed it to:

[event_daemon_startup]
active = true
type = daemon startup

after reinstalling the client, I found this in the logs:

[3] [Mar 08 11:59:19] [opsiclientd] Refusing to set empty value for config value 'block_notifier_command' of section 'opsiclientd_notifier' (opsiclientd.pyo|2161)
[0] [Mar 08 11:59:19] [opsiclientd] Opsiclientd version: 0.5.7.4 (opsiclientd.pyo|2549)
[0] [Mar 08 11:59:19] [opsiclientd] Commandline: C:\Program Files\opsi.org\preloginloader\opsiclientd.exe (opsiclientd.pyo|2550)
[0] [Mar 08 11:59:19] [opsiclientd] Working directory: C:\WINDOWS\system32 (opsiclientd.pyo|2551)
[2] [Mar 08 11:59:20] [opsiclientd] Already processing event (opsiclientd.pyo|2695)
[2] [Mar 08 11:59:23] [event processing] (2, 'CreateProcessAsUser', 'A rendszer nem tal\xe1lja a megadott f\xe1jlt.') (Windows.pyo|676)
[2] [Mar 08 11:59:23] [opsiclientd] Failed to write log to service: Not connected to config service (opsiclientd.pyo|2336)
[2] [Mar 08 11:59:23] [event processing] Failed to process event <event: daemon_startup>: (2, 'CreateProcessAsUser', 'A rendszer nem tal\xe1lja a megadott f\xe1jlt.') (opsiclientd.pyo|1987)
[1] [Mar 08 11:59:23] [event processing] Traceback: (Logger.pyo|647)
[1] [Mar 08 11:59:23] [event processing] line 1950 in 'run' in file 'opsiclientd.pyo' (Logger.pyo|647)
[1] [Mar 08 11:59:23] [event processing] line 1844 in 'startNotifierApplication' in file 'opsiclientd.pyo' (Logger.pyo|647)
[1] [Mar 08 11:59:23] [event processing] line 667 in 'runCommandInSession' in file 'OPSI\System\Windows.pyo' (Logger.pyo|647)
[1] [Mar 08 11:59:23] [event processing] ==>>> (2, 'CreateProcessAsUser', 'A rendszer nem tal\xe1lja a megadott f\xe1jlt.') (opsiclientd.pyo|1988)
-------------------- submitted part of log file ends here, see the rest of log file on client --------------------

additional information: we don't allow the clients to access servers on 4441 and 4442 ports.

regards, np