gpt4 book ai didi

amazon-web-services - AWS BeanstalkL 错误 : InvalidParameterValueError - No Application Version named?

转载 作者:行者123 更新时间:2023-12-03 15:57:23 25 4
gpt4 key购买 nike

我正在尝试通过 Amazon beanstalk 部署一个可扩展的 wordpress 站点,但是当我尝试部署时遇到了问题。我最初创建了一个环境,但终止并创建了一个新环境,现在我遇到了部署问题,而在部署之前,但我的公共(public) IP 无法正常工作。

以下是我运行 eb --debug 命令时得到的结果。

C:\Projects\SwagBox\wordpress>eb --debug 2018-06-23 06:06:54,671 (DEBUG) cement.core.foundation : laying cement for the 'eb' application 2018-06-23 06:06:54,671 (DEBUG) cement.core.hook : defining hook 'pre_setup' 2018-06-23 06:06:54,671 (DEBUG) cement.core.hook : defining hook 'post_setup' 2018-06-23 06:06:54,672 (DEBUG) cement.core.hook : defining hook 'pre_run' 2018-06-23 06:06:54,672 (DEBUG) cement.core.hook : defining hook 'post_run' 2018-06-23 06:06:54,672 (DEBUG) cement.core.hook : defining hook 'pre_argument_parsing' 2018-06-23 06:06:54,672 (DEBUG) cement.core.hook : defining hook 'post_argument_parsing' 2018-06-23 06:06:54,672 (DEBUG) cement.core.hook : defining hook 'pre_close' 2018-06-23 06:06:54,672 (DEBUG) cement.core.hook : defining hook 'post_close' 2018-06-23 06:06:54,672 (DEBUG) cement.core.hook : defining hook 'signal' 2018-06-23 06:06:54,672 (DEBUG) cement.core.hook : defining hook 'pre_render' 2018-06-23 06:06:54,672 (DEBUG) cement.core.hook : defining hook 'post_render' 2018-06-23 06:06:54,672 (DEBUG) cement.core.hook : registering hook 'add_handler_override_options' from cement.core.foundation into hooks['post_setup'] 2018-06-23 06:06:54,673 (DEBUG) cement.core.hook : registering hook 'handler_override' from cement.core.foundation into hooks['post_argument_parsing'] 2018-06-23 06:06:54,673 (DEBUG) cement.core.handler : defining handler type 'extension' (IExtension) 2018-06-23 06:06:54,673 (DEBUG) cement.core.handler : defining handler type 'log' (ILog) 2018-06-23 06:06:54,673 (DEBUG) cement.core.handler : defining handler type 'config' (IConfig) 2018-06-23 06:06:54,673 (DEBUG) cement.core.handler : defining handler type 'mail' (IMail) 2018-06-23 06:06:54,673 (DEBUG) cement.core.handler : defining handler type 'plugin' (IPlugin) 2018-06-23 06:06:54,673 (DEBUG) cement.core.handler : defining handler type 'output' (IOutput) 2018-06-23 06:06:54,673 (DEBUG) cement.core.handler : defining handler type 'argument' (IArgument) 2018-06-23 06:06:54,673 (DEBUG) cement.core.handler : defining handler type 'controller' (IController) 2018-06-23 06:06:54,674 (DEBUG) cement.core.handler : defining handler type 'cache' (ICache) 2018-06-23 06:06:54,675 (DEBUG) cement.core.handler : registering handler '<class 'cement.core.extension.CementExtensionHandler'>' into handlers['extension']['cement'] 2018-06-23 06:06:54,675 (DEBUG) ebcli.core.fileoperations : Project root found at: C:\Projects\SwagBox\wordpress 2018-06-23 06:06:54,680 (DEBUG) ebcli.core.fileoperations : Project root found at: C:\Projects\SwagBox\wordpress 2018-06-23 06:06:54,688 (DEBUG) ebcli.core.fileoperations : Project root found at: C:\Projects\SwagBox\wordpress 2018-06-23 06:06:54,717 (DEBUG) cement.ext.ext_plugin : plugin config dir C:\etc\eb\plugins.d does not exist. 2018-06-23 06:06:54,718 (DEBUG) cement.ext.ext_plugin : plugin config dir C:\Users\saly\.eb\plugins.d does not exist. 2018-06-23 06:06:54,727 (DEBUG) ebcli.core.hooks : -- EBCLI Version: 3.14.1 2018-06-23 06:06:54,727 (DEBUG) ebcli.core.hooks : -- Python Version:
3.6.5 (v3.6.5:f59c0932b4, Mar 28 2018, 16:07:46) [MSC v.1900 32 bit (Intel)] 2018-06-23 06:06:54,727 (DEBUG) ebcli.core.fileoperations : Project root found at: C:\Projects\SwagBox\wordpress 2018-06-23 06:06:54,743 (DEBUG) ebcli.objects.sourcecontrol : Getting current branch name by performing `git rev-parse --abbrev-ref HEAD` 2018-06-23 06:06:54,804 (DEBUG) ebcli.objects.sourcecontrol : master 2018-06-23 06:06:54,804 (DEBUG) ebcli.core.fileoperations : Project root found at: C:\Projects\SwagBox\wordpress 2018-06-23 06:06:54,822 (DEBUG) ebcli.core.fileoperations : Project root found at: C:\Projects\SwagBox\wordpress 2018-06-23 06:06:54,833 (DEBUG) ebcli.core.fileoperations : Project root found at: C:\Projects\SwagBox\wordpress 2018-06-23 06:06:54,840 (DEBUG) ebcli.objects.sourcecontrol : Getting current branch name by performing `git rev-parse --abbrev-ref HEAD` 2018-06-23 06:06:54,889 (DEBUG) ebcli.objects.sourcecontrol : master 2018-06-23 06:06:54,889 (DEBUG) ebcli.core.fileoperations : Project root found at: C:\Projects\SwagBox\wordpress 2018-06-23 06:06:54,903 (DEBUG) ebcli.core.fileoperations : Project root found at: C:\Projects\SwagBox\wordpress 2018-06-23 06:06:54,912 (DEBUG) ebcli.core.fileoperations : Project root found at: C:\Projects\SwagBox\wordpress usage: eb (sub-commands ...) [options ...] {arguments ...}

