Jump to content


Photo

Lost Webif after reboot Vu+ Duo2

Vu+ Duo2 Webif Issue

  • Please log in to reply
26 replies to this topic

#1 SpliNT

  • Member
  • 10 posts

0
Neutral

Posted 24 November 2015 - 09:05

I ran into a problem yesterday.

 

After a reboot of the Vu+Duo2 (OpenPli 4) Webif got inaccessible. Everything else, OScam, FTP, telnet etc. seems to running fine.

I have custom ports on everything, webif, telnet, ssh, ftp and is behind NAT.

 

The thing is that the box is placed on a remote location (an island in fact) so I have no physical access to it. Therefore Webif is essential. 

I have a PC in the local network of the box so I can reach it from inside if needed.  

 

 

I have tried the following without any success:

opkg update
opkg upgrade
root@vuduo2:~# opkg remove —force-depends enigma2-plugin-extensions-openwebif
Removing package enigma2-plugin-extensions-openwebif from root...
root@vuduo2:~# opkg install enigma2-plugin-extensions-openwebif
Installing enigma2-plugin-extensions-openwebif (1+git1332+3f47ff8-r0.1) on root.
Downloading http://downloads.pli-images.org/feeds/openpli-4/vuduo2/enigma2-plugin-extensions-openwebif_1+git1332+3f47ff8-r0.1_vuduo2.ipk.
Configuring enigma2-plugin-extensions-openwebif.
root@vuduo2:~#

I'm stuck, not sure how to proceed.

 

If you'd like to see logs I can pull them out for you, just tell me where.

 

Thanks in advance!

 

 



Re: Lost Webif after reboot Vu+ Duo2 #2 goldeneye

  • Senior Member
  • 1,031 posts

+14
Neutral

Posted 24 November 2015 - 10:25

Difficult to say. OpenWebIf normally presents itself on port 80. If all other functions work perfectly on the given IP and ports you might consider 2 things:

 

1. Port 80 on router has been closed for outside access.

2. OpenWebIf is at fault..

 

In any case: opening up your STB without stringent protection is asking for trouble. At least use a VPN connection and strong passwords. STB's are not designed for internet access. They lack the necessary protection....



Re: Lost Webif after reboot Vu+ Duo2 #3 SpliNT

  • Member
  • 10 posts

0
Neutral

Posted 24 November 2015 - 11:01

Yes, that's about the conclusion i drew myself. I doubt this is a port problem since I get the same results in the local network where the box is situated. 

I get no luck on neither the custom port or port 80. If OpenWebif is at fault, is there no way of rebuilding it from telnet? 

 

It is like its refusing connections. 

 

Is really a flash the only way? 


Edited by SpliNT, 24 November 2015 - 11:05.


Re: Lost Webif after reboot Vu+ Duo2 #4 goldeneye

  • Senior Member
  • 1,031 posts

+14
Neutral

Posted 24 November 2015 - 13:04

The only thing you can do is simply visit the location and check the internet connection. Maybe the router needs a 'kick in the butt'. If you have remote access to the router you may want to check things first...

Best guess now (and it really is a guess/assumption) is that your box has been compromised. So yes.. Flashing is the best thing to do.. Set up a VPN connection to the box and secure the connection... As stated earlier, STB's are NOT designed to advertise themselves over the internet however convenient this might look... In fact, there is no need to unless one wants to engage in illegal activities...



Re: Lost Webif after reboot Vu+ Duo2 #5 WanWizard

  • Forum Moderator
    PLi® Core member
  • 50,216 posts

+905
Excellent

Posted 24 November 2015 - 13:05

If you can telnet into the box, type

netstat -lnp | grep :80

You should get this back:

tcp        0      0 :::80                   :::*                    LISTEN      503/enigma2

If not, then the webserver that is part of Enigma isn't running. As far as I can see there have not been any recent changes to the webif, git1332+3f47ff8 is the latest commit, three days ago.


Currently in use: VU+Duo 4K (2xFBC S2), Amiko Viper T2C (T2), SAB Alpha Triple HD (S2+T2), Zgemma H3.T2C (T/C), Zgemma H6 (fallback), VU+Zero (fallback)

