Superb quality and spec AB-Com PULSe 4K SE. Crazy offer! Only £129! FREE UK DELIVERY! 4K UHD, Enigma 2, Multiboot 4 images & more!...
Superb quality and spec AB-Com PULSe 4K Rev II Twin Satellite tuner only £179! FREE UK DELIVERY! 4K UHD, Enigma 2, SATA HDD facility, Multiboot 4 images & more!...

[VU+ Duo] Turn ON issue

  • Thread starter Thread starter satnav
  • Start date Start date
Same issue for me and and for some other guys on openpli forum. This started with new kernel.
 
Thanks Rob I was using 2.3 but now reverted back to 2.2.1 cant see any difference! same issue.

Can you post your exact setup as brdbch has done above, also please advise if your HDD is EXT 3 or 4 and what filesystem any connected USB stick is using.
 
I wonder if the problem may be related to ntp activation.
After a while in standby mode, the system clock falls back to Oct 26 1970.


It's now Thu Feb 9 15:13:46 2012
[timer.py] next activation: Thu Feb 9 15:15:26 2012 (in 99997 ms)
It's now Thu Feb 9 15:13:46 2012
[timer.py] next activation: Thu Feb 9 15:15:26 2012 (in 99995 ms)
[AutoTimer] Auto Poll
[AutoTimer] Auto Poll Started
[AutoTimer] No changes in configuration, won't parse
job Components.Task.Job name=AutoTimerTask #tasks=1 completed with [] in None
[NTPSync] Poll Started
[ePopen] command: /usr/bin/ntpdate -s -u pool.ntp.org
job Components.Task.Job name=NTPSync #tasks=1 completed with [] in None
child has terminated
pipes closed
poll: unhandled POLLERR/HUP/NVAL for fd 32(16)
[EPGC] 13817934 bytes for cache used
[CrossEPG_Auto] poll
[EPGC] 13817934 bytes for cache used
[eDVBLocalTimerHandler] no transponder tuned... or no TDT/TOT avail .. try to use RTC :)
[eDVBLocalTimerHandler] RTC time is 04:13:41
[eDVBLocalTimerHandler] Receiver time is 15:15:07
[eDVBLocalTimerHandler] RTC to Receiver time difference is 1303038086 seconds
[eDVBLocalTimerHandler] set Linux Time to RTC Time
[EPGC] 13817934 bytes for cache used
[timer.py] timewarp - re-evaluating all processed timers.
It's now Mon Oct 26 04:13:59 1970
[timer.py] next activation: Mon Oct 26 04:15:39 1970 (in 99031 ms)
[timer.py] timewarp - re-evaluating all processed timers.
It's now Mon Oct 26 04:13:59 1970
[timer.py] next activation: Mon Oct 26 04:15:39 1970 (in 99028 ms)
[EPGC] 13817934 bytes for cache used
 
Please post exactly how your Duo was setup.

300 gig WD internal HD

Vix 2.3 latest release with all updates

cross epg set up with open tv 28.2 auto download 440 am.

4 gig rear usb for epg and picons.

If you need more let me know Sic.
 
300 gig WD internal HD

Vix 2.3 latest release with all updates

cross epg set up with open tv 28.2 auto download 440 am.

4 gig rear usb for epg and picons.

If you need more let me know Sic.

Could you list filesystem on the drives, plugins and skins installed please.
 
Turned off ntp.
Same problem, after a while in standby, system time goes back to 1970.
I wonder what side effects this may have on CAMs, smart cards rights and record timers....

[timer.py] next activation: Thu Feb 9 17:53:29 2012 (in 99995 ms)
[EPGC] 13528369 bytes for cache used
no version filtering
0014: 70 00 00 00 00 00
mask: fc 00 00 00 00 00
mode: 00 00 00 00 00 00
[eDVBLocalTimerHandler] diff is -1
[eDVBLocalTimerHandler] diff < 120 .. use Transponder Time
[eDVBLocalTimerHandler] difference between new linux time and RTC time is > 60 sec... transponder time looks not ok... use rtc time
[eDVBLocalTimerHandler] time update to 01:49:36
[eDVBLocalTimerHandler] m_time_difference is -1303056170
[eDVBLocalTimerHandler] set Linux Time
[EPGC] 13528369 bytes for cache used
[EPGC] 13528369 bytes for cache used
[timer.py] timewarp - re-evaluating all processed timers.
It's now Mon Oct 26 01:50:38 1970
 
Hmm interesting to see
Code:
[timer.py] timewarp - re-evaluating all processed timers.
It's now Mon Oct 26 01:50:38 1970
So the system is actually alive when this timewarp occurs. I thought this would be a side-effect of the freezing (in which case it wouldn't have been in the log at all).
 
The system is still alive, but the GUI does not restart correctly (VIX logo rotating).
Also after powering off/on, the smart card would not respond.
Had to power off/on several times before it would work.

I left the box last nigth in standby with no card inserted and ntp off.
Did not freeze, did not go back in time. The RTC seems to have been updated correctly.

It's now Fri Feb 10 06:35:06 2012
[timer.py] next activation: Fri Feb 10 06:36:46 2012 (in 99996 ms)
[eDVBLocalTimerHandler] no transponder tuned... or no TDT/TOT avail .. try to use RTC :)
[eDVBLocalTimerHandler] RTC time is 06:35:43
[eDVBLocalTimerHandler] Receiver time is 06:35:43
[eDVBLocalTimerHandler] RTC to Receiver time difference is 0 seconds
[eDVBLocalTimerHandler] no change needed
[EPGC] 13118043 bytes for cache used
[EPGC] 13118043 bytes for cache used
It's now Fri Feb 10 06:36:46 2012
[timer.py] next activation: Fri Feb 10 06:38:26 2012 (in 99997 ms)
 
