I've run into something weird so I thought I'd share it here in the hopes of helping someone else.
I used EB CLI to create an environment using eb create passing it additional arguments etc.
After a minute or so I received the following error:
2020-07-28 11:20:44 INFO Build in progress. Phase: QUEUED Status: SUCCEEDED
2020-07-28 11:20:44 INFO Build in progress. Phase: PROVISIONING Status: SUCCEEDED 2020-07-28 11:20:44 ERROR Build in progress. Phase: DOWNLOAD_SOURCE Status: FAILED YAML file does not exist
ERROR: ServiceError - Finished processing application version app-5fd9-200728_211901 with status: FAILED.
Changing buildspec.yml to buildspec.yaml solved my problem.
Related
I am just finding wazuh and wanted to test it out. I have tried the step by step and the scripted. Cannot get it to work. So I am consolidating my deployment to just 1 VM and am trying to run the quickstart to get going. When I try to install I get the below error. I cannot find anything related to wazuh-indexer 4.3.1-1. Thoughts?
10/05/2022 12:52:37 INFO: Created wazuh-install-files.tar. It contains the Wazuh cluster key, certificates, and passwords necessary for installation.
10/05/2022 12:52:37 INFO: --- Wazuh indexer ---
10/05/2022 12:52:37 INFO: Starting Wazuh indexer installation.
Updating Subscription Management repositories.
EL-8 - Wazuh 75 kB/s | 3.4 kB 00:00
No match for argument: wazuh-indexer-4.3.1-1
Error: Unable to find a match: wazuh-indexer-4.3.1-1
10/05/2022 12:52:48 ERROR: Wazuh indexer installation failed.
10/05/2022 12:52:48 INFO: --- Removing existing Wazuh installation ---
10/05/2022 12:52:48 INFO: Installation cleaned. Check the /var/log/wazuh-install.log file to learn more about the issue.
The root of that error is that the script is trying to download
wazuh-indexer-4.3.1-1 instead of the current wazuh-indexer-4.3.0-1.
It seems that the production script included this bug for a short period of time. Please download the script and install it again.
Sorry for the inconvenience.
You are correct. After waiting a few days, the bug was fixed. But am now hitting a new bug. When trying to run filebeat setup --dashboards. I get an error: Exiting: Kibana API is not available in Kibana version 1.2.0
I have the setting:
compatibility.override_main_response_version: true
on my opensearch.yml but still no avail.
If you are using the wazuh-install script, it is not required to perform any further configuration.
In order to troubleshoot this issue, could you please provide us with the following information:
Architecture: Single host or multi-node
Installation method: Step by step installation
Documentation page you follow to install your environment
OS of your nodes
I recommend you to join Wazuh slack channel (https://wazuh.com/community/) and move this issue there, or into the Wazuh google group in order to be able to correctly monitor this problem
I have 4 Elastic Beanstalk deployments: 3 are Corretto 8 and the other one is Corretto 11.
On the Corretto 8 deployments, I can set new configuration without issue. On the Corretto 11 instance, however, any attempt to set a new configuration fails and causes a rollback.
The Corretto versions might not be the problem, but it's the only difference I can see. All 4 apps are Spring Boot apps that run as web servers (i.e embedded tomcat with exposed web ports). I am trying to set the exact same configuration name and value, and it only fails on the one instance.
The configuration I'm trying to set is pretty simple:
VALIDATE_RENEWALS = true
Even just trying to set DEBUG = true causes a failure and rollback.
I don't see a lot of information from the console about what's failing. Here is the event log:
2020-03-16 13:55:17 UTC-0600 INFO The environment was reverted to the previous configuration setting.
2020-03-16 13:54:45 UTC-0600 ERROR During an aborted deployment, some instances may have deployed the new application version. To ensure all instances are running the same version, re-deploy the appropriate application version.
2020-03-16 13:54:45 UTC-0600 ERROR Failed to deploy configuration.
2020-03-16 13:54:45 UTC-0600 ERROR Unsuccessful command execution on instance id(s) 'i-00553f4ac36afd327'. Aborting the operation.
2020-03-16 13:54:45 UTC-0600 INFO Command execution completed on all instances. Summary: [Successful: 0, Failed: 1].
2020-03-16 13:54:45 UTC-0600 ERROR [Instance: i-00553f4ac36afd327] Command failed on instance. An unexpected error has occurred [ErrorCode: 0000000001].
2020-03-16 13:54:20 UTC-0600 INFO Updating environment XXX's configuration settings.
2020-03-16 13:54:15 UTC-0600 INFO Environment update is starting.
I've also downloaded the full set of logs for the instance and don't see anything obvious. The app stdout doesn't have any errors or exceptions, it just starts normally and then gets terminated. None of the other log files have messages around the times above, so I'm really not sure what else I can look at.
Edit
The times don't line up but I do see this in eb-engine.log file:
2020/03/16 17:54:38.508634 [INFO] checking whether command is applicable to this instance...
2020/03/16 17:54:38.508658 [INFO] this command is applicable to the instance, thus instance should execute command
2020/03/16 17:54:38.508665 [INFO] check whether this is an enhanced env...
2020/03/16 17:54:38.508794 [INFO] Executing instruction: StageJavaApplication
2020/03/16 17:54:38.508858 [ERROR] GetArchivedFileType with file /opt/elasticbeanstalk/deployment/app_source_bundle failed with error open /opt/elasticbeanstalk/deployment/app_source_bundle: no such file or directory
2020/03/16 17:54:38.508868 [ERROR] An error occurred during execution of command [config-deploy] - [StageJavaApplication]. Stop running the command. Error: staging java app failed with error GetArchivedFileType with file /opt/elasticbeanstalk/deployment/app_source_bundle failed with error open /opt/elasticbeanstalk/deployment/app_source_bundle: no such file or directory
I am Trying to Install Openshift 3.9.1 In CentOS 7.5. All the process Done but Below Failed Issue Occurring. If you have any suggestion about it,
( Running Handler [ openshift_master : verify API Server ])
FAILED - RETRYING Verify API Server (120 retries left).
install configuration
problem occurring...
If any proper step by step guideline notice me. thanks
I'm trying to deploy my grails app to Cloud Foundry and I'm getting the eror below.
I'm wondering if my mysql datasource is correctly configured in DataSource.groovy and this could be causing the issue or I'm missing something else.
====> /logs/staging.log <====
Uploading Application:
Checking for available resources: OK
Processing resources: OK
Packing application: OK
Uploading (116K): OK
Push Status: OK
Staging Application: ..Error 310: Staging failed: 'Staging plugin failed staging application:
/var/vcap/packages/stager/stager/vendor/bundle/ruby/1.9.1/gems/vcap_staging-0.1.44/lib/vcap/staging/plugin/java_web/plugin.rb:25:in block in stage_application': Web application staging failed: web.xml not found (RuntimeError)
from /var/vcap/packages/stager/stager/vendor/bundle/ruby/1.9.1/gems/vcap_staging-0.1.44/lib/vcap/staging/plugin/java_web/plugin.rb:19:inchdir'
from /var/vcap/packages/stager/stager/vendor/bundle/ruby/1.9.1/gems/vcap_staging-0.1.44/lib/vcap/staging/plugin/java_web/plugin.rb:19:in stage_application'
from /var/vcap/packages/stager/stager/bin/run_plugin:19:in'
'
I tried to run grails cf-list-files to check tomcat logs but I got the following error:
| Environment set to development.....
Error: 400 Bad Request
| Error org.cloudfoundry.client.lib.CloudFoundryException: 400 Bad Request (Operation not permitted on a stopped app)
| Error at org.cloudfoundry.client.lib.CloudFoundryClient$ErrorHandler.handleError(CloudFoundryClient.java:78)
| Error at org.cloudfoundry.client.lib.CloudFoundryClient.getFile(CloudFoundryClient.java:463)
As tomas posted on 3/27,
grails install-plugin cloud-foundry followed by grails cf-push
I just added the hudson-artifactory plugin, and everything run marvelously with Maven, but when I tried to build the project with gradle (I added the gradle plugin to hudson)
I got this error:
FAILURE: Build failed with an
exception. * Where: Initialization
script 'C:\Documents and
Settings\qqqqqqqqqqqq.hudson\jobs\skiiiiiiiiiin\builds\2010-08-10_10-45-03\init-artifactory.gradle'
line: 2 * What went wrong: A problem
occurred evaluating initialization
script. Cause: No signature of method:
org.gradle.invocation.DefaultGradle.apply()
is applicable for argument types:
(init_artifactory_gradle_bb54a6ea5f854f8feae8c6181e5acbf4$_run_closure1_closure2)
values:
[init_artifactory_gradle_bb54a6ea5f854f8feae8c6181e5acbf4$_run_closure1_closure2#1d7b222]
* Try: Run with -s or -d option to get more details. Run with -S option to
get the full (very verbose)
stacktrace. BUILD FAILED Total time:
1.942 secs Finished: FAILURE
The plugin requires Gradle 0.9-preview-3+
Try using the latest version.
we must add gradle.artifactoryonline.com/gradle/libs and gradle.artifactoryonline.com/gradle/plugins on remote repository :)) and everything works !