Describe the bug When the Docker container starts, getting a "panic" error from Locast2Tuner. Keeps restarting endlessly. My container was working fine till this morning.

To Reproduce Steps to reproduce the behavior:

1. Run the Docker container.
2. Error message occurs and restarts.

** Logs ** Sorry for the weird control characters, this is what's getting saved to the log file from Docker. Here's two rotations of the logs, showing that it keeps restarting.

stdoutÌ–»ÎÁÒôÍ%config selected = /app/config/config 9 s stderr˜…ÃÑÁÒôÍ_Aug 16 15:20:23.760 INFO locast2tuner 0.1.48 on Linux 5.4.72-microsoft-standard-WSL2 starting.. s W stderrèÍ­ÒÁÒôÍCAug 16 15:20:23.762 INFO UUID: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx W Q stderr”òŽÓÁÒôÍ=Aug 16 15:20:23.764 INFO Logging in with [email protected] Q = stderr´ª®ÃÒôÍ)Aug 16 15:20:24.223 INFO Login succeeded! = j stderrÒ˜ÌÅÒôÍVAug 16 15:20:24.823 INFO Using cached FCC facilities at /root/.locast2tuner/facilities j ß stderrØû÷ËÖÒôÍÊ
thread 'main' panicked at 'called Result::unwrap() on an Err value: reqwest::Error { kind: Decode, source: Error("missing field transcodeId", line: 1, column: 227762) }', src/service/mod.rs:329:10 ß a stderr¸´®ÌÖÒôÍMnote: run with RUST_BACKTRACE=1 environment variable to display a backtrace a 9 stdout ÓºÙÒôÍ%config selected = /app/config/config 9 s stderr¬®¼“ÙÒôÍ_Aug 16 15:20:30.072 INFO locast2tuner 0.1.48 on Linux 5.4.72-microsoft-standard-WSL2 starting.. s W stderr¼ý¨”ÙÒôÍCAug 16 15:20:30.074 INFO UUID: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx W Q stderräÉò”ÙÒôÍ=Aug 16 15:20:30.076 INFO Logging in with [email protected] Q = stderrÀÀÊÛÚÒôÍ)Aug 16 15:20:30.492 INFO Login succeeded! = j stderr¼ÓÝâÜÒôÍVAug 16 15:20:31.044 INFO Using cached FCC facilities at /root/.locast2tuner/facilities j ß stderr´‚¨ïíÒôÍÊ
thread 'main' panicked at 'called Result::unwrap() on an Err value: reqwest::Error { kind: Decode, source: Error("missing field transcodeId", line: 1, column: 227762) }', src/service/mod.rs:329:10 ß a stderr¸¿¯ïíÒôÍMnote: run with RUST_BACKTRACE=1 environment variable to display a backtrace a 9

** Configuration ** Can't get the config from the web interface as it doesn't keep running long enough.

Environment Docker under Windows 10

Screenshots N/A

** Environment** Windows 10

Service crashes when starting on boot. Apparently attempting to connect before the network is ready. Service starts successfully when started manually. Adding ExecStartPre=/bin/sleep 10 to locast2tuner.service seems to function as a workaround

● locast2tuner.service - locast2tuner Loaded: loaded (/lib/systemd/system/locast2tuner.service; enabled; vendor preset: enabled) Active: failed (Result: signal) since Mon 2021-04-12 10:15:05 EDT; 8min ago Process: 372 ExecStart=/usr/bin/locast2tuner -c /etc/locast2tuner/config.ini --cache_dir /var/lib/locast2tuner (code=killed, signal=ABRT) Main PID: 372 (code=killed, signal=ABRT)

Apr 12 10:15:00 raspberrypi systemd[1]: Started locast2tuner. Apr 12 10:15:00 raspberrypi locast2tuner[372]: config selected = /etc/locast2tuner/config.ini Apr 12 10:15:00 raspberrypi locast2tuner[372]: [INFO] - locast2tuner 0.1.10 on Linux 5.10.17-v7l+ starting.. Apr 12 10:15:00 raspberrypi locast2tuner[372]: [INFO] - UUID: Apr 12 10:15:00 raspberrypi locast2tuner[372]: [INFO] - Logging in with Apr 12 10:15:05 raspberrypi locast2tuner[372]: thread 'main' panicked at 'called Result::unwrap() on an Err value: reqwest::Error { kind: Request, url: Url { scheme: "https", username: "", password: None, host: Some(Domain("api.locastnet.org")), port: None, path: "/api/user/login", query: None, fragment: None }, source: hyper::Error(Connect, ConnectError("dns error", Custom { kind: Other, error: "failed to lookup address information: Try again" })) }', src/credentials.rs:73:10 Apr 12 10:15:05 raspberrypi locast2tuner[372]: note: run with RUST_BACKTRACE=1 environment variable to display a backtrace Apr 12 10:15:05 raspberrypi systemd[1]: locast2tuner.service: Main process exited, code=killed, status=6/ABRT Apr 12 10:15:05 raspberrypi systemd[1]: locast2tuner.service: Failed with result 'signal'.

