opsiclientd on_demand: No JSON object could be decoded

[danielc]

Hi,

I'm here again with a new problem.

Now that i have installed opsi-client on my windows machine, and re-installed the products on the server, i try to do the 4.2.2.1 step of getting started documentation: using hwaudit.

I did as explained, select my client, in the config product tab select hwaudit, choose setup for action, right click, choose on demand, and all i get is No JSON object could be decoded.

Exactly the same with swaudit..

But sometimes i get this other error message: timed out after 20.03 seconds (always the same value).

I rebooted manually the client, and no information about the sofware or hardware on opsi server.

In the file opsi-loginblocker on the client machine, i can read that opsiclient is running.

So?...

[n.wenselowski]

Hi,

I did as explained, select my client, in the config product tab select hwaudit, choose setup for action, right click, choose on demand, and all i get is No JSON object could be decoded.

This usually means that the hostkey on the client and on the server differ.
What versions of the opsi packages are installed on your server?
What version of the opsi-client-agent are you running?

But sometimes i get this other error message: timed out after 20.03 seconds (always the same value).

Connecting to a client seems to time out.
Can the client be reached from the server?


Kind regards

Niko

[danielc]

My opsi version is 4.0.6.46 (this is what is written in the help menu of the config editor).

For opsi-client i don't know where to find it.

It is now all the time a timeout problem, but i can ping the client from the server either with the IP address or the name.

[SisterOfMercy]

My opsi version is 4.0.6.46 (this is what is written in the help menu of the config editor).
For opsi-client i don't know where to find it.
It is now all the time a timeout problem, but i can ping the client from the server either with the IP address or the name.

On what linux distribution is your opsi server running?

[danielc]

Debian Jessie. And it is not a virtual machine.

[n.wenselowski]

Hi,

I did as explained, select my client, in the config product tab select hwaudit, choose setup for action, right click, choose on demand, and all i get is No JSON object could be decoded.

Small thing, but did you save after setting it to setup?

I rebooted manually the client, and no information about the sofware or hardware on opsi server.

If you did save and nothing happens you should check the hostkey on the client (in opsiclientd.conf) and the one on the server (ie through opsi-admin -d method getOpsiHostKey id.of.your.client).

Do you see information of a recent connection from that client in the clientconnect tab under logs in the configed?


Kind regards

Niko

[danielc]

Hi,

Small thing, but did you save after setting it to setup?

Yes, as it is written in the manuel.

If you did save and nothing happens you should check the hostkey on the client (in opsiclientd.conf) and the one on the server (ie through opsi-admin -d method getOpsiHostKey id.of.your.client).

I can find the hostkey of the server but on the client, in \opsi.org\opsiclientd\, i don't have a opsiclientd.conf file.

Do you see information of a recent connection from that client in the clientconnect tab under logs in the configed?

Nothing at all

Should i try to uninstall the client and reinstall it from the start?

[n.wenselowski]

Hi,

I can find the hostkey of the server but on the client, in \opsi.org\opsiclientd\, i don't have a opsiclientd.conf file.

the file resides at: c:\program files\opsi.org\opsi-client-agent\opsiclientd\opsiclientd.conf
If there isn't one something is wrong.

Should i try to uninstall the client and reinstall it from the start?

Did you set that client up with opsi?
If so I'd probably just go with this as it's the easier way


Kind regards

Niko

[danielc]

You were wright!

The keys are different. I wonder why, but first how do i correct this?

Thx a lot for all your help!

[n.wenselowski]

Hi,

you can alter the config as an Admin.
To do this stop the opsiclientd service, alter the config, and then start the service again.


Kind regards

Niko