41 replies to this topic

[Florie]

Oh I see. Allright If I could do anything like testing etc. just let me know

Gesendet von meinem ONEPLUS A6003 mit Tapatalk

[Florie]

Ok, just upgraded two of my boxes to 7.1rc.

 

My duo4k is the master box with these locations:

<e2locations>
<e2location>/media/net/NAS/</e2location>
<e2location>/media/net/NAS/Fussball/</e2location>
<e2location>/media/net/NAS/Kinder/</e2location>
<e2location>/media/net/NAS/Lisa/</e2location>
<e2location>/media/net/NAS/Richi/</e2location>
<e2location>/media/net/NAS/Serien/</e2location>
</e2locations>

My client box is a vu zero, also with 7.1rc. There the recording path in settings is set to /media/net/NAS/Lisa/ but when I add a fallback timer this setting is not respected by the timer, it always starts with /media/net/NAS/Fussball/ as recording path

Is there a way it respects the setting on the client box?

 

 

 

 

 

 

Second thing on the client box is this error when pressing the EPG-button. When I press OK with this error on the screen the correct EPG shows up.

 

 

 

Maybe you can fix that or tell me what to do. LAN-connection is availible during this error.

[littlesat]

Is not fallbacktuner feature related... the openwebif gives already an error... is that nas reachable from the fallback/server box?

Edited by littlesat, 30 May 2019 - 22:30.

[Florie]

Yes, both boxes have /media/net/NAS with all its subfolders.

 

But how is EPG (which is fetched from the server box, according to fallback settings) related to the nas?

Edited by Florie, 31 May 2019 - 06:11.

[littlesat]

No idea. But the epg from the recording is stored on the same folder as the recording is done...

Edited by littlesat, 31 May 2019 - 06:49.

[Florie]

Oh sorry, maybe I was not clear enough. The EPG Error is from live TV, so no recording. Even If I Switch channels the error occurs. When I press OK then the EPG is shown correcty. That means I Press the EPG Button -> Error Page -> press OK -> correct Page with EPG

Gesendet von meinem ONEPLUS A6003 mit Tapatalk

[littlesat]

At least the error during collecting the timerlist you also get when you try to get that list via the openwebif interface. That anomaly is related to the server box in combination with OWIF in it. Some wierd characters might cause it.

[Florie]

Ok, very strange:

 

I tested it again with the programmed timers and the error was still there. I did a fullbackup of the master box. After that I deleted every timer and autotimer entry, then I did a reboot on both boxes.

 

Now the error was gone and I reflashed the backup including the timers and autotimers on the masterbox. Now the error still does NOT show up again

 

 

So for now it is "good". Just the directory selection (the two first pictures some posts above) in the fallback timer enty is still weired. Is there a chance to have this fixed, so that the default direcotry of the client box is jused when trying to program a fallback timer on the client box?

[littlesat]

It should be a non issue... al least I cannot verify it here...

[-M-]

I got the same fault as above. Just write about it in the rc thread https://forums.openp...dpost&p=1064677

It comes by pressing Timer button (or select in menu). It also come while presss EPG.

 

I have rc in the slave and home build in the server (several weeks old).

 

PS. Sorry for this double posting.

[littlesat]

See other trend... Some corruption on server box

[-M-]

Can I execute the http command by hand in browser or linux terminal (to see responce and error)?

 

I can see my four timers via webbrowser and DreamDroid app (and in the server box OSD).

[littlesat]

One of these 4 timers has some corrupted info inside (openwebif cannot ‘handle’)
You should be able to find the cullpit by accessing
http//ip.from.you.box/web/timerlist
via your browser

Edited by littlesat, 2 June 2019 - 08:57.

[-M-]

Thanks!

 

I got it with wget, but seems ok. I will try find out what FallbackTimer.py is doing.

 

Run with ENIGMA_DEBUG_LVL=4 gives this:

