Basically, I am following this
https://cloud.ibm.com/docs/services/blockchain/howto?topic=blockchain-ibp-console-smart-contracts#ibp-console-smart-contracts-connect-to-SDK
to deploy a smart contract from my local network to IBM Blockchain Platform. Everything went smoothly until step four. I got an error indicating that something is wrong with my container.
I googled for a while and the most promising answer inferring that there might be some problems on web docker.
Here is the description for the error:
An error occurred during instantiation.
grpc payload is empty: error starting container: error starting container: Post http://localhost:2375/build?t=dev-jdoe-papercontract-0.0.4-c9f772dd033af7a0d2fa0b7aafb268a2f2d8045143cb4344d3356fbe72999ee0: Failed to generate platform-specific docker build: Failed to pull ibmblockchain/fabric-javaenv:amd64-v1.4.1: API error (404): pull access denied for ibmblockchain/fabric-javaenv, repository does not exist or may require 'docker login'
This is what it looks like on my screen:
It would be rather helpful if someone can tell me how to fix it. Thanks a lot in advance.
a little update: I tried to use JS instead of Java to write the smart contract, the same error popped out during the instantiating step.
Related
I am trying to deploy a function in GCP for 2 days and receive the following error each time.
OperationError: code=13, message=Function deployment failed due to a health check failure. This usually indicates that your code was built successfully but failed during test execution. Examine the logs to determine the cause. Try deploying again in a few minutes if it appears to be transient.
The Log viewer doesn't give a proper explanation of the problem. Giving the following logs continuously until the deployment fails.
"Error: function terminated. Recommended action: inspect logs for termination reason. The function cannot be initialized."
Now, the interesting fact is that the same code was working couple of weeks ago.
This issue really makes me wonder that it is a bug from GCP after the recent cloud function upgrade.
I've been having the same issue. I found out part of the issue might be related to a dependency issue. In my specific case, related to the slackclient library, but it seems to come from the yarl library and the recommended fix is to define it as yarl==1.4.2
Reference:
https://github.com/slackapi/python-slackclient/issues/764
P.s. this is a flask python3 app
I have tested this app on local host and it works well, but when I try to deploy this app to the google cloud all I get is an error, which I can't seem to fix, I have tried even giving the compute engine and app engine the admin permission in iAM panel, but still no success, please help.
i have the code on github https://github.com/ManinderSinghAjimal/flask-test-app-1.git
The error:
ERROR: (gcloud.app.deploy) Error Response: [13] Flex operation projects/flask-1-281017/regions/asia-south1/operations/047ccf3a-d10b-446c-98fa-cf8b0030f076 error [INTERNAL]: An internal error occurred while processing task /appengine-flex-v1/insert_flex_deployment/flex_create_resources>2020-06-22T13:46:06.604Z15036.ow.0: Deployment Manager operation flask-1-281017/operation-1592833567657-5a8ac76fc8c66-e121f85c-538636c0 errors: [code: "RESOURCE_ERROR"
location: "/deployments/aef-default-20200622t191524/resources/aef-default-20200622t191524"
message: "{\"ResourceType\":\"compute.beta.regionAutoscaler\",\"ResourceErrorCode\":\"403\",\"ResourceErrorMessage\":{\"code\":403,\"message\":\"The caller does not have permission\",\"status\":\"PERMISSION_DENIED\",\"statusMessage\":\"Forbidden\",\"requestPath\":\"https://compute.googleapis.com/compute/beta/projects/flask-1-281017/regions/asia-south1/autoscalers\",\"httpMethod\":\"POST\"}}"
]
this actually makes no sense to me, so if anyone can suggest something, it will be really helpful.
This issue could be related to resources in the zone that your project is located (some time gcp resources get low in some zones and regions and it is difficult to deploy an app in that zone/region).You could try out different zones/regions for example instead asia-south1 you can try with asia-northeast3
So, this problem is happening randomly (it seems) and between different services.
For example we have a service A which needs to talk to service B, and some times we get this error, but after a while, the error goes away. And this error doesn't happen too often.
When this happens, we see the error log in service A throwing the “upstream connect error” message, but none in service B. So we think it might be related with the sidecars.
One thing we notice is that in service B, we get a lot of this error messages in the istio-proxy container:
[src/istio/mixerclient/report_batch.cc:109] Mixer Report failed with: UNAVAILABLE:upstream connect error or disconnect/reset before headers. reset reason: connection failure
And according to documentation when a request comes in, envoy asks Mixer if everything is good (authorization and other things), and if Mixer doesn’t reply, the request is not success. So that’s why exists an option called policyCheckFailOpen.
We have that in false, I guess is a sane default, we don’t want the request to go through if Mixer cannot be reached, but why can’t?
disablePolicyChecks: true
policyCheckFailOpen: false
controlPlaneSecurityEnabled: false
NOTE: istio-policy is running with the istio-proxy sidecar. Is that correct?
We don’t see that error in some other service which can also fail.
Another log that I can see a lot, and this one happens in all the services not running as root with fsGroup defined in the YAML files is:
watchFileEvents: "/etc/certs": MODIFY|ATTRIB
watchFileEvents: "/etc/certs/..2020_02_10_09_41_46.891624651": MODIFY|ATTRIB
watchFileEvents: notifying
One of the leads I'm chasing is about default circuitBreakers values. Could that be related with this?
Thanks
The error you are seeing is because of a failure to establish a connection to istio-policy
Based on this github issue
Community members add two answers here which could help you with your issue
If mTLS is enabled globally make sure you set controlPlaneSecurityEnabled: true
I was facing the same issue, then I read about protocol selection. I realised the name of the port in the service definition should start with for example http-. This fixed the issue for me. And . if you face the issue still you might need to look at the tls-check for the pods and resolve it using destinationrules and policies.
istio-policy is running with the istio-proxy sidecar. Is that correct?
Yes, I just checked it and it's with sidecar.
Let me know if that help.
was working with deploying contracts using truffle(truffle migrate) for manually created nodes as per "https://docs.goquorum.com/en/latest/Getting%20Started/Getting-Started-From-Scratch/" (using raft-consensus) . I am able to add peer(other machine) and create network, but when i was deploying using truffle i am gettong the following errorError encountered, bailing. Network state unknown. Review successful transactions manually.
Error: Error: Error: Returned error: authentication needed: password or unlock
at Object.run (/usr/lib/node_modules/truffle/build/webpack:/packages/truffle-migrate/index.js:92:1)
at processTicksAndRejections (internal/process/task_queues.js:86:5
This is a duplicate of your question posted on Slack. I suggest avoiding multiple postings to avoid duplication of effort. For reference, here is the link to the Slack conversation:
https://go-quorum.slack.com/archives/C68NY0QQZ/p1562682519077000
(it may require Slack membership to view it).
I'm trying to develop a system service, so I use the echo service as a test.
I developed the service by following the directions on the CF doc.
Now the echo node can be running, but the echo gateway failed with the error "echo_gateway - pid=15040 tid=9321 fid=290e ERROR -- Exiting due to NATS error: Could not connect to server on nats://localhost:4222/"
I got into this issue and struck for almost a week finally someone helped me to resolve it. The underlying problemn is something else and since errors are not trapped properly it gives a wrong message. You need to goto github and get the latest code base. The fix for this issue is http://reviews.cloudfoundry.org/#/c/8891 . Once you fix this issue, you will most likely encounter a timeout field issue. the solution for that is to define the timeout field gateway.yml
A few additional properties became required in the echo_gateway.yml.erb file - specifically, the latest were default_plan and timeout, under the service group. The properties have been added to the appropriate file in the vcap-services-sample-release repo.
Looks like the fix for the misleading error has been merged into github. I haven't updated and verified this myself just yet but the gerrit comments indicate the solution is the same as what the node base has had for some time. I did previously run into that error handling and it was far more helpful.