Hello Guest, if you are reading this it means you have not registered yet. Please take a second, Click here to register, and in a few simple steps you will be able to enjoy our community and use our OpenViX support section.
Results 1 to 13 of 13

Thread: Limbo

  1. #1

    Title
    Member
    Join Date
    Sep 2023
    Posts
    35
    Thanks
    7
    Thanked 2 Times in 2 Posts

    Limbo

    More of an annoyance than a serious problem, I have 3 SF8008 4K twin's which have been setup individually but all have the exact same trait

    OpenVix6.4.011
    Willobuild
    slyk-onyx-1080

    I have removed Autobouquetmaker system plugin from all boxes (I create my own bouquets and restore them with WilloBouquetManager) and have BBC1 setup as start service including standby, though it was just the same without a startup service selected.

    Every night after watching the boxes they are put into normal standby, every morning they have put themselves into deep standby but in a kind of limbo mode,
    pressing the power button on the remote wakes the boxes and they go through the normal waking process finishing with the front display showing 101 (BBC1) before displaying the time,
    but there is no display I either get a Blue screen or Openvix splash screen until I change channel?

    I have no timers running have disabled the Software update background check and I have tried disabling OpenTV EPG Downloader and EPG Importer, there are no crash logs only debug logs
    Would appreciate any ideas why my box does this every night?

  2. #2

    Title
    Member
    Join Date
    Sep 2023
    Posts
    35
    Thanks
    7
    Thanked 2 Times in 2 Posts
    Quote Originally Posted by ACWhitehouse View Post
    More of an annoyance than a serious problem, I have 3 SF8008 4K twin's which have been setup individually but all have the exact same trait

    OpenVix6.4.011
    Willobuild
    slyk-onyx-1080

    I have removed Autobouquetmaker system plugin from all boxes (I create my own bouquets and restore them with WilloBouquetManager) and have BBC1 setup as start service including standby, though it was just the same without a startup service selected.

    Every night after watching the boxes they are put into normal standby, every morning they have put themselves into deep standby but in a kind of limbo mode,
    pressing the power button on the remote wakes the boxes and they go through the normal waking process finishing with the front display showing 101 (BBC1) before displaying the time,
    but there is no display I either get a Blue screen or Openvix splash screen until I change channel?

    I have no timers running have disabled the Software update background check and I have tried disabling OpenTV EPG Downloader and EPG Importer, there are no crash logs only debug logs
    Would appreciate any ideas why my box does this every night?
    I have found this which I have extracted from the bottom of one of my Debug logs, I think I can see the problem, but don't know what it is or how to resolve it

    <322043.2531> 05:17:08.8698 [Skin] Processing screen 'QuitMainloopScreen', position=(0, 0), size=(1920 x 1080) for module 'QuitMainloopScreen'.
    <322043.3300> 05:17:08.9467 [Standby] quitMainloop #1
    <322043.3303> 05:17:08.9470 [Skin] Parsing embedded skin '<embedded-in-TryQuitMainloop>'.
    <322043.3308> 05:17:08.9475 [Skin] Processing screen '<embedded-in-TryQuitMainloop>', position=(1310, 0), size=(0 x 0) for module 'TryQuitMainloop'.
    <322043.3318> 05:17:08.9485 [Skin] Processing screen 'SimpleSummary' from list 'TryQuitMainloop_summary, SimpleSummary', position=(0, 0), size=(1 x 1) for module 'ScreenSummary'.
    <322043.3495> 05:17:08.9662 "::ffff:127.0.0.1" - - [11/Feb/2024:05:17:07 +0000] "GET /web/powerstate?newstate=3 HTTP/1.1" 200 106 "-" "Wget/1.21.3"
    <322043.3508> 05:17:08.9674 [InputHotplug] connectionLost? [Failure instance: Traceback (failure with no frames): <class 'twisted.internet.error.ConnectionLost'>: Connection to the other side was lost in a non-clean fashion: Connection lost.
    ]<322043.3508> 05:17:08.9675
    <322043.3514> 05:17:08.9681 (UNIX Port /tmp/hotplug.socket Closed)
    <322043.3521> 05:17:08.9688 Stopping factory <twisted.internet.protocol.Factory object at 0xaefa22d0>
    <322043.3525> 05:17:08.9692 (TCP Port 80 Closed)
    <322043.3532> 05:17:08.9699 Stopping factory <twisted.web.server.Site object at 0xaefc1f50>
    <322043.3556> 05:17:08.9722 Main loop terminated.
    <322043.3563> 05:17:08.9729 [OpentvZapper] next wake up due -1
    <322043.3571> 05:17:08.9738 [OpentvZapper] next wake up due -1
    <322043.4063> 05:17:09.0230 [OpentvZapper-Scheduler][Scheduleautostart] reason(1), session None
    <322043.4064> 05:17:09.0231 [OpentvZapper-Scheduler][Scheduleautostart] Stop
    <322043.4070> 05:17:09.0237 [XMLTVImport] autostart (1) occured at 1707628629.0236175
    <322043.4071> 05:17:09.0238 [XMLTVImport] Stop
    <322043.4075> 05:17:09.0242 [BouquetMakerXtream] autostart (1) occured at 2024-02-11 05:17:09
    <322043.4081> 05:17:09.0248 [AutoTimer] No changes in configuration, won't parse
    <322043.4155> 05:17:09.0322 [eDVBDB] ---- saving lame channel db
    <322043.4246> 05:17:09.0413 [eDVBDB] saved 70 channels and 899 services!
    <322043.4429> 05:17:09.0596 [eDVBResourceManager] release cached channel (timer timeout)
    <322043.4431> 05:17:09.0598 [Avahi] avahi_timeout_new
    <322043.4437> 05:17:09.0604 [Avahi] avahi_timeout_free
    <322043.4439> 05:17:09.0606 [Avahi] avahi_watch_free
    <322043.4444> 05:17:09.0611 [Avahi] avahi_timeout_update
    <322043.4445> 05:17:09.0612 [Avahi] avahi_timeout_free
    <322043.4946> 05:17:09.1112 [eEPGCache] store epg to realpath '/media/hdd/epg.dat'
    <322043.6584> 05:17:09.2751 [eEPGCache] 176071 events written to /media/hdd/epg.dat
    <322044.5250> 05:17:10.1417 [eDVBLocalTimeHandler] set RTC to previous valid time
    <322044.5257> 05:17:10.0000 [eInit] - (43) eServiceFactoryApp
    <322044.5260> 05:17:10.0003 [eInit] - (41) Stream server
    <322044.5262> 05:17:10.0005 [eInit] - (41) Encoders
    <322044.5264> 05:17:10.0007 [eInit] - (41) eServiceFactoryDVB
    <322044.5266> 05:17:10.0009 [eInit] - (41) eServiceFactoryFS
    <322044.5268> 05:17:10.0011 [eInit] - (41) eServiceFactoryMP3
    <322044.5271> 05:17:10.0014 [eInit] - (41) eServiceFactoryM2TS
    <322044.5273> 05:17:10.0016 [eInit] - (41) eServiceFactoryHDMI
    <322044.5275> 05:17:10.0018 [eInit] - (41) eServiceFactoryTS
    <322044.5277> 05:17:10.0020 [eInit] - (41) eServiceFactoryWebTS
    <322044.5279> 05:17:10.0022 [eInit] - (41) eServiceFactoryDVD
    <322044.5281> 05:17:10.0024 [eInit] - (40) eServiceCenter
    <322044.5283> 05:17:10.0026 [eInit] - (35) CA handler
    <322044.5286> 05:17:10.0029 [eInit] - (35) CI Slots
    <322044.5290> 05:17:10.0033 [eInit] - (30) eActionMap
    <322044.5293> 05:17:10.0036 [eInit] - (22) Hdmi CEC driver
    <322044.5295> 05:17:10.0038 [eInit] - (21) input device driver
    <322044.5840> 05:17:10.0583 [eInit] - (20) AVSwitch Driver
    <322044.5844> 05:17:10.0587 [eInit] - (20) misc options
    <322044.5847> 05:17:10.0590 [eInit] - (20) RC Input layer
    <322044.5849> 05:17:10.0592 [eInit] - (20) UHF Modulator
    <322044.5851> 05:17:10.0594 [eInit] - (20) DVB-CI UI
    <322044.5853> 05:17:10.0597 [eInit] - (15) eWindowStyleManager
    <322044.5856> 05:17:10.0599 [eInit] - (10) gRC
    <322044.5858> 05:17:10.0601 [gRC] waiting for gRC thread shutdown
    <322044.5860> 05:17:10.0603 [gRC] thread has finished
    <322044.5862> 05:17:10.0605 [eInit] - (9) Font Render Class
    <322044.5865> 05:17:10.0608 [eInit] - (9) gLCD
    <322044.5867> 05:17:10.0610 [eInit] - (9) GFBDC
    <322044.5882> 05:17:10.0625 [eInit] - (8) graphics acceleration manager
    <322044.5884> 05:17:10.0627 [eInit] - (5) Tuxtxt
    <322044.5887> 05:17:10.0630 [eInit] - (1) Background File Eraser
    <322044.5889> 05:17:10.0632 [eInit] reached rl -1
    [MAIN] executing main
    TuxTxt cache cleared
    cleaning up
    TuxTxt cache cleared

    enigma2 has exited
    ========== Enigma2 log ends ==========


    Can anyone point me in the right direction ?

  3. #3
    birdman's Avatar
    Title
    Moderator
    Join Date
    Sep 2014
    Location
    Hitchin, UK
    Posts
    7,858
    Thanks
    239
    Thanked 1,673 Times in 1,318 Posts
    That partial log show it shutting down (Processing screen 'QuitMainloopScreen' ...)

    So we'd really need to see what happened before then to see why it decided to do so.

    Although if enigma2 was shutdown then you wouldn't be able to change channel. so that's not the full story.
    MiracleBox Prem Twin HD - 2@DVB-T2 + Xtrend et8000 - 5(incl. 2 different USBs)@DVB-T2[terrestrial - UK Freeview HD, Sandy Heath] - LAN/USB-stick/HDD

  4. #4

    Title
    Member
    Join Date
    Sep 2023
    Posts
    35
    Thanks
    7
    Thanked 2 Times in 2 Posts
    Quote Originally Posted by birdman View Post
    That partial log show it shutting down (Processing screen 'QuitMainloopScreen' ...)

    So we'd really need to see what happened before then to see why it decided to do so.

    Although if enigma2 was shutdown then you wouldn't be able to change channel. so that's not the full story.
    Thanks for the response, OK I can't post full log its too big so here is the bottom hour or so of it..
    ========== Enigma2 log starts ==========


    <318532.7322> 04:18:38.3967 [CacheFlush] sync
    <318532.7710> 04:18:38.4355 [CacheFlush] free pagecache, dentries and inodes
    <318532.7906> 04:18:38.4552 [CacheFlush] fallback to default translation for Mem cleared
    <318533.3818> 04:18:39.0463 [NetworkTime] setting E2 time: 1707625119.0461886
    <318533.3824> 04:18:39.0001 [eDVBLocalTimerHandler] setUseDVBTime: current=dvb, new=dvb
    <318645.1252> 04:20:30.7429 [eDVBDemux] open demux /dev/dvb/adapter0/demux0
    <318645.1255> 04:20:30.7432 [eDVBSectionReader] DMX_SET_FILTER pid=20
    <318648.1045> 04:20:33.7222 [eDVBLocalTimerHandler] diff is 3
    <318648.1045> 04:20:33.7223 [eDVBLocalTimerHandler] diff < 120 .. use Transponder Time
    <318648.1047> 04:20:33.7224 [eDVBLocalTimerHandler] difference between linux time and RTC time is < 60 sec... so the transponder time looks ok
    <318648.1048> 04:20:33.7225 [eDVBLocalTimerHandler] time update to 04:20:36
    <318648.1048> 04:20:33.7225 [eDVBLocalTimerHandler] m_time_difference is 3
    <318648.1048> 04:20:33.7225 [eDVBLocalTimerHandler] slewing Linux Time by 003 seconds
    <318648.1052> 04:20:33.7229 [eDVBChannel] getDemux cap=00
    <318651.0202> 04:20:36.6379 [eEPGChannelData] start reading events(1707625236)
    <318651.0217> 04:20:36.6394 [eDVBSectionReader] DMX_SET_FILTER pid=18
    <318651.0249> 04:20:36.6426 [eDVBSectionReader] DMX_SET_FILTER pid=18
    <318651.0270> 04:20:36.6448 [eDVBSectionReader] DMX_SET_FILTER pid=18
    <318651.0278> 04:20:36.6455 [eEPGChannelData] abort non avail OpenTV EIT reading
    <318658.0280> 04:20:43.6457 [eEPGChannelData] abort non avail schedule reading
    <318658.0285> 04:20:43.6462 [eEPGChannelData] abort non avail schedule other reading
    <318658.1145> 04:20:43.7322 [eEPGChannelData] nownext finished(1707625243)
    <318658.1148> 04:20:43.7325 [eEPGChannelData] stop caching events(1707625243)
    <318658.1148> 04:20:43.7326 [eEPGChannelData] next update in 60 min
    <318714.2234> 04:21:39.8411 [AutoTimer] current auto poll 2024-02-11 04:21:39
    <318714.2236> 04:21:39.8413 [AutoTimer] Auto Poll Started
    <318714.2674> 04:21:39.8851 [AutoTimer] No changes in configuration, won't parse
    <318714.2760> 04:21:39.8937 [Task] job Components.Task.Job name=AutoTimer #tasks=0 completed with [] in None
    <318714.2764> 04:21:39.8941 [AutoTimer] next auto poll at 2024-02-11 04:51:39
    <319100.5702> 04:28:06.1879 [Harddisk] Command: 'sdparm --flexible --readonly --command=stop /dev/sdb'.
    /dev/sdb: Mass Storage Device
    <319490.5703> 04:34:36.1880 [Harddisk] Command: 'sdparm --flexible --readonly --command=stop /dev/sdb'.
    /dev/sdb: Mass Storage Device
    <320000.5702> 04:43:06.1879 [Harddisk] Command: 'sdparm --flexible --readonly --command=stop /dev/sdb'.
    /dev/sdb: Mass Storage Device
    <320332.7428> 04:48:38.3605 [CacheFlush] sync
    <320332.7744> 04:48:38.3921 [CacheFlush] free pagecache, dentries and inodes
    <320332.7931> 04:48:38.4108 [CacheFlush] fallback to default translation for Mem cleared
    <320333.3828> 04:48:39.0005 [NetworkTime] setting E2 time: 1707626919.0004299
    <320333.3834> 04:48:39.0001 [eDVBLocalTimerHandler] setUseDVBTime: current=dvb, new=dvb
    <320448.1053> 04:50:33.7219 [eDVBDemux] open demux /dev/dvb/adapter0/demux0
    <320448.1054> 04:50:33.7221 [eDVBSectionReader] DMX_SET_FILTER pid=20
    <320452.4618> 04:50:38.0785 [eDVBLocalTimerHandler] diff is 1
    <320452.4619> 04:50:38.0786 [eDVBLocalTimerHandler] diff < 120 .. use Transponder Time
    <320452.4621> 04:50:38.0788 [eDVBLocalTimerHandler] difference between linux time and RTC time is < 60 sec... so the transponder time looks ok
    <320452.4622> 04:50:38.0788 [eDVBLocalTimerHandler] time update to 04:50:39
    <320452.4622> 04:50:38.0789 [eDVBLocalTimerHandler] m_time_difference is 1
    <320452.4622> 04:50:38.0789 [eDVBLocalTimerHandler] slewing Linux Time by 001 seconds
    <320452.4638> 04:50:38.0805 [eDVBChannel] getDemux cap=00
    <320514.2766> 04:51:39.8933 [AutoTimer] current auto poll 2024-02-11 04:51:39
    <320514.2769> 04:51:39.8935 [AutoTimer] Auto Poll Started
    <320514.3205> 04:51:39.9372 [AutoTimer] No changes in configuration, won't parse
    <320514.3291> 04:51:39.9458 [Task] job Components.Task.Job name=AutoTimer #tasks=0 completed with [] in None
    <320514.3296> 04:51:39.9463 [AutoTimer] next auto poll at 2024-02-11 05:21:39
    <320930.5703> 04:58:36.1870 [Harddisk] Command: 'sdparm --flexible --readonly --command=stop /dev/sdb'.
    /dev/sdb: Mass Storage Device
    <321290.5704> 05:04:36.1871 [Harddisk] Command: 'sdparm --flexible --readonly --command=stop /dev/sdb'.
    /dev/sdb: Mass Storage Device
    <321830.5702> 05:13:36.1869 [Harddisk] Command: 'sdparm --flexible --readonly --command=stop /dev/sdb'.
    /dev/sdb: Mass Storage Device
    <322041.4367> 05:17:07.0534 [eDVBCAService] free slot 0 demux 0 for service 1:0:19:22CF:80D:2:11A0000:0:0:0:
    <322041.4373> 05:17:07.0540 [eDVBCAService] free service 1:0:19:22CF:80D:2:11A0000:0:0:0:
    <322043.2381> 05:17:08.8548 [eTSMPEGDecoder] decoder state: play, vpid=ffffffff, apid=ffffffff
    <322043.2382> 05:17:08.8549 [eDVBPCR0] DEMUX_STOP ok
    <322043.2383> 05:17:08.8550 [eDVBPCR0] destroy
    <322043.2383> 05:17:08.8550 [eDVBVideo0] DEMUX_STOP ok
    <322043.2383> 05:17:08.8550 [eDVBVideo0] VIDEO_STOP ok
    <322043.2385> 05:17:08.8552 [eDVBVideo0] destroy
    <322043.2385> 05:17:08.8552 [eDVBAudio0] AUDIO_STOP ok
    <322043.2386> 05:17:08.8552 [eDVBAudio0] DEMUX_STOP ok
    <322043.2386> 05:17:08.8553 [eDVBAudio0] AUDIO_CONTINUE ok
    <322043.2386> 05:17:08.8553 [eDVBAudio0] destroy
    <322043.2386> 05:17:08.8553 [eDVBText0] DEMUX_STOP ok
    <322043.2387> 05:17:08.8553 [decoder][eDVBText] stopCaching
    <322043.2387> 05:17:08.8554 [eDVBText0] destroy
    <322043.2387> 05:17:08.8554 [decoder][eDVBText] resetPID
    <322043.2388> 05:17:08.8554 [decoder][eDVBText] freeCache
    <322043.2411> 05:17:08.8578 [eDVBLocalTimerHandler] remove channel 0x2dedbd0
    <322043.2412> 05:17:08.8579 [eEPGTransponderDataReader] remove channel 0x2dedbd0
    <322043.2531> 05:17:08.8698 [Skin] Processing screen 'QuitMainloopScreen', position=(0, 0), size=(1920 x 1080) for module 'QuitMainloopScreen'.
    <322043.3300> 05:17:08.9467 [Standby] quitMainloop #1
    <322043.3303> 05:17:08.9470 [Skin] Parsing embedded skin '<embedded-in-TryQuitMainloop>'.
    <322043.3308> 05:17:08.9475 [Skin] Processing screen '<embedded-in-TryQuitMainloop>', position=(1310, 0), size=(0 x 0) for module 'TryQuitMainloop'.
    <322043.3318> 05:17:08.9485 [Skin] Processing screen 'SimpleSummary' from list 'TryQuitMainloop_summary, SimpleSummary', position=(0, 0), size=(1 x 1) for module 'ScreenSummary'.
    <322043.3495> 05:17:08.9662 "::ffff:127.0.0.1" - - [11/Feb/2024:05:17:07 +0000] "GET /web/powerstate?newstate=3 HTTP/1.1" 200 106 "-" "Wget/1.21.3"
    <322043.3508> 05:17:08.9674 [InputHotplug] connectionLost? [Failure instance: Traceback (failure with no frames): <class 'twisted.internet.error.ConnectionLost'>: Connection to the other side was lost in a non-clean fashion: Connection lost.
    ]<322043.3508> 05:17:08.9675
    <322043.3514> 05:17:08.9681 (UNIX Port /tmp/hotplug.socket Closed)
    <322043.3521> 05:17:08.9688 Stopping factory <twisted.internet.protocol.Factory object at 0xaefa22d0>
    <322043.3525> 05:17:08.9692 (TCP Port 80 Closed)
    <322043.3532> 05:17:08.9699 Stopping factory <twisted.web.server.Site object at 0xaefc1f50>
    <322043.3556> 05:17:08.9722 Main loop terminated.
    <322043.3563> 05:17:08.9729 [OpentvZapper] next wake up due -1
    <322043.3571> 05:17:08.9738 [OpentvZapper] next wake up due -1
    <322043.4063> 05:17:09.0230 [OpentvZapper-Scheduler][Scheduleautostart] reason(1), session None
    <322043.4064> 05:17:09.0231 [OpentvZapper-Scheduler][Scheduleautostart] Stop
    <322043.4070> 05:17:09.0237 [XMLTVImport] autostart (1) occured at 1707628629.0236175
    <322043.4071> 05:17:09.0238 [XMLTVImport] Stop
    <322043.4075> 05:17:09.0242 [BouquetMakerXtream] autostart (1) occured at 2024-02-11 05:17:09
    <322043.4081> 05:17:09.0248 [AutoTimer] No changes in configuration, won't parse
    <322043.4155> 05:17:09.0322 [eDVBDB] ---- saving lame channel db
    <322043.4246> 05:17:09.0413 [eDVBDB] saved 70 channels and 899 services!
    <322043.4429> 05:17:09.0596 [eDVBResourceManager] release cached channel (timer timeout)
    <322043.4431> 05:17:09.0598 [Avahi] avahi_timeout_new
    <322043.4437> 05:17:09.0604 [Avahi] avahi_timeout_free
    <322043.4439> 05:17:09.0606 [Avahi] avahi_watch_free
    <322043.4444> 05:17:09.0611 [Avahi] avahi_timeout_update
    <322043.4445> 05:17:09.0612 [Avahi] avahi_timeout_free
    <322043.4946> 05:17:09.1112 [eEPGCache] store epg to realpath '/media/hdd/epg.dat'
    <322043.6584> 05:17:09.2751 [eEPGCache] 176071 events written to /media/hdd/epg.dat
    <322044.5250> 05:17:10.1417 [eDVBLocalTimeHandler] set RTC to previous valid time
    <322044.5257> 05:17:10.0000 [eInit] - (43) eServiceFactoryApp
    <322044.5260> 05:17:10.0003 [eInit] - (41) Stream server
    <322044.5262> 05:17:10.0005 [eInit] - (41) Encoders
    <322044.5264> 05:17:10.0007 [eInit] - (41) eServiceFactoryDVB
    <322044.5266> 05:17:10.0009 [eInit] - (41) eServiceFactoryFS
    <322044.5268> 05:17:10.0011 [eInit] - (41) eServiceFactoryMP3
    <322044.5271> 05:17:10.0014 [eInit] - (41) eServiceFactoryM2TS
    <322044.5273> 05:17:10.0016 [eInit] - (41) eServiceFactoryHDMI
    <322044.5275> 05:17:10.0018 [eInit] - (41) eServiceFactoryTS
    <322044.5277> 05:17:10.0020 [eInit] - (41) eServiceFactoryWebTS
    <322044.5279> 05:17:10.0022 [eInit] - (41) eServiceFactoryDVD
    <322044.5281> 05:17:10.0024 [eInit] - (40) eServiceCenter
    <322044.5283> 05:17:10.0026 [eInit] - (35) CA handler
    <322044.5286> 05:17:10.0029 [eInit] - (35) CI Slots
    <322044.5290> 05:17:10.0033 [eInit] - (30) eActionMap
    <322044.5293> 05:17:10.0036 [eInit] - (22) Hdmi CEC driver
    <322044.5295> 05:17:10.0038 [eInit] - (21) input device driver
    <322044.5840> 05:17:10.0583 [eInit] - (20) AVSwitch Driver
    <322044.5844> 05:17:10.0587 [eInit] - (20) misc options
    <322044.5847> 05:17:10.0590 [eInit] - (20) RC Input layer
    <322044.5849> 05:17:10.0592 [eInit] - (20) UHF Modulator
    <322044.5851> 05:17:10.0594 [eInit] - (20) DVB-CI UI
    <322044.5853> 05:17:10.0597 [eInit] - (15) eWindowStyleManager
    <322044.5856> 05:17:10.0599 [eInit] - (10) gRC
    <322044.5858> 05:17:10.0601 [gRC] waiting for gRC thread shutdown
    <322044.5860> 05:17:10.0603 [gRC] thread has finished
    <322044.5862> 05:17:10.0605 [eInit] - (9) Font Render Class
    <322044.5865> 05:17:10.0608 [eInit] - (9) gLCD
    <322044.5867> 05:17:10.0610 [eInit] - (9) GFBDC
    <322044.5882> 05:17:10.0625 [eInit] - (8) graphics acceleration manager
    <322044.5884> 05:17:10.0627 [eInit] - (5) Tuxtxt
    <322044.5887> 05:17:10.0630 [eInit] - (1) Background File Eraser
    <322044.5889> 05:17:10.0632 [eInit] reached rl -1
    [MAIN] executing main
    TuxTxt cache cleared
    cleaning up
    TuxTxt cache cleared

    enigma2 has exited
    ========== Enigma2 log ends ==========

    Thanks again for looking at it.

  5. #5
    twol's Avatar
    Title
    Moderator
    Join Date
    Apr 2012
    Posts
    8,618
    Thanks
    1,009
    Thanked 2,964 Times in 2,305 Posts
    Quote Originally Posted by ACWhitehouse View Post
    More of an annoyance than a serious problem, I have 3 SF8008 4K twin's which have been setup individually but all have the exact same trait

    OpenVix6.4.011
    Willobuild
    slyk-onyx-1080

    I have removed Autobouquetmaker system plugin from all boxes (I create my own bouquets and restore them with WilloBouquetManager) and have BBC1 setup as start service including standby, though it was just the same without a startup service selected.

    Every night after watching the boxes they are put into normal standby, every morning they have put themselves into deep standby but in a kind of limbo mode,
    pressing the power button on the remote wakes the boxes and they go through the normal waking process finishing with the front display showing 101 (BBC1) before displaying the time,
    but there is no display I either get a Blue screen or Openvix splash screen until I change channel?

    I have no timers running have disabled the Software update background check and I have tried disabling OpenTV EPG Downloader and EPG Importer, there are no crash logs only debug logs
    Would appreciate any ideas why my box does this every night?
    Have you setup the startup service
    Also you can attach the logs, much better than pasting extracts
    Gigablue Quad 4K & UE 4K
    .........FBC Tuners:
    ------------------> GT-Sat unicable LNB to 1.5M dish(28.2E)
    ------------------> Gigablue unicable LNB to 80 cm dish(19.2E)
    .......................
    Vu+ Uno4KSE, Dreambox dm900
    AX HD61, Edision Osmio 4K+, Zgemma H9Combo, Octagon SF8008 , gbtrio4k, h9se using unicable ports
    Zgemma H9 C/S into Giga4K

  6. #6

    Title
    Member
    Join Date
    Sep 2023
    Posts
    35
    Thanks
    7
    Thanked 2 Times in 2 Posts
    Quote Originally Posted by twol View Post
    Have you setup the startup service
    Also you can attach the logs, much better than pasting extracts
    Yes as per the 1st post I have BBC ch101 set as startup service and as from Deep standby
    Attached Files Attached Files

  7. #7
    Willo3092's Avatar
    Title
    ViX Beta Tester
    Join Date
    Oct 2016
    Location
    East Midlands
    Posts
    1,107
    Thanks
    769
    Thanked 412 Times in 309 Posts
    Try disabling the updater in cron timers.
    Willo
    #######################
    AX HD61 4K UHD Twin (test box)
    Vu+ Uno 4K SE
    Edision OS Mio 4K
    Zgemma H9 Twin
    Vu+ Solo 4K
    Vu+ Uno 4K
    GT-Sat GT-S3DCSS24 Unicable II LNB
    GT-Sat GT-dLNB1-DY Unicable II LNB
    #######################

  8. #8

    Title
    Member
    Join Date
    Sep 2023
    Posts
    35
    Thanks
    7
    Thanked 2 Times in 2 Posts
    Quote Originally Posted by Willo3092 View Post
    Try disabling the updater in cron timers.
    Thanks Willo, now for the silly question where do I access the 'Cron' timers? I've done a quick G00gle but not found it!

  9. #9
    Willo3092's Avatar
    Title
    ViX Beta Tester
    Join Date
    Oct 2016
    Location
    East Midlands
    Posts
    1,107
    Thanks
    769
    Thanked 412 Times in 309 Posts
    MENU > TIMERS

    Press blue button to show hidden items > Highlight Cron Timers and press yellow to show and then Green to save.

    I think it is the bottom cron job. Just highlight it and press red to delete.

    I would restart GUI afterwards.

    Can you use the support thread on the other forum for Willobuild please.
    9 times out of 10 the problem will be down to me.
    Willo
    #######################
    AX HD61 4K UHD Twin (test box)
    Vu+ Uno 4K SE
    Edision OS Mio 4K
    Zgemma H9 Twin
    Vu+ Solo 4K
    Vu+ Uno 4K
    GT-Sat GT-S3DCSS24 Unicable II LNB
    GT-Sat GT-dLNB1-DY Unicable II LNB
    #######################

  10. #10

    Title
    Member
    Join Date
    Sep 2023
    Posts
    35
    Thanks
    7
    Thanked 2 Times in 2 Posts
    Thanks Willo, done- see what happens tomorrow 😊.
    What will I not be getting with this deleted, though I don't think it has ever worked on my installs!

    P. S thought it was going to be an Octogon issue, my Zgemma's had no problem.

  11. #11
    Willo3092's Avatar
    Title
    ViX Beta Tester
    Join Date
    Oct 2016
    Location
    East Midlands
    Posts
    1,107
    Thanks
    769
    Thanked 412 Times in 309 Posts
    It installs updates in the early hours of the morning, reboots and then puts the box into standby. (or should)
    I was going to bin it anyway, there's a plugin to update.
    Willo
    #######################
    AX HD61 4K UHD Twin (test box)
    Vu+ Uno 4K SE
    Edision OS Mio 4K
    Zgemma H9 Twin
    Vu+ Solo 4K
    Vu+ Uno 4K
    GT-Sat GT-S3DCSS24 Unicable II LNB
    GT-Sat GT-dLNB1-DY Unicable II LNB
    #######################

  12. The Following User Says Thank You to Willo3092 For This Useful Post:

    ACWhitehouse (11-02-24)

  13. #12

    Title
    Member
    Join Date
    Sep 2023
    Posts
    35
    Thanks
    7
    Thanked 2 Times in 2 Posts
    Thank's once again Willo for the work you've done and the assistance that you give, very much appreciated��

  14. The Following User Says Thank You to ACWhitehouse For This Useful Post:

    Willo3092 (11-02-24)

  15. #13
    Huevos's Avatar
    Title
    Administrator
    Join Date
    Jun 2010
    Location
    38.5N, 0.5W
    Posts
    13,945
    Thanks
    2,062
    Thanked 5,145 Times in 3,395 Posts
    Is this using a unicable lnb?
    Help keep OpenViX servers online.Please donate!

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
This website uses cookies
We use cookies to store session information to facilitate remembering your login information, to allow you to save website preferences, to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners.