I'm using unRAID 4.4.2 on Lime-Tech (new) hardware.  I have unMenu 1.1 installed.  All was working fine with lots of data moving to / from server.

 

Today, I was attempting to rip a DVD to a server share and it became totally unresponsive - no web interface - no telnet - no ping.

 

I was about to exercise my last option (power switch), when I was able to ping again and web interface / shares came back.

 

Anyway, I notice the [attached] entry in my syslog.  Can anyone tell me what this is - and why it happened? 

 

I was considering that my server was fairly solid, but now I am wondering.

 

Thanks for any information.

It looks to me like a brief 'hiccup' during normal network operations, consistent with your mention of a temporary loss of network responsiveness.  The Linux error handlers appear to have had it under control, and logged relevant info to your syslog.  It's not sufficiently informative enough to tell us exactly what went wrong, but it was something serious enough, and at a very low level, to warrant a logged trace.  What would be useful is check for anything unusual just before this trace, and the messages following, especially any errors and anything informing as to actions taken.  It appears to have restored network operations, but I would always reboot the system, after any evidence of a low-level crash.

 

Conjectures as to causes:  most likely a bug in the network driver, or a 'helper' module; possible bug in NIC firmware; possibly a bug in some other core module due to some very unusual interaction; flaky memory.

 

The one thing you can easily do is run a memory test over night, even though it is a very unlikely cause, it is easy to test and eliminate as a suspect.  Otherwise, all you can do is monitor it, and record each occurrence with what was happening at time of occurrence.

 

[ Note:  For an excerpt that short, it is probably better to use the forum Quote or Code buttons, and paste it within the post, rather than attach it as a file.  Works either way though. ]

Many thanks RobJ,

 

The most recent syslog entry before the problem was a DHCP lease request / grant.  But that was about 2-minutes before the problem.

 

Good suggestion to reboot and run memtest, I'll do it. 

 

I was pretty anxious about this, since I dread just hitting the power button - even on Windows systems which I am familiar with.

 

Yeah, I was 50/50 on whether to attach the syslog snippit or just put it in the post.  I guess it would get more exposure just posting it

 

Thanks again, I'll be watching this. 

 

I just received a Popcornhour A-110 and I'm ripping every DVD I can find trying to find the optimal format for playing back through the A-110 from an unRAID SMB share.  It was during one such rip that the error occurred.