Closed obert0 closed 3 months ago
dfigus
commented
4 months ago @obert0 I did not update to HA OS 12 yet and will only be able to do this on the weekend. But can you try to access TVH directly via http://<HA URL/IP>:9981 (as the addon runs in host network mode)? This will skip the HA ingress & nginx from the container. From the last two log entries there seems to be an connection issue between nginx and TVH...
obert0
commented
4 months ago Yes I tried with the address too. I also tried with the local addon I did for the full acces mode and my other addon fork from GauthamVarmaK. All TVHeadend addon server aren't accessible. I have also Jellyfin addon and this one is still accessible on his port. Maybe this is a bug from the HAOS itself.
dfigus
commented
4 months ago I upgraded just a few minutes ago and everything came back without an issue. But I'm on a RPI4 (aarch64), maybe this only occurs on x86_64.
Can you try the following and report the results:
You can use the advanced SSH addon:
docker ps -> search for the line for the addon and make note of the first characters of the container id so that it's unique.docker exec -it <container ID characters> bash
now you should be in the addon containertop and paste the results hereps -a | grep tvheadend and past the results hereobert0
commented
4 months ago Hi @dfigus ,
This is the result of top:
Mem: 7412160K used, 548796K free, 4116K shrd, 293024K buff, 5132120K cached
CPU: 0% usr 0% sys 0% nic 98% idle 0% io 0% irq 0% sirq
Load average: 0.06 0.12 0.10 1/1003 253
PID PPID USER STAT VSZ %VSZ CPU %CPU COMMAND
173 26 root Z 0 0% 1 0% [tvheadend]
226 204 nginx S 10056 0% 3 0% nginx: worker process
227 204 nginx S 10056 0% 3 0% nginx: worker process
224 204 nginx S 10056 0% 2 0% nginx: worker process
225 204 nginx S 10056 0% 2 0% nginx: worker process
204 179 root S 9600 0% 2 0% nginx: master process nginx -g daemon off;error_log /dev/stdout error;
179 27 root S 4160 0% 0 0% bash /usr/bin/bashio ./run nginx
244 0 root S 2620 0% 3 0% bash
253 244 root R 1624 0% 0 0% top
1 0 root S 440 0% 0 0% /package/admin/s6/command/s6-svscan -d4 -- /run/service
28 1 root S 216 0% 1 0% s6-supervise s6rc-oneshot-runner
27 1 root S 216 0% 3 0% s6-supervise nginx
25 1 root S 216 0% 0 0% s6-supervise s6rc-fdholder
16 1 root S 216 0% 0 0% s6-supervise s6-linux-init-shutdownd
26 1 root S 216 0% 1 0% s6-supervise tvheadend
36 28 root S 208 0% 1 0% /package/admin/s6/command/s6-ipcserverd -1 -- /package/admin/s6/command/s6-ipcserver-access -v0 -E -l0 -i data/rules -- /package/admin/s6/command/s6-sudod -t 30000
19 16 root S 204 0% 3 0% /package/admiAnd this the result of ps -a | grep tvheadend:
26 root 0:00 s6-supervise tvheadend
173 root 0:04 [tvheadend]
258 root 0:00 grep tvheadendThat looks fine so far. I guess you removed the actual TVH command line options. Can you please share the complete TVH line (you may mask the IP of your satip_xml argument)?
Do you have any other TVH processes running that could occupy port 9981 on the host? Can you check whether there is something in the output of docker ps?
Furthermore we could analyze the processes listening on ports. For this do this - first let's do it in the addon container:
apk add net-toolsnetstat -tulpn | grep LISTEN and paste the results here.The entries which have an entry in the last column (e.g. tvheadend & nginx) are processes from the addon container. Can you spot duplicates on 9981?
obert0
commented
3 months ago Hi @dfigus, I installed the last addon version and it doesn't work. I had to disable autostart, reboot and now everything work as expected. I don't really know the problem but it work!
The Problem
Since the last HAOS update the TvHeadend server wont start on the WebUI. I tried to open the server from HA inside the addon and from chrome. The server isn't responsive. Here the addon logs after I try to acces the server from HA. I don't see response in the log when attempt to connect from a browser.
Environment
Logs