Issues tables

View the issues in the following table by the default sort order, Corrected in, which shows the corrected issues first. 

The version number represents the update (Year-Month-Day) in which the issue is fixed.

To view only the open issues, click the Corrected in filter, and select empty. An issue without a value for Corrected in remains open.

When you install the PATROL Agent, the installation log file does not display the group name of the configured Agent.

When the host machine where PATROL Agent is installed has an internal and a public IP address, the PATROL Agent does not select the correct IP address. The Agent should use the public IP if it is configured via the /AgentSetup/publishConnectingIPAddress pconfig variable; otherwise, it should use the internal IP.

25.4.00

DRPIA-4420

When you upgrade the PATROL Agent through BMC Helix Operations Management by deploying a new PATROL Agent package, the PatrolAgent.service file contains incorrect values, and the PATROL Agent does not restart.

DRPIA-4217

On some Linux machines, the PATROL Agent fails to retrieve the system serial number or product number.

DRPIA-4223

When the hostname and the IP address of the server are changed, the PATROL Agent version 25.1.00 fails to restart.

DRPIA-4108

After you install the PATROL Agent, the process ID (PID) reported by the ps-ef | grep PatrolAgent command is not synchronized with the PID shown by the systemctl status PatrolAgent command, resulting in inconsistent process information.

DRPIA-4259