Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - grumpy_geoff

Pages: [1] 2 3 ... 11
1
Strange. I don't see any instances of it over a week's worth of logs on our in-use T4.

Yeah, it's very infrequent - https://www.beyonwiz.com.au/forum/viewtopic.php?f=55&t=13224#p176639

2
I suspect that adoxa's IceTVDesc (or at least the version that you're using) hasn't been updated to take account of the fact that IceTV now has multilingual genre support. I can't find the source code on either his Birbucket or Github accounts to check.

Try uninstalling it and see whether the errors (apart from the expected one on "Politics") go away.

Yep, that is it.  I only had the one lookup failure -
Code: [Select]
{5954}<  5117.459> [EPGFetcher] ERROR: lookup of 0x01 "Politics" returned "Cult"

3
Strictly speaking it was the second fetch, as the first failed with the known "lock held" issue -
Code: [Select]
  File "/usr/lib/enigma2/python/Plugins/SystemPlugins/IceTV/plugin.py", line 514, in doWork
  File "/usr/lib/enigma2/python/Plugins/Extensions/IceTVDesc/hook.py", line 14, in run
  File "/usr/lib/enigma2/python/Plugins/Extensions/IceTVDesc/hook.py", line 31, in makeChanShowMap
exceptions.ImportError: Failed to import _strptime because the import lockis held by another thread.

You need to talk to adoxa about that: it's in his plugin.

It's the same locking conflict with the import of the _strptime module whether IceTVDesc is used or not.

4
Strange. Tonight I'm only seeing the expected errors on "Politics" (ACT guide).

Plugin version is 20191013 (as the T4 is on the beta).  I guess that's why you're not seeing them.

2,511 entries were reported in this morning's boot from deep standby -
Code: [Select]
{1000}<   141.523> [IceTV] 2020-10-27 07:12:06: Start update
{1000}<   147.121> [EPGFetcher] ERROR: lookup of 0x10 "Drama" returned "Movie"
{1000}<   147.124> [EPGFetcher] ERROR: lookup of 0xa0 "Lifestyle" returned "Infotainment"
...
{1000}<   159.571> [EPGFetcher] ERROR: lookup of 0x11 "Mystery" returned "Crime"
{1000}<   159.573> [EPGFetcher] ERROR: lookup of 0x10 "Drama" returned "Movie"
{1000}<   160.287> [IceTV] 2020-10-27 07:12:25: EPG download OK
{1000}<   160.294> [IceTV] 2020-10-27 07:12:25: Timers updated OK
{1000}<   160.294> [IceTV] 2020-10-27 07:12:25: End update


Last night, when the Wiz fetched the guide data for the newly published day (Sun), there were 269 "lookup errors" reported.
The GUI had been running for 5.5 hours by then.

Us "far westies" must be getting special treatment ;0


5
Beyonwiz / Re: Will a V2 load and run the disk from my T3?
« on: October 26, 2020, 10:39:02 PM »
I didn't realise the V2 had no onboard storage - no SSD?

As I said, no onboard SATA connection.

Quote from: pargy
The idea of USB-attached 2.5 inch and 3.5 inch external drives is quite awful from an aesthetic point of view!

If you have a NAS or network storage then you can record from the V2 to a share on that device.  Copy your existing T3 recordings to the share.  Insert a microSD card into the V2 for time shifting, backups, scripts, et. al. 
Job done.

6
Strange. Tonight I'm only seeing the expected errors on "Politics" (ACT guide).

I assume that you've done a GUI restart (at least) since the problems on Sunday?

Yes, that was from the first fetch after a GUI restart this 'arvo.

Strictly speaking it was the second fetch, as the first failed with the known "lock held" issue -
Code: [Select]
  File "/usr/lib/enigma2/python/Plugins/SystemPlugins/IceTV/plugin.py", line 514, in doWork
  File "/usr/lib/enigma2/python/Plugins/Extensions/IceTVDesc/hook.py", line 14, in run
  File "/usr/lib/enigma2/python/Plugins/Extensions/IceTVDesc/hook.py", line 31, in makeChanShowMap
exceptions.ImportError: Failed to import _strptime because the import lockis held by another thread.

