We have an intermittent issue where the Codemeter service on Linux FAILS to start and stop working during operation.
We are using Debian Linux.
We have recently updated to 4.5.0.0 and this fault only occurs with this version from what we have tested.
ii codemeter-lite 7.40.4990.500 amd64 WIBU CodeMeter minimal runtime
ii codesyscontrol 4.5.0.0 amd64 codesyscontrol based on SDK 3.5.18.20 , from Mon 27 Jun 2022
We are Using USB license dongles. When the fault occurs and we run lsusb in linux the dongle cmstick is present.
When going into Linux when the fault occurs, CodesysControl service is still running but the Codemeter service has stopped.
Do you have any idea how we can fix this and use 4.5.0.0?
Don't want to write scripts in Linux to auto restart Codemeter. As far as i know Codesyscontrol will timeout when the codemeter service stops.
In the Codesyscontrol startup in linux, does it automatically wait for Codemeter to start?
Hi
We have an intermittent issue where the Codemeter service on Linux FAILS to start and stop working during operation.
We are using Debian Linux.
We have recently updated to 4.5.0.0 and this fault only occurs with this version from what we have tested.
ii codemeter-lite 7.40.4990.500 amd64 WIBU CodeMeter minimal runtime
ii codesyscontrol 4.5.0.0 amd64 codesyscontrol based on SDK 3.5.18.20 , from Mon 27 Jun 2022
We are Using USB license dongles. When the fault occurs and we run lsusb in linux the dongle cmstick is present.
When going into Linux when the fault occurs, CodesysControl service is still running but the Codemeter service has stopped.
Do you have any idea how we can fix this and use 4.5.0.0?
Don't want to write scripts in Linux to auto restart Codemeter. As far as i know Codesyscontrol will timeout when the codemeter service stops.
In the Codesyscontrol startup in linux, does it automatically wait for Codemeter to start?
Let me know if anyone has suggestions.
Hi,
could you please report this to 'my Question' in the CODESYS Store?
https://store.codesys.com/en/