Open ricardo-mela opened 6 years ago
I'm running into the same issue, I see:
mount.nfs4: Failed to resolve server fs-....efs.....amazonaws.com: Name or service not known
ERROR: Mount command failed!.
@ricardo-mela where in the script did you add this? Can you provide a snippet of the code where you added it? Thanks!
Line 60 of https://github.com/aws-samples/eb-php-wordpress/blob/master/.ebextensions/efs-mount.config is a good place to do so.
Otherwise, you can run a loop with an aws efs describe-mount-targets --file-system-id ${EFS_FILE_SYSTEM_ID}
command and continue when the command returns exit code 0. Try not use exponential backoff or similar, as in any AWS API call.
As mentioned on my previous comment,
I cannot get pass this error at all, please help [Instance: i-0a16d932b349fa6f6,i-0bb65df3635f61985] Command failed on instance. Return code: 1 Output: (TRUNCATED)...vers=4.1,rsize=1048576,wsize=1048576,hard,timeo=600,retrans=2 fs-567aded7.efs.us-east-1.amazonaws.com:/ /wpfiles mount.nfs4: Failed to resolve server fs-567aded7.efs.us-east-1.amazonaws.com: No address associated with hostname ERROR: Mount command failed!. command 01_mount in .ebextensions/efs-mount.config failed. For more detail, check /var/log/eb-activity.log using console or EB CLI.
I have exactly the same problem here. Using a sleep command, as ricardo-mela suggested, did not work for me.
Finally, to get wordpress running, I've had to disable the EFS creation.
A good solution without disabling the EFS creation would be appreciated.
Could you use the built-in wait?
https://docs.aws.amazon.com/cli/latest/reference/ec2/wait/volume-available.html
On Sat, 3 Aug 2019 at 07:00, ricardo-mela notifications@github.com wrote:
Line 60 of https://github.com/aws-samples/eb-php-wordpress/blob/master/.ebextensions/efs-mount.config is a good place to do so.
Otherwise, you can run a loop with an aws efs describe-mount-targets --file-system-id ${EFS_FILE_SYSTEM_ID} command and continue when the command returns exit code 0. Try not use exponential backoff or similar, as in any AWS API call.
As mentioned on my previous comment,
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/aws-samples/eb-php-wordpress/issues/21?email_source=notifications&email_token=AF4P4JCEPEKITZ3NTBZVL2TQCS4ABA5CNFSM4FIOQQJKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3PAMPI#issuecomment-517867069, or mute the thread https://github.com/notifications/unsubscribe-auth/AF4P4JGKRNB6L6APJXY4VOLQCS4ABANCNFSM4FIOQQJA .
-- Onno Benschop
()/)/)() ..ASCII for Onno.. |>>? ..EBCDIC for Onno.. --- -. -. --- ..Morse for Onno..
If you need to know: "What computer should I buy?" http://goo.gl/spsb66
ITmaze - ABN: 56 178 057 063 - ph: 04 1219 8888 - onno@itmaze.com.au
Finally I've found the problem, but not the solution (well, perhaps a possible solution is not using Amazon Linux 2). It is described here:
Yes, I can definitely confirm that using Amazon Linux 1 instead of 2 everything works correctly.
I have exactly the same problem here. Using a sleep command, as ricardo-mela suggested, did not work for me.
Finally, to get wordpress running, I've had to disable the EFS creation.
A good solution without disabling the EFS creation would be appreciated.
Hi @dherrerab How to disable the EFS creation?
I have exactly the same problem here. Using a sleep command, as ricardo-mela suggested, did not work for me. Finally, to get wordpress running, I've had to disable the EFS creation. A good solution without disabling the EFS creation would be appreciated.
Hi @dherrerab How to disable the EFS creation?
Well, it's been a long time since this, I can hardly remember, but I suppose that just not including the files efs-create.config and efs-mount.config in the folder .ebextensions should do the trick.
Hi,
I have noticed that it may happen that your environment is running the ebextensions when the mount targets are not yet created. As such, the update operation fails since the mount-efs.sh script exits due to the mount points not being ready.
I added a sleep 120 in the script to take me out of the immediate issue and it solves it, but it would be good to have some kind of retry logic for that command.