7
Beyonwiz / Re: Will a V2 load and run the disk from my T3?
« on: October 26, 2020, 09:40:02 PM »
So the 2TB offering from IceTV is just a 2TB microSD card in the V2? 

You'd need to ask IceTV, but I highly doubt it is a microSD card for that price.  Likely a 2.5" portable USB HDD.

Quote from: pargy
I assume I could transfer files from the external USB drive that take out of the T3. 

Sure.  Or just use it as the main drive.  It's in the same ext4 format as the V2 would format any drive in.  The V2 won't behave any different.
If you wanted to use a new drive, you could connect both and record to the new drive, and just watch your "T3" recordings from the drive in the enclosure.
There are drive mount order "issues" to be aware of though.

Depending on the health of the T3, and you having a home network, you can leave the T3's HDD in it and play/stream recordings from the T3 to the V2.

Quote from: pargy
Are there any other PVRs that will read the media files from the T3 or is this V2 my only viable 'path'?

edit - I forgot to answer this bit.  The recordings are regular Transport Stream files.  Anything should be able to play them.  You won't get access to the meta data though (only with another Wiz unit).

8
Beyonwiz / Re: Will a V2 load and run the disk from my T3?
« on: October 26, 2020, 08:31:40 PM »
No internal SATA connection in the V2.
See "Unofficial Beyonwiz comparison guide" - https://www.beyonwiz.com.au/forum/viewtopic.php?f=50&t=13269

You can take the HDD out of your T3 and stick it in a powered USB 3.5" HDD enclosure and connect it to the V2 for use as the main drive (thus instant access to your existing recordings).

9
The genre errors that grumpy_geoff reported, though, seem to be due to whatever was happening to the IceTV server yesterday, possibly down to strange things in the EPG, but unfortunately there wasn't enough time to dig into the problem to nail down the exact cause (and I never saw those errors).

I still get them, e.g. just now there were 2,612 "[EPGFetcher]" entries -

{12595}< 16279.068> [IceTV] 2020-10-26 15:41:05: Start update
{12595}< 16282.929> [EPGFetcher] ERROR: lookup of 0x10 "Drama" returned "Movie"
{12595}< 16282.950> [EPGFetcher] ERROR: lookup of 0x10 "Drama" returned "Movie"
{12595}< 16282.954> [EPGFetcher] ERROR: lookup of 0x10 "Drama" returned "Movie"
...
{12595}< 16295.572> [EPGFetcher] ERROR: lookup of 0x01 "Cycling" returned "Cult"
{12595}< 16295.581> [EPGFetcher] ERROR: lookup of 0x20 "Current Affairs" returned "News"
{12595}< 16295.582> [EPGFetcher] ERROR: lookup of 0x01 "Politics" returned "Cult"
{12595}< 16296.289> [IceTV] 2020-10-26 15:41:23: EPG download OK
{12595}< 16296.322> [RecordTimer] ignore double timer
{12595}< 16296.323> [IceTV] 2020-10-26 15:41:23: Timers updated OK
{12595}< 16296.324> [IceTV] 2020-10-26 15:41:23: End update


