By using AWS re:Post, you agree to the Terms of Use
/AWS Elastic Beanstalk/

Questions tagged with AWS Elastic Beanstalk

Sort by most recent
  • 1
  • 90 / page

Browse through the questions and answers listed below or filter and sort to narrow down your results.

How / Where do I upgrade my instance's PostgreSQL Version?

Hello! I am trying to deploy a rails 7 app to elastic beanstalk, but my deploy keeps failing. In the logs I see: `An error occurred while installing pg (1.3.5), and Bundler cannot continue` (installing the postgres gem is failing) I SSHed onto my instance and ran bundle manually, and see `Your PostgreSQL is too old. Either install an older version of this gem or upgrade your database to at least PostgreSQL-9.3.` In my .elasticbeanstalk.packages.config file I have: ``` packages: yum: postgresql14-devel: [] ``` But this seems to have no effect on the version of Postgres on my instance. Creating an RDS instance associated to my beanstalk environment with any version of PostgreSQL does not seem to solve the problem. `postgres -V` is not a command on my beanstalk instance if I ssh onto my instance and cat `usr/bin/pg_config` I think it may be set to version 9.2, but this file doesn't look to me like something I should be editing via SSH and I don't see any references to manipulating how it gets generated. Any assistance would be greatly appreciated! Update1: .elasticbeanstalk.packages.config should be within `.ebextensions` instead. I made this change, still had this error. Found another thread on stack overflow that described the packages.config file to look like ``` packages: yum: amazon-linux-extras: [] commands: 01_postgres_activate: command: sudo amazon-linux-extras enable postgresql10 02_postgres_install: command: sudo yum install -y postgresql-devel ``` I updated the file, still had no luck. I terminated and rebuild my app to try again, and manually ran `sudo amazon-linux-extras enable postgresql10` and `sudo yum install -y postgresql-devel` via ssh, which finally let me successfully bundle install. Still working on making this work via EB deploy instead of manually messing with the boxes. Update 2: After making the above changes and creating a new application + environment I am able to consistently get past the above issue.
1
answers
1
votes
4
views
AWS-User-2956796
asked 10 days ago

Elastic Beanstalk drops connections to load balancer during deployment after Amazon Linux 2 upgrade

