Random nxlog crashes every now and then - Page 1

#1 Michael.Seto II 8 years ago

OS - Windows Server 2012 R2 Datacenter

NXLOG Version - How do I check?

Event Viewer ::

Faulting application name: nxlog.exe, version: 0.0.0.0, time stamp: 0x54fedd1a
Faulting module name: libapr-1-0.dll, version: 0.0.0.0, time stamp: 0x54fedd1a
Exception code: 0xc0000005
Fault offset: 0x00015190
Faulting process id: 0x160
Faulting application start time: 0x01d1b804aaa52028
Faulting application path: D:\Program Files (x86)\nxlog\nxlog.exe
Faulting module path: D:\Program Files (x86)\nxlog\libapr-1-0.dll
Report Id: 79778f7a-2701-11e6-80c2-00155d590419
Faulting package full name:
Faulting package-relative application ID:

Is this a known issue? Are there ways to prevent this from happening?

Thank you!

Permalink

#2 adm Nxlog ✓ 8 years ago

#1 Michael.Seto II

Every now and then I get reports of logs not reporting. I investigate and 99.9% of the time, it is due to a loss of connectivity to the log server due to an nxlog crash. Typically, it is due to a faulting module, per Windows Event Viewer. OS - Windows Server 2012 R2 Datacenter NXLOG Version - How do I check? Event Viewer :: Faulting application name: nxlog.exe, version: 0.0.0.0, time stamp: 0x54fedd1a Faulting module name: libapr-1-0.dll, version: 0.0.0.0, time stamp: 0x54fedd1a Exception code: 0xc0000005 Fault offset: 0x00015190 Faulting process id: 0x160 Faulting application start time: 0x01d1b804aaa52028 Faulting application path: D:\Program Files (x86)\nxlog\nxlog.exe Faulting module path: D:\Program Files (x86)\nxlog\libapr-1-0.dll Report Id: 79778f7a-2701-11e6-80c2-00155d590419 Faulting package full name: Faulting package-relative application ID: Is this a known issue? Are there ways to prevent this from happening? Thank you!

There were some bugs fixed in the EE recently which might be related, these fixes will be merged into the CE sometime soon. You could test the NXLog EE trial to confirm.