Issues tables
Review the following tables for issues that were corrected in PATROL Agent for BMC Helix Operations Management 26.2 and for known issues that remain open.
Corrected issues | 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. |
|---|---|
Known (open) issues | To view only the open issues, click the Corrected in filter, and select empty. An issue without a value for Corrected in remains open. |
You can also filter and sort issues according to found version (version in which the issue was found), or defect ID.
Known and corrected product issues
| Description | Status | Found in | Defect ID |
|---|---|---|---|
When the PATROL Agent streams a high volume of metrics, data collection shows delays or gaps because the Agent uses a fixed chunk size and does not apply updated values until the service restarts. | Fixed in 26.2.00 | 26.1.01 | DRPIA-4724 |
When the PATROL Agent runs on AIX, the Agent crashes intermittently and generates a core dump. This issue occurs when the CurlEntryFun function does not handle invalid memory pointers correctly, which causes the process to abort. | Fixed in 26.2.00 | 25.4.00.001 | DRPIA-4770 |
When you install the PATROL Agent on AIX, the installation log shows a sed -i error because AIX does not support the sed -i option. | Fixed in 26.2.00 | 25.4.00 | DRPIA-4690 |
When PATROL Agent sends events with accented characters to BMC Helix Operations Management, the characters are displayed incorrectly. The issue occurs because the system locale is en_GB.CP1252 and not en_US.CP1252. The PATROL Agent can correctly handle accented characters only if the system locale is en_US.CP1252. | Fixed in 26.2.00 | 25.4.00 | DRPIA-4771 |
When you upgrade the PATROL Agent through BMC Helix Operations Management, the deployment job shows a SUCCESS status even though the Agent upgrade does not run or complete on the target system. This issue occurs because the Agent sends a success acknowledgment to BMC Helix Operations Management without validating the Common Installer execution result. | Fixed in 26.2.00 | 25.1.00 | DRPIA-4592 |
When the PATROL Agent uses a certificate chain to connect to BMC Helix Operations Management, the Agent reports the expiry of the first certificate in the chain instead of the certificate that is actually used for the connection. This issue occurs because certificate monitoring does not correctly identify the active certificate in the chain. | Fixed in 26.2.00 | 25.1.00 | DRPIA-3520 |