Hi Yong,
Thank you very much for your quick response and thank you for creating
systemd-softioc and sharing it with the community. With your advice I
got it working. procServ was not successfully installed and naturally it
did not work. Once I installed procServ, everything works beautifully.
Thank you,
---
Donny Domagoj Cosic
Laboratory for Ion Beam Interactions
Ruđer Bošković Institute
Bijenička cesta 54 | HR-10 000 Zagreb | CROATIA
T: +385 1 4561 041 | @: dcosic at irb.hr | www.irb.hr
Dana 06.01.2022 17:45, Hu, Yong je napisao(la):
Hi Donny,
Could you try these and post your results?
1) Type “which procServ” to see if procServ is successful
installed;
2) Type “cat /etc/systemd/system/softioc-testIOC2.service” to see
the generated service file.
Generally speaking, the main purpose of the "generic" user account
'softioc' is about permission: let ‘softioc’ be the owner of your
IOC's directory as well as the owner of your IOC's process after the
IOC is started (you can try this to see IOC processes: ps -ef | grep
st.cmd). So, you should type “sudo manage-iocs start testIOC2”
under your personal account (or the ‘root’ account).
Cheers,
Yong
FROM: Tech-talk <tech-talk-bounces at aps.anl.gov> on behalf of
"tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov>
ORGANIZATION: Institut Ruđer Bošković
REPLY-TO: Donny Domagoj Cosic <Donny.Domagoj.Cosic at irb.hr>
DATE: Wednesday, January 5, 2022 at 3:31 PM
TO: "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov>
SUBJECT: Start IOC automatically at boot
Happy new year!
I am trying to install systemd-softioc (procServ) as outlines here
https://github.com/NSLS-II/systemd-softioc [1]. I followed the
instructions
and successfully installed it on my Raspberry Pi. I installed the IOC
and can manually start the softioc, however I am not able to start the
IOC using manage-iocs. I get the following output:
softioc@raspberrypi:/epics/iocs/testIOC2$ sudo manage-iocs start
testIOC2
Starting the IOC 'testIOC2' ...
Failed to start the IOC 'testIOC2'; type 'sudo journalctl -xe' for
details.
Below is my config file and output from the journalctl
Config
---------
NAME=testIOC2
PORT=4053
HOST=raspberrypi
USER=softioc
CHDIR="/epics/iocs/testIOC2/iocBoot/ioctestIOC2"
EXEC="$CHDIR/st.cmd"
Output from journalctl
-------------------------
Jan 05 21:11:29 raspberrypi sudo[13371]: softioc : TTY=pts/0 ;
PWD=/epics/iocs/testIOC2 ; USER=root ; COMMAND=/usr/bin/manage-iocs
install testIOC2
Jan 05 21:11:29 raspberrypi sudo[13371]: pam_unix(sudo:session):
session
opened for user root by (uid=0)
Jan 05 21:11:29 raspberrypi sudo[13371]: pam_unix(sudo:session):
session
closed for user root
Jan 05 21:11:43 raspberrypi sudo[13423]: softioc : TTY=pts/0 ;
PWD=/epics/iocs/testIOC2 ; USER=root ; COMMAND=/usr/bin/manage-iocs
start testIOC2
Jan 05 21:11:43 raspberrypi sudo[13423]: pam_unix(sudo:session):
session
opened for user root by (uid=0)
Jan 05 21:11:43 raspberrypi systemd[1]: Reloading.
Jan 05 21:11:43 raspberrypi systemd[1]: [email protected]:
Current command vanished from the unit file, execution of the command
list won't be resume
Jan 05 21:11:43 raspberrypi systemd[1]: plexmediaserver.service:
Current
command vanished from the unit file, execution of the command list
won't
be resumed.
Jan 05 21:11:44 raspberrypi systemd[1]: Condition check resulted in
IOC
testIOC2 via procServ being skipped.
-- Subject: A start job for unit softioc-testIOC2.service has finished
successfully
-- Defined-By: systemd
-- Support:
https://urldefense.com/v3/__https://www.debian.org/support__;!!P4SdNyxKAPE!TP0CWTCKflbs_jaxGE76jgOrTY2iKe98ZI6VnTvLdIlbfMgxQBelzpZthmKH$
[2]
--
-- A start job for unit softioc-testIOC2.service has finished
successfully.
--
-- The job identifier is 1803.
Jan 05 21:11:45 raspberrypi sudo[13423]: pam_unix(sudo:session):
session
closed for user root
Jan 05 21:11:54 raspberrypi sudo[13487]: softioc : TTY=pts/0 ;
PWD=/epics/iocs/testIOC2 ; USER=root ; COMMAND=/usr/bin/journalctl -xe
Jan 05 21:11:54 raspberrypi sudo[13487]: pam_unix(sudo:session):
session
opened for user root by (uid=0)
The softioc testIOC2 contains a few records which get updated from a
python script. Which brings me to my next questions. Is there a way to
automatically start the python script with the ioc?
Thank you very much for your help,
Regards
--
Donny Domagoj Cosic
Laboratory for Ion Beam Interactions
Ruđer Bošković Institute
Bijenička cesta 54 | HR-10 000 Zagreb | CROATIA
T: +385 1 4561 041 | @: dcosic at irb.hr |
https://urldefense.com/v3/__http://www.irb.hr__;!!P4SdNyxKAPE!TP0CWTCKflbs_jaxGE76jgOrTY2iKe98ZI6VnTvLdIlbfMgxQBelzvOwVQv4$
[3]
Links:
------
[1] https://github.com/NSLS-II/systemd-softioc
[2]
https://urldefense.com/v3/__https:/www.debian.org/support__;!!P4SdNyxKAPE!TP0CWTCKflbs_jaxGE76jgOrTY2iKe98ZI6VnTvLdIlbfMgxQBelzpZthmKH$
[3]
https://urldefense.com/v3/__http:/www.irb.hr__;!!P4SdNyxKAPE!TP0CWTCKflbs_jaxGE76jgOrTY2iKe98ZI6VnTvLdIlbfMgxQBelzvOwVQv4$
- References:
- Start IOC automatically at boot Donny Domagoj Cosic via Tech-talk
- Re: Start IOC automatically at boot Hu, Yong via Tech-talk
- Navigate by Date:
- Prev:
RE: motor record startup Mark Rivers via Tech-talk
- Next:
Re: Start IOC automatically at boot Donny Domagoj Cosic 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
<2022>
2023
2024
- Navigate by Thread:
- Prev:
Re: Start IOC automatically at boot Hu, Yong via Tech-talk
- Next:
RE: Start IOC automatically at boot GAGET Alexis 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
<2022>
2023
2024
|