NXLog client failed to read config cache | Log collection solutions

#1 hatula 5 years ago

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

Permalink

#2 Zhengshi Nxlog ✓ 5 years ago

#1 hatula

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

This issue is normally seen when an older version of NXLog creates the /opt/nxlog/var/spool/nxlog/configcache.dat file, a newer version of NXLog is installed, and then tries to read the old version.
This is due to a format change in configcache.dat between certain versions (adding a version number in your case).

Resolution would be to stop NXLog service, remove /opt/nxlog/var/spool/nxlog/configcache.dat, start NXLog service.

Your 3.2.2002 version is quite old. It would be a good idea to update it when you can. There are a lot of fixes between that version and current.

Thank you,
jesse