Here's the unique set:
[EPGFetcher] ERROR: lookup of 0x01 "Cycling" returned "Cult"
[EPGFetcher] ERROR: lookup of 0x01 "Family" returned "Cult"
[EPGFetcher] ERROR: lookup of 0x01 "Horse Racing" returned "Cult"
[EPGFetcher] ERROR: lookup of 0x01 "Politics" returned "Cult"
[EPGFetcher] ERROR: lookup of 0x01 "Renovation" returned "Cult"
[EPGFetcher] ERROR: lookup of 0x01 "Short Film" returned "Cult"
[EPGFetcher] ERROR: lookup of 0x01 "Special" returned "Cult"
[EPGFetcher] ERROR: lookup of 0x01 "Violence" returned "Cult"
[EPGFetcher] ERROR: lookup of 0x01 "Youth" returned "Cult"
[EPGFetcher] ERROR: lookup of 0x10 "Drama" returned "Movie"
[EPGFetcher] ERROR: lookup of 0x11 "Murder" returned "Crime"
[EPGFetcher] ERROR: lookup of 0x11 "Mystery" returned "Crime"
[EPGFetcher] ERROR: lookup of 0x11 "Thriller" returned "Crime"
[EPGFetcher] ERROR: lookup of 0x12 "Action" returned "Adventure"
[EPGFetcher] ERROR: lookup of 0x12 "War" returned "Adventure"
[EPGFetcher] ERROR: lookup of 0x12 "Western" returned "Adventure"
[EPGFetcher] ERROR: lookup of 0x13 "Fantasy" returned "Sci-Fi"
[EPGFetcher] ERROR: lookup of 0x13 "Horror" returned "Sci-Fi"
[EPGFetcher] ERROR: lookup of 0x14 "Sitcom" returned "Comedy"
[EPGFetcher] ERROR: lookup of 0x20 "Current Affairs" returned "News"
[EPGFetcher] ERROR: lookup of 0x45 "AFL" returned "Football"
[EPGFetcher] ERROR: lookup of 0x45 "American Football" returned "Football"
[EPGFetcher] ERROR: lookup of 0x45 "Baseball" returned "Football"
[EPGFetcher] ERROR: lookup of 0x45 "Cricket" returned "Football"
[EPGFetcher] ERROR: lookup of 0x45 "Netball" returned "Football"
[EPGFetcher] ERROR: lookup of 0x45 "Rugby League" returned "Football"
[EPGFetcher] ERROR: lookup of 0x45 "Rugby" returned "Football"
[EPGFetcher] ERROR: lookup of 0x55 "Cartoon" returned "Animation"
[EPGFetcher] ERROR: lookup of 0x60 "Dance" returned "Music"
[EPGFetcher] ERROR: lookup of 0x60 "Musical" returned "Music"
[EPGFetcher] ERROR: lookup of 0x80 "Business & Finance" returned "Society & Culture"
[EPGFetcher] ERROR: lookup of 0x80 "Parliament" returned "Society & Culture"
[EPGFetcher] ERROR: lookup of 0x90 "Science" returned "Education"
[EPGFetcher] ERROR: lookup of 0xa0 "Fishing" returned "Infotainment"
[EPGFetcher] ERROR: lookup of 0xa0 "Lifestyle" returned "Infotainment"
[EPGFetcher] ERROR: lookup of 0xa5 "Food/Wine" returned "Cooking"

10
I believe the issue started occurring last evening (AWST).

Did IceTV add a new genre?

Code: [Select]
{780}< 46871.718> [IceTV] 2020-10-24 20:56:11: EPG download OK
{780}< 46871.718> [IceTV] 2020-10-24 20:56:11: Timers updated OK
{780}< 46871.719> [IceTV] 2020-10-24 20:56:11: End update
...
{780}< 47770.899> [IceTV] 2020-10-24 21:11:11: Start update
{780}< 47771.889> [EPGFetcher] ERROR: lookup of 0x20 "Current Affairs" returned "News"
{780}< 47771.897> [EPGFetcher] ERROR: lookup of 0x10 "Drama" returned "Movie"
{780}< 47771.900> [EPGFetcher] ERROR: lookup of 0x10 "Drama" returned "Movie"
{780}< 47771.901> [EPGFetcher] ERROR: lookup of 0x11 "Mystery" returned "Crime"
{780}< 47771.901> [EPGFetcher] ERROR: lookup of 0x01 "Violence" returned "Cult"
...
{780}< 47773.568> [EPGFetcher] ERROR: lookup of 0x01 "Renovation" returned "Cult"
{780}< 47773.573> [EPGFetcher] ERROR: lookup of 0xa0 "Lifestyle" returned "Infotainment"
{780}< 47773.576> [EPGFetcher] ERROR: lookup of 0xa0 "Lifestyle" returned "Infotainment"
{780}< 47773.578> [EPGFetcher] ERROR: lookup of 0xa0 "Lifestyle" returned "Infotainment"
{780}< 47773.579> [EPGFetcher] ERROR: lookup of 0x01 "Renovation" returned "Cult"
{780}< 47773.629> /usr/lib/enigma2/python/Plugins/SystemPlugins/IceTV/plugin.py:517: RuntimeWarning: tp_compare didn't return -1 or -2 for exception
{780}< 47773.649> Unhandled Error
Traceback (most recent call last):
  File "/usr/lib/python2.7/threading.py", line 801, in __bootstrap_inner
   
  File "/usr/lib/python2.7/threading.py", line 754, in run
   
  File "/usr/lib/python2.7/site-packages/twisted/_threads/_threadworker.py", line 46, in work
   
  File "/usr/lib/python2.7/site-packages/twisted/_threads/_team.py", line 190, in doWork
   
