After modifying file reader memory via API detections server type becomes unknown
search cancel

After modifying file reader memory via API detections server type becomes unknown

book

Article ID: 394337

calendar_today

Updated On: 04-15-2025

Products

Data Loss Prevention Core Package

Issue/Introduction

While attempting to increase the file reader memory via API it was found that after a successful API call the detection server type changes to unknown, and becomes non functional.

Environment

DLP16.0.2 "RU2"  it was also found to be a problem in 16.1

Cause

The channel tables have a state column, such as "endpointchannel"

If you don't include the channels in your json request, it sets them all to 2, which is basically OFF

 

Resolution

This issues has been identified and will be resolved in 25.1.

As a work around ensure that your json command includes the box monitor channel to prevent it from defaulting to the nonfunctional channel type.

Example:

json: {"softwareServers": {"serverIds": [12], "serverSettings": {"BoxMonitor.Channels": ["Inline SMTP"], "BoxMonitor.FileReaderMemory": "-Xrs -Xms1200M -Xmx4G"}}}

You can also go into the detection server advanced settings in the GUI, and make any modification at all to box monitor channels, and save and it will correct the problem.