Many answers to your question can be found in our new and improved wiki.

note: I do not provide support via PM !

 


Re: Lost Webif after reboot Vu+ Duo2 #6 SpliNT

  • Member
  • 10 posts

0
Neutral

Posted 24 November 2015 - 13:16

Wanwizard: Seems like you're onto something here.
root@vuduo2:~# netstat -lnp | grep :80
tcp        0      0 :::8002                 :::*                    LISTEN      496/streamproxy
tcp        0      0 :::8003                 :::*                    LISTEN      496/streamproxy
root@vuduo2:~# 

Is there anyway to start the webserver from telnet?



Re: Lost Webif after reboot Vu+ Duo2 #7 SpliNT

  • Member
  • 10 posts

0
Neutral

Posted 24 November 2015 - 13:37

I tried going to 192.168.x.x:8002 in the browser and I do get to a page with system info.

 

So.. the webserver seems to work..



Re: Lost Webif after reboot Vu+ Duo2 #8 WanWizard

  • Forum Moderator
    PLi® Core member
  • 50,216 posts

+905
Excellent

Posted 24 November 2015 - 13:39

The webserver component is a python plugin.

 

Can you stop enigma using the "init 4" command, and than start it manually using "/usr/bin/enigma2". It should that log it's output to the terminal. If you can capture that and see if you see any webif related messages?

 

When you're done you can start enigma again using "init 3".

 

edit: the other ports are serviced by a different component, so that doesn't say anything.


Currently in use: VU+Duo 4K (2xFBC S2), Amiko Viper T2C (T2), SAB Alpha Triple HD (S2+T2), Zgemma H3.T2C (T/C), Zgemma H6 (fallback), VU+Zero (fallback)

Many answers to your question can be found in our new and improved wiki.

note: I do not provide support via PM !

 


Re: Lost Webif after reboot Vu+ Duo2 #9 SpliNT

  • Member
  • 10 posts

0
Neutral

Posted 24 November 2015 - 13:56

