Re: Procserv execute error

["Hu, Yong via Tech-talk" <tech-talk at aps.anl.gov>]

Manualy typing “procServ …” to start an IOC is not a good practice unless it is just for a quick test.

Suppose you are going to run a dozen (or a few hundreds) of  softIOCs on a Linux server, you probably should use a more advanced tool (built upon procServ) for running and managing those IOCs. Here is one of those tools: https://github.com/NSLS-II/systemd-softioc. You are welcome to try it out and let me know if you need any help.

Cheers,
Yong
NSLS-2 Accelerator Controls

From: Tech-talk <tech-talk-bounces at aps.anl.gov> on behalf of Mark Rivers via Tech-talk <tech-talk at aps.anl.gov>
Date: Friday, November 1, 2024 at 8:26 AM
To: 백호령 <holyeongbaeg at gmail.com>
Cc: tech-talk at aps.anl.gov <tech-talk at aps.anl.gov>
Subject: Re: Procserv execute error

I suggest putting the complete path to CXIKSS_st.cmd in the procServ command.

Mark

Sent from my iPhone

> On Nov 1, 2024, at 2:00 AM, 백호령 via Tech-talk <tech-talk at aps.anl.gov> wrote:
>
> 
> Hi, i'd like to take your advice about procserv error.
> I was use very well procserv before, but I don't know why I couldn't use it now.
> I did install again epics and synapps. Is this the reason why I couldn't use procserv?
>
> the error message is :
> (3_8) [root@psc02 CXIKSS]# procServ -L CXIKSS.log 20000 CXIKSS_st.cmd
>
> procServ: spawning daemon process: 4165
>
> (3_8) [root@psc02 CXIKSS]# telnet localhost 20000
>
> Trying ::1...
>
> telnet: connect to address ::1: Connection refused
>
> Trying 127.0.0.1...
>
> Connected to localhost.
>
> Escape character is '^]'.
>
> @@@ Welcome to procServ (procServ Process Server 2.8.0)
>
> @@@ Use ^X to kill the child, auto restart mode is ON, use ^T to toggle auto restart
>
> @@@ procServ server PID: 4165
>
> @@@ Server startup directory: /usr/local/epics/synApps_6_1/support/motor-R7-1/modules/motorOmsAsyn/iocs/omsAsynIOC/iocBoot/iocOmsAsyn/CXIKSS
>
> @@@ Child startup directory: /usr/local/epics/synApps_6_1/support/motor-R7-1/modules/motorOmsAsyn/iocs/omsAsynIOC/iocBoot/iocOmsAsyn/CXIKSS
>
> @@@ Child started as: CXIKSS_st.cmd
>
> @@@ Child log file: CXIKSS.log
>
> @@@ Child "CXIKSS_st.cmd" is SHUT DOWN
>
> @@@ procServ server started at: Fri Nov 1 15:26:44 2024
>
> @@@ 0 user(s) and 0 logger(s) connected (plus you)
>
> @@@ ^R or ^X restarts the child, ^Q quits the server
>
> @@@ Restarting child "CXIKSS_st.cmd"
>
> @@@ The PID of new child "CXIKSS_st.cmd" is: 4168
>
> @@@ @@@ @@@ @@@ @@@
>
> procServ: child could not execute: CXIKSS_st.cmd, No such file or directory
>
> 
>
> @@@ @@@ @@@ @@@ @@@
>
> @@@ Received a sigChild for process 4168. Normal exit status = 255
>
> @@@ Current time: Fri Nov 1 15:26:59 2024
>
> @@@ Child process is shutting down, a new one will be restarted shortly
>
> @@@ ^R or ^X restarts the child, ^Q quits the server
>
> 
>
> telnet> quit
>
>
> =====================
> But I have a st.cmd file in my directory, and it worked very well when I use st.cmd file like this > ./CXIKSS_st.cmd
>
> Can you guys please help me about this?
> Sincerely,
> Baeg