Experimental Physics and
Industrial Control System

Hey all,

I currently have a problem with procserv.
I'm using the latest commit from github compilied on Raspbian OS bullseye.

I used manage-procs to create a service but the service gets stopped
every now and then.
The actual runtime seems to be quite arbitrary. Sometimes a few secs
sometimes several hours.
The log output does not really contain any helpfull information.
Any idea what could causing procserv to shut down?

CPU and RAM usage are way below 10% when the IOC is running.


Cheers,
Florian


pi@scatterchamber:~ $ systemctl --user status procserv-epicsioc.service
● procserv-epicsioc.service - procServ for epicsioc
      Loaded: loaded
(/home/pi/.config/procServ.d/procserv-epicsioc.service; enabled; vendor
preset: enabled)
      Active: inactive (dead)

May 23 10:10:17 scatterchamber procserv-epicsioc[58686]: 2022/05/23
10:10:17.505 drvModbusAsyn::doModbusIO port chillerReadReg error calling
writeRead, error=PilotONE-187144:502 TCP timeout>
May 23 10:10:18 scatterchamber procserv-epicsioc[58686]: 2022/05/23
10:10:18.604 drvModbusAsyn::doModbusIO port chillerReadReg writeRead
status back to normal having had 1 errors, nwrite=6/>

May 23 10:10:45 scatterchamber systemd[58650]: Stopping procServ for
epicsioc...
May 23 10:10:45 scatterchamber procserv-epicsioc[58686]: @@@ Current
time: Mon May 23 10:10:45 2022
May 23 10:10:45 scatterchamber procserv-epicsioc[58686]: @@@ Child
process is shutting down, a new one will be restarted shortly
May 23 10:10:45 scatterchamber procserv-epicsioc[58686]: @@@ ^R or ^X
restarts the child, ^Q quits the server, ^D closes this connection
May 23 10:10:45 scatterchamber systemd[58650]:
procserv-epicsioc.service: Succeeded.
May 23 10:10:45 scatterchamber systemd[58650]: Stopped procServ for
epicsioc.
May 23 10:10:45 scatterchamber systemd[58650]:
procserv-epicsioc.service: Consumed 1.799s CPU time.