Closed calum-chamberlain closed 3 years ago
This is still an issue - it looks like the MainProcess stops the seedlink client, and the StreamingThread re-opens it, but then never returns. Replicating it is quite tricky - it seems to only happen when multiple events are being reacted to (so multiple seedlink clients are run), and the reason for the initial close is unclear - it happens from the seedlinkconnection
class in ObsPy, but no warnings/messages are given for the reason for this...
I ran into an issue with the seedlink client where no new data were coming in, but the process continues. This PR adds checks to make sure that new data are arriving, and if they do not, restarts the streaming client.