Installing 5.2.001 - Plugins restore seems to be stuck/hung

[bsod]

Hi all,

Have just flashed from 5.1.033 to 5.2.001 using the image manager. I am at the point where it asked if I wanted to do a settings restore. I said yes to both settings and plugins. It has not been on the screen saying something along the lines of "Retrieving plugins please wait..." and has been on that screen for close to 40min now.

I can ssh into the system, but the /root/logs folder is empty. Lookin in /var/logs I see the following


root@vuduo2:/var/log# ls -l
-rw-r--r-- 1 root root 0 Sep 24 11:03 boot
-rw-r--r-- 1 root root 9807 Sep 24 11:03 dmesg
-rw-rw-r-- 1 root root 292 Sep 29 02:13 lastlog
-rw-r--r-- 1 root root 30054 Sep 29 02:30 messages
-rw-r--r-- 1 root root 36 Sep 29 01:28 postinstall.log
drwxr-xr-x 2 root root 40 Sep 24 11:03 samba
-rw-rw-r-- 1 root root 3456 Sep 29 02:17 wtmp


One thing I have noticed is the tz on the system is wrong, presumably in UTC. The messages file seems to mostly consist of the following

Sep 29 02:28:01 vuduo2 cron.info crond[1046]: (readme.txt) ORPHAN (no passwd entry)
Sep 29 02:29:01 vuduo2 cron.info crond[1046]: (readme.txt) ORPHAN (no passwd entry)
Sep 29 02:30:01 vuduo2 cron.info crond[1046]: (readme.txt) ORPHAN (no passwd entry)
Sep 29 02:30:01 vuduo2 authpriv.info crond[3167]: pam_unix(crond:session): session opened for user root by (uid=0)
Sep 29 02:30:01 vuduo2 cron.info CROND[3168]: (root) CMD (/usr/bin/ntpdate-sync silent)
Sep 29 02:30:09 vuduo2 daemon.notice ntpdate[3172]: adjust time server 133.243.238.244 offset -0.047514 sec
Sep 29 02:30:09 vuduo2 authpriv.info CROND[3167]: pam_unix(crond:session): session closed for user root
Sep 29 02:31:01 vuduo2 cron.info crond[1046]: (readme.txt) ORPHAN (no passwd entry)
Sep 29 02:32:01 vuduo2 cron.info crond[1046]: (readme.txt) ORPHAN (no passwd entry)
Sep 29 02:33:01 vuduo2 cron.info crond[1046]: (readme.txt) ORPHAN (no passwd entry)


ad the postinstall.log file only contains these 2 lines

adding crontab
Configuring ntpdate.

Had a look at what processes were running and the package installer was listed, but had <defunct> after it's name. Not entirely sure what that signifies though.

1249 ? 00:00:09 opkg <defunct>

Really couldn't find much else apart from a file called ExtraInstalledPlugins in /var/tmp. It consists of

root@vuduo2:/var/tmp# cat ExtraInstalledPlugins
enigma2-plugin-skins-OverlayHD
enigma2-plugin-extensions-youtube
enigma2-plugin-systemplugins-IanSavOpenViXFeed
enigma2-plugin-extensions-netspeedtest
enigma2-plugin-extensions-epgrefresh
enigma2-plugin-extensions-tsmedia
enigma2-plugin-extensions-seriesplugin
enigma2-plugin-extensions-openwebif-terminal
enigma2-plugin-extensions-openwebif-vxg
run-postinsts


Lastly I decided to see what network connections were active. There does not appear be any back to any OpenVix server(s).

