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.

View Entry Info: Can't reach feeds with 6.4, works with 6.3

Category:
Possible Bug
What ViX Image build number are you using?
Please provide your ViX Team image build number. Menu > Information > About > Build number > ENTER THIS NUMBER e.g. 4.2.028
6.4.007
Have you tried a flash WITHOUT settings restore?
Have you tried this? PLEASE SELECT YES OR NO.
Yes
Have you tried a flash WITH settings restore?
Have you tried this? PLEASE SELECT YES OR NO.
Yes
Attachments
Page 2 of 2 FirstFirst 12
Results 16 to 24 of 24

Thread: Can't reach feeds with 6.4, works with 6.3

  1. #16

    Title
    Junior Member
    Join Date
    Sep 2017
    Posts
    22
    Thanks
    1
    Thanked 1 Time in 1 Post
    Does the debug log survive a change of boot image? I only get the "cannot connect to network" message the first time 6.4 boots so if I have to boot into 6.4 to enable the debug log it will already be too late to catch that one.

  2. #17
    twol's Avatar
    Title
    Moderator
    Join Date
    Apr 2012
    Posts
    8,423
    Thanks
    997
    Thanked 2,895 Times in 2,248 Posts
    Quote Originally Posted by peterthevicar View Post
    Does the debug log survive a change of boot image? I only get the "cannot connect to network" message the first time 6.4 boots so if I have to boot into 6.4 to enable the debug log it will already be too late to catch that one.
    Well, if you backup your settings and then online flash and restore settings ….Yes
    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)
    .......................> FBC & DVB-S2X into 90cm dish (27.5W) Opticum robust Unicable LNB
    AX HD61, Edision Osmio 4K+, Zgemma H9Combo, Octagon SF8008 , gbtrio4k, h9se using unicable ports
    Zgemma H9 C/S into Giga4K

  3. #18

    Title
    Junior Member
    Join Date
    Sep 2017
    Posts
    22
    Thanks
    1
    Thanked 1 Time in 1 Post
    Excellent, that's tonight's project then!

  4. #19

    Title
    Junior Member
    Join Date
    Sep 2017
    Posts
    22
    Thanks
    1
    Thanked 1 Time in 1 Post
    Rather frustrating. With the logs enabled I went to Setup/Plugins/Download Plugins. It showed a green traffic light and said the feeds were stable. It then did its delay spinner thing for a while and finally came up with the message on the TV,
    Sorry the feeds are down for maintenance
    Sadly the debug log looks exactly the same as when I did the same thing in 6.3 (bar a couple of minor name changes in the [Skin] list). Here's the bit from the failed run in 6.4:
    Code:
    <   611.8796> 23:24:45.5305 [InfoBarGenerics] Key: 399 (Break) KeyID='KEY_GREEN' Binding='('GREEN',)'.
    <   611.8798> 23:24:45.5306 [ActionMap] Keymap 'ColorActions' -> Action = 'green'.
    <   611.8806> 23:24:45.5315 [About] ifreq:  {'ifname': 'eth0', 'addr': '192.168.0.20', 'brdaddr': '0.0.0.0', 'hwaddr': '18:99:F5:F2:2B:8A', 'netmask': '255.255.255.0'}
    <   611.8807> 23:24:45.5315 [OnlineUpdateCheck][adapterAvailable] PASSED
    <   611.8964> 23:24:45.5473 [OnlineUpdateCheck][NetworkUp] PASSED
    <   615.4657> 23:24:49.1166 [gRC] main thread is non-idle! display spinner!
    <   617.0693> 23:24:50.7202 [OnlineUpdateCheck][kernelMismatch] no kernel mismatch found
    <   617.0733> 23:24:50.7242 [Skin] Processing screen 'PluginDownloadBrowser', position=(0, 0), size=(1920 x 1080) for module 'PluginDownloadBrowser'.
    <   617.0815> 23:24:50.7323 [About] ifreq:  {'ifname': 'eth0', 'addr': '192.168.0.20', 'brdaddr': '0.0.0.0', 'hwaddr': '18:99:F5:F2:2B:8A', 'netmask': '255.255.255.0'}
    <   617.0816> 23:24:50.7324 [OnlineUpdateCheck][adapterAvailable] PASSED
    <   617.0988> 23:24:50.7497 [OnlineUpdateCheck][NetworkUp] PASSED
    <   617.0991> 23:24:50.7499 [OnlineUpdateCheck][getFeedStatus] checking feeds state
    <   619.1382> 23:24:52.7890 [gRC] main thread is non-idle! display spinner!
    <   622.1604> 23:24:55.8112 trafficLight stable
    <   622.1608> 23:24:55.8117 [OnlineUpdateCheck][getFeedsBool] stable
    <   622.1609> 23:24:55.8119 [eConsoleAppContainer] Starting /bin/sh
    <   622.1636> 23:24:55.8144 [Skin] Processing screen 'PluginBrowserSummary' from list 'PluginDownloadBrowser_summary, PluginBrowserSummary, SimpleSummary', position=(0, 0), size=(132 x 64) for module 'PluginBrowserSummary'.
    <   672.2855> 23:25:45.9364 [eConsoleAppContainer] Starting /bin/sh
    <   672.3929> 23:25:46.0437 [eConsoleAppContainer] Starting /bin/sh
    Here's the log from the (successful) run on 6.3 which is nearly identical:
    Code:
    <   251.4243> 23:33:12.0258 [InfoBarGenerics] Key: 399 (Break) KeyID='KEY_GREEN' Binding='('GREEN',)'.
    <   251.4248> 23:33:12.0263 [ActionMap] Keymap 'ColorActions' -> Action = 'green'.
    <   251.4258> 23:33:12.0273 [About] ifreq:  {'ifname': 'eth0', 'addr': '192.168.0.20', 'brdaddr': '0.0.0.0', 'hwaddr': '18:99:F5:F2:2B:8A', 'netmask': '255.255.255.0'}
    <   251.4267> 23:33:12.0281 [OnlineUpdateCheck][adapterAvailable] PASSED
    <   251.4444> 23:33:12.0458 [OnlineUpdateCheck][NetworkUp] PASSED
    <   254.2904> 23:33:14.8918 [gRC] main thread is non-idle! display spinner!
    <   256.6182> 23:33:17.2197 [OnlineUpdateCheck][kernelMismatch] no kernel mismatch found
    <   256.6219> 23:33:17.2233 [Skin] Processing screen 'PluginDownloadBrowser', position=(0, 0), size=(1920 x 1080) for module 'PluginDownloadBrowser'.
    <   256.6303> 23:33:17.2318 [About] ifreq:  {'ifname': 'eth0', 'addr': '192.168.0.20', 'brdaddr': '0.0.0.0', 'hwaddr': '18:99:F5:F2:2B:8A', 'netmask': '255.255.255.0'}
    <   256.6309> 23:33:17.2324 [OnlineUpdateCheck][adapterAvailable] PASSED
    <   256.6458> 23:33:17.2472 [OnlineUpdateCheck][NetworkUp] PASSED
    <   256.6463> 23:33:17.2478 [OnlineUpdateCheck][getFeedStatus] checking feeds state
    <   258.6861> 23:33:19.2876 [gRC] main thread is non-idle! display spinner!
    <   261.7093> 23:33:22.3108 trafficLight stable
    <   261.7101> 23:33:22.3116 [OnlineUpdateCheck][getFeedsBool] stable
    <   261.7105> 23:33:22.3120 [eConsoleAppContainer] Starting /bin/sh
    <   261.7123> 23:33:22.3138 [Skin] Processing screen 'PluginBrowserSummary' from list 'PluginDownloadBrowserSummary, PluginDownloadBrowser_summary, PluginBrowserSummary, SimpleSummary, ScreenSummary', position=(0, 0), size=(132 x 64) for module 'PluginBrowserSummary'.
    <   313.6097> 23:34:14.2112 [eConsoleAppContainer] Starting /bin/sh
    <   313.7276> 23:34:14.3290 [eConsoleAppContainer] Starting /bin/sh
    I've attached the full log from 6.4 in case there's something earlier on that is interesting (apart from an insight into my family's taste in TV!)

    Not sure what to try next so any suggestions gratefully received.
    Attached Files Attached Files
    Last edited by peterthevicar; 05-10-23 at 00:06.

  5. #20
    birdman's Avatar
    Title
    Moderator
    Join Date
    Sep 2014
    Location
    Hitchin, UK
    Posts
    7,800
    Thanks
    237
    Thanked 1,659 Times in 1,307 Posts
    Well, the broadcast address is wrong (it should be 192.168.0.255), but I doubt that's an issue.
    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

  6. #21
    twol's Avatar
    Title
    Moderator
    Join Date
    Apr 2012
    Posts
    8,423
    Thanks
    997
    Thanked 2,895 Times in 2,248 Posts
    Quote Originally Posted by peterthevicar View Post
    Rather frustrating. With the logs enabled I went to Setup/Plugins/Download Plugins. It showed a green traffic light and said the feeds were stable. It then did its delay spinner thing for a while and finally came up with the message on the TV,

    Sadly the debug log looks exactly the same as when I did the same thing in 6.3 (bar a couple of minor name changes in the [Skin] list). Here's the bit from the failed run in 6.4:
    Code:
    <   611.8796> 23:24:45.5305 [InfoBarGenerics] Key: 399 (Break) KeyID='KEY_GREEN' Binding='('GREEN',)'.
    <   611.8798> 23:24:45.5306 [ActionMap] Keymap 'ColorActions' -> Action = 'green'.
    <   611.8806> 23:24:45.5315 [About] ifreq:  {'ifname': 'eth0', 'addr': '192.168.0.20', 'brdaddr': '0.0.0.0', 'hwaddr': '18:99:F5:F2:2B:8A', 'netmask': '255.255.255.0'}
    <   611.8807> 23:24:45.5315 [OnlineUpdateCheck][adapterAvailable] PASSED
    <   611.8964> 23:24:45.5473 [OnlineUpdateCheck][NetworkUp] PASSED
    <   615.4657> 23:24:49.1166 [gRC] main thread is non-idle! display spinner!
    <   617.0693> 23:24:50.7202 [OnlineUpdateCheck][kernelMismatch] no kernel mismatch found
    <   617.0733> 23:24:50.7242 [Skin] Processing screen 'PluginDownloadBrowser', position=(0, 0), size=(1920 x 1080) for module 'PluginDownloadBrowser'.
    <   617.0815> 23:24:50.7323 [About] ifreq:  {'ifname': 'eth0', 'addr': '192.168.0.20', 'brdaddr': '0.0.0.0', 'hwaddr': '18:99:F5:F2:2B:8A', 'netmask': '255.255.255.0'}
    <   617.0816> 23:24:50.7324 [OnlineUpdateCheck][adapterAvailable] PASSED
    <   617.0988> 23:24:50.7497 [OnlineUpdateCheck][NetworkUp] PASSED
    <   617.0991> 23:24:50.7499 [OnlineUpdateCheck][getFeedStatus] checking feeds state
    <   619.1382> 23:24:52.7890 [gRC] main thread is non-idle! display spinner!
    <   622.1604> 23:24:55.8112 trafficLight stable
    <   622.1608> 23:24:55.8117 [OnlineUpdateCheck][getFeedsBool] stable
    <   622.1609> 23:24:55.8119 [eConsoleAppContainer] Starting /bin/sh
    <   622.1636> 23:24:55.8144 [Skin] Processing screen 'PluginBrowserSummary' from list 'PluginDownloadBrowser_summary, PluginBrowserSummary, SimpleSummary', position=(0, 0), size=(132 x 64) for module 'PluginBrowserSummary'.
    <   672.2855> 23:25:45.9364 [eConsoleAppContainer] Starting /bin/sh
    <   672.3929> 23:25:46.0437 [eConsoleAppContainer] Starting /bin/sh
    Here's the log from the (successful) run on 6.3 which is nearly identical:
    Code:
    <   251.4243> 23:33:12.0258 [InfoBarGenerics] Key: 399 (Break) KeyID='KEY_GREEN' Binding='('GREEN',)'.
    <   251.4248> 23:33:12.0263 [ActionMap] Keymap 'ColorActions' -> Action = 'green'.
    <   251.4258> 23:33:12.0273 [About] ifreq:  {'ifname': 'eth0', 'addr': '192.168.0.20', 'brdaddr': '0.0.0.0', 'hwaddr': '18:99:F5:F2:2B:8A', 'netmask': '255.255.255.0'}
    <   251.4267> 23:33:12.0281 [OnlineUpdateCheck][adapterAvailable] PASSED
    <   251.4444> 23:33:12.0458 [OnlineUpdateCheck][NetworkUp] PASSED
    <   254.2904> 23:33:14.8918 [gRC] main thread is non-idle! display spinner!
    <   256.6182> 23:33:17.2197 [OnlineUpdateCheck][kernelMismatch] no kernel mismatch found
    <   256.6219> 23:33:17.2233 [Skin] Processing screen 'PluginDownloadBrowser', position=(0, 0), size=(1920 x 1080) for module 'PluginDownloadBrowser'.
    <   256.6303> 23:33:17.2318 [About] ifreq:  {'ifname': 'eth0', 'addr': '192.168.0.20', 'brdaddr': '0.0.0.0', 'hwaddr': '18:99:F5:F2:2B:8A', 'netmask': '255.255.255.0'}
    <   256.6309> 23:33:17.2324 [OnlineUpdateCheck][adapterAvailable] PASSED
    <   256.6458> 23:33:17.2472 [OnlineUpdateCheck][NetworkUp] PASSED
    <   256.6463> 23:33:17.2478 [OnlineUpdateCheck][getFeedStatus] checking feeds state
    <   258.6861> 23:33:19.2876 [gRC] main thread is non-idle! display spinner!
    <   261.7093> 23:33:22.3108 trafficLight stable
    <   261.7101> 23:33:22.3116 [OnlineUpdateCheck][getFeedsBool] stable
    <   261.7105> 23:33:22.3120 [eConsoleAppContainer] Starting /bin/sh
    <   261.7123> 23:33:22.3138 [Skin] Processing screen 'PluginBrowserSummary' from list 'PluginDownloadBrowserSummary, PluginDownloadBrowser_summary, PluginBrowserSummary, SimpleSummary, ScreenSummary', position=(0, 0), size=(132 x 64) for module 'PluginBrowserSummary'.
    <   313.6097> 23:34:14.2112 [eConsoleAppContainer] Starting /bin/sh
    <   313.7276> 23:34:14.3290 [eConsoleAppContainer] Starting /bin/sh
    I've attached the full log from 6.4 in case there's something earlier on that is interesting (apart from an insight into my family's taste in TV!)

    Not sure what to try next so any suggestions gratefully received.
    so what happened after ...OnlineUpdateCheck][getFeedsBool] stable ?? can we see rest of log?
    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)
    .......................> FBC & DVB-S2X into 90cm dish (27.5W) Opticum robust Unicable LNB
    AX HD61, Edision Osmio 4K+, Zgemma H9Combo, Octagon SF8008 , gbtrio4k, h9se using unicable ports
    Zgemma H9 C/S into Giga4K

  7. #22

    Title
    Junior Member
    Join Date
    Sep 2017
    Posts
    22
    Thanks
    1
    Thanked 1 Time in 1 Post
    Quote Originally Posted by twol View Post
    so what happened after ...OnlineUpdateCheck][getFeedsBool] stable ?? can we see rest of log?
    That was the end of the log. I also attached the whole uncut log if that's useful but it ends at the same place.

  8. #23
    twol's Avatar
    Title
    Moderator
    Join Date
    Apr 2012
    Posts
    8,423
    Thanks
    997
    Thanked 2,895 Times in 2,248 Posts
    Quote Originally Posted by peterthevicar View Post
    That was the end of the log. I also attached the whole uncut log if that's useful but it ends at the same place.
    So the image stopped? i don,t see anything about not being able to access the feeds
    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)
    .......................> FBC & DVB-S2X into 90cm dish (27.5W) Opticum robust Unicable LNB
    AX HD61, Edision Osmio 4K+, Zgemma H9Combo, Octagon SF8008 , gbtrio4k, h9se using unicable ports
    Zgemma H9 C/S into Giga4K

  9. #24

    Title
    Junior Member
    Join Date
    Sep 2017
    Posts
    22
    Thanks
    1
    Thanked 1 Time in 1 Post
    Quote Originally Posted by twol View Post
    So the image stopped? i don,t see anything about not being able to access the feeds
    I was surprised that it didn't show the failure. Maybe "feeds down for maintenance" isn't considered worth logging. Is there a way to increase the detail in the logs?

Page 2 of 2 FirstFirst 12

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.