[f_prg@XXXX-XXXX-XXXX] $ firebase login:ci
Visit this URL on any device to log in:
https://accounts.google.com/o/oauth2/auth?XXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Waiting for authentication...
✔ Success! Use this token to login on a CI server:
FIREBASE_TOKENFIREBASE_TOKENFIREBASE_TOKENFIREBASE_TOKEN
Example: firebase deploy --token "$FIREBASE_TOKEN"
「Action Required – Your certificate renewal」という件名のメールが届きました。
メールの本文はこちらです。
Greetings from Amazon Web Services,
You have an AWS Certificate Manager (ACM) SSL/TLS certificate in your AWS account that expires on May 28, 2019 at 12:00:00 UTC. That certificate includes the primary domain blog.star-flare.com and a total of 1 domains.
AWS account ID: 123456789012
AWS Region name: us-east-1
Certificate identifier: arn:aws:acm:us-east-1:123456789012:certificate/AAAAAAAA-BBBB-CCCC-DDDD-EEEEEEEEEEEE
ACM was unable to automatically renew your certificate. The domain owner or someone authorized by the domain owner must take one of the following actions before May 28, 2019 at 12:00:00 UTC. If no action is taken, the certificate will expire, which might cause your website or application to become unreachable.
1. If you can write records into your DNS configuration, create and install DNS-validated certificates to replace all of your existing email-validated certificates. After you add a CNAME record to your DNS configuration, ACM can automatically renew your certificate as long as the record remains in place. You can learn more about DNS validation in the ACM User Guide.[1]
2. If you want to continue using email validation to renew this certificate, the domain owners must use the approval link that was sent in a separate validation request email. That email was last sent on Apr 13, 2019 at 12:38:10 UTC. The link in that email is valid for three days from the time the email was sent. If you did not use the link within three days, go to the ACM console to have AWS resend the validation email. For instructions, see the AWS Support website.[2]
If you have questions about this process, contact the AWS Support Center[3]. If you don’t have an AWS support plan, post a new thread in the AWS Certificate Manager discussion forum.[4]
[1] https://docs.aws.amazon.com/acm/latest/userguide/gs-acm-validate-dns.html
[2] https://aws.amazon.com/premiumsupport/knowledge-center/resend-email-ssl/.
[3] https://console.aws.amazon.com/support
[4] https://forums.aws.amazon.com/forum.jspa?forumID=206
Sincerely,
Amazon Web Services
Warning: Permanently added '10.0.68.89' (ECDSA) to the list of known hosts.
_____ _ _ _ ____ _ _ _
| ____| | __ _ ___| |_(_) ___| __ ) ___ __ _ _ __ ___| |_ __ _| | | __
| _| | |/ _` / __| __| |/ __| _ \ / _ \/ _` | '_ \/ __| __/ _` | | |/ /
| |___| | (_| \__ \ |_| | (__| |_) | __/ (_| | | | \__ \ || (_| | | <
|_____|_|\__,_|___/\__|_|\___|____/ \___|\__,_|_| |_|___/\__\__,_|_|_|\_\
Amazon Linux AMI
This EC2 instance is managed by AWS Elastic Beanstalk. Changes made via SSH
WILL BE LOST if the instance is replaced by auto-scaling. For more information
on customizing your Elastic Beanstalk environment, see our documentation here:
http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/customize-containers-ec2.html
[ec2-user@ip-10-0-68-89 ~]$ php -v
PHP 7.2.13 (cli) (built: Jan 9 2019 22:12:27) ( NTS )
Copyright (c) 1997-2018 The PHP Group
Zend Engine v3.2.0, Copyright (c) 1998-2018 Zend Technologies
with Zend OPcache v7.2.13, Copyright (c) 1999-2018, by Zend Technologies
バージョンは、7.2.13と確認できました。
AWS EB CLI でアプリケーションをデプロイします。
業務で使ってるアプリケーションをデプロイしたところ
[f_prg@serverapp] $ eb deploy
Creating application version archive "app-v20180611-822-ga782-190410_150350".
Uploading: [##################################################] 100% Done...
2019-04-10 06:05:13 INFO Environment update is starting.
2019-04-10 06:06:19 INFO Deploying new version to instance(s).
2019-04-10 06:06:40 ERROR [Instance: i-XXXXXXXX] Command failed on instance. Return code: 2 Output: (TRUNCATED)...- /etc/php-7.0.d/30-wddx.ini
- /etc/php-7.0.d/30-xmlreader.ini
- /etc/php-7.0.d/aws.ini
- /etc/php-7.0.d/environment.ini
- /etc/php-7.0.d/php.ini
You can also run `php --ini` inside terminal to see which files are used by PHP in CLI mode.
Hook /opt/elasticbeanstalk/hooks/appdeploy/pre/10_composer_install.sh failed. For more detail, check /var/log/eb-activity.log using console or EB CLI.
2019-04-10 06:06:44 ERROR [Instance: i-YYYYYY] Command failed on instance. Return code: 2 Output: (TRUNCATED)...- /etc/php-7.0.d/30-wddx.ini
- /etc/php-7.0.d/30-xmlreader.ini
- /etc/php-7.0.d/aws.ini
- /etc/php-7.0.d/environment.ini
- /etc/php-7.0.d/php.ini
You can also run `php --ini` inside terminal to see which files are used by PHP in CLI mode.
Hook /opt/elasticbeanstalk/hooks/appdeploy/pre/10_composer_install.sh failed. For more detail, check /var/log/eb-activity.log using console or EB CLI.
2019-04-10 06:06:44 INFO Command execution completed on all instances. Summary: [Successful: 0, Failed: 2].
2019-04-10 06:06:45 ERROR Unsuccessful command execution on instance id(s) 'i-YYYYYY,i-XXXXXXXX'. Aborting the operation.
2019-04-10 06:06:45 ERROR Failed to deploy application.
ERROR: ServiceError - Failed to deploy application.
