by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Lucas
    @Lucas1sanz_twitter
    {"timestamp":"2020-03-05T09:08:46,812","container":"231460a0d7e5","level":"ERROR","thread":"vert.x-eventloop-thread-0","class":"HttpErrorHandler","message":"null failed HttpError{error='0x000000F'}","throwable":" no null host accepted"}
    {"timestamp":"2020-03-05T09:08:46,813","container":"231460a0d7e5","level":"ERROR","thread":"vert.x-eventloop-thread-0","class":"LoggerHandlerImpl","message":"172.18.0.4 - - [Thu, 05 Mar 2020 09:08:46 GMT] POST /send HTTP/1.1 500 21 - -","throwable":""}
    But im almost sure this is a configuration error on my side
    Antoine Toulme
    @atoulme
    My guess: this exception points to the vertx client throwing a NPE when issuing a request to connect to a remote peer. I think it's possible you're associating a public key to a peer with an invalid host name? I'll let @lucassaldanha pitch in, I'm not familiar with the example you are running.
    Lucas Saldanha
    @lucassaldanha
    @Lucas1sanz_twitter try double checking the keys.js file to double-check they match your Besu nodes and keys, and your Orion nodes and keys. Let me know if this helps!
    Lucas
    @Lucas1sanz_twitter
    Hi @lucassaldanha I've triple checked and they seem to be right. I have also seen this error pop up a few times:
    {"timestamp":"2020-03-06T10:33:48,478","container":"231460a0d7e5","level":"ERROR","thread":"vert.x-eventloop-thread-2","class":"HttpErrorHandler","message":"null failed HttpError{error='ObjectJsonDeserialization'}","throwable":" com.fasterxml.jackson.databind.exc.UnrecognizedPropertyException: Unrecognized field "uri" (class net.consensys.orion.network.ReadOnlyNetworkNodes), not marked as ignorable (3 known properties: "nodeURLs", "url", "nodePKs"])
     at [Source: (byte[])"curixhttp://81.43.198.55:8080gnodePKs�x,D2l377/LyF+sSb6DafLg1Ufma1viI76xUM2T1r5PIDY=xhttp://81.43.198.55:8080�hnodeURLs�xhttp://81.43.198.55:8080�"; line: -1, column: 150] (through reference chain: net.consensys.orion.network.ReadOnlyNetworkNodes["uri"])"}
    Lucas
    @Lucas1sanz_twitter
    Definitely it is an error on my side, sorry
    Antoine Toulme
    @atoulme
    This deserialization error was fixed. Please use a new snapshot
    Lucas Saldanha
    @lucassaldanha
    @Lucas1sanz_twitter No worries! Try updating to the latest snapshot and let me know how it goes! :)
    Lucas
    @Lucas1sanz_twitter
    Hi everyone, sorry again for the late response. I updated to the latest snapshot and everything is working fine
    Lucas Saldanha
    @lucassaldanha
    @Lucas1sanz_twitter Thanks for letting us know!
    magooster
    @magooster
    Hi according to the docs when starting up orion with clientconnectiontls strict -> server crt and key should be generated howver I got an exception io.vertx.core.VertxException: io.vertx.core.file.FileSystemException: java.nio.file.NoSuchFileException: /var/orion/client-connection-tls-server-key.pem
    magooster
    @magooster
    Looking in code seems this is only done for external tls not internal tls
    Are you now tracking bugs etc as github issues?
    Lucas Saldanha
    @lucassaldanha
    @magooster Hi! Yes, we are using GH issues now
    If you open a new GH issue we’ll get someone from the team to take a look at it!
    magooster
    @magooster
    thanks
    redbull
    @kgkang
    Hi I setup ibft2.0 besu - orion network.
    I used besu 1.4.0 , orion 1.5.0
    now testing private tx with web3js-eea
    I saw @atoulme says private tx should be signed with besu node private key.
    redbull
    @kgkang
    but when i tested private tx after changing besu node private key in web3js-eea/example/keys.js to user's private key , It works ok
    Is that changed in besu 1.4.0 ?
    because of multi-tenancy feature.
    @atoulme Could you give me comment about this ?
    Lucas Saldanha
    @lucassaldanha
    I’m not aware of any changes in the way one signs private txs in 1.4.0. Maybe @atoulme meant something else?
    redbull
    @kgkang
    @lucassaldanha you are saying that private tx can be signed with user's private key ?
    Lucas Saldanha
    @lucassaldanha
    They can be signed with any private key pair (as “regular” Ethereum txs).
    In web3js-eea examples, you can see that keys.js has got a list of keys that will be used to create private txs.
    redbull
    @kgkang
    image.png
    I found the notion in the document .. so confusing...
    redbull
    @kgkang
    image.png
    Lucas Saldanha
    @lucassaldanha
    To clarify. Each private tx has a corresponding public tx (we call it Privacy Marker Transaction - PMT). The PMT is generated by the node creating the private tx and it is can be signed by the node key (or any other key).
    You also have the option of sending private txs in a “two-step” process. You can distribute your signed private tx and then create the PMT (also signed by any other key).
    redbull
    @kgkang
    I want to know the private key used to sign private transaction before sending it to besu node through eea_sendRawTransaction.
    because I saw some confusing document and talks here...
    again... you are saying that we can sign private tx with user's private key and send it to besu node using eea_sendRawTransaction. Right?
    Lucas Saldanha
    @lucassaldanha
    Correct
    redbull
    @kgkang
    Thank you for your clarification !!
    Lucas Saldanha
    @lucassaldanha
    You’re welcome!!!
    MadelineMurray
    @MadelineMurray

    📣 We've identified a critical issue for privacy users with private transactions created using Hyperledger Besu v1.3.4 or earlier. If you have a network with private transaction created using v1.3.4 or earlier, please read the following and take the appropriate steps:
    https://wiki.hyperledger.org/display/BESU/Critical+Issue+for+Privacy+Users

    As always, the PegaSys team is happy to answer any questions or help with any issues you have. 📣

    The Watcher
    @juleznakamoto
    Hi folks,
    I ran into this issue when trying to create Key Pairs. Can someone please help?
    >orion -g nodeKey
    [INFO ] [main] 04-09-2020 16:25:43 n.c.o.c.Orion - starting orion
    [WARN ] [main] 04-09-2020 16:25:43 n.c.o.c.Orion - no config file provided, using default
    [INFO ] [main] 04-09-2020 16:25:44 n.c.o.c.Orion - generating Key Pairs
    Enter password for key pair [nodeKey] :
    [ERROR] [main] 04-09-2020 16:25:44 n.c.o.c.Orion - Unexpected exception upon starting Orion
    java.lang.UnsatisfiedLinkError: unknown
            at jnr.ffi.provider.jffi.NativeLibrary.loadNativeLibraries(NativeLibrary.java:87) ~[jnr-ffi-2.1.8.jar:?]
            at jnr.ffi.provider.jffi.NativeLibrary.getNativeLibraries(NativeLibrary.java:70) ~[jnr-ffi-2.1.8.jar:?]
            at jnr.ffi.provider.jffi.NativeLibrary.getSymbolAddress(NativeLibrary.java:49) ~[jnr-ffi-2.1.8.jar:?]
            at jnr.ffi.provider.jffi.NativeLibrary.findSymbolAddress(NativeLibrary.java:59) ~[jnr-ffi-2.1.8.jar:?]
            at jnr.ffi.provider.jffi.AsmLibraryLoader.generateInterfaceImpl(AsmLibraryLoader.java:158) ~[jnr-ffi-2.1.8.jar:?]
            at jnr.ffi.provider.jffi.AsmLibraryLoader.loadLibrary(AsmLibraryLoader.java:89) ~[jnr-ffi-2.1.8.jar:?]
            at jnr.ffi.provider.jffi.NativeLibraryLoader.loadLibrary(NativeLibraryLoader.java:44) ~[jnr-ffi-2.1.8.jar:?]
            at jnr.ffi.LibraryLoader.load(LibraryLoader.java:325) ~[jnr-ffi-2.1.8.jar:?]
            at jnr.ffi.LibraryLoader.load(LibraryLoader.java:304) ~[jnr-ffi-2.1.8.jar:?]
            at org.apache.tuweni.crypto.sodium.Sodium.libSodium(Sodium.java:180) ~[tuweni-crypto-0.10.0.jar:0.10.0]
            at org.apache.tuweni.crypto.sodium.Sodium.crypto_box_publickeybytes(Sodium.java:1044) ~[tuweni-crypto-0.10.0.jar:0.10.0]
            at org.apache.tuweni.crypto.sodium.Box$PublicKey.length(Box.java:147) ~[tuweni-crypto-0.10.0.jar:0.10.0]
            at org.apache.tuweni.crypto.sodium.Box$KeyPair.random(Box.java:458) ~[tuweni-crypto-0.10.0.jar:0.10.0]
            at net.consensys.orion.enclave.sodium.FileKeyStore.keyPair(FileKeyStore.java:159) ~[orion-1.5.0.jar:1.5.0]
            at net.consensys.orion.enclave.sodium.FileKeyStore.generateKeyPair(FileKeyStore.java:147) ~[orion-1.5.0.jar:1.5.0]
            at net.consensys.orion.cmd.Orion.generateKeyPairs(Orion.java:582) ~[orion-1.5.0.jar:1.5.0]
            at net.consensys.orion.cmd.Orion.run(Orion.java:312) ~[orion-1.5.0.jar:1.5.0]
            at net.consensys.orion.cmd.Orion.main(Orion.java:118) [orion-1.5.0.jar:1.5.0]
    An unexpected exception was reported while starting Orion. Please refer to the logs for more information
    Danno Ferrin
    @shemnon
    orion isn’t finding the libSodium library (https://docs.orion.pegasys.tech/en/stable/HowTo/Dependencies/#libsodium) - it looks in /usr/local/lib, /opt/local/lib, /usr/lib, and /lib
    The Watcher
    @juleznakamoto
    @shemnon thanks a lot!
    MadelineMurray
    @MadelineMurray
    Kevin Ekt
    @deveckt
    Hello, I have followed this tutorial exactly https://docs.orion.pegasys.tech/en/stable/HowTo/Run-Docker-Image/ and get: Failed to read password list '/opt/orion/passwordFile' suggesting that docker is looking for the passwordFile in /opt/orion/passwordFile instead of /data/passwordFile, is the tutorial obsolete ? thanks !
    Joshua Fernandes
    @joshuafernandes
    Hello @deveckt could you post the contents of your config file please?
    If you could also post the stacktrace when you start Orion like the pic above that would be really helpful
    Kevin Ekt
    @deveckt
    thank you, I think that the issue was simply that the docker command does not work when there is a dash in the Orion directory path.