Hi. I just upgraded my Elastic Beanstalk environment from "PHP 7.3 running on 64bit Amazon Linux/2.9.28" to "PHP 7.3 running on 64bit Amazon Linux 2/3.3.12" (using Apache) and found that my application load balancer returns 502 errors for a few seconds every single time I deploy a new application version. I checked the ALB logs and found the 502 responses have a target_processing_time of -1 which the [documentation](https://docs.aws.amazon.com/elasticloadbalancing/latest/application/load-balancer-access-logs.html) says means that "the load balancer can't dispatch the request to a target. This can happen if the target closes the connection before the idle timeout or if the client sends a malformed request." I ran a test where I sent one request per second to both the ALB and directly to the EC2 instance during deployment. I found that during those 2-3 seconds where the application version is switching over, the requests to the ALB return 502 while the requests directly to the instance just have a brief pause but respond correctly anyway. Everything I've been able to find on this topic says it's related to KeepAlive timeouts and needing different timeouts on the server and ALB but I've tried every combination of timeouts I can imagine and no luck. I've tried a few different environment platforms and it happens 100% of the time on the Amazon Linux 2 platforms and 0% of the time on Amazon Linux 1 platforms. Thanks!
0
answers
0
votes
2
views
benp
asked 24 days ago

Linux OS networking bug in Elastic Beanstalk AMI with Tomcat & Corretto

We use AWS Elastic Beanstalk with an Amazon AMI with Tomcat & Corretto running on Amazon Linux 2 (`aws-elasticbeanstalk-amzn-2.0.20220316.64bit-eb_tomcat85corretto8_amazon_linux_2-hvm-2022-03-29T20-48`) and are running into an [OS networking bug](https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924298) when Tomcat is under load. The result of this bug are that TCP connections from clients connect but timeout while the server is under load. The networking bug is due to a race condition in the TCP stack which is fixed in Linux 5.10 kernels. A description and diff of the bug can be found in [this commit](https://github.com/torvalds/linux/commit/01770a166165738a6e05c3d911fb4609cc4eb416). From the description of this bug it looks like this race condition affects all TCP networking and is not specific to Tomcat, but manifests more often under load. Currently, as far as I can tell, all the latest Amazon AMIs for Elastic Beanstalk for Tomcat or Corretto are using a 4.14 kernel. The AMI which we are using has a kernel of `4.14.268-205.500.amzn2.x86_64`. I have been able to reproduce the bug on this AMI using the sample server code in the Ubuntu bug report, which is independent of Tomcat. I have also tried reproing the bug on newer versions of Amazon Linux 2 (AMI `amzn2-ami-kernel-5.10-hvm-2.0.20220419.0-x86_64-gp2`) which are using a `5.10.109-104.500.amzn2.x86_64` kernel, but have not been able to repro the bug on this kernel. We would prefer not to have to create our own AMI for using Elastic Beanstalk, but were wondering if and when there will be an update to the Amazon Elastic Beanstalk AMI's which incorporate this OS bug fix since this is affecting the reliability of networking under load?
0
answers
2
votes
5
views
Chris-G-206
asked 24 days ago

Elastic Beanstalk error after migrating from python 3.7 to python3.8.

I am using the EB platform: Python 3.7 AL2 version 3.3.11, and all is working fine. But, the troubleshooting comes when I try to upgrade both to a newer AL2 version (3.3.12) and to a newer Python version (3.8). The error happens on the "[app-deploy] - [StageApplication]": eb-engine: ``` 022/04/20 11:51:08.170326 [INFO] Executing instruction: StageApplication 2022/04/20 11:51:08.171215 [INFO] extracting /opt/elasticbeanstalk/deployment/app_source_bundle to /var/app/staging/ 2022/04/20 11:51:08.171232 [INFO] Running command /bin/sh -c /usr/bin/unzip -q -o /opt/elasticbeanstalk/deployment/app_source_bundle -d /var/app/staging/ 2022/04/20 11:51:08.208452 [INFO] finished extracting /opt/elasticbeanstalk/deployment/app_source_bundle to /var/app/staging/ successfully 2022/04/20 11:51:08.212657 [ERROR] An error occurred during execution of command [app-deploy] - [StageApplication]. Stop running the command. Error: chown /var/app/staging/venv/dev/lib/python3.8/collections: no such file or directory ``` The error specifically says: **[ERROR] An error occurred during execution of command [app-deploy] - [StageApplication]. Stop running the command. Error: chown /var/app/staging/venv/dev/lib/python3.8/collections: no such file or directory** I don't know why it goes there, instead of /var/app/venv/staging-LQM1lest/lib/python3.8 that is where I think it should go and where it is the virtual environment. I can assure that the local /venv folder is ignored when deploying (following this related question https://stackoverflow.com/questions/61805345/aws-elastic-beanstalk-chown-pythonpath-error). Said that though, after connecting to the instance by ssh, I can see a venv folder in /var/app/staging/ containing a pyton3.8 sub folder. I am curious to know why this happens and what can I be doing wrong in the process Thanks in advance!
1
answers
0
votes
0
views
llpujol
asked a month ago

Beanstalk deployment process fails to update Proxy configuration

I've seen this several times where it appears that Beanstalk will not deploy a bundle because artifacts contained in a previous deployment had syntax errors. I don't understand why Beanstalk would validate old artifacts rather than deploy the artifact as contained in the bundle currently being deployed. In order to resolve resolve the issue the syntactically bad files have to be manually replaced (or deleted?) before Beanstalk will deploy successfully. The current problem is highlighted below: eb-engine log 3:57 2022/04/07 22:12:51.580831 [INFO] Executing instruction: configure proxy server 2022/04/07 22:12:51.584473 [INFO] Running command /bin/sh -c cp -rp /var/app/staging/.platform/httpd/. /var/proxy/staging/httpd This is done correctly – contains the version of the file from the app bundle I’m deploying … 2022/04/07 22:13:31.619080 [INFO] Executing instruction: start proxy with new configuration 2022/04/07 22:13:31.619124 [INFO] Running command /bin/sh -c /usr/sbin/apachectl -t -f /var/proxy/staging/httpd/conf/httpd.conf 2022/04/07 22:13:31.687560 [INFO] [Thu Apr 07 22:13:31.670790 2022] [core:warn] [pid 21978:tid 139968169546304] AH00111: Config variable ${njpf_host} is not defined AH00526: Syntax error on line 1 of /etc/httpd/conf.d/apache_overides.conf: Cannot parse condition clause: syntax error, unexpected T_OP_BINARY Why is he looking at /etc/httpd/conf.d/apache_overides.conf when the latest is in /var/proxy/staging/httpd? (or why wasn’t the latest apache_overides.conf copied from /var/proxy/staging/httpd to /etc/httpd/conf.d?) 2022/04/07 22:13:31.687593 [ERROR] An error occurred during execution of command [app-deploy] - [start proxy with new configuration]. Stop running the command. Error: copy proxy conf from staging failed with error validate httpd configuration failed with error Command /bin/sh -c /usr/sbin/apachectl -t -f /var/proxy/staging/httpd/conf/httpd.conf failed with error exit status 1. Stderr:[Thu Apr 07 22:13:31.670790 2022] [core:warn] [pid 21978:tid 139968169546304] AH00111: Config variable ${njpf_host} is not defined AH00526: Syntax error on line 1 of /etc/httpd/conf.d/apache_overides.conf: Cannot parse condition clause: syntax error, unexpected T_OP_BINARY This seems to confirm the copy from /var/proxy/staging/httpd failed but the reason it failed is that the last version (prior to the current deploy) of /etc/httpd/conf.d/apache_overides.conf had a syntax error. Well no kidding – that’s why I’m deploying the latest version of apache_overides.conf (in /var/proxy/staging/httpd/conf.d) which does not have the reported syntax error). Again, I'm not sure why beanstalk is concerned about a syntax error that doesn't exist in the current deployment. Help! Thanks.
0
answers
0
votes
1
views
jack
asked a month ago

Setting JVM options on Beanstalk Tomcat

Trying to set options as follows: -Xdebug -Xrunjdwp:server=y,transport=dt_socket,address=5004,suspend=n Using both "Container Options > JVM options" and as a Environment Property as follows: Name: _JAVA_OPTIONS Value: -Xdebug -Xrunjdwp:server=y,transport=dt_socket,address=5004,suspend=n Neither approach seemed to work. Tomcat starts as follows: 12-Apr-2022 02:24:46.838 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server version name: Apache Tomcat/8.5.75 12-Apr-2022 02:24:46.844 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server built: Feb 28 2022 18:26:53 UTC 12-Apr-2022 02:24:46.848 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server version number: 8.5.75.0 12-Apr-2022 02:24:46.850 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Name: Linux 12-Apr-2022 02:24:46.851 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Version: 4.14.268-205.500.amzn2.x86_64 12-Apr-2022 02:24:46.851 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Architecture: amd64 12-Apr-2022 02:24:46.852 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Java Home: /usr/lib/jvm/java-1.8.0-amazon-corretto.x86_64/jre 12-Apr-2022 02:24:46.853 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Version: 1.8.0_322-b06 12-Apr-2022 02:24:46.854 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Vendor: Amazon.com Inc. 12-Apr-2022 02:24:46.854 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_BASE: /usr/share/tomcat 12-Apr-2022 02:24:46.855 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_HOME: /usr/share/tomcat 12-Apr-2022 02:24:46.858 INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent The Apache Tomcat Native library which allows using OpenSSL was not found on the java.library.path: [/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib] 12-Apr-2022 02:24:47.016 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio-8080"] 12-Apr-2022 02:24:47.045 INFO [main] org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a shared selector for servlet write/read 12-Apr-2022 02:24:47.074 INFO [main] org.apache.catalina.startup.Catalina.load Initialization processed in 1048 ms 12-Apr-2022 02:24:47.165 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Catalina] 12-Apr-2022 02:24:47.173 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet engine: [Apache Tomcat/8.5.75] 12-Apr-2022 02:24:47.242 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployWAR Deploying web application archive [/var/lib/tomcat/webapps/jcs.war] 12-Apr-2022 02:24:56.187 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployWAR Deployment of web application archive [/var/lib/tomcat/webapps/jcs.war] has finished in [8,943] ms 12-Apr-2022 02:24:56.192 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployWAR Deploying web application archive [/var/lib/tomcat/webapps/work.war] 12-Apr-2022 02:25:35.849 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployWAR Deployment of web application archive [/var/lib/tomcat/webapps/work.war] has finished in [39,657] ms 12-Apr-2022 02:25:35.863 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-8080"] 12-Apr-2022 02:25:35.875 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in 48794 ms How are JVM options supposed to be set in this environment? Thanks much.
2
answers
0
votes
1
views
jack
asked a month ago