[ActionMap] Keymap 'InfobarTimerButtonActions' -> Action = 'timerSelection'
[FallbackTimer] getURL web/timerlist
[Skin] Processing screen: TimerEditList
[SKIN] Parsing embedded skin <embedded-in-'SimpleSummary'>
[Skin] Processing screen: <embedded-in-'SimpleSummary'>
[Skin] Processing screen: MessageBox
warning, skin is missing element WarningPixmap in <class 'Screens.MessageBox.MessageBox'>(Error while retreiving fallback timer information
[Failure instance: Traceback: <type 'exceptions.ValueError'>: invalid literal for int() with base 10: 'False'
/usr/lib/python2.7/site-packages/twisted/internet/tcp.py:289:connectionLost
/usr/lib/python2.7/site-packages/twisted/web/client.py:223:connectionLost
/usr/lib/python2.7/site-packages/twisted/internet/defer.py:459:callback
/usr/lib/python2.7/site-packages/twisted/internet/defer.py:567:_startRunCallbacks
--- <exception caught here> ---
/usr/lib/python2.7/site-packages/twisted/internet/defer.py:653:_runCallbacks
/usr/lib/enigma2/python/Tools/FallbackTimer.py:64:gotFallbackTimerList
])
warning, skin is missing element autoresize in <class 'Screens.MessageBox.MessageBox'>(Error while retreiving fallback timer information
[Failure instance: Traceback: <type 'exceptions.ValueError'>: invalid literal for int() with base 10: 'False'
/usr/lib/python2.7/site-packages/twisted/internet/tcp.py:289:connectionLost
/usr/lib/python2.7/site-packages/twisted/web/client.py:223:connectionLost
/usr/lib/python2.7/site-packages/twisted/internet/defer.py:459:callback
/usr/lib/python2.7/site-packages/twisted/internet/defer.py:567:_startRunCallbacks
--- <exception caught here> ---
/usr/lib/python2.7/site-packages/twisted/internet/defer.py:653:_runCallbacks
/usr/lib/enigma2/python/Tools/FallbackTimer.py:64:gotFallbackTimerList
])
[SKIN] Parsing embedded skin <embedded-in-'SimpleSummary'>
[Skin] Processing screen: <embedded-in-'SimpleSummary'>
 

[WanWizard]

It fails in processing the timer XML in https://github.com/O...ackTimer.py#L49, one of the required XML elements is missing (is false instead of an integer).

 

The integer fields are e2disabled, e2timebegin, e2timeend, e2duration, e2startprepare, e2state, e2repeated, e2justplay, e2eit and e2afterevent.

 

Check the result of your wget, most likely one is missing... 

[-M-]

Yes... where we have it, one: <e2repeated>False</e2repeated>

 

I also notice a lot of printouts: [eventData] EPG Cache is corrupt (eventData::~eventData), you should restart Enigma!

 

So I restarted Enigma in server STB and let it download some EPG. Now the client box can display the timer list. Also the "False" above is now "0".

 

Wonder what had happend!

[littlesat]

You do not need wget for that... any browser can get this info as well.

[WanWizard]

Question I think is if the webif sends the timers.xml as it is on disk, or does it generate it from the loaded timers. If the last one, it suggests a bug in the WebIf...

[-M-]

The file timers.xml isn't the same as the webif data. However it should have been really good to look at this file when I had the fault, now timers.xml might be changed. Webif return more data.

 

I think repeat value in timers.xml is written with "str(int(timer.repeated))". Wonder if int() in python always return an integer?

 

I think webif take data from RecordTimer (session.nav.RecordTimer). ...but now my time ends for today!

 

* If the same problem happen again, I will look at timers.xml file.

[-M-]

It was very easy to reproduce. Happens directly, every time. This by adding a timer via webif. I have found the faulty row, it's in plugin/controllers/models/timers.py

Please let me come back tomorrow evening.

 

PS. However maybe more fault in this file.