[ViX_Misc] Zap timers lock box

[mrocm]

Don't know about that settings restore thing. This is a new installation, replacing the previous vti image. No settings were taken from the old installation apart from satellites.xml, tv bouquet favorites and oscam configuration.

Entering a timer seem to work fine regardless of type. However, when the timer is triggered the box completely locks up with zap and "zap and record" timers. Recording only timers seems to work, probably because it is then using the second tuner and no zapping is necessary.

The symptoms are:
* The "busy" animation is shown.
* All attempts to communicate with the box using the remote control are useless - nothing happens.
* If you are in some kind of menu when the timer triggers you can't get out of it.
* If you are watching TV, the channel continues running normally, apart from the "busy" animation. It's not possible to change channel, go to settings or anything else (at least not by using the remote control, haven't tried anything else).

The only ways I've found to get out of it is to do a hard reset, i.e. switch power off using the switch on the back, or to kill enigma by logging in via ssh and execute a console cmd.

This means I can only use one tuner for watching and one tuner for recording since I have to do all zapping manually. It also means I can't use a zap timer as a wake-up timer.

Apart from this issue (which is actually a biggie for me since I use it very frequently) I really like the vix image and I certainly prefer it to the vti and black hole images that I've tried before. It actually seems to be a strong contender for best image I've tried even if I include the images I used on my previous DM8000 unit.

 

[tapkor]

My Vu+ Ultimo seems to suffer from similar symptoms at least with the current image 032.

 

[DaMacFunkin]

I'll give you a tip that solved some problems on my solo4k and access to the hard drive after I had run other images on it, such as VTi... re-initialise your drive within vix and then mount it in vix as media/hdd.
Yes you will loose all data on the drive.

 

[mrocm]

Hmmm, interesting input. My current disc is actually a legacy from my previous Dreambox unit (DM8000) but it is mounted as media/hdd and recording on the disc (and playback) has worked fine using the vti image and it seems to work fine on vix as well. I've had some sporadic problems with gui crashing when deleting from disc but if I remember correctly this was only on vti.

I don't want to lose the content on the disc but if I can find a way to backup and restore the contents it may certainly be worth a try to re-init the disc. If if works it would be an easy fix. However, since the disc *should* not be involved for zap timers it seems unlikely to be causing the problem (not impossible though in this strange world of ones and zeros).

 

[mrocm]

I have now tried to re-initialize the HDD and it did not change anything. The problem remains unchanged.

 

[twol]

Assuming there are no logs (do you have debug logs enabled?) then maybe you can telnet into the box, stop it (init 5) and display the log on the terminal (enigma2 command)
If debug logs not enabled, then enable and after problem reboot and have a look at the log.
Maybe it will show whats going on.

 

[tapkor]

I attched a debug log from my Ultimo at the moment of endless spinning VIX after it was forced to zap due to the lack of free tuners (I suppose so). This may be something completely different from mrocm's problem, but I will give it a try.

 

[mrocm]

You are right. I did not have logging activated but it was simple enough the activate it and recreate the problem.

This is pretty much what happens in my case. It seems it may in some way be connected to the timeshift function, which is strange since I am not using timeshift at all.

<   392.804208> [eConsoleAppContainer] Starting sdparm
<   393.510825> [eMainloop::processOneEvent] unhandled POLLERR/HUP/NVAL for fd 71(16)
[TIMER] activating state 1
[TIMER] prepare ok, waiting for begin
[SoftcamManager] oscam-latest already running
[SoftcamManager] Checking if oscam-latest is frozen
<   405.182730> [eConsoleAppContainer] Starting /bin/sh
<   405.293809> [eMainloop::processOneEvent] unhandled POLLERR/HUP/NVAL for fd 71(16)
[SoftcamManager] oscam-latest is responding like it should
job Components.Task.Job name=SoftcamCheck #tasks=1 completed with [] in None
[TIMER] activating state 2
<   413.725145> [eDVBServicePlay] timeshift
[TIMER] zapping
<   417.621475> [gRC] main thread is non-idle! display spinner!