CFM stack is stuck after failure deleting Beanstalk app

Hi, I have a CloudFormation stack which includes a Beanstalk app along with an environment. I tried to remove this whole Beanstalk app within the CFM stack by simply removing the resources within the template. However, because temination protection was enabled on the nested stack that was created for the Beanstalk app, the deletion failed. The following error appeared within the Beanstalk console. ERROR Service:AmazonCloudFormation, Message:Stack [awseb-e-xxxxxxxxxx-stack] cannot be deleted while TerminationProtection is enabled I fixed it by disabling termination protection on the nested stack, but the problem is that the main/root/parent stack is stuck in the UPDATE_COMPLETE_CLEANUP_IN_PROGRESS state. At no point has CFM/Beanstalk tried to delete the nested stack again since the initial failure. Essentially the stack update has been stuck ever since and has not recovered into a useful state, effectively taking our whole stack as hostage. So basically: Beanstalk failed to delete its nested stack due to a misconfiguration, causing the root stack to be indefinitely stuck. Apparently there is no retry logic happening, since CFM/Beanstalk only attempted the operation once (I fixed the underlying problem almost immediately). It seems like Beanstalk doesn't properly communicate to CFM that the operation failed, causing the stack update to be left hanging. How do I get out of this state? It's been so long now that I doubt CFM is able to handle it automatically. Is it safe to manually delete the nested Beanstalk stack? I just don't want to mess anything up if I do things outside of CFM's control. Thanks!
1
answers
0
votes
2
views
thio123
asked a month ago

AWS Elastic Beanstalk - Ruby 3.0 running on 64bit Amazon Linux 2/3.4.4 - 100.0 % of the requests are failing with HTTP 5xx

Hello, Another amazing day today for all of us :) I am trying to use the AWS EB Ruby 3.0 running on 64bit Amazon Linux 2/3.4.4 with a Ruby-on-Rails v6.0.4.4 app, but until now, I did not manage to make it work In env status I get: ``` 100.0 % of the requests are failing with HTTP 5xx ``` also in /var/log/nginx/error.log ``` [error] 2459#2459: *596 connect() to unix:///var/run/puma/my_app.sock failed (11: Resource temporarily unavailable) while connecting to upstream, client: 172.31.34.113, server: _, request: "POST / HTTP/1.1", upstream: "http://unix:///var/run/puma/my_app.sock:/", host: "52.29.66.93" ``` and in /var/log/puma/puma.log ``` [4898] ! Unable to start worker [4898] /opt/rubies/ruby-3.0.3/lib/ruby/site_ruby/3.0.0/bundler/runtime.rb:309:in `check_for_activated_spec!' [4898] Early termination of worker ``` The `pumactl` it looks ok ``` [ec2-user@ip-172-31-xx-xx ~]$ pumactl -V 5.6.2 ``` If I check the processes: ``` ps aux | grep puma healthd 25925 0.0 3.6 828800 36624 ? Ssl 09:39 0:15 puma 5.3.2 (tcp://127.0.0.1:22221) [healthd] webapp 26497 0.2 2.2 255768 22912 ? Ss 09:40 1:07 puma 5.6.2 (unix:///var/run/puma/my_app.sock) [current] webapp 28653 64.0 2.1 327180 21668 ? Rl 16:08 0:00 puma: cluster worker 0: 26497 [current] ec2-user 28656 0.0 0.0 119420 924 pts/0 S+ 16:08 0:00 grep --color=auto puma ``` So the puma is running... correct? Also, there is another puma v5.3.2 Maybe this other puma version is used for another reason (health service)? In the Rails app I have the following: .ebextensions/02_yarn.config ``` commands: 01_node_get: cwd: /tmp command: 'curl --silent --location https://rpm.nodesource.com/setup_14.x | sudo bash -' 02_node_install: cwd: /tmp command: 'yum -y install nodejs' 03_yarn_get: cwd: /tmp # don't run the command if yarn is already installed (file /usr/bin/yarn exists) test: '[ ! -f /usr/bin/yarn ] && echo "yarn not installed"' command: 'sudo wget https://dl.yarnpkg.com/rpm/yarn.repo -O /etc/yum.repos.d/yarn.repo' 04_yarn_install: cwd: /tmp test: '[ ! -f /usr/bin/yarn ] && echo "yarn not installed"' command: 'sudo yum -y install yarn' 05_mkdir_webapp_dir: command: "mkdir /home/webapp" ignoreErrors: true 06_chown_webapp_dir: command: "chown webapp:webapp /home/webapp" ignoreErrors: true 07_chmod_webapp_dir: command: "chmod 0744 /home/webapp" ignoreErrors: true 08_chmod_logs: command: "chown webapp:webapp -R /var/app/current/log/" ignoreErrors: true 09_create_log_file: command: "touch /var/app/current/log/production.log" ignoreErrors: true 10_chown_log_production: command: "chown webapp:webapp /var/app/current/log/production.log" ignoreErrors: true 11_chmod_log_dir: command: "chmod 0664 -R /var/app/current/log/" ignoreErrors: true 12_update_bundler: command: "gem update bundler" ignoreErrors: true 13_chown_current: command: "chown webapp:webapp -R /var/app/current/" ignoreErrors: true 14_chmod_current: command: "chmod 0755 -R /var/app/current/" ignoreErrors: true 15_chown_current: command: "chown webapp:webapp -R /var/app/ondeck/" ignoreErrors: true 16_chown_current: command: "chmod 0644 -R /var/app/ondeck/" ignoreErrors: true container_commands: 17_install_webpack: command: "npm install --save-dev webpack" 18_precompile: command: "bundle exec rake assets:precompile" ``` .ebextensions/03_nginx.config ``` files: "/etc/nginx/conf.d/02_app_server.conf": mode: "000644" owner: root group: root content: | # The content of this file is based on the content of /etc/nginx/conf.d/webapp_healthd.conf # Change the name of the upstream because it can't have the same name # as the one defined by default in /etc/nginx/conf.d/webapp_healthd.conf upstream new_upstream_name { server unix:///var/run/puma/my_app.sock; } # Change the name of the log_format because it can't have the same name # as the one defined by default in /etc/nginx/conf.d/webapp_healthd.conf log_format new_log_name_healthd '$msec"$uri"' '$status"$request_time"$upstream_response_time"' '$http_x_forwarded_for'; server { listen 80; server_name _ localhost; # need to listen to localhost for worker tier if ($time_iso8601 ~ "^(\d{4})-(\d{2})-(\d{2})T(\d{2})") { set $year $1; set $month $2; set $day $3; set $hour $4; } access_log /var/log/nginx/access.log main; # Match the name of log_format directive which is defined above access_log /var/log/nginx/healthd/application.log.$year-$month-$day-$hour new_log_name_healthd; location / { # Match the name of upstream directive which is defined above proxy_pass http://new_upstream_name; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; } location /assets { alias /var/app/current/public/assets; gzip_static on; gzip on; expires max; add_header Cache-Control public; } location /public { alias /var/app/current/public; gzip_static on; gzip on; expires max; add_header Cache-Control public; } location /packs { alias /var/app/current/public/packs; gzip_static on; gzip on; expires max; add_header Cache-Control public; } } container_commands: 01_restart_nginx: command: "sudo service nginx reload" ``` Any ideas why it is not working? Thank you very much in advance for your kind help and support and for your valuable time I wish to all of us all the best and an amazing continuation in our lives...
1
answers
0
votes
3
views
aaon
asked a month ago

