Hi - I am just starting with jdraw/synopticappli, and I am getting errors like this for all attributes:
pc_name:10000/l1/tco/01/maxtempchange.idl5_periodic ? NOT FOUND
Although the application seems to be working ok
I am running tango 9.1.0 on Scientific Linux (RHEL) 6.7
My attributes are being polled at 3000ms (default)
Thanks in advance
Steve
Hi
Could make a test ?
Thanks
Pascal
Thanks Pascal,
Shall I email it to you ? what is your email address?
Could this be because I have two networks in my machine?
Steve
You can copy your standard error trace in the forum message area.
Yes, it could be due to the double network connection.
Your servers are written in C++ ?
Of course
yes C++, I now see I also get similar messages with jive.
My TANGO_HOST is localhost:10000, but the messages also indicate the normal name - the second network card was not configured at this time. So looking at the output below is this the problem ? if so how do I get it to ignore the normal address and just use localhost?
This is stdio output:
CLASSPATH=/usr/local/share/java/zmq_trace.jar::/usr/local/share/java/JTango.jar:/usr/local/share/java/ATKCore.jar:/usr/local/share/java/ATKWidget.jar:/usr/local/share/java/atkpanel.jar
====================== ZMQ (3.22) event system is available ============================
Connecting to a StateScalar attribute : L1/TCO/01/State
Connecting to a StateScalar attribute : L1/TCO/01/State
======== Shutting down ZMQ event system ==========
tango://cfeld-pcx19361.desy.de:10000/l1/tco/01/maxtempchange.idl5_periodic NOT FOUND
keys are:
tango://localhost:10000/l1/tco/01/maximumoutputcurrent.idl5_periodic
tango://localhost:10000/l1/tco/01/maximumdevicetemperature.idl5_periodic
tango://localhost:10000/l1/tco/01/actualoutputcurrent.idl5_attr_conf
tango://localhost:10000/l1/tco/01/lowererrorthreshold.idl5_attr_conf
tango://localhost:10000/l1/tco/01/actualoutputvoltage.idl5_attr_conf
tango://localhost:10000/l1/tco/01/uppererrorthreshold.idl5_attr_conf
tango://localhost:10000/l1/tco/01/pidlowerlimit.idl5_attr_conf
…
Did your server started with TANGO_HOST=cfeld-pcx19361.desy.de:10000 ?
try to start server and client with the real name:
TANGO_HOST=cfeld-pcx19361.desy.de:10000
Thanks fixed!
I have run device servers recently on a number of hosts, often with locahost … never had this before, is it because this machine has two networks?
Steve
No it is not linked to the double connection.
It is a problem that sounds like a bug. A not clear specification.
In C++ API (server side) localhost is translated to the real host name.
In java API client side, the real TANGO_HOST is used.
So received and expected message are different and not recognized.
We will clarified and fixed it in future release.
Regards
Pascal
Thanks Pascal