New answers tagged

2

This snapshot is not associated with an EC2 instance. It is associated with an AMI image as mentioned in the error message. AMI images that are EBS-backed have associated EBS snapshots. These associated snapshots cannot be deleted until you deregister the AMI image. The snapshot you are trying to delete is such a snapshot. If you want to delete this ...


0

Seems like the issue had been linked to the line prerequisite_check in the script which was placed before all variables had been setup. I moved the check down to below the point where the cron primer is linked and everything worked fine. It is strange that a script so commonly used has such an error without anyone reporting it. I assume the bug had been ...


0

Function prerequisite_check definition says, basename, cut, date and aws commands should be available. Script is unable to find aws command when running from crontab. Hence, you are hitting error. In crontab, you need to modify PATH variable to include path to aws executable, by writing them before your cron lines. You can use below syntax to add path ...


-1

In most cases httpd.conf is located in /etc/apache2/conf/httpd.conf You need to change the DocumentRoot setting in your httpd.conf file. More information here: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/3/html/Reference_Guide/s1-apache-config.html You should see something like <Directory "/var/www/html"> - change it to ...


1

As everything including the journal is on the same storage device (i.e. your dbpath is not mapped to multiple EBS volumes) then you don't need flush and lock the database. This is only the case where these are spread across multiple volumes. Assuming the journal is present on the same volume as the data files, a snapshot will capture both the state of the ...



Top 50 recent answers are included