Done. Couldn't find any webif related messages. Pasted the output here in case I missed something. 
root@vuduo2:~# /usr/bin/enigma2
PYTHONPATH: /usr/lib/enigma2/python
DVB_API_VERSION 5 DVB_API_VERSION_MINOR 10
< 37531.613562> [eInit] + (1) Background File Eraser
< 37531.614272> [eInit] + (5) Tuxtxt
< 37531.614507> [eInit] + (8) graphics acceleration manager
< 37531.614836> [eInit] + (9) GFBDC
< 37531.615169> [fb] 21600k video mem
< 37531.615794> [fb] double buffering available!
< 37531.625368> [gFBDC] resolution: 2d0x576x32 stride=7680, 12960kB available for acceleration surfaces.
< 37531.625685> [eInit] + (9) gLCD
< 37531.625863> [eFbLCD] /dev/fb1: No such file or directory
< 37531.625977> [eFbLCD] framebuffer not available
< 37531.626594> [eDboxLCD] xres=140, yres=32, bpp=8 lcd_type=3
< 37531.626755> [eLCD] (140x32x8) buffer 0x7cf7e8 4480 bytes, stride 140
< 37531.626834> [gLCDDC] resolution: 140x32x8 stride=140
< 37531.626908> [eInit] + (9) Font Render Class
< 37531.626993> [FONT] initializing lib...
< 37531.627473> [FONT] loading fonts...
< 37531.627612> [FONT] Intializing font cache, using max. 4MB...
< 37531.627849> [eInit] + (10) gRC
< 37531.628670> [gRC] thread created successfully
< 37531.628800> [eInit] + (15) eWindowStyleManager
< 37531.628903> [eInit] + (20) DVB-CI UI
< 37531.628974> [eInit] + (20) UHF Modulator
< 37531.629135> [eRFmod] couldnt open /dev/rfmod0: No such file or directory
< 37531.629227> [eInit] + (20) RC Input layer
< 37531.629300> [eInit] + (20) misc options
< 37531.629354> [eInit] + (20) AVSwitch Driver
< 37531.629436> [eAVSwitch] failed to open /dev/dbox/fp0 to monitor vcr scart slow blanking changed: No such file or directory
< 37531.629523> [eInit] + (21) input device driver
< 37531.629804> [eRCInputEventDriver] devicename=dreambox advanced remote control (native)
< 37531.629912> [eRCDeviceInputDev] device "dreambox advanced remote control (native)" is a remotecontrol
< 37531.630163> [eInputDeviceInit] Found 1 input devices.
< 37531.630250> [eInit] + (22) Hdmi CEC driver
< 37531.630574> [eInit] + (30) eActionMap
< 37531.630702> [eInit] + (35) CI Slots
< 37531.631343> [CI] scanning for common interfaces..
< 37531.632489> [CI] Slot 0 setSource(0)
< 37531.633415> [CI] Slot 1 setSource(0)
< 37531.634401> [CI] eDVBCIInterfaces->setInputSource(0, 0)
< 37531.635068> [CI] eDVBCIInterfaces->setInputSource(1, 1)
< 37531.635807> [CI] eDVBCIInterfaces->setInputSource(2, 2)
< 37531.636480> [CI] eDVBCIInterfaces->setInputSource(3, 3)
< 37531.636631> [CI] done, found 2 common interface slots
< 37531.636700> [eInit] + (35) CA handler
< 37531.636947> [eInit] + (40) eServiceCenter
< 37531.637123> [eServiceCenter] settings instance.
< 37531.637202> [eInit] + (41) eServiceFactoryDVD
< 37531.637314> [eInit] + (41) eServiceFactoryHDMI
< 37531.637390> [eInit] + (41) eServiceFactoryM2TS
< 37531.637611> [eInit] + (41) eServiceFactoryMP3
< 37531.637800> [eInit] + (41) eServiceFactoryFS
< 37531.637887> [eInit] + (41) eServiceFactoryDVB
< 37531.637991> [eInit] + (41) Encoders
< 37531.638239> [eInit] + (41) Stream server
< 37531.639078> [eInit] reached rl 70
< 37531.639249> [eDVBDB] ---- opening lame channel db
< 37531.639418> [eDVBDB] reading services (version 4)
< 37531.689121> [eDVBDB] loaded 104 channels/transponders and 1469 services
< 37531.689452> [eDVBResourceManager] scanning for frontends..
< 37531.689699> [eDVBFrontend] opening frontend 0
< 37531.723053> [eDVBFrontend] close frontend 0
< 37531.757254> [eDVBFrontend] opening frontend 1
< 37531.805098> [eDVBFrontend] close frontend 1
< 37531.838223> [eDVBFrontend] opening frontend 2
< 37531.886065> [eDVBFrontend] close frontend 2
< 37531.919252> [eDVBFrontend] opening frontend 3
< 37531.967060> [eDVBFrontend] close frontend 3
< 37532.000386> [eDVBAdapterLinux] get demux 0
< 37532.000502> [eDVBAdapterLinux] get demux 1
< 37532.000611> [eDVBAdapterLinux] get demux 2
< 37532.000690> [eDVBAdapterLinux] get demux 3
< 37532.000753> [eDVBAdapterLinux] get demux 4
< 37532.000812> [eDVBAdapterLinux] get demux 5
< 37532.000866> [eDVBAdapterLinux] get demux 6
< 37532.000917> [eDVBAdapterLinux] get demux 7
< 37532.000971> [eDVBAdapterLinux] get demux 8
< 37532.001145> [eDVBResourceManager] found 1 adapter, 4 frontends(4 sim) and 9 demux
< 37532.001352> [eDVBLocalTimeHandler] RTC not ready... wait for transponder time
< 37532.001516> [eEPGCache] Initialized EPGCache (wait for setCacheFile call now)
< 37532.002736> [MAIN] Loading spinners...
< 37532.007576> [ePNG] couldn't open /usr/share/enigma2/skin_default/spinner/wait8.png
< 37532.007668> [MAIN] found 7 spinner!