When this happens the init command does not work. I guess it is also affected by the problem. To stop the gui I have to use the kill cmd. With debug logging deactivated the gui restarts automatically after killing it. However, with debug logging activated it seems I have to manually start the gui using "init 3" after killing the gui.

If there is any doubt I can also make it clear that even though I'm using a softcam I still have a "real" card with a payed subscription.

 

[mrocm]

I have tried updating to the latest release version but not change, problem remains. I'm not saying I expected it to go away but every new version is worth trying just in case the cause of the problem have been located and remedied.

 

[mrocm]

I'm not sure whether or not new version adress this issue or not but I thought I might as well add an entry here indicating whether nor not the issue has been solved.

Update was done through the software update menu option, not a complete USB installation. Not sure if this makes a difference.

I have now tried 3.2.036 and there was no change to this issue. Problem remains.

 

[mrocm]

Updated to 3.2.037. Still no change. Problem remains.

 

[abu baniaz]

Adding deug logs of issue may be to your advantage

 

[mrocm]

Thanks for the tip. Log is already provided though (entry #8). That's all that ends up in the log. Behavior has not changed since then. Must admit I haven't checked for changes in the log since the behavior is still unchanged but I will check for it now.

Really like this image and the skin I'm using right now but this is a really annoying bug that may make me try my luck with some other image, perhaps the recently released OpenPLi (which I was using successfully on my DM8k box).

 

[abu baniaz]

Thanks for the tip. Log is already provided though (entry #8). That's all that ends up in the log. Behavior has not changed since then. Must admit I haven't checked for changes in the log since the behavior is still unchanged but I will check for it now.

Really like this image and the skin I'm using right now but this is a really annoying bug that may make me try my luck with some other image, perhaps the recently released OpenPLi (which I was using successfully on my DM8k box).

That is not the debug log. That is little bit of your debug log.

 

[mrocm]

True enough. Being a software developer myself I figured the log of the time when the error occurred would be enough. The entire log contains quite a lot of irrelevant information. Here's a bit more from the log. It's everything that happens from the point when I open the EPG to register a zap event until it hangs. Not sure if this actual

< 87152.998942> [eInputDeviceInit] 1 166 1
[InfoBarGenerics] KEY: 358 INFO
< 87153.330143> [eInputDeviceInit] 0 166 1
[InfoBarGenerics] KEY: 358 INFO
[Skin] processing screen GraphicalEPGPIG:
[Skin] Valign must be either top, center or bottom!, not centre. Please contact the skin's author!
[Skin] Valign must be either top, center or bottom!, not centre. Please contact the skin's author!
warning, skin is missing element key_blue in <class 'Screens.EpgSelection.EPGSelection'>
warning, skin is missing element number in <class 'Screens.EpgSelection.EPGSelection'>
warning, skin is missing element jump in <class 'Screens.EpgSelection.EPGSelection'>
warning, skin is missing element key_red in <class 'Screens.EpgSelection.EPGSelection'>
warning, skin is missing element primetime in <class 'Screens.EpgSelection.EPGSelection'>
warning, skin is missing element timeline2 in <class 'Screens.EpgSelection.EPGSelection'>
warning, skin is missing element timeline3 in <class 'Screens.EpgSelection.EPGSelection'>
warning, skin is missing element timeline0 in <class 'Screens.EpgSelection.EPGSelection'>
warning, skin is missing element timeline1 in <class 'Screens.EpgSelection.EPGSelection'>
warning, skin is missing element timeline4 in <class 'Screens.EpgSelection.EPGSelection'>
warning, skin is missing element timeline5 in <class 'Screens.EpgSelection.EPGSelection'>
warning, skin is missing element change_bouquet in <class 'Screens.EpgSelection.EPGSelection'>
warning, skin is missing element key_green in <class 'Screens.EpgSelection.EPGSelection'>
[Skin] Attribute not implemented: valign value: center
warning, skin is missing element key_yellow in <class 'Screens.EpgSelection.EPGSelection'>
warning, skin is missing element page in <class 'Screens.EpgSelection.EPGSelection'>
< 87153.398376> [gAccel] alloc failed

< 87153.398442> [gSurface] ERROR: accelAlloc failed
[Skin] processing screen GraphicalEPGPIG_summary:
< 87157.338680> [eInputDeviceInit] 1 6c 1
[InfoBarGenerics] KEY: 108 DOWN
[ActionMap] DirectionActions down
< 87157.560126> [eInputDeviceInit] 0 6c 1
[InfoBarGenerics] KEY: 108 DOWN
< 87157.738211> [eInputDeviceInit] 1 6c 1
[InfoBarGenerics] KEY: 108 DOWN
[ActionMap] DirectionActions down
< 87157.960113> [eInputDeviceInit] 0 6c 1
[InfoBarGenerics] KEY: 108 DOWN
< 87162.931043> [eInputDeviceInit] 1 67 1
[InfoBarGenerics] KEY: 103 UP
[ActionMap] DirectionActions up
< 87163.150173> [eInputDeviceInit] 0 67 1
[InfoBarGenerics] KEY: 103 UP
< 87164.713861> [eInputDeviceInit] 1 6a 1
[InfoBarGenerics] KEY: 106 RIGHT
[ActionMap] DirectionActions right
< 87164.940148> [eInputDeviceInit] 0 6a 1
[InfoBarGenerics] KEY: 106 RIGHT
< 87170.241525> [eInputDeviceInit] 1 18f 1
[InfoBarGenerics] KEY: 399 GREEN
< 87170.570102> [eInputDeviceInit] 0 18f 1
[InfoBarGenerics] KEY: 399 GREEN
[ActionMap] EPGSelectActions timerAdd
[ActionMap] unknown action EPGSelectActions/timerAdd! typo in keymap?
[ActionMap] ColorActions green
[Skin] processing screen TimerEntry:
[Skin] processing screen NumericalTextInputHelpDialog:
[Skin] processing screen SetupSummary:
[AutoTimer] Auto Poll
[AutoTimer] Auto Poll Started
< 87171.029234> [eEPGCache] event 1b23 not found in epgcache
< 87171.029386> [eEPGCache] event 08e6 not found in epgcache
< 87171.029470> [eEPGCache] event a0ed not found in epgcache
< 87171.029549> [eEPGCache] event 090f not found in epgcache
< 87171.029627> [eEPGCache] event 0955 not found in epgcache
< 87171.029709> [eEPGCache] event ed6c not found in epgcache
< 87171.029868> [eEPGCache] event 279e not found in epgcache
< 87171.029974> [eEPGCache] event 951c not found in epgcache
< 87171.030149> [eEPGCache] event 24c6 not found in epgcache
< 87171.030466> [eEPGCache] event 0a8c not found in epgcache
< 87174.940802> [eInputDeviceInit] 1 6c 1
[InfoBarGenerics] KEY: 108 DOWN
[ActionMap] PiPSetupActions down
[ActionMap] unknown action PiPSetupActions/down! typo in keymap?
[Skin] processing screen NumericalTextInputHelpDialog:
< 87175.160148> [eInputDeviceInit] 0 6c 1
[InfoBarGenerics] KEY: 108 DOWN
< 87175.344724> [eInputDeviceInit] 1 6c 1
[InfoBarGenerics] KEY: 108 DOWN
[ActionMap] PiPSetupActions down
[ActionMap] unknown action PiPSetupActions/down! typo in keymap?
< 87175.570115> [eInputDeviceInit] 0 6c 1
[InfoBarGenerics] KEY: 108 DOWN
< 87175.701361> [eInputDeviceInit] 1 6c 1
[InfoBarGenerics] KEY: 108 DOWN
[ActionMap] PiPSetupActions down
[ActionMap] unknown action PiPSetupActions/down! typo in keymap?
< 87175.920117> [eInputDeviceInit] 0 6c 1
[InfoBarGenerics] KEY: 108 DOWN
< 87176.050532> [eInputDeviceInit] 1 6c 1
[InfoBarGenerics] KEY: 108 DOWN
[ActionMap] PiPSetupActions down
[ActionMap] unknown action PiPSetupActions/down! typo in keymap?
< 87176.270131> [eInputDeviceInit] 0 6c 1
[InfoBarGenerics] KEY: 108 DOWN
< 87176.442051> [eInputDeviceInit] 1 6c 1
[InfoBarGenerics] KEY: 108 DOWN
[ActionMap] PiPSetupActions down
[ActionMap] unknown action PiPSetupActions/down! typo in keymap?
< 87176.660155> [eInputDeviceInit] 0 6c 1
[InfoBarGenerics] KEY: 108 DOWN
< 87179.992687> [eInputDeviceInit] 1 2 1
[InfoBarGenerics] KEY: 2 1
[ActionMap] SetupActions 1
[ActionMap] unknown action SetupActions/1! typo in keymap?
< 87180.210142> [eInputDeviceInit] 0 2 1
[InfoBarGenerics] KEY: 2 1
< 87180.883978> [eInputDeviceInit] 1 9 1
[InfoBarGenerics] KEY: 9 8
[ActionMap] SetupActions 8
[ActionMap] unknown action SetupActions/8! typo in keymap?
< 87181.210121> [eInputDeviceInit] 0 9 1
[InfoBarGenerics] KEY: 9 8
< 87181.854141> [eInputDeviceInit] 1 6 1
[InfoBarGenerics] KEY: 6 5
[ActionMap] SetupActions 5
[ActionMap] unknown action SetupActions/5! typo in keymap?
< 87182.080105> [eInputDeviceInit] 0 6 1
[InfoBarGenerics] KEY: 6 5
< 87182.375521> [eInputDeviceInit] 1 6 1
[InfoBarGenerics] KEY: 6 5
[ActionMap] SetupActions 5
[ActionMap] unknown action SetupActions/5! typo in keymap?
< 87182.600087> [eInputDeviceInit] 0 6 1
[InfoBarGenerics] KEY: 6 5
< 87184.026317> [eInputDeviceInit] 1 67 1
[InfoBarGenerics] KEY: 103 UP
[ActionMap] PiPSetupActions up
[ActionMap] unknown action PiPSetupActions/up! typo in keymap?
< 87184.250150> [eInputDeviceInit] 0 67 1
[InfoBarGenerics] KEY: 103 UP
< 87184.522751> [eInputDeviceInit] 1 67 1
[InfoBarGenerics] KEY: 103 UP
[ActionMap] PiPSetupActions up
[ActionMap] unknown action PiPSetupActions/up! typo in keymap?
< 87184.740118> [eInputDeviceInit] 0 67 1
[InfoBarGenerics] KEY: 103 UP
< 87185.048781> [eInputDeviceInit] 1 67 1
[InfoBarGenerics] KEY: 103 UP
[ActionMap] PiPSetupActions up
[ActionMap] unknown action PiPSetupActions/up! typo in keymap?
< 87185.270106> [eInputDeviceInit] 0 67 1
[InfoBarGenerics] KEY: 103 UP
< 87185.873259> [eInputDeviceInit] 1 69 1
[InfoBarGenerics] KEY: 105 LEFT
[ActionMap] SetupActions left
[ActionMap] unknown action SetupActions/left! typo in keymap?
[ActionMap] PiPSetupActions left
[ActionMap] unknown action PiPSetupActions/left! typo in keymap?
[ActionMap] SetupActions left
< 87186.090282> [eInputDeviceInit] 0 69 1
[InfoBarGenerics] KEY: 105 LEFT
< 87187.241931> [eInputDeviceInit] 1 160 1
[InfoBarGenerics] KEY: 352 OK
[ActionMap] SetupActions ok
[Config] getResolvedKey config.usage.remote_fallback empty variable.
e00000(DiSEqC reset)
e00003(DiSEqC peripherial power on)
e01038f0(?)
[Config] getResolvedKey config.usage.remote_fallback empty variable.
e00000(DiSEqC reset)
e00003(DiSEqC peripherial power on)
e01038f0(?)
[Config] getResolvedKey config.usage.remote_fallback empty variable.
e00000(DiSEqC reset)
e00003(DiSEqC peripherial power on)
e01038f2(?)
[Config] getResolvedKey config.usage.remote_fallback empty variable.
[Config] getResolvedKey config.usage.remote_fallback empty variable.
[RecordTimer] record time changed, start prepare is now: Thu Feb 25 18:54:40 2016
[RecordTimer] Record RecordTimerEntry(name=Vänner, begin=Thu Feb 25 18:55:00 2016, serviceref=1:0:19:1A91:43:46:E080000:0:0:0:, justplay=True, isAutoTimer=False)
< 87187.460156> [eInputDeviceInit] 0 160 1
[InfoBarGenerics] KEY: 352 OK
< 87189.198824> [eInputDeviceInit] 1 ae 1
[InfoBarGenerics] KEY: 174 EXIT
[ActionMap] OkCancelActions cancel
< 87189.420255> [eInputDeviceInit] 0 ae 1
[InfoBarGenerics] KEY: 174 EXIT
[RecordTimer] activating state 1
[RecordTimer] prepare ok, waiting for begin
[RecordTimer] activating state 2
< 87249.029079> [eDVBServicePlay] timeshift
[RecordTimer] zapping
< 87251.207485> [gRC] main thread is non-idle! display spinner!

 

[abu baniaz]

I am just a moderator/tester.

From what I have gathered, you need to look for something amiss in the leadup to the event or something not quite right in the normal startup processes.

What is the service you are zapping to?

1:0:19:1A91:43:46:E080000:0:0:0:

Are you able to zap to it using CLI?

As a separate matter, what skin are you using? The center/centre issue ought to be reported and fixed.

 

[mrocm]

Don't really know what to look for since I am unfamiliar with these platforms. I could of course supply the entire log file if it would change anything. Just figured it would be quite a lot of irrelevant, and to some extent personal, information to sift through.

I have tried zapping (via timers) to several different channels. Does not seem to matter which channel I try to zap to. It also doesn't matter if it's a zap timer or a zap-and-record timer. In this specific case I was trying to zap to "Kanal 5" from the provider Canal Digital (in Sweden). Don't know if that is the information you asked for.

I'm not sure what you mean by zapping using CLI. Zapping to any channel, including the one mentioned above, works without issues when done manually through either the simple channel list or the graphical EPG.

Zap timers work without issue using other images but I like this image and this skin so I would prefer staying with it if zap timers can be made to work.

The skin I am using is "YouViX-Blue".

 

[abu baniaz]

I am guessing that this is what is happening:

You have set a zap timer to the channnel which has a service reference

1:0:19:1A91:43:46:E080000:0:0:0:

It is not finding the channel and hence the loop. I have checked the lamedb, the file that stores the services/channels, I cannot find that one. This is why I asked if you can zap to it by command line. There may be an issue with the 0.8w/1w debate. Some organisations use 1w, others 0.8w. Or you may have discovered a bug that needs to be resolved.

Can you issue the following command and see if the receiver zaps to it

wget -q -O - http://127.0.0.1/web/zap?sRef=1:0:19:1A91:43:46:E080000:0:0:0:

Before you do so, can you save the following files from you receiver and upload them here as attachments please? This will help in trying to reproduce the issue you are having.

"lamedb" located in /etc/enigma2
"satellites.xml" located in /etc/enigma2
"satellites.xml" located in /etc/tuxbox

 

[mrocm]

Cmd line zapping works fine.

The problem is most likely NOT caused by unability to zap to a certain service because zapping manually by remote control or by cmd line works fine. All service settings are defined in the satellites.xml file and the same file works without issue with zap timers using other images.

 

[birdman]

I am guessing that this is what is happening:

You have set a zap timer to the channnel which has a service reference

1:0:19:1A91:43:46:E080000:0:0:0:

It is not finding the channel and hence the loop.

I wonder whether:

1:0:19:1A91:43:46:E080000:0:0:0:
​

doesn't match

1a91:0e080000:0043:0046:25:0​

(which is what lamedb has) because of the mis-match in leading zeroes?

(I can't test that directly, as I don't have any channels with leading zeros in lamedb)