events are blocked or slowed down after a while

# 5 years ago
Reynald	Hi Jens, I added this line in /etc/apt/sources.list: `deb [trusted=yes] https://dl.bintray.com/tango-controls/debian stretch main` Then I did: `sudo apt update sudo apt install libtango9lts-dev` This installed the include files under /usr/local/include and the 9.3.3 lib under /usr/local/lib on my Debian Stretch VM. Hoping this helps. Reynald Rosenberg's Law: Software is easy to make, except when you want it to do something new. Corollary: The only software that's worth making is software that does something new.

# 5 years ago

Hi Jens,
I added this line in /etc/apt/sources.list:

deb [trusted=yes] https://dl.bintray.com/tango-controls/debian stretch main

Then I did:

sudo apt update
sudo apt install libtango9lts-dev

This installed the include files under /usr/local/include and the 9.3.3 lib under /usr/local/lib on my Debian Stretch VM.

Hoping this helps.
Reynald

Rosenberg's Law: Software is easy to make, except when you want it to do something new.
Corollary: The only software that's worth making is software that does something new.

# 5 years ago
Reynald	And if you want the debug version of the library (recommended to help to find bugs), you should install: `sudo apt install libtango9lts-dbg` Cheers, Reynald Rosenberg's Law: Software is easy to make, except when you want it to do something new. Corollary: The only software that's worth making is software that does something new.

# 5 years ago
jkrueger1	Hi Reynald, I tried both version, but nothing helped with the event problem in my case. I got always events with errors, but after installing the zmq version 4.2.5 it works. Jens

# 5 years ago
Reynald	Hi Jens, Thanks for your feedback. What kind of errors did you get? Do you mean you didn't receive any event after a while like JCM who created this topic on the forum? Could you give us more details? Glad to hear ZMQ 4.2.5 solved your problems. Cheers, Reynald Rosenberg's Law: Software is easy to make, except when you want it to do something new. Corollary: The only software that's worth making is software that does something new.

# 5 years ago

Reynald

Hi Jens,

Thanks for your feedback.
What kind of errors did you get? Do you mean you didn't receive any event after a while like JCM who created this topic on the forum?
Could you give us more details?

Glad to hear ZMQ 4.2.5 solved your problems.

Cheers,
Reynald

Rosenberg's Law: Software is easy to make, except when you want it to do something new.
Corollary: The only software that's worth making is software that does something new.

# 5 years ago
jkrueger1	Hi Reynald, the story becomes more and more strange. After installing the 4.2.5 version of ZMQ all worked fine for me, but I hadn't store the output of the ZMQ and TANGO on the screen for my little test program. So I wanted to switch back to the original ZMQ version and deinstalled the 4.2.5 (compiled from sources) version. After starting my test program works now fine as before with the installed 4.2.5 version. Also the restarting of server, client, and Tango-DB didn't change the behavior. Maybe a system restart will change this. But What I could tell you from my memory, is that the first event came as expected and all others had the 'err' flag set. The error messages gave me the hint that the server would not run, but it wasn't the case and with the help of Astor and Jive I saw that the events are fired from the server. I'm using the Debian 9.8 (stretch), the libtango9 (9.2.5a+dfsg1-2), tango-db (9.2.5a+dfsg1-2), and python-pytango (9.2.0-2) packages.

# 5 years ago

jkrueger1

Hi Reynald,

the story becomes more and more strange. After installing the 4.2.5 version of ZMQ all worked fine for me, but I hadn't store the output of the ZMQ and TANGO on the screen for my little test program. So I wanted to switch back to the original ZMQ version and deinstalled the 4.2.5 (compiled from sources) version. After starting my test program works now fine as before with the installed 4.2.5 version. Also the restarting of server, client, and Tango-DB didn't change the behavior. Maybe a system restart will change this.

But What I could tell you from my memory, is that the first event came as expected and all others had the 'err' flag set. The error messages gave me the hint that the server would not run, but it wasn't the case and with the help of Astor and Jive I saw that the events are fired from the server.

I'm using the Debian 9.8 (stretch), the libtango9 (9.2.5a+dfsg1-2), tango-db (9.2.5a+dfsg1-2), and python-pytango (9.2.0-2) packages.

# 5 years ago
Reynald	Hi Jens, What you are describing sounds like a typical heartbeat problem where you get an error event every 10 seconds, followed by a synchronous read_attribute call because the event client tries to subscribe again because it thinks the remote device server is not running. Does this corresponds to what you are observing? Rosenberg's Law: Software is easy to make, except when you want it to do something new. Corollary: The only software that's worth making is software that does something new.

# 5 years ago

Reynald

Hi Jens,

What you are describing sounds like a typical heartbeat problem where you get an error event every 10 seconds, followed by a synchronous read_attribute call because the event client tries to subscribe again because it thinks the remote device server is not running.
Does this corresponds to what you are observing?

Rosenberg's Law: Software is easy to make, except when you want it to do something new.
Corollary: The only software that's worth making is software that does something new.

# 5 years ago
jkrueger1	Hi Reynald, exactly, that is what I saw, before installing and de-installing the 4.2.5 version of ZMQ lib. But now it's working without any problem.

# 5 years ago
Reynald	Be careful with the ZMQ 4.2.0 or 4.2.1 because as I said to the original poster on this forum thread, there is a bug preventing you to receive more than 1000 events when using these versions, unless you use cppTango 9.3.3 Rosenberg's Law: Software is easy to make, except when you want it to do something new. Corollary: The only software that's worth making is software that does something new.

# 5 years ago
jkrueger1	Reynald is a bug preventing you to receive more than 1000 events when using these versions How sharp is this number? In my short testing program I reached the number of 3000 events and it's yet working (or in other words: receiving events).

# 5 years ago
Reynald	This number is sharp (1000 by default, corresponding to TANGO_EVENT_BUFFER_HWM) but the problem occurs only if the client subscribes to several publishers. This is probably why you didn't see it with your test program. In this specific case (event client subscribing to at least 2 subscribers), it will receive only 1000 events (it might be 1000 events after having subscribed to the 2nd publisher). This issue is described in cppTango#444. Rosenberg's Law: Software is easy to make, except when you want it to do something new. Corollary: The only software that's worth making is software that does something new.

# 5 years ago

Reynald

This number is sharp (1000 by default, corresponding to TANGO_EVENT_BUFFER_HWM) but the problem occurs only if the client subscribes to several publishers.
This is probably why you didn't see it with your test program.
In this specific case (event client subscribing to at least 2 subscribers), it will receive only 1000 events (it might be 1000 events after having subscribed to the 2nd publisher).
This issue is described in cppTango#444.

Rosenberg's Law: Software is easy to make, except when you want it to do something new.
Corollary: The only software that's worth making is software that does something new.