Hi, 

 

I'm new to unraid an still in the trial period. Over the last few days I have been moving my data over to the server, but I just noticed that Fix Common Problems reports the Call Traces Error. Maybe anyone can help me where the error is coming from and how i can fix it. Thanks in advance.

ziva-diagnostics-20171212-0914.zip

This usually helps:

 

https://forums.lime-technology.com/topic/55910-out-of-memory-errors-detected-on-your-server-call-traces-found-on-your-server/?do=findComment&comment=546982

 

Thanks for the fast reply. I will try the fix.

I applied the above mentioned fix, but I'm still getting the call trace error. Any other idea how to fix this?

ziva-diagnostics-20171213-2225.zip

15 minutes ago, Luftgucker said:

Any other idea how to fix this?

No, that usually does it, make sure the settings are enable, they reset after a reboot if just set on the console.

You have multiple call traces.  The bulk of these are Page Allocation Failures, which FCP is ignoring because they are informative only, and not indicative of a problem.

 

The trace that's triggering the notification is.

Dec 13 21:34:10 Ziva kernel: alloc_bts_buffer: BTS buffer allocation failure

which googling seems to imply that its related to memory fragmentation.  I think that its also simply an informational trace as the system falls back to another method of allocating the buffer in this circumstance.

 

An upgrade to 6.4 and the later kernel version will probably get rid of it for good.

 

Of course, this is all assuming that you're seeing no problems

 

2 minutes ago, johnnie.black said:

No, that usually does it, make sure the settings are enable, they reset after a reboot if just set on the console.

FYI, FCP only looks for any trace surrounded by ---[ cut here ]---  It limits the amount of spam postings here regarding informational traces (such as page allocation failures)

I'm noticing no problems at all, only the syslog fills up to 100% with the call trace errors. But I can live with that and will wait for 6.4 to hopefully resolve this issue.

10 minutes ago, Luftgucker said:

I'm noticing no problems at all, only the syslog fills up to 100% with the call trace errors. But I can live with that and will wait for 6.4 to hopefully resolve this issue.

That is a problem.  How long does it take to do that?  

 

Once you hit 100% some strange things *may* happen

It's also strange that the page allocation stalls start less than an hour after a fresh reboot, they usually happen after a few days, so you probably a different issue than the usual memory related stalls, maybe try starting in safe mode to see it's plugin related.