Elastic Beanstalk npm install fails without error message

I am now trying for way to long to deploy a Node.js v16, npm v8 NestJS Api to AWS Elastic Beanstalk with no success. It always stops at the point where npm install is called, which fails without further explanation. The EC2 instance used is a `t4g.small` with AWS Linux. Those are the only information I get from the log files: ``` 2022/04/06 12:17:27.564667 [INFO] Executing instruction: Use NPM to install dependencies 2022/04/06 12:17:27.564707 [INFO] use npm to install dependencies 2022/04/06 12:17:27.564755 [INFO] Running command /bin/sh -c npm config set jobs 1 2022/04/06 12:17:27.918363 [INFO] Running command /bin/sh -c npm --production install 2022/04/06 12:17:41.632070 [ERROR] An error occurred during execution of command [app-deploy] - [Use NPM to install dependencies]. Stop running the command. Error: Command /bin/sh -c npm --production install failed with error signal: killed 2022/04/06 12:17:41.632467 [INFO] Executing cleanup logic 2022/04/06 12:17:41.643564 [INFO] CommandService Response: {"status":"FAILURE","api_version":"1.0","results":[{"status":"FAILURE","msg":"Engine execution has encountered an error.","returncode":1,"events":[{"msg":"Instance deployment: 'npm' failed to install dependencies that you defined in 'package.json'. For details, see 'eb-engine.log'. The deployment failed.","timestamp":1649247461630,"severity":"ERROR"},{"msg":"Instance deployment failed. For details, see 'eb-engine.log'.","timestamp":1649247461633,"severity":"ERROR"}]}]} 2022/04/06 12:17:41.650817 [INFO] Platform Engine finished execution on command: app-deploy ``` The interesting part is that when I run everything in AWS CodeBuild it works flawlessly, but including node_modules the artifact is too big to upload to Elastic Beanstalks as the maximum file size seems to be 500 MB. Does anyone know what the problem could be?
0
answers
0
votes
4
views
Simon
asked a month ago

Elastic beanstalk Enhanced health not generating healthd/application.log files

I have Enhanced health reporting turned on for my Elastic beanstalk environment. The environment is: 1. Multicontainer docker setup running in “Amazon Linux 2” 2. It has an nginx proxy (Configuration > Software shows: Log streaming: disabled / Proxy server: nginx / Rotate logs: disabled / X-Ray daemon: disabled) 3. Enhanced monitoring is on (Configuration > Monitoring shows: CloudWatch Custom Metrics-Environment: CloudWatch Custom Metrics-Instance: / Health event log streaming: disabled / Ignore HTTP 4xx: enabled / Ignore load balancer 4xx: disabled System: Enhanced) However, on the Health page, none of the requests, response, or latency fields are populating, while load & CPU utilization are populating. It is my understanding that this data is populated from a log file that is written to `/var/log/nginx/healthd/`, but that directory is empty. It seems like this is a bug or some sort of misconfiguration. Does anyone know why this might be happening? I included some relevant info from the machine below. --- The healthd config file (I commented out the `group_id`, which is a uuid in the actual file): ``` $ cat /etc/healthd/config.yaml group_id: XXXX log_to_file: true endpoint: https://elasticbeanstalk-health.us-east-2.amazonaws.com appstat_log_path: /var/log/nginx/healthd/application.log appstat_unit: sec appstat_timestamp_on: completion ``` The output of the healthd daemon log—showing warnings for not finding previous application.log.YYYY-MM-DD-HH files: ``` $ head /var/log/healthd/daemon.log # Logfile created on 2022-04-02 21:02:22 +0000 by logger.rb/66358 A, [2022-04-02T21:02:24.123304 #4122] ANY -- : healthd daemon 1.0.6 initialized W, [2022-04-02T21:02:24.266469 #4122] WARN -- : log file "/var/log/nginx/healthd/application.log.2022-04-02-21" does not exist W, [2022-04-02T21:02:29.266806 #4122] WARN -- : log file "/var/log/nginx/healthd/application.log.2022-04-02-21" does not exist W, [2022-04-02T21:02:34.404332 #4122] WARN -- : log file "/var/log/nginx/healthd/application.log.2022-04-02-21" does not exist W, [2022-04-02T21:02:39.406846 #4122] WARN -- : log file "/var/log/nginx/healthd/application.log.2022-04-02-21" does not exist W, [2022-04-02T21:02:44.410108 #4122] WARN -- : log file "/var/log/nginx/healthd/application.log.2022-04-02-21" does not exist W, [2022-04-02T21:02:49.410342 #4122] WARN -- : log file "/var/log/nginx/healthd/application.log.2022-04-02-21" does not exist W, [2022-04-02T21:02:54.410611 #4122] WARN -- : log file "/var/log/nginx/healthd/application.log.2022-04-02-21" does not exist W, [2022-04-02T21:02:59.410860 #4122] WARN -- : log file "/var/log/nginx/healthd/application.log.2022-04-02-21" does not exist ``` The /var/logs/nginx/ directory with perms and ownership. Is `nginx` supposed to own healthd? ``` $ ls -l /var/log/nginx/ total 12 -rw-r--r-- 1 root root 11493 Apr 4 21:15 access.log drwxr-xr-x 2 nginx nginx 6 Apr 2 21:01 healthd drwxr-xr-x 2 root root 6 Apr 2 21:02 rotated ``` The empty /var/logs/nginx/healthd/ directory: ``` $ ls /var/log/nginx/healthd/ # this directory is empty ```
1
answers
3
votes
4
views
petersprst
asked a month ago

