PDA

View Full Version : Quad hangs (Spinning VIX), no crash, Debug created (what does it mean?)



BubbleBalls
30-06-14, 21:14
Using Apollo 12

Quad is near 5 months old and has developed an issue where it freezes for up to 30 mins randomly. I have....

reflashed with/without settings restore
Disconnected/changed HDD (remounted also)
Disconnected/changed USB (remounted also)
Tested with only pre-installed tuners (disabled terrestrial and Sat in slots C and D)

The YAD is within those discussed in the link so it looks like a dodgy one........

http://www.world-of-satellite.com/showthread.php?34556-gigablue-quad-restarts-but-no-crash-report/page12&highlight=quad+hangs

Before I send it back I am posting the debug log to see if you knowledgeable guys can shed some light on it? This log is from a virgin flash - No restore - Cross EPG set to 28E - Bouquets are FTA only - Additional tuners are disabled - No Cams - No additional plug-ins. The log is dated 01.01.1970!! but happened between 18:30 and 20:00 today.

35644

nsw9154
01-07-14, 01:04
Hello Bubbleballs now I am Glad I bought the Solo2 :D

BubbleBalls
01-07-14, 15:27
Bump

Tapatalker

BubbleBalls
01-07-14, 22:25
Hi,

Another debug log when I checked tonight
35671

When I tried to view it, on the box, E2 restarted (no crash log) then this debug log was created
35672

Would really appreciate any feedback if anybody understands the info on these. I would like to have some concrete info when I return the box.

Cheers

judge
01-07-14, 22:44
You have lots of:

[eDVBRecordStreamThread] failed to cancel, killing all waiting IO
[eDVBRecordFileThread] poll: aio_return returned failure: Interrupted system call
[eDVBRecordFileThread] poll: aio_return returned failure: Interrupted system call
[eDVBRecordFileThread] poll: aio_return returned failure: Interrupted system call
[eDVBRecordFileThread] Waiting for I/O to complete
[eFilePushThreadRecorder] Warning: All write buffers busy
[eDVBRecordFileThread] cancelling

No idea what's causing that though, but it's not usual.

judge
01-07-14, 22:54
Also, the logs in your last post aren't from a fresh flash of 014 with nothing restored.
Can you upload one in this situation please.

nsw9154
01-07-14, 23:10
Hello mate I thought that your Serial number was OK but it looks you got one with the dodgy YAD numbers
I had them all written down but must have binned them when I bought the Solo2
But how do you stand if you send it back surly they would have to replace it with a Quad Plus

Mr. Mister
01-07-14, 23:17
I bought one of the so-called dud serial number Quads from a user on this forum about 6 months ago..

I put it in my bedroom and It runs 24/7.. Never turned off.. I can honestly say that i have never had 1 single issue with it since i got it..

I dont remember who the user was.. But as far as i remember.. He was having issue after issue with it..

All i can say is.. This boils down to the way the user has the receiver set up..

This is just my own observation.. As i can NOT re-create an issues that any of you guys are having with my Quad with the dodge serial number..

judge
01-07-14, 23:28
I bought one of the so-called dud serial number Quads from a user on this forum about 6 months ago..

Don't think a dud serial number has ever been confirmed. Bought my Quad secondhand too & it's never had a single issue besides the usual expected issues on test builds/boxes.

BubbleBalls
01-07-14, 23:58
Judge - I have just flashed 14 and enabled debug logs. I have run ABM and set Crossepg (opentv provider 28E) with scheduled DL at 4am daily. Will wait for any logs and post as soon as I see them. EDIT - As before I have disabled the additional tuners - should I enable them?

NSW - I have already gotten the return address and will see what they find. It's well within warranty.

Mr. Mister - I have two Quads. The first was bought just after launch. This has been faultless, and the reason I wanted a second one. I have set both up exactly the same - the same plugins, EPG settings, HDD settings, Timeshift settings, bouquets etc. The older Quad has no problems and must be over a year old. In the past few weeks the newer Quad began acting up. I have reflashed all of my saved images/builds, even 3.808 (which never caused an issue for the many weeks while Zeus was being finalised), but still it froze. So from a user viewpoint I can't explain why the same set up causes issues on only one of my receivers.

