Tvheadend

start other service before TVH

That's not really feasible when these services run as daemons.

... and yes, I have this issue too :/

While I'm at it, even though I found, and checked the "disable upnp" setting, port 1900 is still being used :/
I'm running HTS Tvheadend 4.3-1789~g6bfeca6c0

Michael M wrote:

While I'm at it, even though I found, and checked the "disable upnp" setting, port 1900 is still being used :/
I'm running HTS Tvheadend 4.3-1789~g6bfeca6c0

Do you use SAT>IP server?

No. And can't see a way to turn off, or disable it.

Compile it without it

Ah - cool.
What's the config option to disable it?

NVM - found it.

https://tvheadend.org/boards/4/topics/24116

./configure --help

Hi guys,

I have the same problem.

I have three services using upnp and therefore need port 1900.

After disabling the option in tvheadend and a reboot of my server, I still see port 1900 used by tvheadend.

:~# netstat -unlp | grep ":1900" 
udp   8390400      0 0.0.0.0:1900            0.0.0.0:*                           4599/perl
udp        0      0 0.0.0.0:1900            0.0.0.0:*                           4599/perl
udp        0      0 239.255.255.250:1900    0.0.0.0:*                           4411/tvheadend

I don't use "SAT>IP Server" with tvheadend. I can't compile tvheadend without this option, because I use a docker container from linuxserver.io.

What else can be done?

I am using tvheadend version: 4.3-1802~g6be300c43

EDIT: I updated to the latest server version: 4.3-1804~gebb096804 It's still not possible to "disable UPnP". Now, I am using my tvheadend docker container in network mode "Bridge". I exposed the ports 9981 and 9982 only. So port 1900 is blocked by the Bridge. This can only be a workaround and not a solution.

netdata reported a lot of udp packet receive errors and receive buffer errors by email. So I started to analyze what was going wrong. I described my complete issue here: https://github.com/netdata/netdata/issues/6527

Thanks and regards Hoppel