OK guys I have two solutions to avoid this issue. One Load the Auto shut down plugin set it up to close down during the night and then just turn STB on again when required, this worked fine. Second option and preferred choice is to enable the VIX power manager setting up all options to suit my needs, apart from GUI restart. This also works fine switching the STB on in the morning ready for use.:amen:
 
Got a log of the freeze (ntp active, no card inserted)

Top shows that enigma2 is running in a loop.

top - 05:20:24 up 4:10, 1 user, load average: 1.12, 1.31, 1.22
Tasks: 91 total, 2 running, 89 sleeping, 0 stopped, 0 zombie
Cpu(s): 50.2%us, 1.8%sy, 0.0%ni, 45.0%id, 0.0%wa, 0.0%hi, 2.9%si, 0.0%st
Mem: 138272k total, 135600k used, 2672k free, 1312k buffers
Swap: 199996k total, 3400k used, 196596k free, 33700k cached

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
506 root 20 0 153m 65m 1264 R 102 48.5 195:09.90 enigma2

Log shows:
First went back to 1970:

It's now Fri Feb 10 08:27:39 2012
[timer.py] next activation: Fri Feb 10 08:29:19 2012 (in 99995 ms)
[EPGC] 12582465 bytes for cache used
[EPGC] 12582465 bytes for cache used
[eDVBLocalTimerHandler] no transponder tuned... or no TDT/TOT avail .. try to use RTC :)
[eDVBLocalTimerHandler] RTC time is 01:45:37
[eDVBLocalTimerHandler] Receiver time is 08:29:16
[eDVBLocalTimerHandler] RTC to Receiver time difference is 1303109019 seconds
[eDVBLocalTimerHandler] set Linux Time to RTC Time
[EPGC] 12582465 bytes for cache used
[timer.py] timewarp - re-evaluating all processed timers.
It's now Mon Oct 26 01:45:40 1970
[timer.py] next activation: Mon Oct 26 01:47:20 1970 (in 99996 ms)

then half an hour later:

It's now Mon Oct 26 02:12:20 1970
[timer.py] next activation: Mon Oct 26 02:14:00 1970 (in 99995 ms)
It's now Mon Oct 26 02:12:20 1970
[timer.py] next activation: Mon Oct 26 02:14:00 1970 (in 99993 ms)
[AutoTimer] Auto Poll
[AutoTimer] Auto Poll Started
[AutoTimer] No changes in configuration, won't parse
job Components.Task.Job name=AutoTimerTask #tasks=1 completed with [] in None
Traceback (most recent call last):
File "/usr/lib/enigma2/python/mytest.py", line 619, in <module>
runScreenTest()
File "/usr/lib/enigma2/python/mytest.py", line 502, in runScreenTest
runReactor()
File "/usr/lib/enigma2/python/mytest.py", line 91, in runReactor
reactor.run(installSignalHandlers=False)
File "/usr/lib/python2.6/site-packages/twisted/internet/base.py", line 1166, in run

--- <exception caught here> ---
File "/usr/lib/python2.6/site-packages/twisted/internet/base.py", line 1178, in mainLoop

File "/usr/lib/enigma2/python/e2reactor.py", line 158, in doPoll

exceptions.OverflowError: long int too large to convert to int
Traceback (most recent call last):
File "/usr/lib/enigma2/python/mytest.py", line 619, in <module>
runScreenTest()
File "/usr/lib/enigma2/python/mytest.py", line 502, in runScreenTest
runReactor()
File "/usr/lib/enigma2/python/mytest.py", line 91, in runReactor
reactor.run(installSignalHandlers=False)
File "/usr/lib/python2.6/site-packages/twisted/internet/base.py", line 1166, in run

--- <exception caught here> ---
File "/usr/lib/python2.6/site-packages/twisted/internet/base.py", line 1178, in mainLoop

File "/usr/lib/enigma2/python/e2reactor.py", line 158, in doPoll

.... same output for the next 500Mb of log file.
 
I turned off all EPG (there are still some EPG messages in the log, but nothing displays in the GUI).
Crashed the same way.
The log in zip format.
Could not truncate it since it generated a 2.6 Gb log overnight, and could not get any editor to accept it.
The only way to look at it is to use vi.

This morning i did "kill -9" on the enigma2 program, and the GUI restarted nicely.
 

Attachments

Just in case, i reinstalled everything from scratch over the week-end, and the problem is still there.
 
List all the plugins you have installed, softcam, epg storage location, mounts, file system used on HDD & USB.

Post exact step by step how you setup the receiver after flashing.
 

OpenViX Feeds Status

Back
Top