February 15, 20179 yr Hey all, Upon running the 'Fix Common Problems' plugin, it's found issued call traces. I was hoping someone might be able to assist, as I'm not sure what the problem is. I've attached the diagnostics file. Thanks. diagnostics-20170215-1900.zip
February 15, 20179 yr I got the same. See here: https://lime-technology.com/forum/index.php?topic=56509.0 Already figured out that it's probably not a memory issue. Maybe something with v6.3.1 Kernel?
February 15, 20179 yr Author I got the same. See here: https://lime-technology.com/forum/index.php?topic=56509.0 Already figured out that it's probably not a memory issue. Maybe something with v6.3.1 Kernel? Interesting, thanks. I might try some of the suggestions your thread mentions anyway, just to be safe.
February 15, 20179 yr Yours is segfaulting, which is not identical. But it's resulting in a failure to allocate memory and an OOM, which results in processes being killed. You shouldn't continue without rebooting. You'll certainly want to run a good long Memtest, but also look at your processor cooling arrangements as you're using a 65 W TDP CPU in a box that was originally designed for 35 W. I recommend the newer version of Memtest that installs onto a separate USB stick. Again, turning off the VM service might give some clues if it results in more stable operation.
February 16, 20179 yr Author Yours is segfaulting, which is not identical. But it's resulting in a failure to allocate memory and an OOM, which results in processes being killed. You shouldn't continue without rebooting. You'll certainly want to run a good long Memtest, but also look at your processor cooling arrangements as you're using a 65 W TDP CPU in a box that was originally designed for 35 W. I recommend the newer version of Memtest that installs onto a separate USB stick. Again, turning off the VM service might give some clues if it results in more stable operation. Thanks for the info mate. As a start, I rebooted the server on your instructions, did an extended scan with the plugin and it appears the call trace error is not coming up again. I haven't done the memtest yet, so I'll make sure to do that sometime. Also, the cpu has been in there for about a year and I've had no real issues even when it's stressed to 100%. I also turned the boost off so it stays at stock speeds. Overall, the temps are good. The passive heatsink deals with the xeon quite well. Thanks again.
Archived
This topic is now archived and is closed to further replies.