I am unable to deploy the business network using the local playground. It hangs at "Please Wait: Installing Business Network"...and the browser console log shows the following error -
WebSocket is already in CLOSING or CLOSED state.
I am able to deploy the network using CLI.
I am at 0.13.0 version.
Please advise.
Thanks,
Naveen
Related
I installed pact broker using Docker-compose file. And able to run it successfully on port 9292. But i am unable to access the Ui for it. It doesnt return any index page for it. So am unable to verify the pacts or versions published. Kindly help me with it.
Thanks in advance.
I am getting the below response while calling /businesspartners api after deploying s4sdk app to cf.
I was able to test this app by deploying locally (after ALLOW_MOCKED_AUTH_HEADER: true), so i deployed the appl'n to cloud foundry, and tried using destinations service(insted of env), below are the steps that i followed.
step 1: Set up the cloud connector
step 2: Create service instance of xsuaa and destinations
step 3: Refer this in app yaml file
step 4: Push the package to cloud. (mvn clean package; cf push)
step 5: Now i went ahead and configured destinations; (app>> service instance>>destinations)
Here i couldn't test the connectivity, when i pressed "check connection" i was getting the below error:
How do i test this connection?
step 6: With the belief that the connection is working i went ahead and restarted the app, and started testing api's. the app was up but when i was getting above(fig.1) error.
step 7: Tried looking at the logs, and notices the below to errors
could anyone help over here to resolve this issue..?
Tried with setting "ALLOW_MOCKED_AUTH_HEADER" -> same two issue
Tried removing properties in destinations, but same errors.
Could not try with destinations variable in CF, as our S4 system is not publicly opened, so tried it locally it works.
Tried with Neo, it works both locally and on cloud.
But after pushing to CF, couldn't manage to run
Thanks,
Girish
You additionally need to bind your application to an instance of the connnectivity service on Cloud Foundry to communicate via the Cloud Connector. This is mentioned, albeit a bit hidden, in the error message "Failed to get connectivity service credentials: no service binding found".
Create a service instance with cf create-service connectivity lite my-connectivity.
Add the name of this instance to the section services in your manifest.yml file.
If you still face issues afterwards, please also try to remove the proxyPort and proxyHost properties from your destination. Those should not be required.
For more details about on-premise connectivity on SAP Cloud Platform Cloud Foundry, consult the following blog post.
At my company we had some proxy settings which restricted the installation of cypress via CMD->npm.
After some discussions with the network guys we added *.cypress.io and registry.npmjs.org to the proxy settings and after that "npm install cypress" worked perfectly. The message "Finished Installation" is shown and I could also open the Cypress GUI by typing "node_modules.bin\cypress open" in CMD.
But when the GUI was opened I tried to click on the LogIn button I get "Cannot connect to API server"
"We tried but failed to connect to the API server at https://api.cypress.io/"
Any idea why I cannot connect to the api server when I just did the whole installation without any problems?
I'm not sure why you're getting this error - my best guess is that the request for api.cypress.io is also hitting another server that isn't allowed through your firewall. Most likely this is Github, as the only option for logging in is by connecting your Github account.
That said, unless you're using the dashboard service, you don't actually need to log in to run tests. If the Log In button works properly, you'll get a message that looks like this:
Logging in gives you access to the Cypress Dashboard Service. You can set up projects to be recorded and see test data from your project.
This message is accompanied by a button prompting you to log in via Github.
I am on composer 0.16.0 and Fabric 1.0.4
While experimenting with Historian queries via composer-client consistently run into a situation when the network becomes non-responsive and the only way to reanimate it seems to be restarting the Fabric and redeploying the network.
The error follows:
>
Error: Error trying to ping. Error: Error trying to query business network. Error: chaincode error (status: 500, message: Error: The current identity has not been registered: admin)
>
So, the questions are:
1. Is this a known issue and is there a workaround? Happy to do more diagnostics and file it properly if that helps.
2. Any way to reboot the network without restarting the Fabric?
Thank you!
so the error "The current identity has not been registered: admin" is fundamentally caused by the fact you are restarting your CA server each time - ie a new CA server, a new authority issuing new credentials effectively for 'admin' (and hence your present admin credentials from 'previous' in your card store are not recognised by the new CA server).
Suggest to
1) clear out old admin cards from your card store eg. composer card delete --name admin#tutorial-network
2) re-import your 'admin' card through playground or CLI - and do a composer network ping to retrieve credentials to the card store.
3) Reduce your Historian queries result sets by adding selection criteria
Note: To restart your existing Dev Fabric - just use docker stop to stop your containers - and docker start you can restart them from the same state (or use docker-compose stop and docker-compose start if you're familiar with that command). Else, use docker persistence to persist your data.
https://hyperledger.github.io/composer/tutorials/developer-tutorial.html
Probably good to
I made a dashing app that queries the google api as part of its jobs. On my local everything works fine and I used git to clone the repo on a remote machine and ran bundle install there but when I try to run dashing start I get this error:
/home/mwerner/.rvm/gems/ruby-2.1.2/gems/signet-0.5.1/lib/signet/oauth_2/client.rb:941:in `fetch_access_token': Authorization failed. Server message: (Signet::AuthorizationError)
{
"error" : "invalid_grant"
}
I am using relative paths in the app so it can't be there is an authentication issue. I tried manually installing all the gems I use on the local machine on the remote machine via gem install ... but no luck. Hints?
I had the very same issue today. I got it resolved by checking back into my google developers account. In my case I had entered a wrong Mail address under service_account_email in the .rb file.
I inserted the data shown under "Client ID for Web Apps" where it had to be the one from "Service Account" out of my Google Developer API Account. Make sure you use Service Account Credentials for the widget!
Also I reassured that I had setup that very same address for read access in my google analytics account.
In short, getting that error means there is something wrong with the data you put in the analytics.rb file.
Once I did the above it resolved my issue and I was able to start dashing.