EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

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

Subject: Re: medm unable to contact CA repeater after 50 tries
From: "M.C.Shao" <[email protected]>
To: "Jeff Hill" <[email protected]>
Cc: "Tech-talk" <[email protected]>
Date: Thu, 27 Mar 2003 13:07:55 +0800
hi, I am using EPICS BASE cvs snapshot downloaded from epics homepage on 2003-03-12, I forgot when it's committed to the base repository.
medm version is the lastest version: 3.03beta2. There is no such problem before, it's very strange. I met this problem twice, last time is a few days ago.
Here is the details of this condition:
1) caRepeater's path(/usr/local/epics/base/bin/linux-x86) is inlucluded in my path environment. 
2)After start medm, issue the following command, indicating that a copy of caRepeater is running. 
[root@Ashao root]# ps axj |grep caRepeater
    1  7450  7445   991 pts/0     7841 S        0   0:00 caRepeater
 7236  7850  7849  7236 pts/1     7849 R        0   0:00 grep caRepeater
3)Issue the following command
    [root@Ashao root]# netstat -a |grep 5065
    udp        0      0 *:5065                  *:*


--
Shao Mingchao
Engineering Physics Department
Tsinghua University
Beijing,100084,China
Tel:86-10-62784552
----- Original Message ----- 
From: "Jeff Hill" <[email protected]>
Sent: Thursday, March 27, 2003 12:50 AM
> 1) In general, to avoid this message make sure that the directory
> containing the caRepeater is in your path when running CA client
> programs.
> 
> 2) Verify that there is a CA repeater process running by using
> the ps command. If not then run it by hand and verify that it
> does not unexpectedly emit a message and quit. Make certain that
> both the CA client program and the CA repeater have the same
> value in the environment variable EPICS_CA_REPEATER_PORT.
> 
> 3) Next, use the netstat -a | grep 5065 command to verify that
> the repeater daemon is listening on the repeater's port number.
> The above port might be different if you have set
> EPICS_CA_REPATER_PORT to a non default value.
> 
> Jeff
> 


Replies:
RE: medm unable to contact CA repeater after 50 tries Jeff Hill
References:
RE: medm unable to contact CA repeater after 50 tries Jeff Hill

Navigate by Date:
Prev: RE: medm unable to contact CA repeater after 50 tries Jeff Hill
Next: RE: medm unable to contact CA repeater after 50 tries Jeff Hill
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  <20032004  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: medm unable to contact CA repeater after 50 tries Jeff Hill
Next: RE: medm unable to contact CA repeater after 50 tries Jeff Hill
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  <20032004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 10 Aug 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·