I'm having a problem with Amazon hosted site - AWS experience pl
- or -
Post a project like this1635
£148(approx. $185)
- Posted:
- Proposals: 3
- Remote
- #2563907
- OPPORTUNITY
- Awarded
Description
Experience Level: Entry
Our website is not working. Says 'This site can’t be reached fact.btbclientportal.co.uk took too long to respond' .
This is the response received from Amazon -
I understand that you are unable to reach fact.btbclientportal.co.uk. I checked the resources in your account and found a t2.micro EC2 instance (i-f2eb98b1) running in the eu-west-1b availability zone.
Checking the IP address for fact.btbclientportal.co.uk () I checked on our side and confirmed it's associated with this EC2 instance i-f2eb98b1 in your AWS account. Please correct me if I'm not looking at the correct instance.
After investigating the instance (i-f2eb98b1), I confirmed that it's passing System Status Checks, and failing Instance Status Checks starting on 2019-10-01 at 11:10 UTC.
System Status checks [1], monitor the AWS systems on which your instance runs. Whereas, Instance Status Checks [2] monitor the software and network configuration of your individual instance.
From the instance screenshot [3], I can see Windows experienced a blue screen of death (BSOD). This can be viewed from the console by selecting the instance and choosing Actions > Instance Settings > Get Instance Screenshot. The screenshot shows a failure for termdd.sys on the OS level.
With the instance in this state, there are a few options available to troubleshoot the issue.
If the goal is to quickly resolve the issue, I noticed there are snapshots available for the root volume (vol-b6104dbd) of the instance. Instance Status Checks started failing on 2019-10-01 at 11:10 UTC, which indicates the issue likely occurred around this time.
Looking at the volume there are many snapshots available, however snap-0b867d0cc16c60406 seems to be the latest snapshot available (snapshot completed 2019-09-29 at 03:00:48 UTC), prior to the issue. The following are steps to restore the snapshot as an EBS volume:
Stop the instance and detach the existing root EBS volume (vol-b6104dbd) using the console [4]. Keep in mind when you stop the instance, the public IP address with change.
Create an EBS volume from the snapshot (snap-0b867d0cc16c60406) using the console [5] in the same availability zone (eu-west-1b).
Attach the volume to the instance as /dev/sda1 following the steps here [6] and start the instance again.
Alternatively, I'm happy to help troubleshoot the issue that occurred. In order to troubleshoot the BSOD, we have a tool named EC2Rescue that can be used to collect logs, including a memory dump (if memory dumps are enabled on the instance). Please follow the steps below before restoring from the snapshot above.
Step 1. Launch a new temporary instance (Win Server 2012 R2 base OS or later) in the same availability zone (eu-west-1b) or use any existing instance (Win Server 2012 R2 base OS) you have RDP access to.
Step 2. Stop the current instance i-f2eb98b1 . Detach the root volume of the instance and attach it as a secondary volume to the temp instance above. (xvdf Block device mapping is fine) Step 3. Download the EC2Rescue.exe tool from https://s3.amazonaws.com/ec2rescue/windows/EC2Rescue_latest.zip onto the temporary Windows instance Step 4. Run the EC2Rescue.exe tool.
Step 5. Click Next > Offline instance
Step 6. Select the offline disk that you just attached and then click Next, and Yes to verify this is the correct volume and bring it online.
Step 7. Click Capture Logs
Step 8. Keep all log options checked
Step 9. Click Collect...> Yes > save the Zip file then click Finish > OK to offline the selected disk and fix any disk signature issues.
Step 10. Shutdown the temporary instance Step 11. Detach the volume from the temporary Windows instance and attach it to the original instance that you were attempting to RDP into (Attach as /dev/sda1 ) and start it again. Alternatively, if you'd like to restore from the snapshot at this point you can attach the newly created volume.
I have had someone look at this but apparently its not connected to the real world internet? This person says that we need someone to 'trouble shoot connecting the instance to your web address after stopping and starting instance' as he says the link through our website isn't working any more after restarting the instance.
This is the response received from Amazon -
I understand that you are unable to reach fact.btbclientportal.co.uk. I checked the resources in your account and found a t2.micro EC2 instance (i-f2eb98b1) running in the eu-west-1b availability zone.
Checking the IP address for fact.btbclientportal.co.uk () I checked on our side and confirmed it's associated with this EC2 instance i-f2eb98b1 in your AWS account. Please correct me if I'm not looking at the correct instance.
After investigating the instance (i-f2eb98b1), I confirmed that it's passing System Status Checks, and failing Instance Status Checks starting on 2019-10-01 at 11:10 UTC.
System Status checks [1], monitor the AWS systems on which your instance runs. Whereas, Instance Status Checks [2] monitor the software and network configuration of your individual instance.
From the instance screenshot [3], I can see Windows experienced a blue screen of death (BSOD). This can be viewed from the console by selecting the instance and choosing Actions > Instance Settings > Get Instance Screenshot. The screenshot shows a failure for termdd.sys on the OS level.
With the instance in this state, there are a few options available to troubleshoot the issue.
If the goal is to quickly resolve the issue, I noticed there are snapshots available for the root volume (vol-b6104dbd) of the instance. Instance Status Checks started failing on 2019-10-01 at 11:10 UTC, which indicates the issue likely occurred around this time.
Looking at the volume there are many snapshots available, however snap-0b867d0cc16c60406 seems to be the latest snapshot available (snapshot completed 2019-09-29 at 03:00:48 UTC), prior to the issue. The following are steps to restore the snapshot as an EBS volume:
Stop the instance and detach the existing root EBS volume (vol-b6104dbd) using the console [4]. Keep in mind when you stop the instance, the public IP address with change.
Create an EBS volume from the snapshot (snap-0b867d0cc16c60406) using the console [5] in the same availability zone (eu-west-1b).
Attach the volume to the instance as /dev/sda1 following the steps here [6] and start the instance again.
Alternatively, I'm happy to help troubleshoot the issue that occurred. In order to troubleshoot the BSOD, we have a tool named EC2Rescue that can be used to collect logs, including a memory dump (if memory dumps are enabled on the instance). Please follow the steps below before restoring from the snapshot above.
Step 1. Launch a new temporary instance (Win Server 2012 R2 base OS or later) in the same availability zone (eu-west-1b) or use any existing instance (Win Server 2012 R2 base OS) you have RDP access to.
Step 2. Stop the current instance i-f2eb98b1 . Detach the root volume of the instance and attach it as a secondary volume to the temp instance above. (xvdf Block device mapping is fine) Step 3. Download the EC2Rescue.exe tool from https://s3.amazonaws.com/ec2rescue/windows/EC2Rescue_latest.zip onto the temporary Windows instance Step 4. Run the EC2Rescue.exe tool.
Step 5. Click Next > Offline instance
Step 6. Select the offline disk that you just attached and then click Next, and Yes to verify this is the correct volume and bring it online.
Step 7. Click Capture Logs
Step 8. Keep all log options checked
Step 9. Click Collect...> Yes > save the Zip file then click Finish > OK to offline the selected disk and fix any disk signature issues.
Step 10. Shutdown the temporary instance Step 11. Detach the volume from the temporary Windows instance and attach it to the original instance that you were attempting to RDP into (Attach as /dev/sda1 ) and start it again. Alternatively, if you'd like to restore from the snapshot at this point you can attach the newly created volume.
I have had someone look at this but apparently its not connected to the real world internet? This person says that we need someone to 'trouble shoot connecting the instance to your web address after stopping and starting instance' as he says the link through our website isn't working any more after restarting the instance.
Karen S.
100% (2)Projects Completed
1
Freelancers worked with
1
Projects awarded
50%
Last project
19 Feb 2020
United Kingdom
New Proposal
Login to your account and send a proposal now to get this project.
Log inClarification Board Ask a Question
-
Can you please confirm that the solution suggested by AWS has been implanted. Cause from the issue it's seems that status check 2/2 failure can be recovered from the last volume snapshot. Let me know
853609
We collect cookies to enable the proper functioning and security of our website, and to enhance your experience. By clicking on 'Accept All Cookies', you consent to the use of these cookies. You can change your 'Cookies Settings' at any time. For more information, please read ourCookie Policy
Cookie Settings
Accept All Cookies