Jump to content
Sign in to follow this  
romainhc

romainhc: System Log - Fatal Error

10 posts in this topic Last Reply

Recommended Posts

On 3/23/2020 at 5:20 PM, romainhc said:

Same problem here !!!

Not obvious how similar your problem actually is.

 

Go to Tools - Diagnostics and attach the complete diagnostics zip file to your NEXT post.

 

I have split this into another thread so the OP can have that one.

Share this post


Link to post
Posted (edited)
On 3/23/2020 at 10:37 PM, trurl said:

Not obvious how similar your problem actually is.

 

Go to Tools - Diagnostics and attach the complete diagnostics zip file to your NEXT post.

 

I will likely split this into another thread so the OP can have this one.

Hi, thx for your answer. Of course someone need this diagnostic, sorry ! I said I have the same pb because of the log showing full on the dashboard, sluggish webui and same error : Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 133640224 bytes) in /usr/local/emhttp/plugins/dynamix/include/Syslog.php on line 20

 

I've updated to 6.8.3, and the problem appears after that. Thank you in advance if you have a possible fix !

nasl42-diagnostics-20200326-1759.zip

Edited by romainhc

Share this post


Link to post

You have a completely different problem filling syslog:

...
Mar 24 00:32:24 NASL42 kernel: EDAC sbridge MC1: HANDLING MCE MEMORY ERROR
Mar 24 00:32:24 NASL42 kernel: EDAC sbridge MC1: CPU 44: Machine Check Event: 0 Bank 7: cc0357c000010090
Mar 24 00:32:24 NASL42 kernel: EDAC sbridge MC1: TSC 0 
Mar 24 00:32:24 NASL42 kernel: EDAC sbridge MC1: ADDR 203fba0600 
Mar 24 00:32:24 NASL42 kernel: EDAC sbridge MC1: MISC 152108a86 
Mar 24 00:32:24 NASL42 kernel: EDAC sbridge MC1: PROCESSOR 0:306e4 TIME 1585006344 SOCKET 1 APIC 35
Mar 24 00:32:24 NASL42 kernel: EDAC MC1: 3423 CE memory read error on CPU_SrcID#1_Ha#0_Chan#0_DIMM#0 (channel:0 slot:0 page:0x203fba0 offset:0x600 grain:32 syndrome:0x0 -  OVERFLOW area:DRAM err_code:0001:0090 socket:1 ha:0 channel_mask:1 rank:0)
...

Is this a new build?

 

Share this post


Link to post

New build or not, its 100% bad memory (or possibly very badly seated memory).  Your event log in the BIOS might contain further suggestions on which stick is giving the problems (other than Channel 0, Dimm 0)

Share this post


Link to post

We have a new build based on refurbished hardware :

SuperM|CSE-846 X9DRi-F|

2 x Intel Xeon E5-2697 V2 2.70Ghz Twelve (12) Core

16 x 8GB PC3L-12800R (DDR3 Low-Power-1600Mhz, 2RX4) 

 

I have transferred the Unraid flash from our previous server. I updated to the new Unraid OS, and these problems appeared.

I think I'll have to check each memory !

 

Thx guys

Share this post


Link to post
3 hours ago, romainhc said:

Is there a way to stop the log filling ? While fixing the ram pb.

You shouldn't need to run very long to determine whether or not you are still getting those in your syslog. You need to fix it, not keep running it without filling your log.

Share this post


Link to post

Yeah I know, but I'm working at home (covid-19) and have no physical access to the server for now. :) 

Share this post


Link to post

I wouldn't want to risk running a server with memory problems. Everything goes through memory, your data, the executable code, everything.

 

Share this post


Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this