Issues tables
Review the following tables for issues that were corrected in PATROL Agent for BMC Helix Operations Management 25.4 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 |
|---|---|---|---|
After you upgrade the PATROL Agent from version 22.1.00.05 to 25.2.00, the agent configured with the Linux knowledge module stops responding on RHEL. | Fixed in 25.4.00 | 25.2.00 | DRPIA-4053 |
When the proxy server experiences network or connectivity issues, the CPU usage of the PATROL Agent increases. | Fixed in 25.3.01 | 24.4.00 | DRPIA-3836 |
| The PATROL Agent does not include the host name and port number in the source_identifier event slot during event generation when the source_identifier slot is customized. | Fixed in 25.3.01 | 25.2.00 | DRPIA-3662 |
If the History Retention Period field is not configured, the PATROL Agent fails to report annotations in the Container Agent during event generation. | Fixed in 25.3.01 | 25.2.01 | DRPIA-3780 |
When you create annotations for knowledge modules, the PATROL Agent precedes them with the %Text string. | Fixed in 25.3.01 | 25.2.00 | DRPIA-3814 |
| If the password is not configured during PATROL Agent package creation, the pconfig variable fails to update the default account. | Fixed in 25.3.01 | 25.1.00 | DRPIA-3570 |
| The PATROL Agent version 25.1 stops responding shortly after it initializes on Solaris version 5.10. | Fixed in 25.3.01 | 25.1.00 | DRPIA-3773 |
| After a server restart, the PATROL Agent process starts with the root account instead of the default account. | Fixed in 25.3.01 | 25.1.00 | DRPIA-3651 |
When two proxies are configured, the PATROL Agent successfully connects to the next available proxy if it disconnects from the first. However, the error log fails to reflect this change accurately and displays the following message: Connecting forward proxy server http://xxxx.xx.x/3128 | Fixed in 25.3.01 | 24.3.00 | DRPIA-3441 |
| When the Agent switches from the root account to the default account user, the PATROL Agent fails to load the user profile. | Fixed in 25.3.01 | 25.2.00 | DRPIA-3854 |