Discovered this application a couple days ago after troubleshooting an issue with locast2plex and installed it via homebrew. Been working great so far and wanted to get a thank you in before noting the exception below.

Running on mac in terminal, the application failed overnight with the error message below. I had set a sleep timer on the TV and the channel was streaming while waiting for the Roku to timeout/stop streaming (I'm assuming), so I'm not sure if the issue was from the network, the station, Plex, or the Roku. I figured I'd pass along the message to see if there was an opportunity to improve the exception handling so the application doesn't exit.

2021-04-13T01:47:43 [INFO] - Serving https://sea.locastnet.org/proxy/sea/kffv_src269717279.ts (6 s) in 5.6484375s
2021-04-13T01:47:49 [INFO] - Stream 76d4518 - playing: segment "https://sea.locastnet.org/proxy/sea/kffv_src269717279.ts"
thread 'actix-rt|system:0|arbiter:3' panicked at 'called `Result::unwrap()` on an `Err` value: Error { inner: MissingTag { tag: "#EXTM3U", input: " " } }', src/http/mod.rs:382:83
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
zsh: abort      locast2tuner -c ./config.ini

Not sure if there is anything that can be done about this, but the epg.xml file from locast doesn't seem to contain any season and episode numbers that are usable by Emby. I recently switched to m3u tuner and epg.xml and am no longer have the option to "record series" in emby. Taking a closer look at the program information in emby guide, there are no season / episode numbers. I'm not sure exactly what emby is looking for, but it doesn't seem to be provided by the locast file. If there isn't anything that can be done about this, just let it serve as a caveat to other users.

Example of program data from epg <programme start="20210524010000 +0000" stop="20210524020000 +0000" channel="channel.104"><title lang="en">NCIS: Los Angeles</title><desc lang="en">Deeks is kidnapped by an associate of Kirkin's who is in need of his help; NCIS investigates the shooting of a militarized dolphin equipped with a Russian microchip; Beale makes Nell an interesting offer.</desc><credits><director>John P. Kousakis</director><actor>Chris O'Donnell</actor><actor>LL Cool J</actor><actor>Linda Hunt</actor></credits><date>20210523</date><category lang="en">Crime drama</category><category lang="en">Action</category><category lang="en">Adventure</category><category lang="en">Mystery</category><category lang="en">Series</category><length units="seconds">3600</length><icon src="https://fans.tmsimg.com/assets/p18964076_b_v13_aa.jpg?w=240&amp;h=360" height="360" width="240"/><episode-num system="xmltv_ns">11.17.</episode-num><episode-num system="dd_progid">EP011583610288</episode-num><video><present>yes</present><aspect>16:9</aspect><quality>HDTV</quality></video><audio><present>yes</present><stereo>stereo</stereo></audio><new/><rating system="VCHIP"><value>TV14</value></rating></programme>

Forked from #7

The Docker version is going to be an interesting challenge for me - I could build it realtime inside of a Rust image, but that would mean a 10 minute process anytime the container is created. There's also the problem of dynamically linked libraries:

roddie@testubuntu:~/dev/locast2tuner/target/debug (main)% ldd locast2tuner
        linux-vdso.so.1 (0x00007ffd43baf000)
        libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f19c75e4000)
        libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f19c75c1000)
        libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f19c7472000)
        libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f19c746c000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f19c727a000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f19c8ff5000)

Looking at some options now - A lot of this is new to me, so it'll be learning on the fly.

Locast or your docker is Haveing an issue again

config selected = /config/config May 09 22:03:30.417 INFO locast2tuner 0.1.33 on Linux 5.10.19-Unraid starting.. May 09 22:03:30.418 INFO UUID: 78e455a6-39fc-456b-8279-bb4a2c7e3f2f May 09 22:03:30.418 INFO Logging in with [email protected] May 09 22:03:30.603 INFO Login succeeded! May 09 22:03:30.950 INFO Using cached FCC facilities at /root/.locast2tuner/facilities " this is the issue thread 'main' panicked at 'called Result::unwrap() on an Err value: reqwest::Error { kind: Decode, source: Error("missing field showType", line: 1, column: 161536) }', src/service/mod.rs:333:10

