Error when editing Policies (Failed to load targets.: Internal report error)

[tobiasperschon 0]

Hi,

I noticed the following error when trying to edit e.g. Endpoint Policies.

If I click on "Change Assignments" for a policy or just go to the regular "edit" screen of a policy I get the Pop error: "Failed to load targets.: Internal report error"

In the tomcat log I see:

02-Feb-2023 01:07:01.539 SEVERE [http-nio-8080-exec-49] sk.eset.era.g2webconsole.server.modules.logger.LoggerWithPrefix.error [sysadmin] Call  failed on server. Reason: 'Internal report error'

in the ESET Server trace,log I see

2023-02-02 00:07:53 Error: CReportsModule [Thread 7ff5421d6700]: 3 MessageProcessorThread: Failed to generate a report: std::bad_alloc: GenerateReportRequest(id:51753, query-usage-definition-id:20, used-symbol-count:13)
2023-02-02 00:07:53 Error: CReportsModule [Thread 7ff5421d6700]: MsgGenerateReport: Query did not generate a report: MessageProcessorThread: Failed to generate a report: std::bad_alloc
2023-02-02 00:07:53 Error: ConsoleApiModule [Thread 7ff523198700]: 57 Error while processing GenerateReport request: MsgGenerateReport: Query did not generate a report: MessageProcessorThread: Failed to generate a report: std::bad_alloc

any ideas how to fix this? Thanks in advance!

Server infos:

Debian 10
java 17.0.5 2022-10-18 LTS
Java(TM) SE Runtime Environment (build 17.0.5+9-LTS-191)
Java HotSpot(TM) 64-Bit Server VM (build 17.0.5+9-LTS-191, mixed mode, sharing)

ESET:

ESET PROTECT (Server), Version 10.0 (10.0.2133.0)
ESET PROTECT (Web Console), Version 10.0 (10.0.132.0)

tomcat:

Using CATALINA_BASE:   /usr/share/tomcat9
Using CATALINA_HOME:   /usr/share/tomcat9
Using CATALINA_TMPDIR: /usr/share/tomcat9/temp
Using JRE_HOME:        /usr/lib/jvm/java-17-oracle
Using CLASSPATH:       /usr/share/tomcat9/bin/bootstrap.jar:/usr/share/tomcat9/bin/tomcat-juli.jar
NOTE: Picked up JDK_JAVA_OPTIONS:  --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.io=ALL-UNNAMED --add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED
Server version: Apache Tomcat/9.0.31 (Debian)
Server built:   Oct 25 2022 15:43:18 UTC
Server number:  9.0.31.0
OS Name:        Linux
OS Version:     4.19.0-23-cloud-amd64
Architecture:   amd64
JVM Version:    17.0.5+9-LTS-191
JVM Vendor:     Oracle Corporation

tomcat9 service is started with:

Environment="JAVA_HOME=/usr/lib/jvm/java-17-oracle"
Environment="JRE_HOME=/usr/lib/jvm/java-17-oracle"
Environment="JDK_JAVA_OPTIONS=--add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.io=ALL-UNNAMED --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.base/java.util.concurrent=ALL-UNNAMED --add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED"

Edited February 2, 2023 by tobiasperschon

[tobiasperschon 0]

In addition to the error I can't edit the policy assignments:

 

Edited February 2, 2023 by tobiasperschon

[Marcos 5,295]

Since this will require deeper investigation of logs, please open a support ticket for further troubleshooting of the issue.

[jst 0]

I am currently seeing the same issue occur with one of our instances. A temporary solution was re-download and installing the latest (version matching the Protect version) era.war package within tomcat and restarting the process. But the issue appears to keep coming back after some time.