[MAIN] executing main
< 37532.008100> [setIoPrio] best-effort level 3 ok
< 37532.215383> [eDVBFrontend] Failed to open /dev/dbox/fp0
< 37532.215704> [Misc_Options] 12Vdetect cannot open /proc/stb/misc/12V_output: No such file or directory
[HardwareInfo] Scanning hardware info
Detected: vuduo2 (1500A0)
[Harddisk] enumerating block devices...
new Harddisk sda -> /dev/sda -> /dev/sda
[ePopen] command: ('hdparm', 'hdparm', '-S0', '/dev/sda')
< 37532.236538> [eConsoleAppContainer] Starting hdparm
new Harddisk sdb -> /dev/sdb -> /dev/sdb
Reading satellites.xml
removing internal link on frontend id 1
removing internal link on frontend id 2
removing internal link on frontend id 3
sec config cleared
< 37533.329244> [eDVBFrontend] setSlotInfo for dvb frontend 0 to slotid 0, descr Vuplus DVB-S NIM(AVL6222), need rotorworkaround No, enabled Yes, DVB-S2 Yes
< 37533.329428> [eDVBFrontend] setSlotInfo for dvb frontend 1 to slotid 1, descr Vuplus DVB-S NIM(AVL6222), need rotorworkaround No, enabled Yes, DVB-S2 Yes
< 37533.329525> [eDVBFrontend] setSlotInfo for dvb frontend 2 to slotid 2, descr Vuplus DVB-S NIM(AVL6222), need rotorworkaround No, enabled Yes, DVB-S2 Yes
< 37533.329615> [eDVBFrontend] setSlotInfo for dvb frontend 3 to slotid 3, descr Vuplus DVB-S NIM(AVL6222), need rotorworkaround No, enabled Yes, DVB-S2 Yes
slot: 0 configmode: advanced
add 3592 to 1
slot: 1 configmode: equal
slot: 2 configmode: advanced
add 48 to 1
add 192 to 1
slot: 3 configmode: equal
sec config completed
[Picon] adding path: /usr/share/enigma2/picon/
[Picon] adding path: /media/BREAKOUT/picon/
< 37534.021994> [eDVBDB] loading bouquet... /etc/enigma2//bouquets.tv
< 37534.022602> [eDVBDB] loading bouquet... /etc/enigma2//userbouquet.favourites.tv
< 37534.023329> [eDVBDB] 40 entries in Bouquet userbouquet.favourites.tv
< 37534.024109> [eDVBDB] loading bouquet... /etc/enigma2//userbouquet.808cf.tv
< 37534.024495> [eDVBDB] 11 entries in Bouquet userbouquet.808cf.tv
< 37534.024916> [eDVBDB] loading bouquet... /etc/enigma2//userbouquet.fcad7.tv
< 37534.025730> [eDVBDB] 49 entries in Bouquet userbouquet.fcad7.tv
< 37534.026141> [eDVBDB] loading bouquet... /etc/enigma2//userbouquet.4032f.tv
< 37534.026740> [eDVBDB] 37 entries in Bouquet userbouquet.4032f.tv
< 37534.027227> [eDVBDB] loading bouquet... /etc/enigma2//userbouquet.b88c9.tv
< 37534.037184> [eDVBDB] 951 entries in Bouquet userbouquet.b88c9.tv
< 37534.037576> [eDVBDB] loading bouquet... /etc/enigma2//userbouquet.31a78.tv
< 37534.050915> [eDVBDB] 1319 entries in Bouquet userbouquet.31a78.tv
< 37534.051320> [eDVBDB] loading bouquet... /etc/enigma2//userbouquet.LastScanned.tv
< 37534.061397> [eDVBDB] 970 entries in Bouquet userbouquet.LastScanned.tv
< 37534.061594> [eDVBDB] 7 entries in Bouquet bouquets.tv
< 37534.062179> [eDVBDB] loading bouquet... /etc/enigma2//bouquets.radio
< 37534.062512> [eDVBDB] loading bouquet... /etc/enigma2//userbouquet.favourites.radio
< 37534.062753> [eDVBDB] 3 entries in Bouquet userbouquet.favourites.radio
< 37534.062921> [eDVBDB] 1 entries in Bouquet bouquets.radio
< 37534.063135> [eDVBDB] Renumbering...
Traceback (most recent call last):
  File "/usr/lib/enigma2/python/mytest.py", line 53, in <module>
    config.misc.prev_wakeup_time = ConfigInteger(default=0)
  File "/usr/lib/enigma2/python/Components/config.py", line 1576, in __setattr__
  File "/usr/lib/enigma2/python/Components/config.py", line 80, in load
  File "/usr/lib/enigma2/python/Components/config.py", line 794, in fromstring