root@vuduo2:/var/tmp# netstat -a
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 0.0.0.0:ssh 0.0.0.0:* LISTEN
tcp 0 320 vuduo2.bsod:ssh BSOD.bsod:50597 ESTABLISHED
tcp 0 0 :::8001 :::* LISTEN
tcp 0 0 :::8002 :::* LISTEN
tcp 0 0 localhost:4200 :::* LISTEN
tcp 0 0 :::http :::* LISTEN
tcp 0 0 :::ftp :::* LISTEN
tcp 0 0 :::ssh :::* LISTEN
tcp 0 0 :::telnet :::* LISTEN
udp 0 0 0.0.0.0:mdns 0.0.0.0:*
udp 0 0 0.0.0.0:hostmon 0.0.0.0:*
udp 0 0 0.0.0.0:60816 0.0.0.0:*
udp 0 0 :::dhcpv6-client :::*
udp 0 0 :::mdns :::*
udp 0 0 :::hostmon :::*
udp 0 0 :::57701 :::*
raw 0 0 ::%4788280:58 ::%4953664:* 58
Active UNIX domain sockets (servers and established)
Proto RefCnt Flags Type State I-Node Path
unix 2 [ ACC ] STREAM LISTENING 783 /var/run/dbus/system_bus_socket
unix 2 [ ACC ] STREAM LISTENING 3154 /tmp/.listen.camd.socket
unix 2 [ ACC ] STREAM LISTENING 3156 /tmp/.listen.ciplus.socket
unix 2 [ ACC ] STREAM LISTENING 3196 /tmp/hotplug.socket
unix 2 [ ACC ] STREAM LISTENING 1451 /tmp/nxserver_ipc
unix 2 [ ACC ] STREAM LISTENING 3256 /tmp/hotplug.socket
unix 7 [ ] DGRAM 1998 /dev/log
unix 2 [ ACC ] STREAM LISTENING 2027 /var/run/avahi-daemon/socket
unix 2 [ ] DGRAM 3214
unix 3 [ ] STREAM CONNECTED 2030 /var/run/dbus/system_bus_socket
unix 3 [ ] STREAM CONNECTED 1817
unix 3 [ ] STREAM CONNECTED 2023
unix 3 [ ] STREAM CONNECTED 3153
unix 2 [ ] STREAM 1443
unix 3 [ ] STREAM CONNECTED 2065
unix 2 [ ] STREAM 1447
unix 2 [ ] DGRAM 2046
unix 3 [ ] STREAM CONNECTED 1818
unix 3 [ ] STREAM CONNECTED 2064 /var/run/dbus/system_bus_socket
unix 2 [ ] DGRAM 2370
unix 2 [ ] STREAM 1446
unix 2 [ ] STREAM 1442
unix 3 [ ] STREAM CONNECTED 2066 /tmp/nxserver_ipc
unix 2 [ ] STREAM 1450
unix 2 [ ] DGRAM 2020
unix 3 [ ] STREAM CONNECTED 3383
unix 2 [ ] STREAM 1445
unix 2 [ ] STREAM 1441
unix 3 [ ] STREAM CONNECTED 1454 /tmp/nxserver_ipc
unix 2 [ ] STREAM 1449
unix 3 [ ] STREAM CONNECTED 2029
unix 3 [ ] STREAM CONNECTED 2024
unix 3 [ ] STREAM CONNECTED 3384
unix 2 [ ] DGRAM 955
unix 2 [ ] STREAM 1444
unix 2 [ ] STREAM 1440
unix 3 [ ] STREAM CONNECTED 1453
unix 2 [ ] STREAM 1448
root@vuduo2:/var/tmp#


Is there anyway to find out if it is actually working on thew plugins or if it's just hung in some loop or something?

Craig

[Andy_Hazza]

Can you try flashing with a usb flash drive and restore your settings & plugins.


Sent from my iPhone using Tapatalk

[bsod]

Hi Andy,

sorry but I have since rebooted the unit. Waited a good 4+hrs (needed an excuse to go out and do some gardening!). Decided to try a reboot so ssh'd into the unit, did a shutdown -r now and the unit booted fine, with 5.2.001 and all of my plugins and settings. It looks as if it completed but failed to restart, or something along those lines.

Craig

[Donkey14]

Hi,

Experienced the same issue with Vu Uno. Used image manager to update from version 5.1.033 to 5.2. All went ok, then I try restore all settings and plugins snd tuner stuck on Vix screen and message olease wait. Flashed also by Usb and stuck on the same place after restore settings and plugins. Was waiting 30 min and nothings hapen. Flashed buck to ver 5.1.033 and used again setting and plugin restore and all working after 5min. So no update from my side to 5.2 ver untill some update are done. Possible problem with one of the extensions: cccam 2.3.1, Iptv player(e2player) or skin MagicFHD OE-A by Rob van der Does.

Donkey
(QUOTE=bsod;475299]Hi Andy,

sorry but I have since rebooted the unit. Waited a good 4+hrs (needed an excuse to go out and do some gardening!). Decided to try a reboot so ssh'd into the unit, did a shutdown -r now and the unit booted fine, with 5.2.001 and all of my plugins and settings. It looks as if it completed but failed to restart, or something along those lines.

Craig[/QUOTE]

[abu baniaz]

It's the readme file for crond that is causing it.

No need to wait that long. If you get stuck, init 4, init 3 after 5 minutes is a workaround

[Donkey14]

Was thinking that on version 5.2.004 issue reported are solved. Unfortunately is still exist.
Stuck on vix scrin and flashing circle (busy) after tuner reboot after selecting restore settings and plugins. Nothing more instalked than reported previously.
Flashed by image manager and by usb- the same results. Back to 5.1.033 again and probably will not try again as noticed more problems users have with VU+ tuners.

[

QUOTE=Donkey14;475333]Hi,

Experienced the same issue with Vu Uno. Used image manager to update from version 5.1.033 to 5.2. All went ok, then I try restore all settings and plugins snd tuner stuck on Vix screen and message olease wait. Flashed also by Usb and stuck on the same place after restore settings and plugins. Was waiting 30 min and nothings hapen. Flashed buck to ver 5.1.033 and used again setting and plugin restore and all working after 5min. So no update from my side to 5.2 ver untill some update are done. Possible problem with one of the extensions: cccam 2.3.1, Iptv player(e2player) or skin MagicFHD OE-A by Rob van der Does.