Can I freely configure AWSEBSecurityGroups created by ElasticBeanstalk in ebxtensions?

The following "01-security-group.config" was create under the .ebxtensions directory. I then ran eb create using [PHP sample application (php.zip)](https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/tutorials.html). The VPC is a custom VPC, not a default VPC. EC2 and ELB are located on public subnets. KeyPair also sets. ``` Resources: AWSEBSecurityGroup: Type: AWS::EC2::SecurityGroup Properties: GroupDescription: EC2 SecurityGroup for ElasticBeanstalk environment. SecurityGroupIngress: - ToPort: 80 FromPort: 80 IpProtocol: tcp SourceSecurityGroupId: { "Fn::GetAtt" : [ "AWSEBLoadBalancerSecurityGroup", "GroupId" ]} - ToPort: 22 FromPort: 22 IpProtocol: tcp CidrIp: xx.xx.xx.xx/32 ``` The expectation is that the AWSEBSecurityGroup description field and inbound rules will be as specified. However, the results are as follows, with a different description and an unnecessary rule (SSH, 0.0.0.0/0). ID:sg-058b4d99a88ea5c75 Description: VPC Security Group Inbound Rule | Type | Protocol | Port | Source | | --- | --- | --- | --- | | SSH | TCP | 22 | 0.0.0.0/0 | | HTTP | TCP | 80 | awseb-e-kbmrvrb9qk-stack-AWSEBLoadBalancerSecurityGroup-DXLN25QVL0F9 | | SSH | TCP | 22 | xx.xx.xx.xx/32 | Next, eb deploy was run with the following changes. ``` Resources: AWSEBSecurityGroup: Type: AWS::EC2::SecurityGroup Properties: GroupDescription: EC2 SecurityGroup for ElasticBeanstalk environment. SecurityGroupIngress: - ToPort: 80 FromPort: 80 IpProtocol: tcp SourceSecurityGroupId: { "Fn::GetAtt" : [ "AWSEBLoadBalancerSecurityGroup", "GroupId" ]} option_settings: aws:autoscaling:launchconfiguration: SSHSourceRestriction: tcp, 22, 22, xx.xx.xx.xx/32 ``` There are no more unnecessary rules in the security group as shown below. ID: sg-058b4d99a88ea5c75 Description: VPC Security Group Inbound Rule | Type | Protocol | Port | Source | | --- | --- | --- | --- | | HTTP | TCP | 80 | awseb-e-kbmrvrb9qk-stack-AWSEBLoadBalancerSecurityGroup-DXLN25QVL0F9 | | SSH | TCP | 22 | xx.xx.xx.xx/32 | Based on the above, I have two questions. 1. I would like to complete the configuration with just Resources instead of separating it with Resouces and option_seggings, is there a way to do this? 2. Is it possible to change the description field? for your information, AWSEBLoadBalancerSecurityGroup reflects the description field (security group is replaced). Thanks.
1
answers
0
votes
3
views
zizi
asked a month ago
1
answers
0
votes
6
views
AWS-User-4976942
asked a month ago

Elastic Beanstalk | .Net with Docker containg custon nginx.conf

Current Setup: Elastic Beanstalk running Docker running on 64bit Amazon Linux 2/3.4.11. I was trying to follow AWS Guidelines for overwrite nginx.conf file located in /etc/nginx/nginx.conf without any success. I have .NET 5 project containing the .platform/nginx/nginx.conf (also trying .ebextenstion). When I'm building my dockerfile and deploying to ECR, adding dockerrun.aws.json to pull the latest image its not taking my custom nginx.conf. nginx.file: ``` user nginx; worker_processes auto; error_log /var/log/nginx/error.log; pid/var/run/nginx.pid; worker_rlimit_nofile 8192; events { worker_connections 4096; } http { include /etc/nginx/mime.types; default_type application/octet-stream; access_log /var/log/nginx/access.log; log_format main '$remote_addr - $remote_user [$time_local] "$request" ' '$status $body_bytes_sent "$http_referer" ' '"$http_user_agent" "$http_x_forwarded_for"'; include conf.d/*.conf; map $http_upgrade $connection_upgrade { default "upgrade"; } server { listen 80 default_server; gzip on; gzip_comp_level 4; gzip_types text/plain text/css application/json application/x-javascript text/xml application/xml application/xml+rss text/javascript; access_log /var/log/nginx/access.log main; location / { proxy_pass http://docker; proxy_http_version 1.1; proxy_set_header Connection$connection_upgrade; proxy_set_header Upgrade$http_upgrade; proxy_set_header Host$host; proxy_set_header X-Real-IP$remote_addr; proxy_set_header X-Forwarded-For$proxy_add_x_forwarded_for; } # Include the Elastic Beanstalk generated locations include conf.d/elasticbeanstalk/*.conf; } } ``` I would like to know how can I fix it and replace the nginx default file. Thanks!
1
answers
0
votes
6
views
Ron
asked 2 months ago

AWS Elastic Beanstalk Python Application ebextenstions pip install command failed