ValueError: invalid literal for int() with base 10: '1448265935.02'
< 37534.084302> [eDVBDB] ---- saving lame channel db
< 37534.134225> [eDVBDB] saved 104 channels and 1469 services!
< 37534.137377> [eDVBResourceManager] release cached channel (timer timeout)
< 37534.142400> [eInit] - (41) eServiceFactoryDVD
< 37534.142896> [eInit] - (41) eServiceFactoryHDMI
< 37534.143088> [eInit] - (41) eServiceFactoryM2TS
< 37534.143190> [eInit] - (41) eServiceFactoryMP3
< 37534.143259> [eInit] - (41) eServiceFactoryFS
< 37534.143326> [eInit] - (41) eServiceFactoryDVB
< 37534.143393> [eInit] - (41) Encoders
< 37534.143825> [eInit] - (41) Stream server
< 37534.144059> [eInit] - (40) eServiceCenter
< 37534.144228> [eServiceCenter] clear instance
< 37534.144364> [eInit] - (35) CI Slots
< 37534.144526> [eInit] - (35) CA handler
< 37534.144699> [eInit] - (30) eActionMap
< 37534.144797> [eInit] - (22) Hdmi CEC driver
< 37534.144893> [eInit] - (21) input device driver
< 37534.169128> [eInit] - (20) DVB-CI UI
< 37534.169312> [eInit] - (20) UHF Modulator
< 37534.169404> [eInit] - (20) RC Input layer
< 37534.169478> [eInit] - (20) misc options
< 37534.169548> [eInit] - (20) AVSwitch Driver
< 37534.169613> [eInit] - (15) eWindowStyleManager
< 37534.169685> [eInit] - (10) gRC
< 37534.170124> [gRC] waiting for gRC thread shutdown
< 37534.170830> [gRC] thread has finished
< 37534.171077> [eInit] - (9) GFBDC
< 37534.171886> [eInit] - (9) gLCD
< 37534.172163> [eInit] - (9) Font Render Class
< 37534.172276> [eInit] - (8) graphics acceleration manager
< 37534.172365> [eInit] - (5) Tuxtxt
< 37534.172500> [eInit] - (1) Background File Eraser
< 37534.172705> [eInit] reached rl -1



Re: Lost Webif after reboot Vu+ Duo2 #10 WanWizard

  • Forum Moderator
    PLi® Core member
  • 50,216 posts

+905
Excellent

Posted 24 November 2015 - 14:10

You seem to have an error in your config file:

Traceback (most recent call last):
File "/usr/lib/enigma2/python/mytest.py", line 53, in <module>
config.misc.prev_wakeup_time = ConfigInteger(default=0)
File "/usr/lib/enigma2/python/Components/config.py", line 1576, in __setattr__
File "/usr/lib/enigma2/python/Components/config.py", line 80, in load
File "/usr/lib/enigma2/python/Components/config.py", line 794, in fromstring
ValueError: invalid literal for int() with base 10: '1448265935.02'

which might be related?


Currently in use: VU+Duo 4K (2xFBC S2), Amiko Viper T2C (T2), SAB Alpha Triple HD (S2+T2), Zgemma H3.T2C (T/C), Zgemma H6 (fallback), VU+Zero (fallback)

Many answers to your question can be found in our new and improved wiki.

note: I do not provide support via PM !

 


Re: Lost Webif after reboot Vu+ Duo2 #11 SpliNT

  • Member
  • 10 posts

0
Neutral

Posted 24 November 2015 - 15:27

Hmm. I can't seem to find config.py at that location, only config.pyo. I tried to open config.pyo but it didn't make me wiser. 