Donkey
(QUOTE=bsod;475299]Hi Andy,

sorry but I have since rebooted the unit. Waited a good 4+hrs (needed an excuse to go out and do some gardening!). Decided to try a reboot so ssh'd into the unit, did a shutdown -r now and the unit booted fine, with 5.2.001 and all of my plugins and settings. It looks as if it completed but failed to restart, or something along those lines.

Craig[/QUOTE][/QUOTE]

[Donkey14]

Tried also flashing by image manager and by usb without restoring any settings. And after setup is done tuner should re-boot. And after re-noot is stuck on the same place. So issue are not with plugins or skin but with software 5.2.....

[bellejt]

flashed both duo2s here in severall differant ways and no problems.Even update online works fine except the read me file before updating shows old information from 5.1

[Donkey14]

It is something in version 5.2... which create issue as I didn't get any issue flash back to 5.1.033 with plugins and settings wizard or clear flash to version 5.1.033.

[Donkey14]

I have logs from tuner but can't see how to attach them to this reply or thread.

[ccs]

Click the advanced button when posting.

It's then under manage attachments.

[Donkey14]

57617

I hope is attached. Two logs together. One should be for version flash 5.1.033 and other for flash for 5.2.004

[ccs]

Maybe this part of the 5.2 release notes is significant...…



Known Plugin/Receiver issues

Older receivers with lower amounts of memory struggle with downloading OpenTV EPG data using Cross EPG downloader. Use a swap file in such cases.
Some 3rd party plugins may not be currently compatible with OE-A 4.2x core, streaming plugins may require their respective author's to add dependencies for GST 1.xx.
HbbTV not working for all receivers. Please raise issue with respective Manufacturer.

[Donkey14]

Swap file used - so this is not a issue. Installed from usb without plugins and existing settings so no extras- version 5.2.004 and tuner stuck on after reboot. On version 5.1.033 still have 12.5mb flash free memory.

I have logs from tuner but can't see how to attach them to this reply or thread.

[Andy_Hazza]

Swap file used - so this is not a issue. Installed from usb without plugins and existing settings so no extras- version 5.2.004 and tuner stuck on after reboot. On version 5.1.033 still have 12.5mb flash free memory.

Swap file used??? What receiver???


Sent from my iPhone using Tapatalk

[ccs]

Before, you were saying that a settings and plugins restore caused the box to hang, are you now saying that a simple reflash without a settings and plugins restore causes the same problem?

[Donkey14]

Yes correct. First I try with restore settings and plugins. Yesterday I tried only flash to clean 5.2.004 version without restore anything. Results the same. Stook after reboot. Vu+ Uno
I have logs from tuner but can't see how to attach them to this reply or thread.

[Donkey14]

Yes, swap used to 256mb. Vu+ uno tuner

[twol]

Swap file used - so this is not a issue. Installed from usb without plugins and existing settings so no extras- version 5.2.004 and tuner stuck on after reboot. On version 5.1.033 still have 12.5mb flash free memory.
12.5mb is not a lot!
Try a flash of 5.2 don‘t restore any thin, allow to reboot.
Then use putty to access and enter: (after login)
Init 4
Enigma2
And capture log.
Post.

[Donkey14]

Log already posted. Please see above. Flashed without restoring plugins. The same issue. Can't do anything with it. Tuner starting, then basics settings done then ask to reboot. After reboot vix screen with message please wait and vix logo on top corner show for few seconds and disappear and that forever. No reactiin to remote at all even if flashing green led on front panel when pressed. Yes maybe 12.5mb with 5.1.033 it's not a lot but enough. Maybe Vu+ uno flash drive are to small for 5.2.... image


I have logs from tuner but can't see how to attach them to this reply or thread.

[twol]

Log already posted. Please see above. Flashed without restoring plugins. The same issue. Can't do anything with it. Tuner starting, then basics settings done then ask to reboot. After reboot vix screen with message please wait and vix logo on top corner show for few seconds and disappear and that forever. No reactiin to remote at all even if flashing green led on front panel when pressed. Yes maybe 12.5mb with 5.1.033 it's not a lot but enough. Maybe Vu+ uno flash drive are to small for 5.2.... image
No its not the same ...when you use putty and enigma2 you see it as it happens....... when you post a log it may not contain the last information... when I have an a boot issue for me this is (and always has been) the best way of capturing everything..... so I realise its extra effort but could you do this??

[Donkey14]

Ok. Can you tell me what is Putty?
And what to do with it?

I have logs from tuner but can't see how to attach them to this reply or thread.

[twol]

Telnet application that runs on windows or ubuntu (linux) and allows you to enter commands to the receiver
So like filezilla you can log in as usual ...filezilla is great for transferring files, puuty for commands to the receiver

[Donkey14]

Ok. Thanks for help. As soon as I have lig I will post it here