EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  <20222023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  <20222023  2024 
<== Date ==> <== Thread ==>

Subject: issue with procserv
From: Florian Feldbauer via Tech-talk <tech-talk at aps.anl.gov>
To: "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov>
Date: Mon, 23 May 2022 10:32:24 +0200
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. May 23 10:19:00 scatterchamber systemd[58764]: /home/pi/.config/procServ.d/procserv-epicsioc.service:11: Standard output type syslog is obsolete, automatically updating to journal. Please u>




--
Ruhr-Universität Bochum
AG der Experimentalphysik I
Dr. Florian Feldbauer
NB 2/131 / Fach 125
Universitätsstr. 150
D-44801 Bochum

Office: NB 2/134
Phone:  (+49)234 / 32-23563
Fax:    (+49)234 / 32-14170
https://paluma.ruhr-uni-bochum.de


Replies:
Re: issue with procserv Ralph Lange via Tech-talk

Navigate by Date:
Prev: Re: Bus errors accessing VME with base 7.0.6.1 and latest synApps modules Michael Davidsaver via Tech-talk
Next: Qt-Epics for Python Anas Mohammad via Tech-talk
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  <20222023  2024 
Navigate by Thread:
Prev: PVXS release 1.1.1 Michael Davidsaver via Tech-talk
Next: Re: issue with procserv Ralph Lange via Tech-talk
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  <20222023  2024 
ANJ, 15 Dec 2022 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·