Sign In with your
Trend Micro Account
Need Help?
Need More Help?

Create a technical support case if you need further support.

Same server appears twice in the Deep Security as a Service (DSaaS) console

    • Updated:
    • 18 Oct 2019
    • Product/Version:
    • Deep Security As A Service
    • Platform:
    • N/A
Summary

The same server is showing twice in the dashboard. This happens in Deep Security as a Service with AWS Cloud Connector. The issue still persists even after doing the following:

  1. Re-activate the agent and enable Do not allow agent to specify hostname.
  2. Re-install the agent.
Details
Public

Based on the ds_agent.log, the agent was not able to report its AWS instance metadata because it cannot connect to IP address 169.254.169.254.

2019-09-05 15:32:59.000000 [+0800]: [Error/1] | couldn't connect to 169.254.169.254:80 (10060: select socket (error 0x274c: a connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.)) | http\HTTPClient.cpp:269:DsaCore::CHTTPClient::ConnectToHost | 1BE8:11A8:dsa.Scheduler_0001
2019-09-05 15:32:59.673193 [+0800]: [Cmd/5] | failed to http get: http://169.254.169.254/latest/meta-data/network/interfaces/macs/ | common\CloudEnvInfo.cpp:153:DsaCore::HttpGet | 1BE8:11A8:dsa.Scheduler_0001
2019-09-05 15:32:59.674122 [+0800]: [Cmd/5] | Failed to query http://169.254.169.254/latest/meta-data/network/interfaces/macs/ | common\CloudEnvInfo.cpp:205:DsaCore::DetectAWSWSAgent | 1BE8:11A8:dsa.Scheduler_0001
2019-09-05 15:32:59.674122 [+0800]: [Cmd/5] | This is not an AWS workspace | common\CloudEnvInfo.cpp:269:DsaCore::DetectAWSWSAgent | 1BE8:11A8:dsa.Scheduler_0001
2019-09-05 15:33:20.676336 [+0800]: [Cmd/5] | failed to query meta-data/instance-id | common\CloudEnvInfo.cpp:906:DsaCore::HandleEC2Prop | 1BE8:11A8:dsa.Scheduler_0001

Since it cannot query the AWS metadata, the agent assumed that the machine is not in AWS. For more information, please refer to this AWS article: Retrieving Instance Metadata.

To resolve the issue, run the following command to fix the communication to IP address 169.254.169.254 on Port 80.

curl http://169.254.169.254/latest/meta-data/

GET http://169.254.169.254/latest/meta-data/

Premium
Internal
Rating:
Category:
Troubleshoot
Solution Id:
000150798
Feedback
Did this article help you?

Thank you for your feedback!

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.

If you need additional help, you may try to contact the support team. Contact Support

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.