I did some modification in a working app,but during pushing it on bluemix cloud ,I am getting some error.
Below is the snippet:
Starting app resapp in org x / space y ... OK
-----> Downloaded app package (1.8M)
-----> Downloaded app buildpack cache (9.2M)
-----> Buildpack Version: v1.4-20140908-1746
FAILED
Server error, status code: 400, error code: 170004, message: App staging failed in the
buildpack compile phase
TIP: use 'cf logs resapp --recent' for more information
Can you please try again, googled and found that its an intermittent issue.
Hope it helps...
I faced the same issue when I created my own buildpack from github and modified https://github.com/ibmdb/db2heroku-buildpack-php/blob/master/bin/compile file. After modifying compile file, 'cf push' was failing with same error when I was trying to push my app in bluemix. The issue was with new changes in 'compile' file.
The error clearly says that "App staging failed in buildpack compile phase". So, there is an issue with compile file of buildpack. If you are using original buildpack that is not modified by you, then try after sometime; issue may get solved. If, you have created your own buildpack by cloning the original from github, then verify the changes in 'compile' file. Yes, you should run 'cf logs resapp --recent' command to get details about error.
Its an intermittent issue,i too faced this once, retry if happening again. It will work.
Related
My firebase hosting deployments have suddenly started failing both in my Github CI Workflows and from my local machine.
$ firebase deploy --only hosting
=== Deploying to '<project>'...
i deploying hosting
Error: Failed to list functions for <project>
The project in question does not have any functions, and only hosts a static site. Google searches for "Failed to list functions" turn up empty, it seems like not a common problem. The only leads I can find indicate some kind of network error.
I have updated my firebase-tools, logged out and in again to generate a new CI token, tried the process from my Github workflows and also manually from my machine, all to the same effect.
I can't find any information about this problem, except that the error seems to come from this part of the firebase-tools codebase:
https://github.com/firebase/firebase-tools/blob/c0f19a32845135108c75a1050024965cb1e3f52d/src/gcp/cloudfunctions.ts
My firebase tools version was 11.14.0. I changed that to 11.13.0. Installed this specific version through npm install -g firebase-tools#11.13.0. After that I could successfully deploy.
I came across the issue. using firebase-tools version 10.5 or upgrading it to blaze plan fixed my issue
I deployed a bna archive file to my ibm cloud instance. It has all the files you'd expect including the package.json. This was done following the tutorial here: https://console.bluemix.net/docs/services/blockchain/develop_starter.html#deploying-a-business-network
The last step in the process is a ping issued to ensure the network is up and running. I am getting an error telling me that the "chaincode is not instantiated".
I went to the web interface ( https://blockchain-starter.eu-gb.bluemix.net/network/myid ) and under My Code / Install Code section I can see my network. Under Actions there is an option to instantiate it on a peer. Clicking that gives me this error : Unknown error occurred when instantiating chaincode, check your peer logs.
Looking at the logs on the peer I can see this:
{"log":"npm ERR! enoent ENOENT: no such file or directory, open '/usr/local/src/package.json'\n","stream":"stderr","time":"2018-06-19T13:20:48.455812355Z"}
That particular file IS part of my bna archive.
I can deploy the bna file to both my local composer-playground and also IBM's one ( https://blockchaindevelop.mybluemix.net/ ) and it works fine in both environments.
The same issue happens if I deploy the bna using the web interface, I simply can't instantiate it.
Any suggestions what I can do to get this network running?
In the end it was a software version issue.
The original documentation specified using composer 0.18.1 as the only one compatible with the IBM cloud infrastructure.
This has recently been updated to 0.19.x.
In the IBM cloud, I removed the original peer with all the old chaincode, removed the old certificate as well.
On my local machine I started from scratch:
reinstalled latest composer,
recreated the bna file
I then re-did all the steps as in the original documentation and this time everything worked and I managed to start the network and ping it.
Everything is up and running now. There was one last timeout issue when I tried to start the network, but I simply ran the command again and the problem went away.
My application is developed in Grails 2.4.4. It uses MongoDB-3.0.2 plugin. I use Hudson as my CI system.
Sometimes when the job in hudson tries to build the application war, I get the below error.
Error | Resolve error obtaining dependencies: Failed to read artifact
descriptor for
org.grails:grails-datastore-gorm-plugin-support:jar:3.1.3.BUILD-SNAPSHOT
(Use --stacktrace to see the full trace)
It doesn't happen all the time. Many times the war was built successfully. Recently I am facing this problem more frequently.
In one of the question similar to this this, someone has suggested to change the Snapshot version to Release version. I tried it but didn't help me.
I also faced this problem in dev environment few times.
Can anyone let me know what could be the issuse? Could it be connectivity problem between the repository and my system?
Our SSL certificate expired this morning. We are working to get it addressed. An option to use as a workaround would be to use http instead of https. See comments at https://github.com/grails/grails-core/issues/9200.
The process is almost complete to get the new cert in place. Sorry for the trouble.
Hi my friend and I are facing this problem where we are unable to create a Heroku application in eclipse. We keep running into the error and the error is java.lang.reflect.InvocationTargetException. We followed Heroku eclipse but it still gives the error. My friend even downloaded the newest eclipse no no avail.
You must have reached the app limit in heroku. Heroku provides 5 free apps. Delete one and try again.
Go to heroku.com and login. You will see all the apps you created.
Then go to the settings and delete one app and try creating template again in eclipse.
No help I know, but I am also seeing this. I have used heroku from the command line in the past, but following the instructions on the heroku site don't appear to be working.
I have to Work with WorkerRole project to deploy some services to perform the data sync with the other databses. i tried to publish but stuck, Internalization, Starting, Preparing, Recovering and finally aborted.
After getting the above stituation i build a simple workerrole project and tried to upload the result is same.
And i am not able to find out the problem with the same.
Please provide some help.
A typical problem, when deploying, is having a connection string pointing to the local emulated storage. This is the first thing I'd check if the worker role code runs locally in the emulator but fails when being published to Windows Azure.