Experimental Physics and Industrial Control System
|
Hi,
I've several soft IOCs happily running 7.0.3 on linux-x86_64 on different ports. However,
I have a new one which is connected to a ethernet<->serial converter which runs
without issue from a terminal, but fails with "No TCP server started" when started
from procServ. A similar message was reported to core-talk by Heinz Junkes when
using 3.16.0.1-DEV-fhi.
This has nothing to do with my databases, as I have them commented out:
My startup command is:
epics:~/epicsDEV/Config/ProcLauncher> procServ -i ^D^C --killsig 15 --logfile /home/epics/epicsDEV/ioc_logs/Keithley2700_2019_10_29__11_59_38.log --name Keithley2700 --pidfile /home/epics/.PROCSERV_CMD_1572368378214534208 --quiet 7718
/home/epics/epicsDEV/iocTops/Multimeter/iocBoot/iocKeithley2700/st.cmd
And the resulting log file has:
@@@ Restarting child "Keithley2700"
@@@ (as /home/epics/epicsDEV/iocTops/Multimeter/iocBoot/iocKeithley2700/st.cmd)
@@@ The PID of new child "Keithley2700" is: 7855
@@@ @@@ @@@ @@@ @@@
#!../../bin/linux-x86_64/Keithley2700
## You may have to change Keithley2700 to something else
## everywhere it appears in this file
< envPaths
epicsEnvSet("IOC","iocKeithley2700")
epicsEnvSet("TOP","/home/epics/epicsDEV/iocTops/Multimeter")
epicsEnvSet("EPICS_BASE","/home/epics/epicsDEV/base")
epicsEnvSet("EPICS_SUPPORT","/home/epics/epicsDEV/Support")
epicsEnvSet("ASYN","/home/epics/epicsDEV/Support/asyn")
epicsEnvSet("CALC","/home/epics/epicsDEV/Support/calc")
epicsEnvSet("STREAM","/home/epics/epicsDEV/Support/StreamDevice")
epicsEnvSet("ALIVE","/home/epics/epicsDEV/Support/alive")
epicsEnvSet("KEITHLEY","/home/epics/epicsDEV/Support/Keithley")
epicsEnvSet("EPICS_IOC_OWNER","hanlet")
epicsEnvSet("EPICS_IOC_GROUP","FE_group")
epicsEnvSet("EPICS_IOC_LOCATION","???")
cd "/home/epics/epicsDEV/iocTops/Multimeter"
## Register all support components
dbLoadDatabase "dbd/Keithley2700.dbd"
Keithley2700_registerRecordDeviceDriver pdbbase
## Configure IP port
drvAsynIPPortConfigure("keithley","131.225.138.251:10002",0,0,0)
## Debuggin
asynSetTraceIOMask("keithley",0,2)
asynSetTraceMask("keithley",0,9)
## Load record instances
#dbLoadRecords("db/Keithley2700.db")
#dbLoadRecords("db/alive.db")
#dbLoadRecords("db/watcher.db")
## Protocol file
epicsEnvSet("STREAM_PROTOCOL_PATH","/home/epics/epicsDEV/Support/Keithley/Keithley2700App/protocol")
## Start IOC
cd "/home/epics/epicsDEV/iocTops/Multimeter/iocBoot/iocKeithley2700"
iocInit
Starting iocInit
############################################################################
## EPICS R7.0.3
## EPICS Base built Oct 23 2019
############################################################################
CAS: No TCP server started
Thread _main_ (0x1b50450) can't proceed, suspending.
Dumping a stack trace of thread '_main_':
[ 0x7fc82a4fe25b]: /home/epics/epicsPRO/base-7.0.3/lib/linux-x86_64/libCom.so.3.17.5(epicsStackTrace+0x4b)
[ 0x7fc82a4ee818]: /home/epics/epicsPRO/base-7.0.3/lib/linux-x86_64/libCom.so.3.17.5(cantProceed+0xb8)
[ 0x7fc82a9f4be9]: /home/epics/epicsPRO/base-7.0.3/lib/linux-x86_64/libdbCore.so.3.17.4(rsrv_init+0xf69)
[ 0x7fc82a9e07ab]: /home/epics/epicsPRO/base-7.0.3/lib/linux-x86_64/libdbCore.so.3.17.4(dbInitServers+0x1b)
[ 0x7fc82a9f19de]: /home/epics/epicsPRO/base-7.0.3/lib/linux-x86_64/libdbCore.so.3.17.4(iocBuild+0x2e)
[ 0x7fc82a9f1b89]: /home/epics/epicsPRO/base-7.0.3/lib/linux-x86_64/libdbCore.so.3.17.4(iocInit+0x9)
[ 0x7fc82a4e9555]: /home/epics/epicsPRO/base-7.0.3/lib/linux-x86_64/libCom.so.3.17.5(iocshBody+0xb15)
[ 0x407bb2]: ../../bin/linux-x86_64/Keithley2700(main+0x12)
[ 0x7fc828d64545]: /lib64/libc.so.6(__libc_start_main+0xf5)
[ 0x407bfd]: ../../bin/linux-x86_64/Keithley2700(_start+0x29)
Any ideas? If helpful, the device is a Lantronix UDS2100 serial-to-ethernet converter; though I
don't know if that matters.
Thanks,
Pierrick
--
Pierrick Hanlet
Fermi National Accelerator
Accelerator Front End Controls
+1-630-840-5555 -- lab
+1-312-687-4980 -- mobile
"Whether you think you can or think you can't, you're right" -- Henry Ford
|
- Replies:
- Re: No TCP server started Heinz Junkes via Tech-talk
- Re: No TCP server started Michael Davidsaver via Tech-talk
- Navigate by Date:
- Prev:
Re: building synApps from Git Lang, Keenan C. via Tech-talk
- Next:
Re: No TCP server started Heinz Junkes 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: building synApps from Git Mark Rivers via Tech-talk
- Next:
Re: No TCP server started Heinz Junkes 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
|
ANJ, 31 Oct 2019 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
·
Search
·
EPICS V4
·
IRMIS
·
Talk
·
Bugs
·
Documents
·
Links
·
Licensing
·
|