I follow the link at https://hyperledger-fabric.readthedocs.io/en/latest/write_first_app.html and try to setup the test network. When I run the script startFabric.sh, I get the following error on Mac OS:
Error connecting due to rpc error: code = Unavailable desc= grpc:the connection is unavailable.
Please help me with this.
It is likely that given the timing of this question that you may have run into a race condition with the code and the in-progress release, which was being prepared at this point in time. I suspect that with the advent of the Hyperledger Fabric 1.0.0 release that this problem is resolved.
Related
I'm seeing errors in StackDriver logging for my Compute instance. The logs are showing repeated issues every hour, creating a lot of noise. I have a Spring Boot API deployed in a container to a VM in Compute Engine using latest stable version of Container OS.
I'm relatively new to GCP and don't understand what is causing this issue, searches have come up empty so far.
Failed to call method: org.chromium.SessionManagerInterface.RetrieveActiveSessions: object_path= /org/chromium/SessionManager: org.freedesktop.DBus.Error.ServiceUnknown: The name org.chromium.SessionManager was not provided by any .service files
CallMethodAndBlockWithTimeout(...): Domain=dbus, Code=org.freedesktop.DBus.Error.ServiceUnknown, Message=The name org.chromium.SessionManager was not provided by any .service file
Error calling D-Bus proxy call to interface '/org/chromium/SessionManager': The name org.chromium.SessionManager was not provided by any .service files
The same 3 lines are repeating every hour. Anyone aware of what might be causing this or how to fix/suppress these?
I looked into this error, and as per my findings:
The error message that you have been receiving is a manifestation of Chrome to reliably exit shortly after starting up.
The UI’s job (which encompasses Chrome, the session_manager and the window manager) gets shut down by upstart because of it's thrashing, and when the test tries to restart the session_manager, the session_manager cannot communicate it over to the D-Bus.
The crash collection software in Container OS was originally for Chromebooks (The laptop using Chrome browser). So the code typically expects Chrome and some other related software on the system.
However, Container OS is a server OS, and does not have Chrome. So if Chrome is missing, the software will report some errors. They are actually not real failures, just some verbose error messages.
Overall, It is safe to ignore these logs and continue using your VM Instances.
Hope this helps.
I'm trying to install AWS Greengrass core software in Ubuntu 14.04 LTS, using this tutorial.
when I tried to start the connection using
sudo ./greengrassd start
following error shows
/greengrass/ggc/packages/1.1.0/bin/daemon: 1: /greengrass/ggc/packages/1.1.0/bin/daemon: Syntax error: "&" unexpected
There's not a lot of information to go on, but: Syntax error: "$THING" unexpected is typically output by the shell when it tries to run a program as a shellscript after the kernel has given up trying to launch it as a binary, even though it had binary magic. See this question for more info.
That, in turn, is often the result of trying to launch a program that is a compiled binary for a different architecture or operating system than the one you are running.
In this case, I would bet that this is your problem. Since the greengrass stuff can be downloaded for multiple architectures, make sure you have downloaded the correct .tar.gz for your platform's architecture. This step in the greengrass tutorial has the download step in the final subsection--make sure that you have selected the correct architecture in the highlighted box in the lower left:
To determine your architecture, use the arch command, or uname -m. If the two disagree, prefer the latter in most cases. For more information on how to determine your system's architecture, see the answers to this question.
This is also mentioned in the official help docs: it is the first troubleshooting step mentioned in the "The AWS Greengrass core software does not start successfully" category of the official greengrass troubleshooting guide.
This error means you can't run it on your hardware, I've faced with that when I wanted to install GG on Raspberry PI zero.
Before installing Greengrass core, consider which hardware you are using. You can find the minimum hardware requirements and compatible hardware architecture for Greengrass here. Also you can find your hardware architecture type using uname -m. If you have compatible hardware then go on with this tutorial,
and download Greengrass software which is compatible with your hardware architecture.
After installation, it's recommended to run greengrass dependency checker, you can find it here.
I am using the fabric to run an experiment in amazon web services ec2 cluster(50 instances). The experiment is mainly about using some clients to perform requests to my servers.
Because I am testing the scalability of my project, I increase the server numbers while keeping the client number at the same. In this process, I ocaasionally come across this error that interrupt my fabric task.
If I run task again, then this error will not happen. I read the question No handlers could be found for logger “paramiko.transport” , but that does not really explain why this error terminate my task and why the error happened occasionally.
I also checked the context where the error occurs, but the last executed commands are not even the same
Could someone just provide some debugging tricks to identify where the problem is.
Working on the commercial paper example as outlined here:
https://github.com/IBM-Blockchain/cp-web
Works fine until I try to log into my project here:
http://cp-web-jklondon-1411.mybluemix.net/login
Get error saying:
Waiting on the node server to open up so we can talk to the blockchain. This app is likely still starting up. Check the server logs if this message does not go away in 1 minute.
This application cannot run without the blockchain network :(
Whats going on?
Thanks
Rav
Bluemix might have been unstable / the app is still staging. This actually happened quite frequently.
Play framework 1.2.5 was already setup on an ubuntu 11 server. I stopped the process, ran play clean and then deployed the new app (I have since then ran play clean a few times as well without any luck). I keep getting LinkageErrors and the application is throwing classcast exceptions for objects for different classes. Any suggestions to help pinpoint what's causing the issue and how best to resolve it - thanks in advance.
Oops: LinkageError
An unexpected error occured caused by exception LinkageError: loader (instance of play/classloading/ApplicationClassloader): attempted duplicate class definition for name: "models/testModel/TestClass"
Reference to play framework is still set up in the system path. I am using "play start" to run the application.
Try using Prod mode in application.conf and check if you receive more verbose error messages during pre-compilation. Also, replacing your deployment or even the play directory might help (though that did not resolve the issue in my case). Hope it helps.