VU+ Solo 2 - VIX image Hades / VIX 3.2 - Crashing

[Sicilian]

My setup at home is fibre optic and the Vu duo is a straight ethernet cable from router to box. I have had it like this for over a year with no problems all of a sudden i get these problems also my dad has the same problems.

Try a different image then, sorry cannot replicate whatsoever, nor can any of the testers, this whole thread is going round in circles.

 

[judge]

when I turned the box on it comes up with an error and a red symbol

Not much use to anyone without the logs or even the error message.

 

[Davitat]

Try a different image then, sorry cannot replicate whatsoever, nor can any of the testers, this whole thread is going round in circles.

I know it is difficult if you cannot replicate but me and others are having the same problem.
It is NOT local and is probably a mix of various factors.

Nothing has changed in my box nor in my network (BTW I still don't understand how a network could crash a box...)
What we know for sure is:
1) Something has been changed ('memorized') in the boxes as the prior versions now also crash.
2) Erased /tmp/ (at least) is a common denominator to all this crashes.

I've tried yesterday to deactivate the softcam check as you suggested because many crashes involve it. It lasted longer but it finally crashed.
I see there is a 016 build and I gone try it.

 

[Sicilian]

I know it is difficult if you cannot replicate but me and others are having the same problem.
It is NOT local and is probably a mix of various factors.

Nothing has changed in my box nor in my network (BTW I still don't understand how a network could crash a box...)
What we know for sure is:
1) Something has been changed ('memorized') in the boxes as the prior versions now also crash.
2) Erased /tmp/ (at least) is a common denominator to all this crashes.

I've tried yesterday to deactivate the softcam check as you suggested because many crashes involve it. It lasted longer but it finally crashed.
I see there is a 016 build and I gone try it.

All images here http://www.openvix.co.uk/index.php/downloads/vu-plus-images/vu-duo/ for your Duo. Hades and Apollo archives.

 

[judge]

Something has been changed ('memorized') in the boxes as the prior versions now also crash.

Are you sure you're using the correct bootloader?

 

[Sicilian]

1) Something has been changed ('memorized') in the boxes as the prior versions now also crash.

Be serious please. If this was a widespread issue the forum would be full of this report. Only 2-4 peeps posting about this issue.

Go and try Openpli, Blackhole or another image, let us know your results with any logs.

 

[iwg]

sorry all - I do risk replying partial way through a thread here, but last poster (Davitat) just suggested /tmp was erased!!! Not a big loss as it is only a symbolic link to /var/tmp (should be there dated on the 70 epoch) but if not try: ln -s /var/tmp/ /tmp at the -sh shell PS1 (that is $) prompt you get after telnet-ing in. It might help repair any ErrNo 2's related to temp files.

 

[iwg]

looks like I replied before the big un's did!!! Sorry guys! Just recognised the symptom about /tmp missing

 

[Davitat]

Be serious please. If this was a widespread issue the forum would be full of this report. Only 2-4 peeps posting about this issue.

Go and try Openpli, Blackhole or another image, let us know your results with any logs.

I'm very serious.
How if not do you explain that prior versions now crash please?
If all is identical and gives different results... then basic physics rules (causality) as to be questioned... Perhaps you could apply for a Nobel's prize!

The fact that we are few having the problem is probably due, as I try to explain from the beginning, to the fact of one 'poised' version (not everybody installs every version) combined with other special factors (specific setups).

You also have had the 'crash', don't forget it so you know is 'real'.
And yes, as I see more and more displeasent comments and no solution, after loosing one week of my time tying to help with this problem, I'll return to Black Hole.

Good luck, you'll need it.

 

[Sicilian]

I'm very serious.
How if not do you explain that prior versions now crash please?
If all is identical and gives different results... then basic physics rules (causality) as to be questioned... Perhaps you could apply for a Nobel's prize!

The fact that we are few having the problem is probably due, as I try to explain from the beginning, to the fact of one 'poised' version (not everybody installs every version) combined with other special factors (specific setups).

You also have had the 'crash', don't forget it so you know is 'real'.
And yes, as I see more and more displeasent comments and no solution, after loosing one week of my time tying to help with this problem, I'll return to Black Hole.

Good luck, you'll need it.

Even your own posted logs using different versions of openvix show different crashes. Your crashlog from Hades is completely different from 3.2 images.

For your info I got the crash that stops ftp etc.. on a Duo2 and MB Micro around 10 days, totally unexplained and have been unable to replicate since. So that blows your theory of something being 'memorized'.

 

[lxt1024]

I wonder if a common factor may be people who tried to online update to build 10? I did and didn't get notified of future update to build 15. I then couch flashed build 15. I then noticed in mornings I had an error on screen similar when trying Update Version Check. It checks every 6hrs but seems only problem at night when maybe site down? I have disabled auto check and not had error but would like to turn it on again at some point

Sent from my SM-N9005 using Tapatalk

 

[lxt1024]

So maybe something has been left on the hard drive which is effecting reflash of any image/build?

Sent from my SM-N9005 using Tapatalk

 

[lxt1024]

As in a directory missing, permissions on a folder?

Sent from my SM-N9005 using Tapatalk

 

[lxt1024]

Afterthought.. Might be nice to have info on folders to delete from drive other than restores and recordings etc or have this automated as part of an image flash (maybe on first boot?) so that we truly have a "fresh" flash of an image?

Sent from my SM-N9005 using Tapatalk

 

[Rob van der Does]

You don't want your box to delete anything from your drive!
And what folders/files do you have in mind that could influence the image?

 

[judge]

so that we truly have a "fresh" flash of an image?

If you want a fresh flash, just flash by USB or image manager.
Then the user area of flash is formatted leaving nothing behind.

This thread has really gone into silly territory.

 

[lxt1024]

My apologies, I figured that there would be some OS system files on the drive when the set top box is running which might be the issue from a particular build

Sent from my SM-N9005 using Tapatalk

 

[Dale-Carrick]

Not going to jynx myself yet but last night I flashed with the newest build 3.2.16 and haven't installed anything just like before only been watching the freeview channels and so far it's gone 12 hours without crashing, the longest I have ever managed.

Btw I always disable auto update check and background checks I've only had this problem btw since I tried to update my box online which was around build 10/9.

I flashed from usb just like before but for some reason seems fine at minute, but that might change when I install softcams but I will leave it another 12 hours before I do that. I don't know if this information helps or not.

 

[judge]

but that might change when I install softcams but I will leave it another 12 hours before I do that. I don't know if this information helps or not.

Which softcam & what version do you use?

 

[ronand]

BTW I still don't understand how a network could crash a box...)

A bad mgcamd config will crash the network & box (it causes a ddos attack if logging to a non-existent ip address) - its quite a common problem as people download config files and dont check the contents. It may not be your problem but its an example.