SystemEDGE 6.x excessive log file monitor log prints

Products

• SystemEDGE Agent

Issue/Introduction

Every time Sysedge reads a file, it checks each monitor entry until it finds the one that matches the log message.

All the other monitors without any matches are logged in the journal. Is there a way to suppress that?

The output comes from the system journal.

To access it I need to run journalctl command.

Example:

Feb 05 07:46:05 hostname CA-SystemEDGE.service[80727]: 1466880253 2024-02-05 07:46:05 WARNING  se/re.c[543]                     line_exec(): pcre2_match str=Feb  5 07:45:06 hostname 1242309: Feb  5 2024 12:44:>

Feb 05 07:46:05 hostname CA-SystemEDGE.service[80727]: 1466880254 2024-02-05 07:46:05 WARNING  se/re.c[552]                     line_exec(): called function pcre2_match_data_create_from_pattern rc=-1

Resolution

• There were a few code changes in the SystemEDGE-6.2\6.3 during the pcre2 library upgrade.
• The next SystemEDGE release will delete this log line print for 0 matches.
• In the meantime you can change the log level to critical to avoid the excess warning prints:

1. Stop SystemEDGE

In PORT#/sysedge.cf:

sysedge_loglevel critical

2. Start SystemEDGE

Additional Information

There is a defect created for this code work:

DE590938 -  Excessive systemedge pcre2  logging in version 6.3