I am unable to create a virtual environment to run VOLTTRON. Every time I run bootstrap.py, I get an error saying [SSL: CERTIFICATE_VERIFY_FAILED]. The screenshot is attached below.
Is this the issue with the VOLTTRON version or do I need additional dependencies to run the file?
There was a pull request that was just merged into master that fixes this issue on raspberry pis. The ssl context is only required with rabbitmq and/or web services enabled. Please update to the latest version of master and try again.
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 have implemented Xero oAuth20 in Asp.Net Web forms using Xero.NetStandard.OAuth2 -Version 0.4.0 version from Nuget package manager.
This is working fine in my local, how ever if I try to deploy solution in Azure server, the publish is getting failed.
Please help to fix this issue.
This is the error
"Your role instances have recycled a number of times during an update or upgrade operation. This indicates that the new version of your service or the configuration settings you provided when configuring the service prevent the role instances from running. Verify your code does not throw unhandled exceptions and that your configuration settings are correct and then start another update or upgrade operation."
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.
In Hyperledger composer, composer network start always fails with the following error.
*"Error trying to instantiate composer runtime. Error: Error: SERVICE_UNAVAILABLE"*.
But I installed the runtime environment for the same card using composer runtime install. My machine is under proxy, but in ignore list, I added the peer domain name too.
I installed the docker too.
I referred the previous posts but that solution also I tried but it didn't help me. Please guide me
Attached the screenshot of terminal with the output
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.