Hi I am deploy an EB Python Web Application to a private VPC without internet access. I will install python dependency packages offline. I have all the packages ready together with application file. ``` application.py packages/*.whl packages/requirements.txt (CONTENT will be those whl packages name) .ebextensions/python_packages.config ... OTHER_VENV_RELATED_FOLDERS ``` The `ebextensions/python_packages.config` content: ``` commands: use_python_venv: command: source /opt/elasticbeanstalk/deployment/env install_python_requirements: command: pip install --no-index --find-links /var/app/current/packages -r /var/app/current/packages/requirements.txt ``` The application tested working on my local computer and I zipped `application.py`, `ebextensions` and `packages` folder into one zip file and upload and deploy into one single instance with EIP. it gets the below failed message in `/var/log/cfn-init-cmd.log` on the AMI EC2 instance. (python3.8 runtime) ``` 022-03-25 06:59:11,289 P3318 [INFO] ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 2022-03-25 06:59:11,289 P3318 [INFO] Config prebuild_0_test_xl 2022-03-25 06:59:11,289 P3318 [INFO] ============================================================ 2022-03-25 06:59:11,289 P3318 [INFO] Command install_python_requirements 2022-03-25 06:59:12,675 P3318 [INFO] -----------------------Command Output----------------------- 2022-03-25 06:59:12,675 P3318 [INFO] ERROR: Could not open requirements file: [Errno 2] No such file or directory: '/var/app/current/packages/requirements.txt' 2022-03-25 06:59:12,675 P3318 [INFO] ------------------------------------------------------------ 2022-03-25 06:59:12,675 P3318 [ERROR] Exited with error code 1 ``` I checked the path of the `requirements.txt` file and it is not there and here is the directory and files under that `/var/app` directory: ``` staging/Pipfile venv ``` It means the `/var/app/current` directory not get created so my command failed. Where is my package file during the staging process? How can I install offline python dependency packages on ElasticBeanstalk EC2 instance without internet access? Edit `Pipfile` instead? Thank you
1
answers
0
votes
2
views
xianlin_hcl
asked 2 months ago

AWS Elastic Beanstalk Running in Private VPC without internet access

My objective is to deploy a web application in a VPC **without internet access **and using Elastic Beanstalk as the platform. A single AZ deployment will be sufficient and the load balancer will be "**internal**" facing where we will access it from a windows client in the same subnet. I have created a private subnet in a VPC without internet gateway. Added a bunch of VPC endpoint interface such as `S3, SSM, ElasticBeanstalk, ElasticBeanstalk-health, sqs, cloudformation, logs` etc. Used the default security group for each endpoint. I have created EC2 instance profile with the 2 managed policy [`AWSElasticBeanstalkWebTier` and `AmazonSSMManagedInstanceCore`] and also allows sts:AssumeRole by "EC2" service. This instance profile will be used for the EB environment EC2 intance launch. I have created Elastic Beanstalk service role with the 2 managed policy [`AWSElasticBeanstalkEnhancedHealth` and `AWSElasticBeanstalkManagedUpdatesCustomerRolePolicy`] and also allows sts:AssumeRole by elasticbeanstalk service if sts:ExternalId StringEquals elasticbeanstalk. I have used a simple Nodejs.zip example file from AWS website to test. I created an environment where I have put ELB and EC2 in the same subnet without any public IP address assigned to. Used "loadbalancer" environment with min and max number of instances set to "1" (auto-scaling not needed). EBL set to "internal". Health reporting chose "Enhanced". When the environment get created, it reports error saying that "Instance has not sent any data since launch" and "None of the instances are sending data". I searched online and some answer indicate that NTP UDP port 123 should be allowed in the security group so that the EC2 instance will have a valid time sync and the health reporting will become valid. However my VPC has no internet access and does that mean I have to setup my own NTP server in the VPC and write a bootstrap script in the EC2 instance to change the NTP server from the internet NTP to the intranet NTP? That sounds a lot of work, is the NTP access the real cause for my deployment to be a failure in the private VPC? Thank you.
1
answers
0
votes
1
views
xianlin_hcl
asked 2 months ago

Run (custom) Keycloak 17 Docker Image on AWS Beanstalk

I've been trying to get a Keycloak Docker image to run on a Beanstalk environment for the last week without success. My Dockerfile looks like this: FROM quay.io/keycloak/keycloak:17.0.0 as builder ENV KC_DB=postgres RUN /opt/keycloak/bin/kc.sh build FROM quay.io/keycloak/keycloak:17.0.0 COPY --from=builder /opt/keycloak/lib/quarkus/ /opt/keycloak/lib/quarkus/ WORKDIR /opt/keycloak ENV KC_HTTP_ENABLED=true ENV KC_HOSTNAME_STRICT=false ENV KC_DB_POOL_INITIAL_SIZE=1 ENTRYPOINT ["/opt/keycloak/bin/kc.sh", "start-dev"] The Dockerimage runs fine on localhost (`docker run --rm -p 8080:8080 --env-file env.txt my/keycloak`). http://localhost:8080/ shows a start page. The chosen Plattform is a "Docker running on 64bit Amazon Linux 2/3.4.12". I upload the image to Amazon ECR and load it in a Beanstalk instance with the following Dockerrun.aws.json: { "AWSEBDockerrunVersion": "1", "Image": { "Name": "0815.eu-central-1.amazonaws.com/my/keycloak:latest" }, "Ports": [ {"ContainerPort": "8080"} ] } I have saved the necessary environment variables: KC_DB, KC_DB_PASSWORD, KC_DB_POOL_INITIAL_SIZE, KC_DB_SCHEMA, KC_DB_URL, KC_DB_USERNAME, KC_HOSTNAME_STRICT, KC_HTTP_ENABLED, KEYCLOAK_ADMIN, KEYCLOAK_ADMIN_PASSWORD As a load balancer, I set up the Classic Load Balancer with a listener from 8080/HTTP to 8080/HTTP. Now when I try to call the Beanstalk URL (http://Keycloak0815.eu-central-1.elasticbeanstalk.com:8080) I get a 503 error status. A look at the logs shows no abnormalities. Keycloak has started successfully within the docker. What am I doing wrong? What else do I need to configure to get access to the Docker image? I'm grateful for any further information.
0
answers
0
votes
1
views
akor
asked 2 months ago

How to resolve "deprecated platform branch" for EB CLI

