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

Avoid messages "error: couldn't writev to local_ip:local_port/udp (Connection refused)" #25

Closed
salvaaod opened this issue Oct 12, 2020 · 1 comment

Comments

@salvaaod
Copy link

salvaaod commented Oct 12, 2020

Hi, I have been using DVBLast in a production environment for the last few years, great software and super stable.

I am demultiplexing a MPTS udp source and sending the individual demuxed programs to local ffmpeg instances for further processing via udp, all works ok and it has been working fine for the last few years. The problem I always have had is that whenever I have to restart the ffmpeg instances the log is full of messages like this:

error: couldn't writev to 192.168.3.201:2500/udp (Connection refused)

The messages are produced at a rate of 5 per second, so, since the MPTS has 6 channels and the ffmpeg takes a few seconds to restart whenever that happens the log is filled with 100 to 150 log lines with the same message, I have tried all -quiet options and the message always appear.

Is there any way to avoid "error: couldn't writev to....." messages being produced or decrease the frequency of them?

Thanks in advance.
Salva.

PS: DVBLast versión being used is DVBlast 3.4 (release) and OS is raspbian (Ubuntu) on a Raspberry PI 3B+

@salvaaod salvaaod changed the title Avoid messages "error: couldn't writev to 192.168.0.10:1234/udp (Connection refused)" Avoid messages "error: couldn't writev to local_ip:local_port/udp (Connection refused)" Oct 12, 2020
@gfto
Copy link
Owner

gfto commented Oct 13, 2020

The way you are currently doing it, when there is nothing listening on 192.168.3.201:2500 you are getting the errors.

A better way is to send the output to multicast address. An additional extra by using multicast is that you can have multiple subscribers and even if there are no subscribers dvblast would be able to output the stream.

@gfto gfto closed this as completed Oct 13, 2020
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

2 participants