Interestingly, the seller has confirmed that "There has been a similar software problem with same kinds of receivers some time ago. Please try an older or newest software. New OpenViX and OpenViX from beginning of the year should work."

But rather than just send it back I would like to confirm, if possible, that the issue it is not something I have done. After all it has worked great for many months. I have tried everything I can think of, with my limited experience, hence this post.

seame
02-07-14, 02:05
Can you get a backup image from the quad that's running perfectly and use it on the faulty quad? If it still crashed it would prove it isn't something you have done.

BubbleBalls
02-07-14, 12:04
Can you get a backup image from the quad that's running perfectly and use it on the faulty quad? If it still crashed it would prove it isn't something you have done.
Cheers. I have already tried that and still the newer one froze. Interesting that for the 2.5 hrs I watched the footie last night on the newer box there were no lock ups so am curious to see if there will be logs when I finish work. Wife/Kids starting to get pi..ed off now - first the lockups, now only the basics working. Shows how accustomed she has become to the benefits of E2 receivers and plug ins etc. (And how easy Vix is to use)

If there are no logs tonight I might reflash both receivers (again, and no restore) to 14 and introduce plugins, settings etc one by one to see if one of them is responsible for the lockups, and monitor.

Might actually swap them both to rule out cable damage.



Tapatalker

stanley1
02-07-14, 20:32
Spinning Vix tonight and last night,trying openrsi at the moment.

judge
02-07-14, 23:10
Spinning Vix tonight and last night,trying openrsi at the moment.

Reports like this really don't help this thread or help solve the issue.
Please upload a debug log so it can at least be compared to the debug logs BubbleBalls is uploading.
Might help find a common issue.

stanley1
03-07-14, 12:20
Yes, should have done that, if it's any help serial number of box begins YAD..........

Regards

BubbleBalls
03-07-14, 23:28
Hi,

Just to update.

I fresh flashed to 14 three nights ago. I set it up with CrossEPG scheduled and FTA channels only. I did not FTP old timers/autotimers and did not FTP my personalised skin (night HD). I left it for 24 hrs and there were no hang ups and no crash/debug logs. Last night I installed Cam and set up NFS and asked my wife to keep an eye out for spinning VIX. Though she watched very little TV she said there were no hang ups today. There are no crash logs and the debug logs are timed to the Cam install and the NFS setup - Is it normal for debug logs to be created in these instances?

I plan on introducing the remainder of the plug ins one by one to see how they act and leave my personalise skin file last. Previous fresh flashes lasted a max of three days before the hang ups started - and today is day three so fingers crossed.

Anything else you think I should be doing, taking things slowly as I am?

judge
03-07-14, 23:59
Is it normal for debug logs to be created in these instances?


Debug log if enabled is a live log, capturing every button press & STB reaction. So extremely handy in tracking down any issues.

BubbleBalls
04-07-14, 23:32
Hi,

So everything was running great tonight so next on my list was Samba. Installed and within an hour box locked up. World Cup was on and picture/sound continued - just box was totally unresponsive for 18 minutes.

In the debug files there are several blocks of 165 lines of "TuxTxt <Biterror in p28>"

There are 14955 line entries of "creating ap&sc files:" which start at 0% and finish at 100%

[eDVBLocalTimerHandler] set Linux Time
broken startcode

[eDVBLocalTimerHandler] set Linux Time
broken startcode

I do not understand the above entries but they form a huge part of the debug logs. As there are personal info in the logs I do want to post them here. Can the above be a result of installing Samba? Has Samba ever been a cause of lock ups?

EDIT - debug log was titled 01.01.1970 again

Thanks again for your time.

rossi2000
04-07-14, 23:34
remove samba see if still does it?

