Configed json error [solved]

[SisterOfMercy]

I'm getting an error with configed, it's been happening a while now. Updated from opsi 4.0 to 4.1, but this problem did not go away.

Code: Alles auswählen

jun 08  15:13:44.940  2018 -- Exception while data reading, de.uib.opsicommand.JSONthroughHTTP$JSONCommunicationException: receiving json
jun 08  15:13:44.940  2018 -- JSONReMapper: Exception on reproducing  null, java.lang.NullPointerException

jun 08  15:45:19.863  2018 -- Exception while data reading, de.uib.opsicommand.JSONthroughHTTP$JSONCommunicationException: receiving json
jun 08  15:45:19.910  2018 -- JSONReMapper: Exception on reproducing  null, java.lang.NullPointerException

opsi-configed 4.0.7.6.34-1

I get this error only when I select too many clients. Example:
Selection -> Other than current version installed for product -> mozilla-firefox.
This gives 75 clients. When I switch to the product configuration with 75 clients selected I get the error I mentioned.
If I first select half of the clients, say 50 clients, then switch to product configuration, no problem.

Is there something I can do? Should configed get more memory?

[r.roeder]

Hi,

I suppose that this is the sporadic error occurring because of an imcompatibility of some implementations of java and python SSL libraries, typically only when relatively big volumes of data are involved.

There are two workarounds. Each can be activated by property selection when installing the local configed product:

(1) set fallback_tlsv1 to true. Then the older TSL protocol version is used, there were no problems reported. You don't provoke a real security problem since everything should take place in the local network, and if you have got an attacker there you will be confronted with a bunch of greater problems than the communication between configed and opsiserver.

In practice, this configuration means that the option Dhttps.protocols="TLSv1" is set for the javaw call in the start menu entry

(2) set the algorithmic variant for TLSv1.2 as proposed in the cipher property. With this algorithm everything seems to run fine.

With this, there is a configed option added looking like --use_tls_cipher CIPHERNAME, which tells the configed to require TLSv1.2 connection powered by the specifically named encryption algorithm.

Hoping that this clarifies things a litte bit and helps in practice

Best greetings
Rupert

[SisterOfMercy]

In practice, this configuration means that the option Dhttps.protocols="TLSv1" is set for the javaw call in the start menu entry

This works, but you can not add it somewhere on the back of the command line!

Code: Alles auswählen

"C:\Program Files\Java\jre8\bin\javaw.exe" -Xmx2048m -Dhttps.protocols="TLSv1" -jar "C:\Program Files (x86)\opsi.org\configed\configed.jar" -h "opsi-config.domain.nl"

Phew, at least that's solved. Thank you very much.

[r.roeder]

indeed, it does not work if you add this option at the end of the command line since it is not a configuration option for the configed.jar but for the java(w).exe

With the selection of a different algorithm the opposite holds.


Greetins
Rupert