Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bgpstream_record_get_next_elem being sucked and not giving any output #104

Open
ksalamat opened this issue Mar 21, 2020 · 5 comments
Open

Comments

@ksalamat
Copy link

Hi Alistair,

thanks for the hard work on libbgpstream. I have an issue that is bugging me for a long time.

I want to gather bgp data on long time frame (like 15 days in past). When I run my program everything goes fine for some hours of data (sometime 4 hours of BGP, sometimes even more). But at some (random) point of time bgpstream_record_get_next_elem get blocked and does not return like if it is not receiving data anymore. I have a watchdog timer that is set to 10 min. So the bgpstream_record_get_next_elem can get sucked for more than 10 mins. I am wondering what to do.
One solution would be for me to detect such an event through my watchdog and remake my bgpstream, but as bgpstream_record_get_next_elem is not yielding back I have to kill my thread and rerun it. So would be nice to have a timer inside bgpstream_record_get_next_elem that yield back with an eventual error code.
A second solution would be to figure out why such blocking can happen. Any idea is welcome.

Rgds

@digizeph
Copy link
Contributor

@ksalamat can you provide the version of the libbgpstream you're using and the environment you code is running on? If possible, can you provide a code snippet so that we can reproduce the issue?

@ksalamat
Copy link
Author

ksalamat commented Mar 22, 2020 via email

@ksalamat
Copy link
Author

ksalamat commented Mar 28, 2020 via email

@ksalamat
Copy link
Author

ksalamat commented Mar 28, 2020 via email

@listenerri
Copy link

Hi @ksalamat ,
Have you tested alistairking's commit to wandio in your project? Has this problem been fixed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants