Create a Post
cancel
Showing results for 
Search instead for 
Did you mean: 
PetterD
Collaborator
Jump to solution

Log Exporter stopped working in R82.10 T50


Hello,

I recently upgraded (advanced migration to new VM) a R81.20 SmartCenter/Log Server to R82.10 Take 50.
Have been running Log Exporter for a long time, configured on the SmartCenter object.
Logging works fine, viewing indexed logs and fw.log in SmartConsole works and logswitch does nothing.

Currently have a case with TAC aswell, just curious if anyone else have seen this issue.
When/if I get a resolution from TAC i will update.



The issue is;

After the advanced migration, when checking "cp_log_export status" i could see that it was not running, although "cp_log_export show" showed the configuration that was on the SmartCenter object.


To investigate further we removed the configuration from the SmartCenter object and added it manually via CLI;


#cp_log_export add name LogExporterTest target-server 1.2.3.4 target-port 1234 protocol tcp format splunk read-mode raw --apply-now



However it still fails to start and in the log_indexer.elg we see that it tries to access "/opt/CPrt-R82.10/bin/conf/SplunkFieldsMapping.xml".


Output from log_indexer.elg after adding it:

[log_indexer 937531 4157140032]@fwmngt[4 Nov 15:18:00] log_indexer: Wed Nov 4 15:18:00 2026
[4157140032][4 Nov 15:18:00] Set process priority to 19
[4157140032][4 Nov 15:18:00] ExportConfiguration::init working dir path:/opt/CPrt-R82.10/log_exporter/targets/LogExporterTest
[4157140032][4 Nov 15:18:00] ExportConfiguration::init target conf path:/opt/CPrt-R82.10/log_exporter/targets/LogExporterTest/targetConfiguration.xml
[4157140032][4 Nov 15:18:00] ExportConfiguration::getWebSslPortFromFile - setting web ssl port to 4434
[4157140032][4 Nov 15:18:00] DestinationConfiguration::init - Destination type: [syslog]
[4157140032][4 Nov 15:18:00] EnrichmentConfiguration::init - domain name won't be exported in the field: domain
[4157140032][4 Nov 15:18:00] EnrichmentConfiguration::init - orig_log_server won't be exported
[4157140032][4 Nov 15:18:00] SourceConfiguration::init: - Reading logs mode is raw
[4157140032][4 Nov 15:18:00] SourceConfiguration::init - read log files from directory: [/opt/CPsuite-R82.10/fw1/log]
[4157140032][4 Nov 15:18:00] ExportConfiguration::setLinkIP - export_link_ip is set to default
[4157140032][4 Nov 15:18:00] FormatTypeMetadataFactory::create - Creating FormatTypeMetadata for the type: [splunk]
[4157140032][4 Nov 15:18:00] FormatTypeMetadataFactory::create - Format Metadata default format definition: [/opt/CPrt-R82.10/bin/conf/SplunkFormatDefinition.xml]
[4157140032][4 Nov 15:18:00] FormatTypeMetadataFactory::create - Format Metadata default fields mapping: [/opt/CPrt-R82.10/bin/conf/SplunkFieldsMapping.xml]
[4157140032][4 Nov 15:18:00] ResolverConfiguration::init - Fields mapping file is not set, using default: [/opt/CPrt-R82.10/bin/conf/SplunkFieldsMapping.xml]
[4157140032][4 Nov 15:18:00] ExportConfiguration::init failed to parse /opt/CPrt-R82.10/log_exporter/targets/LogExporterTest /opt/CPrt-R82.10/bin/conf/SplunkFieldsMapping.xml: cannot open file
[4157140032][4 Nov 15:18:00] LogsExporter::Start configuration initialization failure - exiting.
[4157140032][4 Nov 15:18:00] export_log_main:: Existing with code -1
[Expert@fwmngt:0]#

##########


After copying SplunkFormatDefinition.xml & SplunkFieldsMapping.xml to "/opt/CPrt-R82.10/log_exporter/targets/LogExporterTest/conf" and then editing "/opt/CPrt-R82.10/log_exporter/targets/LogExporterTest/targetConfiguration.xml" and changing these lines:

From: <formatHeaderFile></formatHeaderFile>
To: <formatHeaderFile>conf/SplunkFormatDefinition.xml </formatHeaderFile>

From: <mappingConfiguration></mappingConfiguration><!--if empty the fields are sent as is without renaming-->
To: <mappingConfiguration>conf/SplunkFieldsMapping.xml</mappingConfiguration><!--if empty the fields are sent as is without renaming-->

I was then able to start the Log Exporter manually but it stops after a few seconds..

 

The log_indexer.elg now contains the following messags;

og_indexer 731305 4048542400]@fwmngt[4 Nov 15:30:23] CBinaryLogFile::ReadLog: failed to find FileIdFormat=10 in m_FormatIdFileToMem, malformed log in file /opt/CPsuite-R82.10/fw1/log/2026-11-04_000000.adtlog
[4048542400][4 Nov 15:30:23] CpLogReader::ReadNext: ReadNextLog returned error while reading log file: /opt/CPsuite-R82.10/fw1/log/2026-11-04_000000.adtlog cpresult= -2147467259, error message: unspecified error
[4048542400][4 Nov 15:30:23] LogFetcherFiles::FileReadSession: failed to read from 2026-11-04_000000.adtlog; position 159
[log_indexer 731305 4048542400]@fwmngt[4 Nov 15:30:23] CBinaryLogFile::ReadLog: failed to find FileIdFormat=10 in m_FormatIdFileToMem, malformed log in file /opt/CPsuite-R82.10/fw1/log/2026-11-04_000000.adtlog
[4048542400][4 Nov 15:30:23] CpLogReader::ReadNext: ReadNextLog returned error while reading log file: /opt/CPsuite-R82.10/fw1/log/2026-11-04_000000.adtlog cpresult= -2147467259, error message: unspecified error
[4048542400][4 Nov 15:30:23] LogFetcherFiles::FileReadSession: failed to read from 2026-11-04_000000.adtlog; position 160


I found sk1000275, however cpinfo -yall contains the "BUNDLE_LOGEXPORTER_AUTOUPDATE" and according to "autoupdater cli show" we`re running "Check_Point_LOGEXPORTER_AUTOUPDATE_Bundle_linux80_T70_FULL.tgz"



CCSM / CCSE / CCVS / CCTE
0 Kudos
1 Solution

Accepted Solutions
nooni
Collaborator
Collaborator

Hi,

It seems like the cp_log_exporter is not being updated automatically.

https://support.checkpoint.com/results/sk/sk182866

I am not sure if this is an issue in R82.10 or if this is something that has been in previous versions also.

I updated as per this sk and thing started working again, it looks like you have Take70 but Take82 was released... today ? 🙂

 

 

 

View solution in original post

3 Replies
nooni
Collaborator
Collaborator

Hi,

It seems like the cp_log_exporter is not being updated automatically.

https://support.checkpoint.com/results/sk/sk182866

I am not sure if this is an issue in R82.10 or if this is something that has been in previous versions also.

I updated as per this sk and thing started working again, it looks like you have Take70 but Take82 was released... today ? 🙂

 

 

 

PetterD
Collaborator

Thanks! I was thinking about doing a manual upgrade and asked TAC about it, also checked another customer running same version of both CP and Log Exporter (T70) with two identical log exporter setups where everything was working.

Though it also seemed they had more XML files than this installation for some reason, so it looks like the log exporter installation is fubar here 😅

If I dont hear anything from TAC I’ll probably just try the manual update tomorrow, not sure if it will fix a potentially fubar log exporter installation but i guess I will find out;)

On the other identical install/versions there was no need to manually copy/reference the xml files

CCSM / CCSE / CCVS / CCTE
0 Kudos
PetterD
Collaborator

Just wanted to add that after manually upgrading Log Exporter to Take 82 from https://support.checkpoint.com/results/sk/sk165653 and re-creating the Log Exporter setup with "cp_log_export add" the complaining about missing XML-files, crashing service and complaining about unable to read the logfiles suddently dissappeared..

Log Exporter has now successfully started and processing/sending logs! 🙂 

CCSM / CCSE / CCVS / CCTE

Leaderboard

Epsum factorial non deposit quid pro quo hic escorol.

Upcoming Events

    CheckMates Events