wget connection refused error for url grabber

Sterling Rorden

I'm running Tvheadend 4.2.8-36 in CoreELEC 19.3 on a Ugoos X3 Amlogic box.
I run the tv_grab_url and zap2epg grabbers 3 times a day.

Things will run fine for a couple of days and then I get the following error for tv_grab_url:

2021-12-02 00:15:52.084 [ INFO] spawn: Executing "/storage/.kodi/addons/service.tvheadend42/bin/tv_grab_url"
2021-12-02 00:15:52.150 [ ERROR] spawn: wget: can't connect to remote host (192.168.1.83): Connection refused
2021-12-02 00:15:52.153 [ ERROR] xmltv: /storage/.kodi/addons/service.tvheadend42/bin/tv_grab_url: no output detected

2021-12-02 00:15:52.153 [WARNING] xmltv: /storage/.kodi/addons/service.tvheadend42/bin/tv_grab_url: grab returned no data

192.168.1.83 is the address of the box that runs Tvheadend. The zap2epb grabber still runs fine and doesn't get the connection refused error. If I reboot the box I'm good for another couple of days.

I've also noticed that the grabbers appear to run twice for some reason. I don't know if this is related. I've got the cron set to:
5 0 5 8

5 16 *

Is this a Tvheadend problem or a problem with tv_grab_url, my box, my router, CoreELEC, etc.?

Any help would be appreciated.

I've attached a complete service.log file for reference.

Saen Acro

Configuration problem in your side
Allow correct permissions.

Sterling Rorden

