silentnotaryecosystem / cil-core Goto Github PK

Another suggestion would be to consider getting a newer Docker base image and/or updating the version of Python and NodeJS.

The base image used for this container:
https://github.com/SilentNotaryEcosystem/Cil-core/blob/master/Dockerfile#L1

The upstream image is a year old and NodeJS 10 has its own issues:
https://hub.docker.com/layers/nikolaik/python-nodejs/python2.7-nodejs10/images/sha256-4f82aca70243cb3ec93d2f81ed89d22c5dd5a859e2186c28af3995638bb6517f?context=explore

It would be nice to have a sample.pk file and a password to go along with it that could validate that the Master node can join up and run successfully before entering in one's keystore information.

Apologies that this isn't an issue, but it would be great to have a "validator" step before entering in keystore info etc. and joining the Concilium. One would want to be able to do a quick test join and ensure the master node will join successfully.

Hi team!
I'm running a node for a few weeks, and had issues that require to complety reinstall the node (delete the container and create it from scratch, sync, etc..).
I'm not the only one with similar issues, we've been discussing that in the telegram group for masternode support.
I'm facing this error again today, here are the first lines of the log:

2021-04-09T06:55:00.370490350Z [ 'Block 6784220cfa430af890c7a0b642a2db865f4a7471166e77da3379bc69f368fa5a. ConciliumId: 0. With 1 TXns and parents 0096b379cca507255e37b8bd9079fbc0112778c34bcf9a216dc4484ce8116ce5 was accepted' ]
2021-04-09T06:55:39.297127329Z [ 'connect ETIMEDOUT 3.17.139.84:8223' ]
2021-04-09T06:55:39.418784557Z [ 'connect ECONNREFUSED 3.17.181.53:8223' ]
2021-04-09T06:55:39.443715760Z [ 'connect ECONNREFUSED 146.59.12.211:8223' ]
2021-04-09T06:56:01.175203691Z [ 'Blocks 0096b379cca507255e37b8bd9079fbc0112778c34bcf9a216dc4484ce8116ce5 are stable now' ]
2021-04-09T06:56:01.222489392Z [ 'Block 3056f078b3262c643bd1831e06aee95d87b5ada7b2001a284d799487d2634eeb. ConciliumId: 4. With 1 TXns and parents 6784220cfa430af890c7a0b642a2db865f4a7471166e77da3379bc69f368fa5a was accepted' ]
2021-04-09T06:56:55.503809749Z [ 'Blocks 6784220cfa430af890c7a0b642a2db865f4a7471166e77da3379bc69f368fa5a are stable now' ]
2021-04-09T06:56:55.669584351Z [ 'Failed to execute "d7a242e4a05075f30c92a78a1e75f6916ce6b4490d64665d1a9ff8ee456a3d76"',
2021-04-09T06:56:55.669603678Z 'Already exist' ]
2021-04-09T06:56:55.681724739Z [ 'Block d7a242e4a05075f30c92a78a1e75f6916ce6b4490d64665d1a9ff8ee456a3d76. ConciliumId: 1. With 2 TXns and parents 3056f078b3262c643bd1831e06aee95d87b5ada7b2001a284d799487d2634eeb was accepted' ]
2021-04-09T06:56:55.694973756Z [ 'Witness: "172.17.0.2" block "d7a242e4a05075f30c92a78a1e75f6916ce6b4490d64665d1a9ff8ee456a3d76" Round: 4404 commited at Fri Apr 09 2021 06:56:55 GMT+0000 (Coordinated Universal Time) ' ]
2021-04-09T06:57:00.496135850Z [ Error: Block ec008729bca79f3c35c037e13cb782b55e398463cc56af76a2d707bbf4d2ae23 refer to bad parent d7a242e4a05075f30c92a78a1e75f6916ce6b4490d64665d1a9ff8ee456a3d76
2021-04-09T06:57:00.496155180Z at Witness._canExecuteBlock (/app/node/node.js:1914:27)
2021-04-09T06:57:00.496212282Z at Witness._processBlock (/app/node/node.js:2105:28)
2021-04-09T06:57:00.496222002Z at Witness._handleArrivedBlock (/app/node/node.js:444:24) ]
2021-04-09T06:57:00.496662408Z [ 'Incoming message. Peer 54.38.150.125',
2021-04-09T06:57:00.496715983Z Error: Block ec008729bca79f3c35c037e13cb782b55e398463cc56af76a2d707bbf4d2ae23 refer to bad parent d7a242e4a05075f30c92a78a1e75f6916ce6b4490d64665d1a9ff8ee456a3d76
2021-04-09T06:57:00.496725068Z at Witness._canExecuteBlock (/app/node/node.js:1914:27)
2021-04-09T06:57:00.496728872Z at Witness._processBlock (/app/node/node.js:2105:28)
2021-04-09T06:57:00.496732434Z at Witness._handleArrivedBlock (/app/node/node.js:444:24) ]
2021-04-09T06:57:27.487999000Z [ Error: Block 25034a9b6d1c918c2517449dfb0ed2ca1c1e9f4bbef3ed19549ab5a0531bb668 refer to bad parent ec008729bca79f3c35c037e13cb782b55e398463cc56af76a2d707bbf4d2ae23
2021-04-09T06:57:27.488027272Z at Witness._canExecuteBlock (/app/node/node.js:1914:27)
2021-04-09T06:57:27.488032467Z at Witness._processBlockMessage (/app/node/witness.js:321:36) ]

I saved more content of the log here

Is there something I can do to prevent this issue or to solve it without to recreate the node from scratch?

Let me know if anything
Fred

When i try to create new wallet, in some step i see next popup window, after i press "download keystore file" interface immediatly switch to Wallets page, download operation not starting.

Hi team!
Just wanted to point out some discrepancy between node's logs and ubikiri explorer.
In the logs of the node we can see that all the block have at least 1 transaction but in ubikiri explorer only a few ones have transactions.

Here is an example, block 612e38cb04490a84f5f14b74fc54f8da146af923094cec28ca1e1cdce9aa1def

In the logs
Block 612e38cb04490a84f5f14b74fc54f8da146af923094cec28ca1e1cdce9aa1def. ConciliumId: 4. With 1 TXns and parents 1d2394fc8db7abe3f902c1fea23057b9196d9367b0cec51871cf88fc107797f0 was accepted

Same block in the explorer

Not a critical issue :), but good to check anyway

Hi,
Detailed info would be appreciated in the logs to understand the error and be able to solve it (or report it).
like which system are we trying to connect? remote? local? etc

Thanks!

Should we consider building a Vagrantfile/vagrant box to have the setup and pre-configuration done. So, someone can run the vagrant box and then add their keystore information and run the docker image then?

That way, the master node could be run on Windows/Linux via Vagrant and the configuration would be handled?

Let me know.

I am setting up a masternode per instruction on Ubix Wiki; however I am getting an error when running the nodeStatus.js

Please help.
see the error below -

============ Error =======================

dayzie@dayzie-masternode:~$ sudo docker exec cil-witness node scripts/nodeStatus.js
[sudo] password for dayzie:
events.js:174
throw er; // Unhandled 'error' event
^

Error: connect ECONNREFUSED 127.0.0.1:8222
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1106:14)
Emitted 'error' event at:
at Socket.socketErrorListener (_http_client.js:392:9)
at Socket.emit (events.js:198:13)
at emitErrorNT (internal/streams/destroy.js:91:8)
at emitErrorAndCloseNT (internal/streams/destroy.js:59:3)
at process._tickCallback (internal/process/next_tick.js:63:19)