Welcome to the Elastic Beanstalk Command Line Interface (EB CLI). For more information on a specific command, type "eb {cmd} --help".

commands: abort Cancels an environment update or deployment. appversion Listing and managing application versions clone Clones an environment. codesource Configures the code source for the EB CLI to use by default. config Modify an environment's configuration. Use subcommands to manage saved configurations. console Opens the environment in the AWS Elastic Beanstalk Management Console. create Creates a new environment. deploy Deploys your source code to the environment. events Gets recent events. health Shows detailed environment health. init Initializes your directory with the EB CLI. Creates the application. labs Extra experimental commands. list Lists all environments. local Runs commands on your local machine. logs Gets recent logs. open Opens the application URL in a browser. platform Commands for managing platforms. printenv Shows the environment variables. restore Restores a terminated environment. scale Changes the number of running instances. setenv Sets environment variables. ssh Opens the SSH client to connect to an instance. status Gets environment information and status. swap Swaps two environment CNAMEs with each other. tags Allows adding, deleting, updating, and listing of environment tags. terminate Terminates the environment. upgrade Updates the environment to the most recent platform version. use Sets default environment.

optional arguments: -h, --help show this help message and exit --debug toggle debug output --quiet suppress all output -v, --verbose toggle verbose output
--profile PROFILE use a specific profile from your credential file -r REGION, --region REGION
use a specific region --no-verify-ssl do not verify AWS SSL certificates --version show application/version info

To get started type "eb init". Then type "eb create" and "eb open"

我得到的实际错误是:
Creating application version archive "app-3422-180623_061101".
Uploading: [##################################################] 100% Done...
ERROR: InvalidParameterValueError - No Application Version named 'app-3422-180623_061101' found.

应用程序版本是否每次都更改。

我已经在网上寻找解决方案,但我仍然是新手,无法弄清楚。

我也跑了

eb config



并检查我的环境名称和应用程序名称是否正确。第一次通过 AWS 上的 IAM 连接时,我也选择了正确的区域。

再次感谢!对此,我真的非常感激 :)

编辑:错别字

最佳答案

好的,我设法让部署者工作,它在 beanstalk 仪表板中的版本下匹配。

我进入了最初启动 git 的文件夹并删除了 .beanstalk 文件夹。这促使我再次配置所有内容,这次我选择了正确的应用程序名称,这很有效。

谢谢!

关于amazon-web-services - AWS BeanstalkL 错误 : InvalidParameterValueError - No Application Version named?,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/51001505/

25 4 0
Copyright 2021 - 2024 cfsdn All Rights Reserved 蜀ICP备2022000587号
广告合作:1813099741@qq.com 6ren.com