--- <exception caught here> ---
  File "/usr/lib/python2.7/site-packages/twisted/python/threadpool.py", line 250, in inContext
   
  File "/usr/lib/python2.7/site-packages/twisted/python/threadpool.py", line 266, in <lambda>
   
  File "/usr/lib/python2.7/site-packages/twisted/python/context.py", line 122, in callWithContext
   
  File "/usr/lib/python2.7/site-packages/twisted/python/context.py", line 85, in callWithContext
   
  File "/usr/lib/enigma2/python/Plugins/SystemPlugins/IceTV/plugin.py", line 517, in doWork
   
exceptions.OverflowError: Python int too large to convert to C long

11
So if in doubt, do a GUI restart to confirm the configuration.

Actually, the only way to be sure is to force the use of the USB tuner to see if it's available.  Either (i) go into Setup>>Tuners>>Tuner allocation and set Tuner C as the preferred tuner, or (ii) set off two recordings on different broadcast networks.  Then zap to a broadcaster not currently being used as this will force the USB tuner to be used, then check live TV on that new broadcaster; if it works then fine, if not then reboot.  Then reset Tuner allocation back to "auto" if you used method (i).
The reason for the above is sometimes a GUI restart is enough, and at other times it's not (likely to do with how messed up the drivers get).

12
Would I be correct to assume that if the USB Tuners show the correct settings (DVB-T or DVB-T2) in Openwebif that the turner is both recognised and working?

Not necessarily, that's just enigma2 detailing what was there at the last GUI start, but it may not be operational.
The below entries are from the "messages" log file when I unplugged the USB tuner, you can see from the second line that the tuner instance was nuked (the "r820t" reference is because I am using a Rafael Micro R820T / Realtek RTL2832U tuner/demodulator USB dongle).
Code: [Select]
Oct  8 07:58:16 beyonwizt2 user.info kernel: usb 1-1.7: USB disconnect, device number 3
Oct  8 07:58:16 beyonwizt2 user.info kernel: r820t 0-001a: destroying instance

I plugged the tuner back in after roughly one second of being unplugged and the tuner still shows up in OWIF, as possibly the USB interface is available but the tuner interface has gone as per above.  It can still be set as the preferred tuner, but a zap to a service fails to tune (as expected).   
After restarting the GUI, the USB tuner isn't available in Setup>>Tuners>>Tuner configuration.  After a reboot, it's back to being available.

13
@grumpy_geoff, so you have to reboot rather than restart the GUI?


If the USB tuner is in a non-terrestrial mode (one of DVB-C, DVB-C2, or DVB-S2) then a GUI restart will usually get the mode re-assigned (assuming the tuner is detected).
A reboot is needed to reload the drivers et. al. if the tuner is removed and then replaced.  I think it's something like the USB drivers are quick to detect the removal and thus the DVB drivers unload, but on re-insert the DVB drivers don't reload (thus a boot is required).  Apparently the USB tuner stuff is quite an entangled "maze".

14
..., but why it should start happening now is unclear.

The USB tuner isn't hot-swappable, so if you bumped the connection then it'd not be available for use even if you re-inserted it correctly.  You must then reboot.

15
Each of my T2s has a USB tuner.
...
It is really weird that this started happening in the last few days - not happened previously (had the T2s for several years now).

It's a pity you don't have the timer logs, as it'd show which tuners were used for the recordings.
If you still have the two successful recordings from that time, then take a look at the contents of the {recording}.ts.meta file relevant to each recording.  You should see a "Tuner-{x}" entry on the 5th line.  Then you can deduce which tuner was to be used for the failed timer.
My guess, in the absence of any details, is it was the USB tuner.  If I take a further guess, the failure occurred because either the USB tuner wasn't detected or was in a non-terrestrial mode (not DVB-T nor DVB-T2 mode).
Any time you start the GUI (from a deep standby or GUI restart), you should check the USB tuner mode (MENU>>Information>>Devices).  Restart the GUI if it's not DVB-T/T2.

Pages: [1] 2 3 ... 11