Veritas Cluster Server Bundled Agents Reference Guide
Veritas⢠Cluster Server Bundled Agents Reference Guide - Symantec Veritas⢠Cluster Server Bundled Agents Reference Guide - Symantec
206 Troubleshooting bundled agents Troubleshooting services and application agents The user information specified in the UserAccount information is different from the user information, in whose context the service will run. Recommended Action: Stop the service and modify the user information. Re-issue the online command. Theservice‘Service_Name’sharesthesameprocesswithotherservices.Killing it might affect those services If the service has an invalid state, the agent attempts to offline the service. The agent fails to offline the service, if the process is shared with other services. In such cases, the agent attempts to kill the shared process. You risk potential data loss. Failed to enable the ‘Privilege_Name’ privilege. Error = Error Code The agent failed to enable the privilege required to kill a process. See the Windows error code for further information. Failed to open the service ‘Service_Name’. Error = Error Code The resource definition in the configuration file contains an invalid, or incorrect service name. Recommended Action: Verify the ServiceName attribute defined in the configuration file is the same as the display name used by SCM. Verify that the specified service was opened successfully. Failed to query the status of the service ‘Service Name’. Error = Error Code The agent failed to determine the status of the service. This is a VCS internal error. Recommended Action: Offline and online the service group. Contact Symantec Technical Support if the problem persists. The service ‘Service_Name’ is not in running state. Attempt to stop it might be unsuccessful. The agent failed to offline the service because the service is not in STARTED state. Recommended Action: Verify the state of the service and re-issue the online command. The service ‘Service_Name’ did not stop. Error = Error Code. The agent failed to stop the specified service. Recommended Action: Verify the binaries for the specified service exist, or the service is configured to run in the context of the specified user. Stop the service manually if the problem persists. The service ‘Service_Name’ did not stop within the specified timeout. Error = Error Code
Troubleshooting bundled agents Troubleshooting services and application agents 207 The agent failed to offline the service within the time specified in the DelayAfterOffline attribute. Recommended Action: Verify the state of the service in the SCM. If the state of the service is STOP PENDING, increase the time specified in DelayAfterOffline. If the problem persists, stop the service manually. ServiceMonitor agent error messages The ServiceOrScriptName attribute has not been configured No value specified for the ServiceorScriptName attribute. Recommended Action: Verify the ServiceorScriptName attribute defined in the configuration file is assigned a value. Failed to lookup the account name ‘Account_Name’. Error = Error Code The agent failed to obtain the SID for the specified user. Recommended Action: Verify that the domain controller is accessible, or the specified user exists. See the error code if the problem persists. The password attribute has not been configured No value specified for the Password attribute. Recommended Action: Verify the Password attribute defined in the configuration file is assigned a value and contains alphabets only. Failed to get the password attribute. Error = Error Code The agent failed to decrypt the specified password. Recommended Action: Verify that the password is encrypted using the VCS Encrypt utility (described in the Veritas Cluster Server Administrator's Guide). Failed to convert the password attribute. Error = Error Code The agent failed to convert the password attribute. This is a VCS internal error. Recommended Action: Offline and online the service group. Contact Symantec Technical Support if the problem persists. Failed to open the SCM handle. Error = Error Code The agent failed to obtain the SCM handle. This occurs if the SCM database does not exist, or if the SCM manager denies the requested access. Recommended Action: Verify that SCM can be run on the host. Failed to open the service ‘Service_Name’. Error = Error Code The resource definition in the configuration file contains an invalid, or incorrect service name.
- Page 155 and 156: VCS infrastructure and support agen
- Page 157 and 158: VCS infrastructure and support agen
- Page 159 and 160: VCS infrastructure and support agen
- Page 161 and 162: Chapter 8 VCS hardware replication
- Page 163 and 164: VCS hardware replication agent for
- Page 165 and 166: VCS hardware replication agent for
- Page 167 and 168: VCS hardware replication agent for
- Page 169 and 170: VCS hardware replication agent for
- Page 171 and 172: Chapter 9 Troubleshooting bundled a
- Page 173 and 174: Troubleshooting bundled agents Trou
- Page 175 and 176: Troubleshooting bundled agents Trou
- Page 177 and 178: Troubleshooting bundled agents Trou
- Page 179 and 180: Troubleshooting bundled agents Trou
- Page 181 and 182: Troubleshooting bundled agents Trou
- Page 183 and 184: Troubleshooting bundled agents Trou
- Page 185 and 186: Troubleshooting bundled agents Trou
- Page 187 and 188: Troubleshooting bundled agents Trou
- Page 189 and 190: Troubleshooting bundled agents Trou
- Page 191 and 192: Troubleshooting bundled agents Trou
- Page 193 and 194: Troubleshooting bundled agents Trou
- Page 195 and 196: Troubleshooting bundled agents Trou
- Page 197 and 198: Troubleshooting bundled agents Trou
- Page 199 and 200: Troubleshooting bundled agents Trou
- Page 201 and 202: Troubleshooting bundled agents Trou
- Page 203 and 204: Troubleshooting bundled agents Trou
- Page 205: Troubleshooting bundled agents Trou
- Page 209 and 210: Troubleshooting bundled agents Trou
- Page 211 and 212: Troubleshooting bundled agents Trou
- Page 213 and 214: Troubleshooting bundled agents Trou
- Page 215 and 216: Troubleshooting bundled agents Trou
- Page 217 and 218: Troubleshooting bundled agents Trou
- Page 219 and 220: Index Symbols
- Page 221 and 222: Index 221 FileOnOnly agent (continu
- Page 223 and 224: Index 223 Process agent agent funct
Troubleshooting bundled agents<br />
Troubleshooting services and application agents<br />
207<br />
The agent failed to offline the service within the time specified in the<br />
DelayAfterOffline attribute.<br />
Recommended Action: Verify the state of the service in the SCM. If the state of<br />
the service is STOP PENDING, increase the time specified in DelayAfterOffline.<br />
If the problem persists, stop the service manually.<br />
ServiceMonitor agent error messages<br />
The ServiceOrScriptName attribute has not been configured<br />
No value specified for the ServiceorScriptName attribute.<br />
Recommended Action: Verify the ServiceorScriptName attribute defined in the<br />
configuration file is assigned a value.<br />
Failed to lookup the account name ‘Account_Name’. Error = Error Code<br />
The agent failed to obtain the SID for the specified user.<br />
Recommended Action: Verify that the domain controller is accessible, or the<br />
specified user exists. See the error code if the problem persists.<br />
The password attribute has not been configured<br />
No value specified for the Password attribute.<br />
Recommended Action: Verify the Password attribute defined in the configuration<br />
file is assigned a value and contains alphabets only.<br />
Failed to get the password attribute. Error = Error Code<br />
The agent failed to decrypt the specified password.<br />
Recommended Action: Verify that the password is encrypted using the VCS Encrypt<br />
utility (described in the <strong>Veritas</strong> <strong>Cluster</strong> <strong>Server</strong> Administrator's <strong>Guide</strong>).<br />
Failed to convert the password attribute. Error = Error Code<br />
The agent failed to convert the password attribute. This is a VCS internal error.<br />
Recommended Action: Offline and online the service group. Contact Symantec<br />
Technical Support if the problem persists.<br />
Failed to open the SCM handle. Error = Error Code<br />
The agent failed to obtain the SCM handle. This occurs if the SCM database does<br />
not exist, or if the SCM manager denies the requested access.<br />
Recommended Action: Verify that SCM can be run on the host.<br />
Failed to open the service ‘Service_Name’. Error = Error Code<br />
The resource definition in the configuration file contains an invalid, or incorrect<br />
service name.
Change language