opsiclientd on_demand: No JSON object could be decoded

[danielc]

OK i did this.

As i don't know how to restart the service i restarted the machine

Now the timeout problem has disapeared, but the JSON one is still there. Even after having saved again and again, all reloaded all, restarting opsi-server...

[n.wenselowski]

Hi,

if the service is not stopped it may override the changed config.
Use service.msc for stopping the opsiclientd and then try again, please!


-Niko

[danielc]

Hi,

Use service.msc for stopping the opsiclientd and then try again, please!

OK I did it, reloaded opsi config editor, just in case, but still the same problem. Really sorry to make you spend so much time for helping me...

[n.wenselowski]

Hi,

just to be sure: do the keys now match?

If you don't want to debug you could try to just redeploy the client.


Kind regards

Niko

[danielc]

Yes they match.

About redeploying, i was thinking to do this, but because maybe the problem is that i tried several time to deploy it with the opsi-deploy-client-agent method that obviously doesn't work (i would like to find something that will work all the time, on all machines, without compiling some code).

Then i tried service_setup.cmd and it worked, but maybe some information were still on the client and it wreckled the mess.

So can you tell me the correct way to uninstall and reinstall the client (or the part of the doc where it is explained). I don't find anything about this on the web...

[ueluekmen]

Hi,

there is no clean way to uninstall the client, thats why we recommend to deactivate the agent. If you only want to redeploy it, the easiest way is to call service_setup.cmd again on the client without uninstall or deactivating the agent.