search

cabernetwork / cabernet

Cabernet allows control of IPTV streams. Plugins supports DaddyLive, Pluto TV, XUMO, M3U/XMLTV.XML files (SamsungTV, STIRR, DistroTV, Plex TV)
https://cabernetwork.github.io
MIT License
154 stars 22 forks source link

Version: 0.9.13 streamlink exception on stopping stream #91

Closed Nostradamus1973 closed 1 year ago

Nostradamus1973 commented 1 year ago

Good morning Everyone,

I've come across something I haven't experienced before, and I can't get cabernet working again. I wiped my docker install like I've done many times in the past (reusing docker compose and config.ini), reselected my channels in the editor like I've done before and when trying to look at the stream I get nothing. Here's my log: cabernet.log

On a side note, I know there are some issues with docker and Cabernet doing seamless updates and I know @cookieisland has a work around, and that's great, in fact, I will have to go with his route soon before I drive myself silly. LOL BUT, at the end of the day, I like things to work the way they are intended; I don't know if it's some form of OCD, or the fact that in my older days I'm turning into a purist. I recently started using Docker because it was simple, self-contained, & intuitive. So, I would like to respectfully ask, Would anyone be opposed to getting outside help to get the docker to update properly?

I'm still loving Cabernet and I think it's amazing, I just thought if it could update that way it supposed to, that wouldn't be a bad thing.

Thx in advance for helping me out with this one.

EDIT: I changed the stream type to internal proxy from streamlink and it is working again. So, I think this has something to do with using streamlink and version 0.9.13.01 of Cabernet.

rocky4546 commented 1 year ago

First it says you have Memory Usage enabled in the config.ini file. This is used to map memory leakage and would not recommend having it enabled and just using a ton of CPU. For whatever reason you turned it on, I would recommend turning it off in Settings > Internal > Main > Memory Usage

All the mux stuff in 0.9.13, forgot to test the streamlink. Will take a look and push out a change.

rocky4546 commented 1 year ago

Update with streamlink exception fix in 0.9.13.02

rocky4546 commented 1 year ago

Reviewing the log, it also shows you have the HDHR UDP (port 65001) server running. Not sure why you have it running since most media servers do not require the UDP service. The TCP HDHR service is automatically available from the standard 6077 port. I would try to disable UDP HDHR in the settings client area and see if it all works without it set. If you do need 65001 port enabled, it is also normal to move the cabernet port from 6077 to port 80 in order to simulate the HDHomerun appliance completely. Since you have not moved the main port, I suspect the UDP port is not really being used.

rocky4546 commented 1 year ago

Last advice. Your streamlink executable is terminating during its startup. Not sure why; it is hard to get the STDERR output on these processes. I would check the version of streamlink; it should be 5.3.1. Make sure your path in Cabernet is either no path "streamlink" or has a full path to the streamlink executable you want to use "/path/to/streamlink".

If you are still having issues with streamlink, I can give you the command line Cabernet uses and you can try it on the command line to see if you get any errors...

Nostradamus1973 commented 1 year ago

Thx a bunch for the advice @rocky4546 :) I already disabled the memory usage and I will edit out those ports in my docker compose file right now. Have a great day and thx again.