BubbleBalls
04-07-14, 23:39
Should I wait and see if there are more lockups and keep the logs just to rule out the chance there was a coincidence, unlikely as it seems.

If it is Samba I wonder if there is an explanation on why it would work on one of my Quads and not the other!

BubbleBalls
05-07-14, 23:40
Wife told me that box froze yesterday so Samba may not be the cause.

I was watching an MKV contained movie and the box just froze. I pressed down on the directional control (which usually brings the movie/recordings list) but I find this screen
35756

All/Any button press did nothing to the box - it was stuck at that image. It only moved from a full screenshot of the movie (frozen/unplayable) to the attached screenshot. Nothing else worked - Pressing Stop done nothing but about 10/15 minutes later the box became alive again.

This seems crazy. The box locked up but kept all commands issued via remote - it took an age for the box to become functional (which should have been almost immediately) and the box then followed all of the Remote Control Commands I pressed while it was frozen, albeit 10/15 minutes after the actual button presses.

I go to get the debug logs and there are none, bar previously created ones. Really confused here.

judge
05-07-14, 23:54
Wife told me that box froze yesterday so Samba may not be the cause.

I was watching an MKV contained movie and the box just froze. I pressed down on the directional control (which usually brings the movie/recordings list) but I find this screen
35756

All/Any button press did nothing to the box - it was stuck at that image. It only moved from a full screenshot of the movie (frozen/unplayable) to the attached screenshot. Nothing else worked - Pressing Stop done nothing but about 10/15 minutes later the box became alive again.

This seems crazy. The box locked up but kept all commands issued via remote - it took an age for the box to become functional (which should have been almost immediately) and the box then followed all of the Remote Control Commands I pressed while it was frozen, albeit 10/15 minutes after the actual button presses.

I go to get the debug logs and there are none, bar previously created ones. Really confused here.

Sounds like you're stuck in some flakey plugin list.

BubbleBalls
06-07-14, 00:20
Yes, but why the Autobouquet when it should be movie list? Is there anything I can do to pinpoint the cause?

judge
06-07-14, 00:27
Yes, but why the Autobouquet when it should be movie list? Is there anything I can do to to pinpoint the cause?

What plugins have you installed? something overwriting default behaviour?
A debug log of button presses might help.

BubbleBalls
06-07-14, 00:37
Cheers judge,

AutoBouquets E2
Crossepg
Mediascanner
ondemand
OpenWI
Picture Player
Transcoding setup
NFS
Samba

Looks like I have reached the limit on debug log size (as no new logs have been created) - will increase debug log size (is this correct?)

judge
06-07-14, 00:43
Looks like I have reached the limit on debug log size (as no new logs have been created) - will increase debug log size (is this correct?)

New debug logs will be created as & when needed.
Where are you saving them to? maybe looking in the wrong location?

BubbleBalls
06-07-14, 01:04
home/root/logs

it seems that initial logs are recorded as "Enigma2-01-01-1970_01-00-XX.log

01.01.1970 is OK? why that date format?

judge
06-07-14, 01:10
Date format is fine, you'll notice a different format between a full reboot & an E2 restart.

Joe_90
06-07-14, 01:27
home/root/logs

it seems that initial logs are recorded as "Enigma2-01-01-1970_01-00-XX.log

01.01.1970 is OK? why that date format?
That's when unix time started. Everything in linux (time- wise) is relative to that date. The log files in E2 don't seem to have realtime markers - don't know why, but I presume it's to do with the way the clocks work in set top boxes. I'm used to seeing log entries with date and timestamps in PC versions of linux myself.

BubbleBalls
06-07-14, 09:06
This morning the channel changed twice (edit - three times now) without my input. It then showed that tuner C was recording (or in use) but I have no planned recordings at the time. it's like some one else is controlling the box. Here is netstat data........I do not know if this data contains anything personnal but if it does please delete, or let me know and allow me to delete?

With any fresh flash I change the password (passwd) and my router login is personalised. Bizarre stuff.

Welcome to OpenViX for gbquad
openvix Apollo gbquad

