AGT Agent alert codes
Topic
This article provides definitions of the Agent (AGT) alert and error codes found in Datto BCDR device logs.
AGT codes may appear in the device logs when the Datto device is unable to pair or is having trouble communicating with the agent software on the protected machine. They are not specific to a particular agent software
Environment
- Datto SIRIS
- Datto ALTO
- Datto NAS
Description
Datto appliances log backup activity in the device's /datto/config/keys directory on a per-agent basis (for example, 192.168.1.1.log). Each process taking place during a backup has a specific code associated with it. Errors which happen during processes are also logged. During troubleshooting, AGT error codes can reveal important information.
AGT codes should not be confused with AGENT alerts that appear in device banners and alert e-mails specifically for issues with the Datto Windows Agent (DWA) or Datto Linux Agent (DLA). For a complete list and explanation of DWA and DLA AGENT alerts, see: Troubleshooting Agent Error Codes
| AGT0900 | Warning | Agent pairing failed will re-attempt |
| AGT0910 | Critical | Agent pairing failed giving up |
|
AGT0915 |
Critical |
Agent pairing failed giving up |
| AGT0930 | Critical | Blank hostname in certificate pair |
| AGT0940 | Critical | Curl Keyfile is empty request failed |
| AGT0950 | Critical | Curl Keyfile is Missing request failed |
| AGT1310 | Warning | Metadata XML is invalid |
| AGT1330 | Warning | XML Parser threw an error in gettingAgentData related to version |
| AGT1340 | Critical | Curl returned and HTTP Error state. State was #[STATE]# |
|
AGT1350 |
Warning |
Curl returned false to agentinfo |
|
AGT1360 |
Warning |
Connectivity Failed. Agent Info Request Aborted |
|
AGT1960 |
Warning |
$volName for $hosname has been included for backups |
|
AGT2016 |
Critical |
Unable to get agent due to error 401 Unauthorized |