I have a web site up and running, but want to update it, and have found the Node.js version has now been deprecated (currently 14, should be 16). I am trying to do this from the command line tool. I have created a new environment called "env-node-16", set it to the active one, then deployed. But I still get warnings that it is using the deprecated version of Node.js (or at least I assume it is referring to Node.js). Below is the transcript where I set it to use my new environment, test that that is the actie one, then check I am using the latest version of EB. But when I then deploy, it says I am using a deprecated platform branch. So I do upgrade, and it tells me it is the most recent version, and also check Node is version 16. What is deprecated? And how do I resolve it? ``` (.ebcli-virtual-env) S:\IT\f2web>eb use env-node-16 (.ebcli-virtual-env) S:\IT\f2web>eb list F2web-Mar22 * env-node-16 node-express-env (.ebcli-virtual-env) S:\IT\f2web>eb platform show Current default platform: Node.js New environments will be running: 64bit Amazon Linux 2018.03 v4.17.15 running Node.js Platform info for environment "env-node-16": Current: 64bit Amazon Linux 2018.03 v4.17.15 running Node.js Latest: 64bit Amazon Linux 2018.03 v4.17.15 running Node.js (.ebcli-virtual-env) S:\IT\f2web>eb deploy Alert: Your environment is using a deprecated platform branch. It might not be supported in the future. Creating application version archive "app-220308_105356903519". Uploading: [##################################################] 100% Done... 2022-03-08 10:56:06 INFO Environment update is starting. 2022-03-08 10:56:11 INFO Deploying new version to instance(s). 2022-03-08 10:56:53 INFO New application version was deployed to running EC2 instances. 2022-03-08 10:56:53 INFO Environment update completed successfully. (.ebcli-virtual-env) S:\IT\f2web>eb upgrade Environment already on most recent platform version. (.ebcli-virtual-env) S:\IT\f2web>node --version v16.14.0 (.ebcli-virtual-env) S:\IT\f2web> ```
0
answers
0
votes
1
views
F2Andy
asked 2 months ago

Docker: Stderr:fatal error: runtime: out of memory on AWS Elasticbeanstalk

Each time I am trying to build and deploy my React Project on AWS Elastic Beanstalk using Docker, I am getting this error: ```sh Stderr:fatal error: runtime: out of memory ``` The project is the basic react project and nothing more, serving it via nginx. What might be the reason of this error? And how do I resolve it. Please note, I have emptied my S3 bucket and have restarted the appServer too, to try and resolve any unnecessary memory or cache use. And I am able to successfully build and run this file locally. The logs are as follows: ```sh Step 1/9 : FROM node:alpine as builder ---> eb56d56623e5 Step 2/9 : WORKDIR '/app' ---> Using cache ---> 41d7415dae07 Step 3/9 : COPY package.json . ---> Using cache ---> 95877ba9972c Step 4/9 : RUN npm install ---> Using cache ---> c366758de80f Step 5/9 : COPY . . ---> 5697eace7031 Step 6/9 : RUN npm run build ---> Running in 52cc1a3e6ac0 > react-project-frontend@0.1.0 build > react-scripts --openssl-legacy-provider build Creating an optimized production build... 2022/03/03 13:14:45.346275 [WARN] failed to execute command: docker build -t aws_beanstalk/staging-app /var/app/staging/, retrying... 2022/03/03 13:14:45.425369 [INFO] Running command /bin/sh -c docker build -t aws_beanstalk/staging-app /var/app/staging/ 2022/03/03 13:14:47.001398 [ERROR] An error occurred during execution of command [app-deploy] - [Docker Specific Build Application]. Stop running the command. Error: failed to build docker image: Command /bin/sh -c docker build -t aws_beanstalk/staging-app /var/app/staging/ failed with error exit status 2. Stderr:fatal error: runtime: out of memory ```
2
answers
0
votes
5
views
Harjyot Bagga
asked 2 months ago

Modify Auto Scaling Health Check setting for Elastic Beanstalk Enviornment

Hi I have been go through the documentation for update the "`AWS:AutoScaling:AutoSclaingGroup`" in my existing EB Environment. My current environment is setup using `Docker-compose.yml `file to refer to the default .env file. I decided to go with update environment setting through AWS CLI. But i keep getting the error as below. ``` aws elasticbeanstalk update-environment --environment-name Testenv-env --template-name v1 An error occurred (ConfigurationValidationException) when calling the UpdateEnvironment operation: Configuration validation exception: Invalid option specification (Namespace: 'aws:autoscaling:autoscalinggroup', OptionName: 'HealthCheckType'): Unknown configuration setting. ``` In my v1.json file, I have the setup in below ``` aws:autoscaling:autoscalinggroup: HealthCheckType: ELB ``` Then I researched online a bit, found ppl are discussing this is no longer working, and I checked the latest API documentation, which is conflicting from the instruction in below link. Apparent "HealthCheckType" is no longer in the Support field for EB. Then I turned to another solution mentioned in below link: [https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/environmentconfig-autoscaling-healthchecktype.html](https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/environmentconfig-autoscaling-healthchecktype.html) It suggested that I use the autoscaling.config in the .ebextensions folder. However I found quite not clear instruction to how to use the .ebextensions folder with my current environment setup where I use docer-compose to refer to the default .env file when deploying. Can someone help in pointing to me a clear instruction. Another thought is, since the environment already exist, if I directly go to the ASG group in my environment, and update from there, would new deployment (with upgrade version) into my EB environment override this ASG change each time I do upgrade? Or the change will be honored and kept in the ASG group as long as it was not deleted.
1
answers
0
votes
4
views
AWS-User-3610377
asked 3 months ago

Wordpress/Nginx Failing under loads with ALB, returning 502.

