[VU+ Duo] booting

[cwebb66]

hi all updated my vu duo last night to 695 build , but it appears to be stuck in a boot loop as it gets to 99 and a few seconds after turns it self off in to stand by mode then nothing , I have treied to reset it by switching it off at the rear but this does not work

 

[Larry-G]

as part of the update process your receiver would have made a settings backup ( unless you have disabled it ), simply reflash the receiver then when asked to say yes to restore the backup during the First install wizard.

also if you can FTP into the receiver and retrieve any logs that are associated with this incident so that we may be able to see what's going on.

 

[cwebb66]

I don't how to ftp the unit if it doesn't wake up from standby mode , as it will not connect to my clinet , is there a way to ftp while the unit is in standby mode , thanks for your help

 

[Larry-G]

if you cant FTP then dont worry about it, just reflash the receiver with the latest image from www.openvix.co.uk and go from there.

 

[cwebb66]

I reflashed the box ok , but when I tried to restore the plugins it would not do it , reflashed it again with out restoring the plugins and this worked a treat , have sent the debug file over to vix team , but am I right in thinking that after a flash the crash logs and debug logs that where their before the reflash would be gone because I have over written them with the new flash

 

[Larry-G]

I reflashed the box ok , but when I tried to restore the plugins it would not do it , reflashed it again with out restoring the plugins and this worked a treat

Ok so we at least now know it's one of your plugins thats causing the issue, try re-introducing them one at a time, after each one reboot the receiver, this is a long winded process but should eventually get to the bottom of which one is causing the issues.

am I right in thinking that after a flash the crash logs and debug logs that where their before the reflash would be gone because I have over written them with the new flash

yes thats correct, it's also the reason why i have my logs saved to a USB stick by default so they are never lost in such situations.

 

[cwebb66]

Ok so we at least now know it's one of your plugins thats causing the issue, try re-introducing them one at a time, after each one reboot the receiver, this is a long winded process but should eventually get to the bottom of which one is causing the issues.



yes thats correct, it's also the reason why i have my logs saved to a USB stick by default so they are never lost in such situations.

I might try and save the logs to the hdd then for future reference then and thanks for the help

I will have a go at the plugins and see how I get on

 

[cwebb66]

just updated to 696 with no issues just thought I would update you all

 

[garryboy]

I had similar problems the past when after a re flash I tried to use a setting backup during the initial setup and it would crash and reboot.

I then let it it go through the setup process without using settings backup and then once the image had loaded using the backup manager to restore the settings it worked fine.

Sent from my GT-I9300 using Tapatalk 2

 

[judge]

I then let it it go through the setup process without using settings backup and then once the image had loaded using the backup manager to restore the settings it worked fine.

You are still restoring settings that obviously had issues though...
Maybe better off to make a simple copy of things needed (maybe cams, settings and so on) to a PC, so if the issue ever happens again, you can easily restore required files rather than a back-up that conflicts with a new flash.

 

[garryboy]

You are still restoring settings that obviously had issues though...
Maybe better off to make a simple copy of things needed (maybe cams, settings and so on) to a PC, so if the issue ever happens again, you can easily restore required files rather than a back-up that conflicts with a new flash.

I will do that judge however been working perfectly since.

I have a folder on my desktop with my cams picons etc

If required I quite enjoy setting the box up from scratch.

Sent from my GT-I9300 using Tapatalk 2

 

[tvtv]

ive just had vu+ duo 2 stick on 99% booting up ... not sure what logs you need... i only see smb log in tmp

[1970/01/01 01:00:19, 1] lib/account_pol.c:account_policy_get(286)
account_policy_get: tdb_fetch_uint32 failed for field 1 (min password length), returning 0
[1970/01/01 01:00:19, 1] lib/account_pol.c:account_policy_get(286)
account_policy_get: tdb_fetch_uint32 failed for field 2 (password history), returning 0
[1970/01/01 01:00:19, 1] lib/account_pol.c:account_policy_get(286)
account_policy_get: tdb_fetch_uint32 failed for field 3 (user must logon to change password), returning 0
[1970/01/01 01:00:19, 1] lib/account_pol.c:account_policy_get(286)
account_policy_get: tdb_fetch_uint32 failed for field 4 (maximum password age), returning 0
[1970/01/01 01:00:19, 1] lib/account_pol.c:account_policy_get(286)
account_policy_get: tdb_fetch_uint32 failed for field 5 (minimum password age), returning 0
[1970/01/01 01:00:19, 1] lib/account_pol.c:account_policy_get(286)
account_policy_get: tdb_fetch_uint32 failed for field 6 (lockout duration), returning 0
[1970/01/01 01:00:19, 1] lib/account_pol.c:account_policy_get(286)
account_policy_get: tdb_fetch_uint32 failed for field 7 (reset count minutes), returning 0
[1970/01/01 01:00:19, 1] lib/account_pol.c:account_policy_get(286)
account_policy_get: tdb_fetch_uint32 failed for field 8 (bad lockout attempt), returning 0
[1970/01/01 01:00:19, 1] lib/account_pol.c:account_policy_get(286)
account_policy_get: tdb_fetch_uint32 failed for field 9 (disconnect time), returning 0
[1970/01/01 01:00:19, 1] lib/account_pol.c:account_policy_get(286)
account_policy_get: tdb_fetch_uint32 failed for field 10 (refuse machine password change), returning 0
[1970/01/01 01:00:19, 0] /home/vix2/oe-alliance/builds/openvix/vuduo2/tmp/work/mips32el-oe-linux/samba/samba-3.0.37-r13/samba-3.0.37/source/lib/pidfile.cidfile_create(112)
ERROR: smbd is already running. File /var/run/smbd.pid exists and process id 560 is running.
[2015/04/16 00:12:37, 1] smbd/service.c:make_connection_snum(1042)
192.168.1.100 (192.168.1.100) connect to service Root initially as user root (uid=0, gid=0) (pid 1133)
[2015/04/16 00:12:47, 1] smbd/service.c:close_cnum(1239)
192.168.1.100 (192.168.1.100) closed connection to service Root
[2015/04/16 00:13:26, 1] smbd/service.c:make_connection_snum(1042)
192.168.1.100 (192.168.1.100) connect to service Harddisk initially as user root (uid=0, gid=0) (pid 1133)
[2015/04/16 00:16:03, 0] printing/pcap.ccap_cache_reload(159)
Unable to open printcap file /etc/printcap for read!
[2015/04/16 00:16:03, 0] printing/pcap.ccap_cache_reload(159)
Unable to open printcap file /etc/printcap for read!
[2015/04/16 00:17:11, 1] smbd/service.c:make_connection_snum(1042)
192.168.1.100 (192.168.1.100) connect to service Root initially as user root (uid=0, gid=0) (pid 1133)
[2015/04/16 00:20:44, 1] smbd/service.c:make_connection_snum(1042)
192.168.1.100 (192.168.1.100) connect to service Root initially as user root (uid=0, gid=0) (pid 1133)