False ServiceCommandFailed error

[zzz]

This [ServiceCommandFailed] error in ScadaAdmin has become really annoying,

As setting grows, ~1/3 of my operations begin to yield error like this in ScadaAgent log, but if you check the operation, the service has restarted fine, everything is OK. Maybe it’s just he shell script returns a couple milliseconds later than expected.

2023-07-28 11:27:10 [wsta][appstack][ERR] Process did not complete in 9000 ms. File 9000

Answer to my own question, Need to increase Timeout in AgentConnection in DeploymentProfile from 10×1000 ms to 20s or above.

[Mikhail]

Do you really get messages like [ServiceCommandFailed]? If so, we should find how to fix them. What is your Rapid SCADA version?

You should analyze why services are restarted so long. Restart services one by one using svc_restart.bat or svc_restart.sh and check log files.

[Mikhail]

What hardware do you use for Rapid SCADA?
For example, ScadaServer can take a long time to run on ARM.

[zzz]

[ 0.126751] smpboot: CPU0: Intel(R) Celeron(R) CPU N2840 @ 2.16GHz (family: 0x6, model: 0x37, stepping: 0x8)

It’s a Celeron N2840 box air cooled. The disk is not SSD.
I think give an error on this is not really helpful.
If there is any failing configuration for the service it’s more likely refuse to start,

I think it need 10~15s to do a full restart, So I just increase it to 30s just to make sure when it say ServiceCommandFailed failed, it really means it.
I was having difficulty organizing the compiled files for ServerAdmin, some lang file maybe missing. I think now it looks ok.

[Mikhail]

Log files would help.

[Author]

Posts