Re: Lost Webif after reboot Vu+ Duo2 #12 WanWizard

  • Forum Moderator
    PLi® Core member
  • 50,216 posts

+905
Excellent

Posted 24 November 2015 - 15:29

The problem is not in the code, but in the config somewhere.

 

I'd start by checking /etc/enigma2/settings, which is your main config file. The error suggests there is a config key "config.misc.prev_wakeup_time" which should be defined as an integer, but is in the config file as a float ("1448265935.02").

 

1448265935 is unixtime for Mon, 23 Nov 2015 08:05:35 GMT, not sure how a float value could be stored there. Wakeup time for EPG import perhaps?


Currently in use: VU+Duo 4K (2xFBC S2), Amiko Viper T2C (T2), SAB Alpha Triple HD (S2+T2), Zgemma H3.T2C (T/C), Zgemma H6 (fallback), VU+Zero (fallback)

Many answers to your question can be found in our new and improved wiki.

note: I do not provide support via PM !

 


Re: Lost Webif after reboot Vu+ Duo2 #13 Erik Slagter

  • PLi® Core member
  • 45,419 posts

+503
Excellent

Posted 24 November 2015 - 15:34

You seem to have an error in your config file:

Traceback (most recent call last):
File "/usr/lib/enigma2/python/mytest.py", line 53, in <module>
config.misc.prev_wakeup_time = ConfigInteger(default=0)
File "/usr/lib/enigma2/python/Components/config.py", line 1576, in __setattr__
File "/usr/lib/enigma2/python/Components/config.py", line 80, in load
File "/usr/lib/enigma2/python/Components/config.py", line 794, in fromstring
ValueError: invalid literal for int() with base 10: '1448265935.02'
which might be related?

 

Ah yes, that one. I've had it a few times as well. It IS an error in the config, but it's caused by a bug in enigma. For me it happens when I stop enigma before it has finished completely starting up. The simple workaround is to change the value to zero or to remove the key altogether. But the bug needs to be fixed. Apparently somewhere this value is written as float and read back as integer. I am not completely sure the above value is valid anyway, but it shouldn't crash.


* Wavefrontier T90 with 28E/23E/19E/13E/9E/4.8E/0.8W/5W via SCR switches 2 x 2 x 6 user bands
* Ziggo digital cable TV (FTA)
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.

Re: Lost Webif after reboot Vu+ Duo2 #14 WanWizard

  • Forum Moderator
    PLi® Core member
  • 50,216 posts

+905
Excellent

Posted 24 November 2015 - 15:41

Used here: https://github.com/O...rev_wakeup_time

 

Navigation uses it, and sets it to zero. Mytest checks if it's zero. It isn't used elsewhere in the Enigma2 repo, so I assume it's a plugin that sets it?


Currently in use: VU+Duo 4K (2xFBC S2), Amiko Viper T2C (T2), SAB Alpha Triple HD (S2+T2), Zgemma H3.T2C (T/C), Zgemma H6 (fallback), VU+Zero (fallback)

Many answers to your question can be found in our new and improved wiki.

note: I do not provide support via PM !

 


Re: Lost Webif after reboot Vu+ Duo2 #15 SpliNT

  • Member
  • 10 posts

0
Neutral

Posted 24 November 2015 - 16:00

 

You seem to have an error in your config file:

Traceback (most recent call last):
File "/usr/lib/enigma2/python/mytest.py", line 53, in <module>
config.misc.prev_wakeup_time = ConfigInteger(default=0)
File "/usr/lib/enigma2/python/Components/config.py", line 1576, in __setattr__
File "/usr/lib/enigma2/python/Components/config.py", line 80, in load
File "/usr/lib/enigma2/python/Components/config.py", line 794, in fromstring
ValueError: invalid literal for int() with base 10: '1448265935.02'
which might be related?

 

Ah yes, that one. I've had it a few times as well. It IS an error in the config, but it's caused by a bug in enigma. For me it happens when I stop enigma before it has finished completely starting up. The simple workaround is to change the value to zero or to remove the key altogether. But the bug needs to be fixed. Apparently somewhere this value is written as float and read back as integer. I am not completely sure the above value is valid anyway, but it shouldn't crash.

 

 