Hello, I am testing a Wordpress Instance (PHP8) on Elastic beanstalk setup with a load balancer, running through Nginx. When I visit the website regularly, it works fine and I am able to browse the Wordpress instance. I wanted to try to perform a very simple load test, so I am using artillery (https://www.artillery.io/) as a load/smoke tester. As soon as the load on the server rises the server starts returning 502 responses. I've taken a look at the logs and I am seeing this. > ---------------------------------------- /var/log/nginx/access.log ---------------------------------------- 10.0.0.20 - - [08/Feb/2022:20:45:56 +0000] "GET / HTTP/1.1" 499 0 "-" "Artillery (https://artillery.io)" "IP-ADDRESS" > 10.0.0.20 - - [08/Feb/2022:20:45:57 +0000] "GET / HTTP/1.1" 499 0 "-" "Artillery (https://artillery.io)" "IP-ADDRESS" The error log says: > ---------------------------------------- /var/log/nginx/error.log ---------------------------------------- 2022/02/08 20:45:44 [error] 2882#2882: *1656 connect() to unix:/run/php-fpm/www.sock failed (11: Resource temporarily unavailable) while connecting to upstream, client: 10.0.0.20, server: , request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/run/php-fpm/www.sock:", host: "HOSTNAME.COM" I've been doing some research and it seems like some people suggest that its a PHP issue, or its an Nginx issue or a Load balancer issue. I'm not sure where to go with this, I've been trying to debug the issue and try a few different things, has anyone run into this? Does anyone have any debugging tips? Any help/guidance would be appreciated.
3
answers
0
votes
6
views
Rei
asked 3 months ago

Elastic Beanstalk Deployments Periodically Failing | /var/app/current: directory not empty | Amazon Linux 2/3.4.1

When deploying on Elastic Beanstalk (Amazon Linux 2), deployment periodically fails because the `/var/app/current` directory isn't empty. There is little consistency in when a deployment fails or succeeds. With the exact same code base, we can have multiple successes in a row, multiple failures in a row, or any combination thereof. This issue does not seem specific to one platform either based on this [old AWS Developer Forum post](https://forums.aws.amazon.com/thread.jspa?threadID=335593) that experienced it on PHP, while we're experiencing it on Ruby. Here are the more detailed specifics which are a combination of comments from the now archived thread, and my updated experiences since it was archived. -- Error on `Platform PHP 7.4, Amazon Linux 2/3.1.5` ``` 2021/02/12 19:16:54.204134 Executing instruction: FlipApplication 2021/02/12 19:16:55.339260 An error occurred during execution of command https://forums.aws.amazon.com/ - https://forums.aws.amazon.com/. Stop running the command. Error: remove current dir failed: unlinkat /var/app/current: directory not empty 2021/02/12 19:16:55.339271 Executing cleanup logic 2021/02/12 19:16:55.339344 CommandService Response: {"status":"FAILURE","api_version":"1.0","results":[{"status":"FAILURE","msg":"Engine execution has encountered an error.","returncode":1,"events":} ``` Error on `Platform Ruby 3.0, Amazon Linux 2/3.4.1` ``` 2022/02/01 22:36:13.837697 [ERROR] An error occurred during execution of command [app-deploy] - [flip ruby application]. Stop running the command. Error: remove current dir failed: unlinkat /var/app/current/tmp/cache/bootsnap/compile-cache-iseq/c0: directory not empty 2022/02/01 22:36:13.838041 [INFO] Executing cleanup logic 2022/02/01 22:36:13.838350 [INFO] CommandService Response: {"status":"FAILURE","api_version":"1.0","results":[{"status":"FAILURE","msg":"Engine execution has encountered an error.","returncode":1,"events":[{"msg":"Instance deployment failed. For details, see 'eb-engine.log'.","timestamp":1643754973,"severity":"ERROR"}]}]} ``` I also experienced this same issue on `Platform Ruby 2.7, Amazon Linux 2/3.2.4` -- I am able to get around this issue by removing the ruby gem `bootsnap` which caches some components of the Rails app, but as this issue seems to affect other language platforms as well I can't really blame `bootsnap` directly, and removing it does detrimentally affect our app. I'm not sure if the PHP users also use some sort of caching process. I've also attempted changing file permissions via deployment hooks to force delete the contents of `/var/app/current` but the same issue still is presented. Any ideas would be very welcomed!
1
answers
0
votes
5
views
JoeyParis
asked 3 months ago

Elastic Beanstalk failed to unzip source file with UTF-8 file name

I was trying to deploy a NextJS application to Elastic Beanstalk via `eb deploy`. But the source bundle failed to unzip during deployment as the source bundle contained some pre-built .next page which the file name is in UTF-8 encoding. The error is stated as below. ``` 2022/xx/xx xx:xx:xx.xxxxxx [INFO] Executing instruction: StageApplication 2022/xx/xx xx:xx:xx.xxxxxx [INFO] extracting /opt/elasticbeanstalk/deployment/app_source_bundle to /var/app/staging/ 2022/01/31 04:56:44.300483 [INFO] Running command /bin/sh -c /usr/bin/unzip -q -o /opt/elasticbeanstalk/deployment/app_source_bundle -d /var/app/staging/ 2022/01/31 04:56:45.932820 [ERROR] An error occurred during execution of command [app-deploy] - [StageApplication]. Stop running the command. Error: Command /bin/sh -c /usr/bin/unzip -q -o /opt/elasticbeanstalk/deployment/app_source_bundle -d /var/app/staging/ failed with error exit status 50. Stderr:error: cannot create /var/app/staging/.next/server/pages/\u6e2c\u8a66/\u6e2c\u8a66\u6e2c\u8a66\u6e2c\u8a66\u6e2c\u8a66\u6e2c\u8a66\u6e2c\u8a66\u6e2c\u8a66\u6e2c\u8a66\u6e2c\u8a66\u6e2c\u8a66\u6e2c\u8a66\u6e2c\u8a66\u6e2c\u8a66\u6e2c\u8a66\u6e2c\u8a66\u6e2c\u8a66\u6e2c\u8a66\u6e2c\u8a66\u6e2c\u8a66\u6e2c\u8a66\u6e2c\u8a66.html File name too long error: cannot create /var/app/staging/.next/server/pages/\u6e2c\u8a66/\u6e2c\u8a66\u6e2c\u8a66\u6e2c\u8a66\u6e2c\u8a66\u6e2c\u8a66\u6e2c\u8a66\u6e2c\u8a66\u6e2c\u8a66\u6e2c\u8a66\u6e2c\u8a66\u6e2c\u8a66\u6e2c\u8a66\u6e2c\u8a66\u6e2c\u8a66\u6e2c\u8a66\u6e2c\u8a66\u6e2c\u8a66\u6e2c\u8a66\u6e2c\u8a66\u6e2c\u8a66\u6e2c\u8a66.json File name too long ``` I was able to unzip the file with option `-O UTF-8`, is there any way I could add this flag to the `eb deploy` unzip process? edit 1. I am working with the Platform `64bit Amazon Linux 2/5.4.9`
0
answers
0
votes
2
views
AWS-User-4285016
asked 4 months ago
  • 1
  • 90 / page