-
Suggestion
-
Resolution: Fixed
The following has been observed:
The EA does not start up if shell scripts fail to run successfully. So far this has happened in
/opt/bamboo-elastic-agent/bin/restoreSnapshot.sh and /opt/bamboo-elastic-agent/bin/setAwsEnv.sh
can be failing on getting the availability zone using curl. This is stopping the agent from starting successfully.
The response from amazon is
<?xml version="1.0" encoding="iso-8859-1"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head> <title>404 - Not Found</title> </head> <body> <h1>404 - Not Found</h1> </body> </html>
and the agent is not started up. The instance remains idle - no warning or error messages are sent to the server.
then restoreSnapshot.sh hangs
1 0 1122 1114 23 0 2648 484 wait S ? 0:00 /bin/sh /opt/bamboo-elastic-agent/bin/restoreSnapshot.sh 0 0 1123 1122 24 0 2640 1136 wait S ? 0:00 bash /usr/local/ec2/ec2-api-tools/bin/ec2-create-volume --snapshot snap-d64885bf --availability-zone