Hi all,

 

Hope you can help. My server seems to lock-up roughly every 12 hours or less. At that point I cannot telnet, use the browser - emhttp, or use the console directly.

 

I could not capture syslog but did capture a screen shot of the console, apologies, quality is not fantastic!

 

Can you let me know if there is anything else I can do other than the steps below to isloate the problem? Thankyou all!

 

1.) Overnight memtest (using v4.10)

2.) Disable Plex MM - test, if still getting a KP..

3.) Disable Sickbeard, test. then couchp, then sabnz

4.) Scratch head...

 

I'll also run the tail command once backup so I can get some better feedback.

 

Any thoughts?

 

Thanks for your help.

 

Rgds,

 

Alex.

I just discovered that for me it was a memory issue.  I was trying to clear 2 3TB drives at the same time and only had 1GB of memory installed.  It would throw a panic some time during the first pass.  When I upped my memory to 2GBs I was able to do my normal 3 preclear passes on both at the same time.  I figured this out when I was able to clear a single 3TB drive.  I didn't think it was memory at first because I was able to run preclears on 2 2TB drives at the same time with no problem.  So when I got each of the 3TB drives to clear individually I decided it wasn't the drives themselves since they appeared fine after the individual preclears.  It was confirmed when I upped the memory to 2GB and ran the preclears again but at my normal 3 cycle count.  Not saying that is absolutely your problem but didn't see you specify any computer specs.  Also I am certainly NO expert.  I only know enough about Linux to get me into trouble.

An extended tail and a larger console would probably be your best bets, for more diagnostic info.  I use the command:

  tail -f --lines=120 /var/log/syslog

 

This makes the last 120 lines available, using the Shift-PgUp key combo to page up through the last pages of the syslog.

 

I also adjust the console screen lines to 80X60, to make 60 lines visible, rather than the meager 25 lines default.  To do this, add the VGA=6 parameter to the append line of your syslinux.cfg file.  For more info on this, see here.

 

About the only thing you can do with kernel panics is either remove the offending hardware, if that seems indicated, or use a different kernel.  You might want to try different kernels, either the newer Linux v3.1.1 in v5b14 or the older kernels in v5b12 or older.

Thanks all, really appreciate the input...

 

Will run the extended tail and see what I find.

 

Running with 4gb RAM which should be more than enough and overnight memtest showed no errors so guessing not a ram issue.

 

Anyway, will report back when I have a syslog to share...

Hmm - out put of the tail attached. Nothing obvious I can see, but then I'm no expert...

 

Any ideas?

 

Thanks,

 

Alex

Untitled.txt

Have upgraded to b15 and will run the tail again.

 

Anything you can determine from the log would be great!!

Your tail is showing some serious issues, possibly the cause of the system crashes you have experienced.  There are actually 2 issues present, neither of which I have the experience to help you.  The first appears relatively minor, but involves the Apple support, so perhaps someone with Apple experience can help with that.  The more serious is the issues with rsync and glibc, and requires someone with considerably more Linux experience.  Just guessing here, but there may be a conflict between the libraries included with this distro (v5b13) and libraries included with some of your addons.  A possible solution would be to revert to older kernels, with hopefully more compatible libraries.  Better Linux experts could give you better advice.

 

Since the conflicts and issues appear when rsync was called by the mover, another partial and temporary solution would be to disable the mover.  If nothing else, disabling the mover and avoiding any use of rsync should help confirm if that is the cause of the system crashes.

Thanks - Ill see of it crashes again with b14 and then disable my rsync backup and see if that is the cause.

 

Appreciate the input.

 

Rgds,

 

Alex.

Pretty sure you are right in that it happens when the mover script is executed (i.e. rsync).

 

I've tried running it manually and interestingly enough - no crash!

 

Hmmmm!