Closed pradeeppadmarajaiah closed 6 years ago
Changed the node ip from 0.0.0.0 to 127.0.0.1.Able to run successfully with the fresh setup.
Hi pradeeppadmarajaiah, I am also getting the same error , although I have replaced 0.0.0.0 with 127.0.0.1 but indy_pool is starting with 0.0.0.0 only. I have updated the indy-pool.dockerfile and under indy-sdk/ci and indy-sdk/docker_pool _transactions_genesis. Could you please confirm if these are the correct places to change ?
@vsudip , Please remove the container and restart it. It tested in ubuntu VM. Make sure firewall is opened for all the required port. Once u start, try connecting via telnet
Thanks it worked!
I am trying to run the Java Sample on Intellij and eclipse : https://github.com/hyperledger/indy-sdk/tree/master/samples/java
Error occurs : "A fatal error has been detected by the Java Runtime Environment:"
On the line Wallet.createWallet(poolName, issuerWalletName, "default", null, issuerWalletCredentials).get();
Complete log `Anoncreds sample -> started #
A fatal error has been detected by the Java Runtime Environment:
#
SIGSEGV (0xb) at pc=0x00007f8ae021cf40, pid=6586, tid=0x00007f8ac2ff1700
#
JRE version: Java(TM) SE Runtime Environment (8.0_171-b11) (build 1.8.0_171-b11)
Java VM: Java HotSpot(TM) 64-Bit Server VM (25.171-b11 mixed mode linux-amd64 compressed oops)
Problematic frame:
C 0x00007f8ae021cf40
#
Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
An error report file with more information is saved as:
/home/pradeep/Downloads/indy-sdk-master/samples/java/hs_err_pid6586.log
#
If you would like to submit a bug report, please visit:
http://bugreport.java.com/bugreport/crash.jsp
# `