responses
Hi,
This error is found in the logs nxlog client enterprise from time to time:
2018-12-26 00:00:00 INFO LogFile C:\nxlog\data\nxlog.log reopened
2018-12-26 00:00:00 INFO inode changed for 'C:\nxlog\data\nxlog.log' (79652->79655): reopening possibly rotated file
2018-12-26 00:00:11 ERROR failed to read config cache; string expected for config cache version
2018-12-26 00:00:11 ERROR exiting...
I use recommended configuration for nxlog client:
PersistLogqueue TRUE
SyncLogqueue TRUE
CacheFlushInterval always
CacheSync TRUE
<Input in>
Module im_file
File 'C:\logs\????-??-??.log'
BufferSize 2500000
SavePos TRUE
</Input>
<Output out>
BufferSize 9500000
Module om_batchcompress
Host 192.168.1.100
Port 1514
</Output>
Why is this happening? Thanks for any ideas!
I use
- client nxlog-3.2.2002
- server nxlog-4.1.4046
Comments (16)
Thank you for your reply!
I updated my nxlog client to version 4.1.4016 and still I have this error:
Any ideas? Thanks a lot!
Did you attempt to remove this file and see if it would be rebuilt correctly?
Yes, and file is created correct. But still, an error then occurs after a time.
It sounds like your file is getting corrupted somehow. We don't have any other issues open that are similar.
You could try changing
CacheDir
to somewhere else and see if that helps. Another volume, if you have one available.Thank you for your reply!
I have this problem on multiple hosts. The status of their disks is good, these hosts have not another problems. It seems that the problem occurs during the rotation of the log.
Here is what I see in the logs:
Windows application log
NXLog log
There was a fix to
file_cycle()
in NXLog EE v 4.2.4175. I believe this might might be relevant.I suggest testing the most recent version.
Thanks, b0ti, I will planned update. :)
And now I have a problem with the correct exit modules im_exec and im_msvistalog after system shutdown or reboot:
nxlog-4.2.4192 Windows 10
But Release Notes of this version sayed:
Any ideas, please. Thank you!
Do not crash if a module hangs on shutdown.
This does not look to be a module crashing, but the EventLog service shutting down before NXLog. That is why NXLog can not subscribe to the events, no events to subscribe to with the service down.
By default, Windows does not care much about shutdown order. Please see the following
https://docs.microsoft.com/en-us/windows/desktop/Services/service-control-handler-function
Thank you for yor comment!
It is look so strangle, but this case is not critical for me, thanks a lot!
Hi b0ti, after update I see this error as before:
Also I see crashed clients nxlog after rotation log file:
Any ideas, please!
nxlog-4.2.4216
was released a few days ago that should fix the log rotation deadlock.We could not reproduce the issue with the
configcache.dat
corruption.Hi b0ti,
after upgrade to version nxlog-4.2.4216 I still have this error with crash service nxlog:
It is very sad. Can you help me? Thanks a lot!
This entry is not actually an error message. It is midnight and your log rotate is happening.
Are you stating that your service crashing at the same time? Could you paste a matching EventLog message showing the service crashing?
I assume 10:49:56 is when you manually start the service again?
Yes, I know that this is a daily log rotation. Yes, I am absolutely sure that the service has crashed. Yes, I started service manually, and you can see it in the logs. Believe me.
Problem is actual.
I will watch to get more cases.
Thank you!