Endless Loop

[kpirnie]

Describe the bug

Getting an endless loop with a few "channels". Just getting this message over and over

2024/08/19 09:15:20 Proxying 192.168.2.20:59276 to http://my_provider/the_channel_THIRD.m3u8
2024/08/19 09:15:20 Current number of connections for M3U_1: 1
2024/08/19 09:15:20 Stream ended (EOF reached): 192.168.2.20:59276
2024/08/19 09:15:20 Exit code 1 received from http://my_provider/the_channel_THIRD.m3u8
2024/08/19 09:15:20 Server connection failed: http://my_provider/the_channel_THIRD.m3u8
2024/08/19 09:15:20 Retrying other servers...
2024/08/19 09:15:20 Current number of connections for M3U_1: 0
2024/08/19 09:15:20 Current number of connections for M3U_1: 0

I have 3 separate streams to this specific channel, none of the others get "tried", and this one is actually the last in the list of them.
Example:

#EXTINF:-1 tvg-id="0.0-z - Roseanne" tvg-chno="0.0" tvg-name="z - Roseanne", z - Roseanne
http://my_provider/the_channel_FIRST.m3u8
#EXTINF:-1 tvg-id="0.0-z - Roseanne" tvg-chno="0.0" tvg-name="z - Roseanne", z - Roseanne
http://my_second_provider/the_channel_SECOND
#EXTINF:-1 tvg-id="0.0-z - Roseanne" tvg-chno="0.0" tvg-name="z - Roseanne", z - Roseanne
http://my_provider/the_channel_THIRD.m3u8

[kpirnie]

@sonroyaalmerol if needed, I can send you the actual URL streams for this one, would prefer to do that privately if possible...

[aniel300]

@kpirnie i also got an error like this the other day. hopefully a fix can be implemented 🙏

[sonroyaalmerol]

I've added some logic to track the failed M3Us so it doesn't attempt to try them again. Can you try them out on the latest dev build?

[aniel300]

is there a way to implement a retry option?

[sonroyaalmerol]

Yes, i'm planning to implement retries with customizable max retries after i've confirmed the current solution to be working.

[aniel300]

you are a God sent.

[aniel300]

@sonroyaalmerol here are my logs in case it is of any help, thanks.
#72 (comment)

2024/08/13 02:56:58 Received request from xxx:2590 for URL: /stream/TEE6IFRlbGVtdW5kbyBGb3J0IE15ZXJzIEZsb3JpZGEgV1dEVCBDRA==
2024/08/13 02:56:58 Current number of connections for M3U_1: 0
2024/08/13 02:56:58 Proxying xxx:2590 to http://xxxx.xyz:8080/xxx/xxx/295847
2024/08/13 02:56:58 Current number of connections for M3U_1: 1
2024/08/13 02:59:23 Stream ended (EOF reached): xxx:2590
2024/08/13 02:59:23 Current number of connections for M3U_1: 0
2024/08/13 02:59:23 Exit code 1 received from http://xxx.xyz:8080/xxx/xxx/295847
2024/08/13 02:59:23 Server connection failed: http://xxx.xyz:8080/xxx/xxx/295847
2024/08/13 02:59:23 Retrying other servers...
2024/08/13 02:59:23 http: superfluous response.WriteHeader call from main.streamHandler (stream_handler.go:155)****

[kpirnie]

Yes, i'm planning to implement retries with customizable max retries after i've confirmed the current solution to be working.

i am unable to test due to issue #89

[kpirnie]

Issue appears to be corrected

[aniel300]

was there an update that fixed this?

[kpirnie]

was there an update that fixed this?

Not sure. It's possible the fix for the WRONGTYPE also had fixes for this tho

[aniel300]

ahhh ok

[kpirnie]

So... while the streams are back working again, it does not seem that the MAX_RETRIES is. Hit an endless loop with one of my non-working channels today

2024/08/24 06:53:53 Current number of connections for M3U_1: 0
2024/08/24 06:53:53 Current number of connections for M3U_1: 0
2024/08/24 06:53:54 [DEBUG] Successfully fetched stream from http://myprovider/1356094.m3u8
2024/08/24 06:53:54 Proxying 192.168.2.20:56427 to http://myprovider/1356094.m3u8
2024/08/24 06:53:54 Current number of connections for M3U_1: 1
2024/08/24 06:53:54 Stream ended (EOF reached): 192.168.2.20:56427
2024/08/24 06:53:54 Exit code 1 received from http://myprovider/1356094.m3u8
2024/08/24 06:53:54 Retrying other servers...
2024/08/24 06:53:54 [DEBUG] Stream attempt 1 out of 5
2024/08/24 06:53:54 Skipping M3U_1: marked as previous stream
2024/08/24 06:53:54 [DEBUG] All streams skipped in lap 0
2024/08/24 06:53:54 [DEBUG] Stream attempt 2 out of 5

Repeats until I change the "channel".

[sonroyaalmerol]

Can I confirm if this only happens on .m3u8 streams?

[kpirnie]

Can I confirm if this only happens on .m3u8 streams?

I'll see if I have any that are not m3u or m3u8 and get back to ya :)

[kpirnie]

It does appear to be only the m3u8 streams that are doing it.

[sonroyaalmerol]

I just merged the fix to properly handle m3u files. It should be up in the dev image now

[aniel300]

m3u or m3u8?

[sonroyaalmerol]

Should include both

[aniel300]

ok perfect and thank you.

[kpirnie]

There we go. Perfection :)

[gsanguinetti]

Hi! I've reached out to this error too. I hope you can include it in a release version soon so I can pick it up in my arm64 docker (dev image is only available for amd64).

[sonroyaalmerol]

Should be included in 0.12.1. I just triggered the build and will be done in a few minutes.