note: run with RUST_BACKTRACE=1 environment variable to display a backtrace /config/run.bash: line 19: 7 Aborted locast2tuner --config /config/config -b 0.0.0.0 -m -d 8 -r --tuner_count 4

Currently locast2tuner only logs to stdout and it would be nice to be able to specify --logfile (as locast2dvr has) to log in a specific location as well.

Updated to latest on Raspian OS (armf/ buster) and the service will no longer start

I've tried all kinds of things:

• Basic apt update with no changes to the existing config file
• Updated to the new config.example format with creds, multi = true, remap = true, bind_address = 0.0.0.0
• Ditto, but cranked up the logging (doesn't seem to do much when the service isn't running (it's late and I'm duh)
• apt remove
• apt install (existing configs, etc. were there)
• Same result Unfortunately, this is the extent of the output I get; almost looks like a permission issue? The file it can't find is there but owned by root, where as the other directory for cache is owned by locast2tuner. Not sure which was correct; will likely play around with this after submission and report back.

pi@towerpi:~ $ sudo systemctl status locast2tuner ● locast2tuner.service - locast2tuner Loaded: loaded (/lib/systemd/system/locast2tuner.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2021-08-25 22:10:42 EDT; 3min 31s ago Process: 5246 ExecStart=/usr/bin/locast2tuner -c /etc/locast2tuner/config --cache_dir /var/lib/locast2tuner --logfile /var/log/locast2tuner/locast2tuner.lo Main PID: 5246 (code=exited, status=203/EXEC)

Aug 25 22:10:42 towerpi systemd[1]: Started locast2tuner. Aug 25 22:10:42 towerpi systemd[5246]: locast2tuner.service: Failed to execute command: No such file or directory Aug 25 22:10:42 towerpi systemd[5246]: locast2tuner.service: Failed at step EXEC spawning /usr/bin/locast2tuner: No such file or directory Aug 25 22:10:42 towerpi systemd[1]: locast2tuner.service: Main process exited, code=exited, status=203/EXEC Aug 25 22:10:42 towerpi systemd[1]: locast2tuner.service: Failed with result 'exit-code'.

NOTE THAT UNCLEAR BUG REPORTS (i.e. without the information requested below like logs, settings, versions, etc) MIGHT BE CLOSED WITHOUT ANY HELP!!

Please check https://github.com/wouterdebie/locast2tuner/releases if any breaking changes have been made before filing a bug report.

Describe the bug Tuner is no longer found

To Reproduce Steps to reproduce the behavior:

1. I am trying to add the tuner to Plex. I have also tried to add it to Jellyfin. This system was up and working. I was having a problem with it needing to be restarted every so often ( every couple of days to as short as a couple of hours). So I decided to reinstall this morning. Now the tuner is not found. I have never seen the Default logs. Mine just starts and gives me a new prompt. I liked the way it would show me what was happening at start in Locast2Dvr. I have tried un-notating the quiet option in config, but I still don't see what is happening. I really appreciate the work you all are doing and have liked using this software.

This is running on a Rpi 4b connected via ethernet running headless and connecting via a remote desktop connection.

I also tried installing Locast2Tuner on my Linux Mint which is setup as a dual boot, so this was a fresh install. I installed a Plex server on Linux as well, but this is giving the same result which is "There was a problem adding the device: 192.168.254.XXX:6077"

** Logs ** Please provide any logs that show the error.

I am unable to locate any log files

** Configuration ** Add a copy of your config. You can get a copy of your running config by opening /config in a browser (e.g http://localhost:6077/config). This will not expose your locast password. If you can't access /config, please add your config file without your password.

I am unable to get a log by running this command either on the Rpi or from my windows installation. I have tried this command exactly http://localhost:6077/config as well as replacing localhoast with the IP of the Rpi. Environment What operating system and version you are using. Raspian, also tried in Linux Mint Screenshots

** Environment** What operating system and version you are using. I have been running in Raspian, PRETTY_NAME="Raspbian GNU/Linux 10 (buster)" NAME="Raspbian GNU/Linux" VERSION_ID="10" VERSION="10 (buster)" VERSION_CODENAME=buster ID=raspbian ID_LIKE=debian HOME_URL="http://www.raspbian.org/" SUPPORT_URL="http://www.raspbian.org/RaspbianForums" BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"

I also tried Linux Mint 20 "Ulyana" - Cinnamon (64-bit) with the same results.

Additional context Add any other context about the problem here.

I was having problems with Locast2Tuner needing to be restarted every once in a while, but it was working well otherwise.

I had a situation where I had been using a valid Los Angeles Zip Code (90009), then at some point it seems Locast.org didn't see that as a valid Zip Code, returning this:

'204 No Content' for https://api.locastnet.org/api/watch/dma/zip/90009

So upon reboot of my machine, locast2tuner failed to start up correctly. I even have it running in a Docker container with --restart always so of course it just kept stopping and trying to restart.

I realize we can't control what Locast.org does, but one thing that could be cool is to have an option for "backup" Zip codes. Not the same as multiple zip codes multiplexed. But like pairs. So I could say use 90009 as my primary, but if locast2tuner fails for some reason, try again with my secondary or backup Zip of 90210, rather than bomb out. Just a thought.

I also wondered if you could point me in the right direction on how to be alerted that there is a problem, now that I am using Docker. I know in a previous thread some monitoring tools were mentioned, but was looking for the most simple way to alert me that Docker is having some sort of issue with the locast2tuner app or container.

Thanks,

Chris

I am on 0.1.33 using Homebrew on macOS.

I have run into certain issues where locast2tuner fails for some reason, and since my Mac Mini is headless I have no idea whether locast2tuner is running or not. And let me tell you, when you can't provide your wife with reliable Jeopardy recordings, life is slightly less sweet.

For example, in my logs down below, I had an issue with my internal PiHole DNS servers briefly, and locast2tuner just bombed out immediately.

Here is what I am thinking:

• Some sort of option to have locast2tuner retry when it encounters an error. It could be number of retries, a time span, or maybe the option to combine both.

• Some sort of notification mechanism. Ideally when locast2tuner starts and stops. Email is probably a PITA, so maybe something like Pushover, or maybe something even cooler that I don't know about.

• In line with the above, there could be later enhancement with a "heartbeat" added that just sends out a message like "Running", "Stopped", "Starting", for use in something like a live dashboard (I have several iPads throughout the house).

FYI, there are no labels here in GitHub for enhancement, bug, question, etc.

May 09 13:35:06.325 INFO Login succeeded!
May 09 13:35:13.209 INFO Loading stations for Cleveland (cache: true, cache timeout: 3600, days: 30)..
May 09 14:32:13.230 INFO Reloading FCC facilities..
May 09 14:35:13.141 INFO Login token expired: Mutex { is_locked: true, has_waiters: false }
May 09 14:35:13.142 INFO Logging in with [email protected]
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: reqwest::Error { kind: Request, url: Url { scheme: "https", username: "", password: None, host: Some(Domain("api.locastnet.org")), port: None, path: "/api/dma", query: None, fragment: None }, source: hyper::Error(Connect, ConnectError("dns error", Custom { kind: Other, error: "failed to lookup address information: nodename nor servname provided, or not known" })) }', src/fcc_facilities.rs:112:10
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Abort trap: 6

It's really annoying that Locast went out like that... But I just wanted to say I really appreciated your effort on this project! It was great to use and my family used it on the daily.

Hopefully something similar comes out in the future! I know a lot of people relied on Locast since it was so inexpensive.

But anyways, thank you.

After Locast shut down, my locast2tuner docker will not run. I beleive it may be because it cannot login to locast. In plex when I click on settings for Live TV & DVR, I get "There was an unexpected error". That's it. I cannot do anything right now with that feature of plex. Is there a known fix for this? I am trying to use xTeVe. Thank you.

You have put a lot of effort into an excellent software solution that, it seems, could be easily repurposed for other video service providers.

Please consider adding TV Everywhere support. This would, in turn, allow users to have a single whole home DVR solution (e.g. JellyFin, Plex) for all channels/services to which they subscribe.

Note: in addition to cable operator subscriptions, it's possible to subscribe to OTT services like Philo, Hulu or Fubo to have TVE access to particular channels. So this functionality would benefit subscribers to a wide array of different services. For example: Hulu Philo Fubo

Additionally, please see Channels DVR direct support for TVE: https://getchannels.com/tv-everywhere/

I know that Pluto doesn't have local channels except for CNN in a few big cities but there is some amazing content that could be recorded through Plex or Emby. Your Rust version was the best out of Locast2Plex and FHDHR. FHDHR has Pluto code and there is another Pluto Git repository with the APIs

Thanks for what you accomplished. I am glad I was able to help out the kids as a sponsor. Best Tom

Couldn't find a better place to post this, but due to a lawsuit, they're done. They sent out an email this morning and there is a message on their website.