/etc/enigma2/settings

 

config.misc.prev_wakeup_time=0

 

Changing the value to zero did the trick! 

 

Thank you so much both you for the fast help!  ^_^

You saved me from a cold trip to an island in the Stockholm Archipelago.



Re: Lost Webif after reboot Vu+ Duo2 #16 WanWizard

  • Forum Moderator
    PLi® Core member
  • 50,216 posts

+905
Excellent

Posted 24 November 2015 - 16:47

Think of all the beautiful scenery you will miss on your trip... :)


Currently in use: VU+Duo 4K (2xFBC S2), Amiko Viper T2C (T2), SAB Alpha Triple HD (S2+T2), Zgemma H3.T2C (T/C), Zgemma H6 (fallback), VU+Zero (fallback)

Many answers to your question can be found in our new and improved wiki.

note: I do not provide support via PM !

 


Re: Lost Webif after reboot Vu+ Duo2 #17 Erik Slagter

  • PLi® Core member
  • 45,419 posts

+503
Excellent

Posted 24 November 2015 - 19:43

Fixed (well, attempt at, my Python is not that great...)

commit 708ec16060bd6b7fb5ef4490cb722eae593e39dc
Author: Erik Slagter <erik@openpli.org>
Date:   Tue Nov 24 19:40:00 2015 +0100

    prev_wakeup_time: initialise using strict integers only or gsod will happen.
    
    This fixes http://forums.openpli.org/topic/39519-lost-webif-after-reboot-vu-duo2/#entry515601

diff --git a/mytest.py b/mytest.py
index 5098cf7..d709850 100644
--- a/mytest.py
+++ b/mytest.py
@@ -504,7 +504,7 @@ def runScreenTest():
            setRTCtime(nowTime)
        print "set wakeup time to", strftime("%Y/%m/%d %H:%M", localtime(wptime))
        setFPWakeuptime(wptime)
-       config.misc.prev_wakeup_time.value = startTime[0]
+       config.misc.prev_wakeup_time.value = int(startTime[0])
        config.misc.prev_wakeup_time_type.value = startTime[1]
        config.misc.prev_wakeup_time_type.save()
    else:

* Wavefrontier T90 with 28E/23E/19E/13E/9E/4.8E/0.8W/5W via SCR switches 2 x 2 x 6 user bands
* Ziggo digital cable TV (FTA)
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.

Re: Lost Webif after reboot Vu+ Duo2 #18 SpliNT

  • Member
  • 10 posts

0
Neutral

Posted 24 November 2015 - 20:13

Good work, Erik! 

 

Thank you very much!



Re: Lost Webif after reboot Vu+ Duo2 #19 WanWizard

  • Forum Moderator
    PLi® Core member
  • 50,216 posts

+905
Excellent

Posted 24 November 2015 - 21:34

Is that a fix? I'd call that a workaround. ;)

 

Still no clue which bit of code sets that config key, a search in enigma2 and a few repo's for this key draws a blank...


Currently in use: VU+Duo 4K (2xFBC S2), Amiko Viper T2C (T2), SAB Alpha Triple HD (S2+T2), Zgemma H3.T2C (T/C), Zgemma H6 (fallback), VU+Zero (fallback)

Many answers to your question can be found in our new and improved wiki.

note: I do not provide support via PM !

 


Re: Lost Webif after reboot Vu+ Duo2 #20 Erik Slagter

  • PLi® Core member
  • 45,419 posts

+503
Excellent

Posted 25 November 2015 - 13:04

Is that a fix? I'd call that a workaround. ;)

 

Still no clue which bit of code sets that config key, a search in enigma2 and a few repo's for this key draws a blank...

That IS the code that sets the config key. And therefore it's the fix.


* Wavefrontier T90 with 28E/23E/19E/13E/9E/4.8E/0.8W/5W via SCR switches 2 x 2 x 6 user bands
* Ziggo digital cable TV (FTA)
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.





Also tagged with one or more of these keywords: Vu+ Duo2, Webif, Issue

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users