Perhaps I came across more knowledgeable than I am (I'm not a programmer).

Could you provide some details on where I should change the permissions and to what? I'm at a loss at figuring out where permissions are expiring after a couple of days.

Thanks

Saen Acro

No programming skills needed, just simple logic.
Allow host to "without credentials" user "*" with same password.

Sterling Rorden

Where can I find the screen to change these settings? I'm assuming by host you're referring to my CoreELEC box. I looked through the different CoreELEC setup options and couldn't find anywhere to change credentials.

Sterling Rorden

Giving this a bump. I still don't understand where I need to change permissions. Do I need to change permission settings within the Tvheadend Users tab on my Tvheadend server?

Hiro Protagonist

Sterling Rorden wrote:

> Do I need to change permission settings within the Tvheadend Users tab on my Tvheadend server?

That would be where you change the permission that sean alludes to, but I'm not sure that's your actual problem.

What is your tv_grab_url actually doing? All the versions I've seen are written in python and don't use wget - a grabber accesses XMLTV data and prints it to stdout, it seems rather odd that it would be trying to access your TVH device with wget. I presume tv_grab_url is configured to get XMLTV data from somewhere that is NOT 192.168.1.83?

Sterling Rorden

I use tv_grab_url to grab EPG data for USTVGO and Pluto TV that runs from Cabernet.

I use the Extra arguments: -u http://192.168.1.83:6077/xmltv.xml in the Tvheadend in the EPG Grabber Modules tab for tv_grab_url (6077 is for Cabernet).

A successful run looks like below:

2021-12-01 00:05:00.008 [ INFO] spawn: Executing "/storage/.kodi/addons/service.tvheadend42/bin/tv_grab_url"
2021-12-01 00:06:04.448 [ INFO] xmltv: /storage/.kodi/addons/service.tvheadend42/bin/tv_grab_url: grab took 64 seconds
2021-12-01 00:06:05.925 [ INFO] xmltv: /storage/.kodi/addons/service.tvheadend42/bin/tv_grab_url: parse took 1 seconds
2021-12-01 00:06:05.925 [ INFO] xmltv: /storage/.kodi/addons/service.tvheadend42/bin/tv_grab_url: channels tot= 436 new= 0 mod= 0
2021-12-01 00:06:05.925 [ INFO] xmltv: /storage/.kodi/addons/service.tvheadend42/bin/tv_grab_url: brands tot= 0 new= 0 mod= 0
2021-12-01 00:06:05.925 [ INFO] xmltv: /storage/.kodi/addons/service.tvheadend42/bin/tv_grab_url: seasons tot= 0 new= 0 mod= 0
2021-12-01 00:06:05.925 [ INFO] xmltv: /storage/.kodi/addons/service.tvheadend42/bin/tv_grab_url: episodes tot= 8925 new= 3260 mod= 3260

2021-12-01 00:06:05.925 [ INFO] xmltv: /storage/.kodi/addons/service.tvheadend42/bin/tv_grab_url: broadcasts tot= 8925 new= 3241 mod= 3241

I see the following command and response in the Cabernet log prior to a successful run:

2021-12-01 00:05:00,104-INFO:web_handler [192.168.1.83] "GET /xmltv.xml HTTP/1.1" 200 -
2021-12-01 00:05:02,291-DEBUG:epg2xml Processing EPG data PlutoTV:default 2021-12-01
2021-12-01 00:05:28,333-DEBUG:epg2xml Processing EPG data USTVGO:default 2021-12-01
2021-12-01 00:05:38,407-DEBUG:epg2xml Processing EPG data USTVGO:default 2021-12-02
2021-12-01 00:05:49,152-DEBUG:epg2xml Processing EPG data USTVGO:default 2021-12-03
2021-12-01 00:06:01,092-DEBUG:epg2xml Processing EPG data USTVGO:default 2021-12-04

2021-12-01 00:06:04,205-DEBUG:epg2xml Processing EPG data None:None None

But don't see a corresponding command and response in the Cabernet log when the connection was refused.

Hiro Protagonist

OK, that makes more sense now.

The simplest explanation for "Connection refused" is usually trying to access a port that isn't open - so my first thought is that you may be looking at a cabernet problem rather than a TVH problem. No entry in the cabernet log would support this.

Sterling Rorden

I thought I tried restarting Cabernet once and it didn't fix the problem. I restarted my box again yesterday so the should recur tomorrow, its pretty consistent. I'll try restarting Cabernet then to confirm. It seems like a token or something is expiring.

Is there a way to fix my grabbers from running twice? They rerun right after the initial cron trigger has been completed.

davep

> Is there a way to fix my grabbers from running twice? They rerun right after the initial cron trigger has been completed.

There was a patch committed to the master "development" branch last week which should correct this behaviour. However to get it you would need to either update to the master branch or manually back-port the changes to the version you are now running.

Sterling Rorden

Dave Pickles wrote:
> > Is there a way to fix my grabbers from running twice? They rerun right after the initial cron trigger has been completed.
>

> There was a patch committed to the master "development" branch last week which should correct this behaviour. However to get it you would need to either update to the master branch or manually back-port the changes to the version you are now running.

I'm running Tvheadend 4.2. I'm assuming I'd need to move to 4.3 to get the patched version, correct? I install the Tvheadend server as an addon in CoreELEC.

As a side question, any idea when 4.4 will be released? It seems like it's been close for a while now.

Sterling Rorden

Sterling Rorden wrote:

> I thought I tried restarting Cabernet once and it didn't fix the problem. I restarted my box again yesterday so the should recur tomorrow, its pretty consistent. I'll try restarting Cabernet then to confirm. It seems like a token or something is expiring.

I tried to restart Cabernet but I got a connection refused error from my browser when I tried to access the Cabernet web interface (port 6077). But Cabernet is still running and doing log entries. I could access Tvheadend on the same device on port 9981. I can also browse folders, etc. in file explorer on the device.

Does this indicate the problem is with Cabernet or could it still be somewhere else?

Hiro Protagonist

Sterling Rorden wrote:

> I got a connection refused error from my browser when I tried to access the Cabernet web interface (port 6077)

> Does this indicate the problem is with Cabernet?

Very much so.

You're doing with your browser what wget is trying to do.