gbquad login: root
Password:
root@gbquad:~# netstat
Active Internet connections (w/o servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 gbquad-2.local:ftp KM-TOSH.local:51563 ESTABLISHED
tcp 0 127 gbquad-2.local:telnet KM-TOSH.local:51573 ESTABLISHED
tcp 0 0 localhost.localdomain:898 localhost.localdomain:sunrpc ESTAB LISHED
tcp 0 0 gbquad-2.local:43018 ks205735.kimsufi.com:10015 ESTABLISH ED
tcp 0 0 localhost.localdomain:sunrpc localhost.localdomain:898 ESTAB LISHED
tcp 0 0 ::ffff:192.168.0.20:http ip-83-134-38-74.dsl.scarlet.be:5338 4 ESTABLISHED
tcp 0 0 ::ffff:192.168.0.20:http ip-83-134-38-74.dsl.scarlet.be:5337 9 ESTABLISHED
tcp 0 0 ::ffff:192.168.0.20:http ip-83-134-38-74.dsl.scarlet.be:5338 1 ESTABLISHED
tcp 0 0 ::ffff:192.168.0.20:http ip-83-134-38-74.dsl.scarlet.be:5338 0 ESTABLISHED
tcp 0 0 ::ffff:192.168.0.20:http ip-83-134-38-74.dsl.scarlet.be:5338 2 ESTABLISHED
tcp 0 0 ::ffff:192.168.0.20:http ip-83-134-38-74.dsl.scarlet.be:5338 3 ESTABLISHED
Active UNIX domain sockets (w/o servers)
Proto RefCnt Flags Type State I-Node Path
unix 7 [ ] DGRAM 589 /dev/log
unix 2 [ ] DGRAM 826
unix 3 [ ] STREAM CONNECTED 798 /tmp/camd.socket
unix 3 [ ] STREAM CONNECTED 797
unix 3 [ ] STREAM CONNECTED 764
unix 3 [ ] STREAM CONNECTED 763
unix 2 [ ] DGRAM 760
unix 2 [ ] DGRAM 690
unix 3 [ ] STREAM CONNECTED 1699 /var/run/dbus/system_bu s_socket
unix 3 [ ] STREAM CONNECTED 615
unix 3 [ ] STREAM CONNECTED 610
unix 3 [ ] STREAM CONNECTED 609
unix 2 [ ] DGRAM 607
unix 2 [ ] DGRAM 1697
unix 3 [ ] STREAM CONNECTED 1573
unix 3 [ ] STREAM CONNECTED 1572
root@gbquad:~# netstat
Active Internet connections (w/o servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 gbquad-2.local:ftp KM-TOSH.local:51563 ESTABLISHED
tcp 0 127 gbquad-2.local:telnet KM-TOSH.local:51573 ESTABLISHED
tcp 0 0 localhost.localdomain:898 localhost.localdomain:sunrpc TIME_WAIT
tcp 0 0 gbquad-2.local:43018 ks205735.kimsufi.com:10015 ESTABLISHED
tcp 0 0 ::ffff:192.168.0.20:http ip-83-134-38-74.dsl.scarlet.be:53384 ESTABLISHED
tcp 0 0 ::ffff:192.168.0.20:http ip-83-134-38-74.dsl.scarlet.be:53379 ESTABLISHED
tcp 0 0 ::ffff:192.168.0.20:http ::ffff:87.109.69.4:3592 ESTABLISHED
tcp 0 0 ::ffff:192.168.0.20:http ip-83-134-38-74.dsl.scarlet.be:53381 ESTABLISHED
tcp 0 0 ::ffff:192.168.0.20:http ::ffff:87.109.69.4:3128 ESTABLISHED
tcp 0 0 ::ffff:192.168.0.20:http ip-83-134-38-74.dsl.scarlet.be:53380 ESTABLISHED
tcp 0 0 ::ffff:192.168.0.20:http ::ffff:87.109.69.4:7984 ESTABLISHED
tcp 0 0 ::ffff:192.168.0.20:http ::ffff:87.109.69.4:14080 ESTABLISHED
tcp 0 0 ::ffff:192.168.0.20:http ip-83-134-38-74.dsl.scarlet.be:53382 ESTABLISHED
tcp 0 0 ::ffff:192.168.0.20:http ::ffff:87.109.69.4:6800 ESTABLISHED
tcp 0 0 ::ffff:192.168.0.20:http ip-83-134-38-74.dsl.scarlet.be:53383 ESTABLISHED
tcp 0 0 ::ffff:192.168.0.20:http ::ffff:87.109.69.4:9192 ESTABLISHED
Active UNIX domain sockets (w/o servers)
Proto RefCnt Flags Type State I-Node Path
unix 7 [ ] DGRAM 589 /dev/log
unix 2 [ ] DGRAM 826
unix 3 [ ] STREAM CONNECTED 764
unix 3 [ ] STREAM CONNECTED 763
unix 2 [ ] DGRAM 760
unix 2 [ ] DGRAM 690
unix 3 [ ] STREAM CONNECTED 1699 /var/run/dbus/system_bus_socket
unix 3 [ ] STREAM CONNECTED 615
unix 3 [ ] STREAM CONNECTED 610
unix 3 [ ] STREAM CONNECTED 609
unix 2 [ ] DGRAM 607
unix 2 [ ] DGRAM 1697
unix 3 [ ] STREAM CONNECTED 1573
unix 3 [ ] STREAM CONNECTED 1572
root@gbquad:~#
root@gbquad:~#

BubbleBalls
06-07-14, 09:16
three more channel changes - this is alarming!

And no new debug logs

EDIT - tuner B now in use but no recordings. Am I being hacked or could this be related to SAMBA? Could info I provided in the earlier debug logs have been used to access my box?

Larry-G
06-07-14, 11:03
samba would not have any thing to do with the channel being changed or tying up tuners on the receiver, it does sound like some one is remotely taking control of the receiver, maybe try pulling the network cable or disable the network card on the box all together and see if the channel / tuners are still being messed with.

BubbleBalls
06-07-14, 15:55
I changed the ports in openwebif and no channel changes since this morning.

20 min lock a little earlier - here are the debug logs.

Any advice on what I should do now?

35766

seame
06-07-14, 16:07
Have you the quad setup to stream outside your network? I have mine setup but only activate it if I know I'll be using it. I've read on here countless times that a password is more or less useless and the best way is to use a vpn.

BubbleBalls
06-07-14, 16:31
I do have ports forwarded for use with an app.

Tapatalker

Larry-G
06-07-14, 16:44
I do have ports forwarded for use with an app.

Tapatalker
Thats the best way for a potential hacker to gain access to your receiver / nerwork.

BubbleBalls
06-07-14, 17:05
All forwards now cancelled. Will see if lockups stop. Does the debug or netstat show an intruder?

Tapatalker

BubbleBalls
17-07-14, 23:22
Thank you for the responses and help - much appreciated.

I am now glad I did not return the Quad - It works perfectly. The cause of my issue was due to opening my router to the WWW.

I was hacked - and continuously hacked for at least four weeks. What began as freezing/lock up ended with channel hopping while I watched my TV.

Strange that I was more cautious two years ago, when I began, than I was a few months ago. I got lazy.

Thanks for all the replies and advice - always appreciated - and sorry I wasted your time on an issue of my creating.

stanley1
18-07-14, 12:07
No waste of time, every little bit helps.

nsw9154
18-07-14, 12:53
You are not the first mate and you will not be the last and on a Positive note, because of this thread Hopefully a few more people will not fall in to the same trap and at least you now know that your Quad is working perfect :D

regards norm

rossi2000
18-07-14, 13:46
setup a VPN at home and stuff like this you wont need to worry about.

i have 1 port allowed through my router at home and that is VPN only.

ALL of my stuff is in a VPN and accessible from anywhere.