RE: medm unable to contact CA repeater after 50 tries

["Jeff Hill" <johill@lanl.gov>]

> "unable to contact CA repeater after 50 tries message" was seen

It appears that your CA repeater is running and that it is
listening on port 5065. Perhaps the CA client was not started
with EPICS_CA_REPEATER_PORT set to 5065, but I think I recall
correctly that this was not your situation?

Is your MEDM compiled and linked with this 2003-03-12 base
snapshot? Do you see this problem when the "caEventRate <PV
name>" is run from the 2003-03-12 base snapshot?

Jeff

> -----Original Message-----
> From: M.C.Shao [mailto:ShaoMingchao97@mails.tsinghua.edu.cn]
> Sent: Wednesday, March 26, 2003 10:08 PM
> To: Jeff Hill
> Cc: Tech-talk
> Subject: Re: medm unable to contact CA repeater after 50 tries
> 
> 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" <johill@lanl.gov>
> 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
> >