Why do I get 404 not found error when trying to load my just-deployed Source Bundle in AWS Elastic Beanstalk? - amazon-s3

Overview
I have a very simple CodePipeline that deploys new versions of an application to my AWS Elastic Beanstalk environment. If I run the pipeline, it works and the application is deployed without errors. But if I then navigate to view the "Application versions" for my application, and click the link for the "Source Bundle" for the just-now-deployed version at the top of the list, I'm just shown a generic AWS 404 not found page. If I click on ANY source bundle links, I see the same error.
What in the world is happening?
Some context
The CodePipeline successfully uploads the build artifacts to the designated artifact bucket. Those artifacts are all still there. The links from the Application Versions page don't seem to be resolving correctly.
I have a Lifecycle defined for my Application Versions to limit to the last 50 versions, and to retain the source bundles in S3. The source bundles are in the bucket mentioned in the previous paragraph, designated for the artifacts, but there are no source bundles in the elasticbeanstalk bucket. This has puzzled more than one AWS Support technicians already.

Nevermind, I was using the new fancy redesigned beta console. The link in the old console works perfectly.

Related

Error running Google App Engine Standard via IntelliJ - can't find appengine-web.xml

I'm trying to locally run/debug a Google App Engine Standard app written in Kotlin. Here's the basic stack:
IntelliJ IDEA Ultimate
Google App Engine Standard
Gradle
Kotlin
I followed these directions: https://cloud.google.com/code/docs/intellij/deploy-local#running_your_application_locally
So far so good.
But when I go to run it (via IntelliJ Run menu), I get the following error:
NoSuchFileException during local run: Error occurred during local run. Please first confirm that there is a properly placed appengine-web.xml file. If missing, either use the Cloud Code shortcut action under: 'Tools > Cloud Code > Add App Engine Support > Google App Engine Standard' Or manually generate an appengine-web.xml file in the WEB-INF directory of your module's web resource directory, (show balloon)
Error running '(my run config)': Encountered an error starting the App Engine local development server process.
AFAIK, the file is in the correct place (I even tried deleting it and having Google's plugin regenerate it for me - it put it in the same place/same name).
Any ideas how to fix this error? I've spent 2 days just debugging various tool issues with this stack, but can't get past this one.
UPDATE:
Here's the run configuration I'm using.
If you right-click on the project, then click on Open Module Settings.
Under Project Settings click on Artifacts.
Choose your war exploded file.
You should notice that on the Output Layout tab under Available Elements you will need to add your JPA descriptors by double-clicking that.
This resolved the issue for me with on this exact error.

Just deploy cloudformation changes with serverless framework for AWS

I am making changes just to custom resources in my serverless.yml with an AWS provider. The package from the lambda code is not changing, it's already uploaded to S3 from a previous deploy.
How can I say "use the artifacts already in S3, just upload the changed cloudformation template and update the stack using that"?
Updating only the infrastructure with the Serverless Framework is not something achievable as of right now. You will need to perform a full deployment even if there were no code changes.
However, executing a regular sls deploy won't do the trick if no code has changed as the framework won't detect infrastructure changes only. If you want to force a redeployment (i.e you have hooked up a new trigger for your Lambda function in your serverless.yml file), you must force the deployment by using the --force flag
sls deploy --force

Worklight error: File not found: /css/images/wl_app_warning.png

I have found an issue with my worklight project. What i have done here is as follows:
I have a project which was built and deployed without any issues.
I wanted to edit most of the images and re-arrange the whole images folder structure.
So I deleted all the contents in the images folder completely from eclipse so that i can save each new image to the newly created folders
Now, i created new folders in images folder and saved one image to one of the newly created folders.
I tried to run the application on mobileFirst development server and started getting the error message:
"SRVE0190E: File not found: /css/images/wl_app_warning.png"
We did not even have a folder named images in css folder before.
This is what happened for me and does this give any clue for the issue??
Please help.
This is a defect in the admin service, and is tracked as APAR PI51055, which you can find more information about here:
http://www-01.ibm.com/support/docview.wss?uid=swg1PI51055
The issue has been corrected in iFix IF20151103-1015 and later builds.
If you have paid support, you will be able to download an iFix build from IBM Fix Central sometime soon that includes this fix - it is not out there for download right now, but I expect it will be within a couple of weeks. If you need the fix before it appears on IBM Fix Central, you can open a PMR and ask the support team to provide it. If you are using the free Developer Edition from the Eclipse Marketplace, I expect the fix will appear there soon also, and you can use the Eclipse software update function to get it, but I am not sure how frequently the Developer Edition repository is updated.
In my project I created an "images" folder with an image:
I then used it in the HTML:
<img src="css/images/wl_app_warning.png"/>
No errors and the image is displayed...

IBM Worklight 6.0 - Dojo library uses localhost after deploy

I have a Worklight 6.0 project that uses the new Dojo 1.9 libs, I created an external dojo project, like the documentation suggested, then, in the main project properties, under "Dojo toolkit", it references this dojo19 project.
The project works on the local server, then I did "Run As" | "Build for Remote Server...", and entered the correct domain:port and context path, clicked Build, the *.wlapp files were updated. (I've also updated the settings for publicWorkLightHostname / publicWorkLightPort / publicWorkLightProtocol in the "Environment Entries for Web Modules" in the installed war to match the remote server names/port/protocol.)
But, after deploying both war and -all.wlapp file, accessing the app I get JS errors when it tries to refer to the dojo19 library:
The page at
https://<myIP>:9443/<myproject>/apps/services/www/ /mobilewebapp/default/IODMobile.html
ran insecure content from http://localhost:64441/dojo19/<myproject>/IODMobile/mobilewebapp/dojo/nls/core-web-layer_en-us.js.
The dojo19 is the project name in my Worklight developer workspace that I referred to above.
Why is it trying localhost? Seems there's a missing step here in deploying the dojo library project into Worklight.
Where are you trying to preview the application when you get the error message?
See the changes in Dojo in Worklight 6.0
If launching the application in emulator/simulator/device, see Billy Rowe's answer in this question
Partial copy/paste:
Step 1: Verify your application works in the Mobile Browser Simulator
with Provide Library Resources checked. If the Console log is showing
resources being served from the server, then these have to be copied
to your application before deploying to AVD or a device
Step 2: After you think you have all Dojo/resources within your
project, uncheck Provide Library Resources and test it again in MBS.
If it fails in MBS, then something is missing in your application that
is in the library/server. You can check Provide Library Resources and
retest to see if it shows you what that is. Not all resources are
shown, e.g. if there's a missing CSS file.
Also I would suggest to do all of this in the Development environment (that is, in Eclipse) before starting to deploy the .war file and .wlapp file etc... (which, BTW, I hope you're doing based on the new instructions for Worklight 6.0)
In the information center, it will show you how to uncheck the Provide Library Resources in the Console Log.
I think what you're running into is:
1) Something is being served from the Dojo Library/Server
2) A bug in 6.0 that used "localhost" instead of the IP of the host (your machine running eclipse). This is fixed in the 6.0 iFix. With this fix, you can run your app external to Studio and still use the Dojo Library/Server. Without this fix, you must have everything you need within your app.
Can you install the iFix and let us know if that fixed the problem?

Where Jboss7.1 take war application to deploy

I've deployed the jboss-as-helloworld-errai application in my standalone jboss7.1 instance, and I deleted it later ( in the */standalone/deployments folder). But every time I restart my server it redeploys that application.
Is there another place where jboss reads the application to deploy?
Best regard
Did you delete the file while the server was running?
Probably, JBoss still finds a deployment information in one your /standalone/configuration/standalone*.xml files (at the end of the file). JBoss unpacks its deployments in one of the /standalone/tmp/vfs/temp* folders. As long as it finds a deployment in your configuration file, it will start the application.
The deployment binaries are located under the standalone/data/content. These would also need to be deleted. The best solution is to properly undeploy the application via CLI, the maven plug-in or the web console.
This does not sound like expected behaviour. Can you please confirm the steps that you are taking when using the deployment folder? For example:
Deploy
Copy application file to /standalone/deployments folder
Deployment Scanner creates a .dodeploy marker file
Deployment Scanner picks up application and creates a .deployed marker file
Application confirmed as deployed (checking the Management Console to confirm)
Undeploy
Application deleted from /standalone/deployments folder
Delete application (or) delete .deployed marker file
Deployment scanner undeploys the application and creates .undeployed marker file
Confirm application removed in console
Restart server
Confirmed removal is persistent
The README.txt file in the deployments folder shows the simple undeployment workflow in one easy step in the command line.
rm $AS/standalone/deployments/example.war.deployed
Documentation
You can read more about the deployment scanner in the official docs. There's a topic about the scanner marker files, as well as a parent topic about the scanner and deployments in general. If you are finding issues with the scanner, it's a bug. You might like to test the expected behaviour, and also try the Management Console.
Red Hat Docs - Reference for Deployment Scanner Marker Files
Red Hat Docs - About Application Deployment
Potential Issues
Don't confuse the Deployment Scanner subsystem (which watches the Deployments folder for the Standalone server instance) with the Management Console or Management CLI deployments process. You might be better off using one of the Management tools instead of the hot deployment capability to allow for more control over the state and presence of your application.