The TSCO Gateway Manager and BPA General Manager reports error codes and includes a brief description of the problem. This document provides additional information on the most common error codes and references other documents where appropriate. These error codes are visible in the udrCollectStat command output which is the command line interface into UDR Collection Manager (UCM). |
For any error where the solution is not obvious or needs further details, please open a case with BMC Technical Support for assistance.
|
ID | SEVERITY | KEYWORD | DESCRIPTION | SOLUTION |
0 | Information | TOK | Normal Operation | No error |
1 | Error | ALERTNOCONDITIONS | No conditions in alert | Deprecated. User Error in setting up the Investigate Alert |
2 | Information | DRILLDOWNRECEIVED | Drill down request received | Informational status that an Investigate drill down request has been received. |
3 | Information | DRILLDOWNDELETED | Drill down request cleared | Informational status that an Investigate drill down request has been cleared. |
4 | Error | SELECTORBAD | Bad selector received in message | User Error in setting up the Investigate Drill down |
5 | Error | METRICBAD | Invalid metric request received | Most likely a mismatch between OS of agent and OS of group |
6 | Error | POLICYBAD | Policy file does not exist | Deprecated. User removed policy file |
7 | Warning | ALERTFAILED | Cannot reach agent for alert | Deprecated. Make sure the agent specified valid and is on the network |
8 | Warning | DELETEALERTFAILED | Cannot reach agent for clear | Deprecated. Make sure the agent specified valid and is on the network |
9 | Warning | DELETEGRAPHFAILED | Cannot reach agent to clear graph | Make sure the agent specified valid and is on the network |
10 | Warning | SUSPENDALERTFAILED | Cannot reach agent for suspend | Deprecated. Make sure the agent specified valid and is on the network |
11 | Warning | RESUMEALERTFAILED | Cannot reach agent for resume | Deprecated. Make sure the agent specified valid and is on the network |
12 | Warning | ACKALERTFAILED | Cannot reach agent for acknowledge | Deprecated. Make sure the agent specified valid and is on the network |
13 | Warning | GRAPHALERTFAILED | Cannot reach agent for graphing | Make sure the agent specified valid and is on the network |
14 | Warning | MGBFAILED | Cannot reach agent for drill down | Make sure the agent specified valid and is on the network |
15 | Warning | UPDATEFAILED | Cannot reach agent for update | Make sure the agent specified valid and is on the network |
16 | Error | OLDVERSION | Agent version too old to handle message | Upgrade your agent to a supported version |
17 | Information | AGENTSTOPPED | Agent has been stopped | Informational message that the TSCO Agent has been stopped by request. |
18 | Error | AGENTNOTSTOPPED | Cannot stop Agent | Agent Logs will provide information about why agent could not be stopped |
19 | Error | MAXCOLLECTRESTARTS | Maximum collector restarts exceeded - no data received | The 'Maximum collector restarts exceeded' typically indicates that the TSCO Agent data collection process is crashing or is unable to run on the machine. In many instances this will be due to an OS version specific problem that may be fixed in the latest agent patch set. Debugging steps:
|
20 | Error | COLLECTREGFAILED | Collector registration failed | The 'Collector registration failed' message occurs when the TSCO Agent is unable register the collection request for a metric group in the Collector Input Queue (CIQ). The most common causes for this problem are:
Typical workaround options:
|
21 | Error | UNAUTHORIZED_MESSAGE | Console user not authorized by agent to issue request | This error can occur if the user making the request from the TSCO Gateway Server is not authorized to access the remote agent based upon the BEST1_HOME/local/setup/Authorization.cfg file on the TSCO Agent. The most common sources of this error are a missing or corrupt Authorization.cfg file on the remote agent. Debugging:
|
22 | Error | SD_COMM_ERROR | Service Daemon communication error | Make sure the agent node specified is valid, and the service daemon is running. |
23 | Error | AGENT_START_ERROR | Cannot start agent | Make sure the bgsagent executable is located in $BEST1_HOME/bgs/bin/bgsagent, (%BEST1_COLLECT_HOME%\bgs\bin\bgsagent.exe on Windows). Additional information can be found in service daemon logs. |
24 | Warning | METRICGROUP_NOT_SUPPORTED | Metric group not supported | The TSCO Agent Collector supports data collection for metric groups that are not available on every remote agent. For example, the 'SRM Statistics' group will only be valid on Solaris machines running the Solaris Resource Manager but when the agent receives a collection request it will attempt to enable this group on the machine. The 'Metric group not supported' message indicates that the group happens to not be supported on this particular machine. In most cases this message can be ignored. |
25 | Warning | METRIC_NOT_SUPPORTED | Metric(s) not supported | The version of the operating system does not support the parameter |
26 | Error | REQUEST_NOT_SUPPORTED | Request not supported | Invalid request |
27 | Error | NO_DISK_SPACE | No disk space | Make sure you have enough disk space This message indicates that there is no disk space available in the target directory for the UDR data. If this error occurs during the data transfer phase that is an indication that there is insufficient disk space in the TSCO Gateway Server console data repository directory. |
28 | Error | SHMEM_GEN_ERROR | Shared memory error | Unable to allocate shared memory, memory exhausted or permission issue |
29 | Error | SEM_GEN_ERROR | Semaphore error | Unable to allocate semaphore, system out of semaphores or permission issue |
30 | Error | MEMORY_VIOLATION | Memory violation | Collector crashed you might need to patch the collector |
31 | Error | OUT_OF_MEMORY | Out of memory | The system ran out of memory and the collector exited |
32 | Warning | DB_SERVER_OFFLINE | Database Server off-line | Deprecated |
33 | Error | HISTORY_NOT_AVAILABLE | History not available | Related to an Investigate data request. Most likely a time range was specified outside of what is available in history. |
34 | Warning | METRICGROUP_NOT_AVAILABLE | Metric group not available | The TSCO Agent Collector supports data collection for metric groups that are not available on every remote agent. For example, the 'SRM Statistics' group will only be valid on Solaris machines running the Solaris Resource Manager but when the agent receives a collection request it will attempt to enable this group on the machine. The 'Metric group not supported' message indicates that the group happens to not be supported on this particular machine. In most cases this message can be ignored. |
35 | Error | PROXY_NOT_SUPPORTED | Proxy not supported | Deprecated. Very old versions of the TSCO Agent on Windows supported proxy data collection but this functionality no longer exists in the product. |
36 | Warning | REMOTE_COMPUTER_OFFLINE | Remote computer off-line | Deprecated. This message was associated with proxy data collection. The computer specified was unplugged from the network. |
37 | Error | REMOTE_COMPUTER_NOT_FOUND | Remote computer not found | Deprecated. This message was associated with proxy data collection. The network DNS server is not aware this computer is on the network |
38 | Error | SLOW_NETWORK_SPEED | Slow network speed between proxy and remote computer | Deprecated. This message was associated with proxy data collection. The network speed of the computer is below the threshold set in the proxy configuration |
39 | Error | ACCOUNT_UNAUTHORIZED | Account unauthorized | Deprecated. This message was associated with proxy data collection. The account specified in the proxy configuration does not have privileges to access this computer For additional information see KA 000095975: Setting status for [metric group] to ACCOUNT_UNAUTHORIZED' messages exist in the BPA bgscollect log file and data is not being collected for some groups (https://bmcsites.force.com/casemgmt/sc_KnowledgeArticle?sfdcid=000095975) |
40 | Error | ACCOUNT_UNDEFINED | Account undefined | Deprecated. This message was associated with proxy data collection. The account specified in the proxy configuration does not have configured on this computer |
41 | Error | OS_UNMATCHED | Operating System mismatch | This error typically occurs when either (a) The OS of the machine has been upgraded but the TSCO Agent hasn't been reinstalled (since on several platforms the TSCO Collector binary is OS version specific and the installation deploys the correct binary) or (b) The OS on which the TSCO Agent has been installed isn't supported. For additional information see KA 000293396: TrueSight Capacity Optimization (TSCO) data collection fails with error, "Operating System Mismatch - SYSTEM - Collector Information" (https://bmcsites.force.com/casemgmt/sc_KnowledgeArticle?sfdcid=000293396) |
42 | Error | ONESHOT_INVALID_REQUEST | Collect Request - Invalid fields in request | The request has been corrupted most likely by the network |
43 | Warning | ONESHOT_DUPLICATE_REQUEST | Collect Request - Duplicate request |
Data is being requested multiple times by either different consoles or manager runs. Data corruption or loss can take place if this is not corrected. For additional information see KA 000293394: TrueSight Capacity Optimization (TSCO) data collection fails with message "Collect request - Error: duplicate collect request not scheduled ([nodename]:noInstance)" in the agent log file. (https://bmcsites.force.com/casemgmt/sc_KnowledgeArticle?sfdcid=000293394) |
44 | Error | ONESHOT_NOLOCALREPOSITORY | Collect Request - Agent Repository (Local Repository) does not exist |
Either the default agent repository specified in the BEST1_HOME/bgs/mgroup/Repository.loc file doesn't exist or the agent data repository specified in the domain/policy file for this computer doesn't exist. See KA 000299047: TrueSight Capacity Optimization (TSCO) Agent error: MrHistory::populate - ERROR: Error accessing repository root directory /usr/local/bmc/perform/history (https://bmcsites.force.com/casemgmt/sc_KnowledgeArticle?sfdcid=000299047) |
45 | Error | ONESHOT_INVALID_TIMERANGE | Collect Request - Invalid time range | The time specified in the collection request is invalid |
46 | Error | ONESHOT_NO_METRIC_GROUPS | Collect Request - No Metric groups enabled |
This problem occurs when the TSCO Agent has invalidated the collection for all of the requested metric groups.
Typical reasons are:
The following document describes the most common reasons this happens and resolution options: KA 000306678: TrueSight Capacity Optimization (TSCO) Agent data collection is never started with error "ERROR: No Metric Groups Enabled" even though the computer initially seems to accept the collection request (https://bmcsites.force.com/casemgmt/sc_KnowledgeArticle?sfdcid=000306678) |
47 | Information | ONESHOT_COLLECT_PENDING | Collect Request - Data Collection pending | Nothing to worry about, the collection request will take place at a later time. This is a status most commonly seen in the 'best1collect -Q' collector query output for 'Days in Advance' data collection requests. These are requests pre-registered with the TSCO Agent by the nightly Manager runs for collection in the following days. |
48 | Information | ONESHOT_COLLECT_ACTIVE | Collect Request - Data Collection active | Collecting data without errors. |
49 | Information | ONESHOT_UDR_WRITE_ACTIVE | Collect Request - Agent repository write active | Collecting data without errors. This is a status most commonly seen in the 'best1collect -Q' collector query output for the active current day's data collection request. |
50 | Information | ONESHOT_COLLECT_COMPLETE | Collect Request - Data Collection Complete | Collected data |
51 | Error | ONESHOT_TRANSFER_NODIR | Collect Request - Agent transfer directory does not exist | Unable to find the specified data |
52 | Information | ONESHOT_TRANSFER_LOCAL_SUCCESS | Collect Request - Agent data transfer successful | Data transferred |
53 | Error | ONESHOT_TRANSFER_LOCAL_FAILURE | Collect Request - Agent data transfer failed | Data transfer failed, you may want to increase the data transfer window |
54 | Information | ONESHOT_TRANSFER_SUCCESS | Collect Request - Agent data transfer successful | Data transferred |
55 | Error | ONESHOT_TRANSFER_FAILURE | Collect Request - Agent data transfer failed | Data transfer failed, you may want to increase the data transfer window |
56 | Information | ONESHOT_FILE_AUTO_DELETE | Collect Request - Data deletion in Agent repository pending | Data has been transferred. |
57 | Information | ONESHOT_REPOSITORY_DELETED | Collect Request - Data deleted in Agent repository | Data has been transferred. |
58 | Information | ONESHOT_REQUEST_COMPLETE | Collect Request - Processing complete | Data collected. |
59 | Information | ONESHOT_STOP_REQUEST | Collect Request - Stop request received | Collection request has been stopped. |
60 | Error | GEN_FAILURE | General Failure | Unknown and unexpected error |
61 | Error | REMOTE_COMPUTER_NO_OS | Cannot determine Operating System of remote computer | The proxy agent was not able to determine the operating system of the agentless computer |
62 | Error | DB_ERROR | Database Server error encountered | Deprecated |
63 | Error | SHMEM_KEY_CREATE_ERROR | Error creating key for shared memory segment | Check shared memory permission |
64 | Error | SHMEM_SIZE_LIMIT | Shared memory size limit error | Shared memory limit reached, reconfigure shared memory |
65 | Error | SHMEM_ACCESS_ERROR | No permission to access shared memory segment | No permission to create shared memory |
66 | Error | SHMEM_NO_MEM | Shared memory size exceeds available memory | Shared memory limit reached, shared memory to be reconfigured |
67 | Error | SHMEM_NO_SPACE | Error creating shared memory segment - No more IDs available | The most common cause of this error is that a system imposed limit on shared memory segments has been reached and the system needs to be reconfigured to allow additional shared memory segments to be created. See |
68 | Error | SHMEM_ATTACH_ERROR | Error attaching to shared memory segment | Most likely shared memory permission issue |
69 | Error | SEM_FILE_CREATE_ERROR | Error creating file used for semaphore key | The TSCO agent (bgsagent) creates files in the BEST1_COLLECT_HOME/bgs/monitor/tmp directory that it uses to access shared memory. If this directory doesn't exist or the TSCO Agent Installation Owner account doesn't have write access to this directory this error will be generated. Remediation:
|
70 | Error | SEM_FILE_OPEN_ERROR | Error opening file used for semaphore key | The TSCO Agent creates files in the BEST1_COLLECT_HOME/bgs/monitor/tmp directory that it uses to access shared memory and the semaphores that control shared memory access. If this directory doesn't exist or the TSCO Agent Installation Owner account doesn't have write access to this directory this error will be generated. Remediation:
|
71 | Error | SEM_ACCESS_ERROR | No permission to access semaphore | User does not have permission to access resource |
72 | Error | SEM_NO_SPACE | Error creating semaphore - No more IDs available | The most common cause of this error is that a system imposed limit on semaphore creation has been reached and the system needs to be reconfigured to allow additional semaphores to be created. See KA 000320239: 'Error creating semaphore - No more IDs available' reported for groups failing to collect data via the TrueSight Capacity Optimization (TSCO) Capacity Agent (https://bmcsites.force.com/casemgmt/sc_KnowledgeArticle?sfdcid=000320239) |
73 | Error | SEM_CREATE_ERROR | Error creating semaphore | Reconfigure semaphore limits |
74 | Error | SEM_LOCK_ERROR | Error creating lock using semaphore | Reconfigure system lock limits |
75 | Error | ONESHOT_NODESTREPOSITORY | Collect Request - Console repository (Destination repository) does not exist | The TSCO Gateway Server console UDR data repository has been moved or deleted |
76 | Error | ONESHOT_NOBEST1COLLECTHOME | Collect Request - Best1 collect home does not exist | The best1home specified is invalid |
77 | Error | ONESHOT_NOLOCALPERMISSION | Collect Request - No permission on Agent repository (Local repository) | This error occurs when either the default history repository specified in the BEST1_COLLECT_HOME/bgs/mgroup/Repository.loc file or the agent data repository specified in the domain/policy file for the computer doesn't exist or the TSCO Agent Installation Owner doesn't have write permissions to that directory. Remediation:
|
78 | Error | ONESHOT_NODESTPERMISSION | Collect Request - No permission on Console repository (Destination repository) | This error occurs when directory where UDR data should be transferred on the console does not have sufficient write permissions for the TSCO Gateway Server Installation Owner. Remediation:
|
79 | Warning | ONESHOT_DATA_NOT_COLLECTED | Collect Request - Data not collected for metric group | The collector does not support this group, or a collector patch might be required |
80 | Warning | NO_DATA_AVAILABLE | Metric group currently has no data available for collection | The collector does not support this group, or a collector patch might be required |
81 | Error | PATROL_HOME_NOT_SPECIFIED | Patrol Home directory not specified | Deprecated |
82 | Error | COLLECT_METHOD_NOT_AVAILABLE | Collection method not available | Deprecated |
83 | Error | COLLECT_METHOD_FAILURE | Error executing collection method | Deprecated |
84 | Error | MISSING_PARAMS | Namespace parameter(s) missing from data source | Deprecated |
85 | Error | ONESHOT_NOLOCALPERMISSION_NODE | Collect Request - No data or permission on Agent repository (Local repository) for node | This message occurs when the specified agent repository exists, and either the hostname sub-directory for the collection request already exists but the TSCO Agent Installation Owner doesn't have write access or less commonly doesn't exist (since typically if it didn't exist the TSCO Agent would just create it). Remediation:
|
86 | Error | ONESHOT_NOLOCALPERMISSION_INSTANCE | Collect Request - No data or permission on Agent repository (Local repository) for instance | This message occurs when the specified agent repository exists, the hostname sub-directory exists, and the 'noInstance' directory under that exists but the TSCO Agent Installation Owner doesn't have write access or less commonly doesn't exist (since typically if it didn't exist the TSCO Agent would just create it). Remediation:
|
87 | Error | ONESHOT_NOLOCALPERMISSION_TIME | Collect Request - No data or permission on Agent repository (Local repository) for time | This message means that the collection request was sent to the agent, it was accepted, and the agent was expected to be collecting the data but when the console made the data transfer request the data didn't exist in the Agent Repository. One common source of this error is the agent is part of multiple Manager runs (typically across different consoles) and one Manager run has transferred and deleted the data before the other Manager run has initiated the transfer. Check the [hostname]-bgSD.log for multiple consoles sending start collection or transfer requests. Another possible cause is that the TSCO Agent is accepting the collection request but the bgscollect process PID is in a state where it can't collect data. For example, this can happen on Windows if the bgscollect.exe process fails with a MEMORY_VIOLATION but the process doesn't fully terminate. See KA 000218343: TrueSight Capacity Optimization (TSCO) - Agent data transfer failing with Error 87: 'Collect Request - No data or permission on Agent repository (Local repository) for time' (https://bmcsites.force.com/casemgmt/sc_KnowledgeArticle?sfdcid=000218343) |
88 | Error | ONESHOT_NOLOCALPERMISSION_GROUP | Collect Request - No data or permission on Agent repository (Local repository) for group | The agent repository metric group directory level does not exist or user does not have permission to access |
89 | Error | ONESHOT_DELETE_COLLECT_ACTIVE | Collect Request - Collect still active unable to delete | Possible time skew between console and agent node, make sure agent time and console time is synchronized |
90 | Error | ONESHOT_DELETE_NO_PERMISSION | Collect Request - No permission to delete Agent repository | Check agent repository permission |
91 | Error | SD_COMM_BAD_HOST | Service daemon invalid host name provided (can not find server or DNS error) | This typically means that the specified hostname for data collection isn't defined in DNS or doesn't exist on the network anymore. Verify that the hostname specified is correct and that the computer is accessible over the network using that hostname. Remediation:
TSCO Gateway Server version 10.5 and 10.7: Defect QM002309064 causes this error code to be used for any agent that is unreachable (so any agent where the TSCO Gateway Server can't access the Service Daemon on port 10128). That problem has been fixed in Cumulative Hot Fix (CHF) package 10.5.00.01.C00010 and 10.7.01.00.C00002 and later.
|
92 | Error | SD_COMM_BAD_PORT | Service daemon not installed on the remote node (connection refused) | This message means that the TSCO Gateway Server was unable to initiate a connection to port 10128 on the remote node and the remote computer responded with a 'connection refused' message. This typically occurs when:
For debugging suggestions see KA 000330057: TrueSight Capacity Optimization (TSCO) - Debugging Service Daemon connection problems for the Gateway Server/Agent (https://bmcsites.force.com/casemgmt/sc_KnowledgeArticle?sfdcid=000330057) |
93 | Error | SD_COMM_BAD_PROTOCOL | Service daemon protocol terminated in the middle of session (network or disk timeout) |
This error may occur due to network communication problems between the TSCO Gateway Server and the remote TSCO Agent during the data transfer. Sometimes problems on the remote agent side itself (which will typically be more visible in the logs on the TSCO Agent machine itself) may also trigger this problem. See KA 000320659: UDR data transfer back to the TrueSight Capacity Optimization (TSCO) Gateway Server is failing for some or all machines. Error, "Service daemon protocol terminated in the middle of session network or disk timeout)" (https://bmcsites.force.com/casemgmt/sc_KnowledgeArticle?sfdcid=000320659) for additional information. |
94 | Error | SD_COMM_CONNECT_TIMEOUT | Service daemon connection timed out (node offline) | The agent node is off the network. This message means that the TSCO Gateway Server was unable to initiate a connection to port 10128 on the connection attempt timed out. This typically occurs when:
For debugging suggestions see KA 000330057: TrueSight Capacity Optimization (TSCO) - Debugging Service Daemon connection problems for the Gateway Server/Agent (https://bmcsites.force.com/casemgmt/sc_KnowledgeArticle?sfdcid=000330057) |
95 | Information | ONESHOT_COLREQ_SENT | Collect request sent from console and received by the agent | No issues |
96 | Error | ONESHOT_COLREQ_PERIOD_TIMEOUT | Collect request not successfully sent to the agent during the time period allowed | The time to sent the request has expired |
97 | Error | ONESHOT_DATA_DELETION_FAILED | Request to delete data from agent repository failed after successful transfer | Manually remove the agent data from the agent repository |
98 | Warning | ONESHOT_MISSING_GROUPS | No data collected for some of the configured metric groups | Most likely the groups specified are not supported by the collector |
99 | Error | ONESHOT_QUERY_MISSING_REQUEST | Collect request not scheduled in agent | The request has been sent by the agent, but has been removed. |
100 | Error | ONESHOT_NO_GROUPS_COLLECTED | No data collected for all of the configured metric groups | The collector did not collect any groups, you might need a collector patch |
101 | Error | ONESHOT_PULL_COLLECT_ACTIVE | Collect Request - Collect still active unable to transfer | Most likely there is a time skew between the console and the agent. Make sure the agent and the console are synchronized. |
102 | Error | ONESHOT_TRANSFER_PERIOD_TIMEOUT | Collected data not successfully transferred from agent computer during the time period allowed |
You can increase the transfer time. This problem occurs when the TSCO Gateway Server has run out of time in the transfer window to transfer data from the remote TSCO Agent. This can happen when the number of available transfer slots is too low or if there is a data transfer performance problem that is making the transfer run too slowly. See KA 000309789: TrueSight Capacity Optimization (TSCO) Gateway Server nightly Manager run UDR data transfer failing with error, "Collected data not successfully transferred from agent computer during the time period allowed" (https://bmcsites.force.com/casemgmt/sc_KnowledgeArticle?sfdcid=000309789) |
103 | Error | ONESHOT_DELETE_PERIOD_TIMEOUT | Collected data not deleted from agent repository during the time period allowed | Manually remove the agent data from the agent repository |
104 | Information | ONESHOT_STOP_REQUEST_SENT | Stop collection request sent from console and received by the agent | Collection has been stopped |
105 | Information | ONESHOT_COLREQ_ALREADY_SCHEDULED | Collect request is already scheduled at the agent | Collection has been scheduled previously |
106 | Error | ONESHOT_TRANSFER_RENAME_FAILED | Transferred data _TMP start time directory could not be renamed | Manually rename the _TMP directory |
107 | Error | SD_COMM_BAD_PROTOCOL_START | Service daemon protocol terminated in the start of session (no bgssd executable or another application using port) | This means that the TSCO Gateway Server was able to successfully connect to the Service Daemon port (10128) on the remote TSCO Agent but received an unexpected response. Some common reasons for this to occur are:
Typically the debugging steps in KA 000330057: TrueSight Capacity Optimization (TSCO) - Debugging Service Daemon connection problems for the Gateway Server/Agent (https://bmcsites.force.com/casemgmt/sc_KnowledgeArticle?sfdcid=000330057) |
108 | Error | SD_CANNOT_REACH_AGENT | Service daemon unable to send message to agent (bgsagent is too busy) | This error typically means that the TSCO agent process (bgsagent) master thread is too busy to respond to the messages being sent by the Service Daemon. This error was most typically seen when communicating with a proxy host (functionality that no longer exists). Remediation:
If the problem persists open an issue with Technical Support and provide the logs from the TSCO Agent machine. |
109 | Error | GROUP_DISABLED | Metric group has been disabled | Enable the metric group if you would like to get data for the group. |
110 | Error | COLLECTOR_CRASHED | Collector has crashed | You may need a patch for the collector. |
111 | Error | OPENSSH_NOT_INSTALLED | SSH is not installed | You may need to configure the parameter using /usr/adm/best1_V.V.VV/bgs/scripts/configure_openssh (where V.V.VV is the product version, for example, 20.02.00) |
112 | Error | OPENSSH_MISSING_CONFIG_FILE | SSH could not find config file | You may need to configure the parameter using /usr/adm/best1_V.V.VV/bgs/scripts/configure_openssh (where V.V.VV is the product version, for example, 20.02.00) |
113 | Error | OPENSSH_MISSING_KEY_FILE | SSH could not find key file | You may need to configure the parameter using /usr/adm/best1_V.V.VV/bgs/scripts/configure_openssh (where V.V.VV is the product version, for example, 20.02.00) |
114 | Error | OPENSSH_MISSING_KNOWNHOSTS_FILE | SSH could not find known_hosts file | You may need to configure the parameter using /usr/adm/best1_V.V.VV/bgs/scripts/configure_openssh (where V.V.VV is the product version, for example, 20.02.00) |
115 | Error | OPENSSH_PASSWORD_AUTHENTICATION | SSH using password authentication | You may need to configure the parameter using /usr/adm/best1_V.V.VV/bgs/scripts/configure_openssh (where V.V.VV is the product version, for example, 20.02.00) |
116 | Error | OPENSSH_STRICT_HOST_KEY_CHECKING | SSH not using strict host key checking | You may need to configure the parameter using /usr/adm/best1_V.V.VV/bgs/scripts/configure_openssh (where V.V.VV is the product version, for example, 20.02.00) |
117 | Error | OPENSSH_KEY_MISCONFIGURED | SSH key file misconfigured | You may need to configure the parameter using /usr/adm/best1_V.V.VV/bgs/scripts/configure_openssh (where V.V.VV is the product version, for example, 20.02.00) |
118 | Error | OPENSSH_MISSING_REMOTEHOST | SSH remote host not found in known_hosts file | You may need to configure the parameter using /usr/adm/best1_V.V.VV/bgs/scripts/configure_openssh (where V.V.VV is the product version, for example, 20.02.00) |
119 | Error | OPENSSH_REMOTE_COMMANDS_DISABLED | SSH could not execute command on remote host (remote commands disabled) | |
120 | Error | OPENSSH_PERMISSION_DENIED | SSH could not execute command on remote host (permission denied) | |
121 | Error | COLLECTOR_TRANSIENT_TIMEOUT | Transient collection timeout occurred (will try again next interval) | If this error persists you may need a collector patch |
122 | Error | COLLECTOR_UNRECOVERABLE_TIMEOUT | Unrecoverable collection timeout occurred (will no longer try again) | Unable to collect group, you may need a collector patch |