Hi!
I have been using procServ for a while to run my IOC’s in the background. There are now too many and I want to learn how to use manage-procs, part of procServUtils to create and start processes and configure the conserver.cf file to view
those processes from conserver. Here’s what I’ve done:
-Installed procServ, and included the procServUtils in the build
-Installed conserver
-Set up an IOC that I have tested can start from the command line, or with procServer
If I go to the directory containing the st.cmd file and type:
manage-procs add -P 7010 -A -f sampleIOC1 ./st.cmd
I expect the IOC to start and be accessible on telnet port 7010. Instead I get the following message which I don’t understand:
Created symlink /home/emil/.config/systemd/user/multi-user.target.wants/procserv-sampleIOC1.service → /home/emil/.config/procServ.d/procserv-sampleIOC1.service.
Created symlink /home/emil/.config/systemd/user/procserv-sampleIOC1.service → /home/emil/.config/procServ.d/procserv-sampleIOC1.service.
Failed to start procserv-sampleIOC1.service: Unit procserv-sampleIOC1.service has a bad unit file setting.
See user logs and 'systemctl --user status procserv-sampleIOC1.service' for details.
If I look in that file, I get the following:
cat /home/emil/.config/procServ.d/procserv-sampleIOC1.service
[Unit]
Description=procServ for sampleIOC1
After=network.target remote-fs.target
ConditionPathIsDirectory=/home/emil/Apps/epics/R7.0.4.1/work/ioc/TEST/sampleIOC/iocBoot/iocsampleIOC
[Service]
Type=simple
ExecStart=None --user sampleIOC1
RuntimeDirectory=procserv-sampleIOC1
StandardOutput=syslog
StandardError=inherit
SyslogIdentifier=procserv-sampleIOC1
[Install]
WantedBy=multi-user.target
If I look at the systemd process that failed to start I get:
Jun 11 16:40:46 sissy-serv-02 systemd[29562]: /home/emil/.config/procServ.d/procserv-sampleIOC1.service:9: Executable "None" not found in path "/usr/local/sbin:/usr/local/bin:/usr/sbin:/us…..
Any idea what I am doing wrong?
Thanks,
Will