idexio / idexd Goto Github PK

It would be nice if you could get the snapshots loaded before you have to run idex config and save the signature.

Then you would be able to get the snapshots synced while you buy some IDEX and wait for your staking rewards to sit for a week.

What are the recommended CPU requirements for an IDEX node?
I've been running a 1 CPU instances on AWS and it appeared to be pegged at 99% CPU usage at times so moved to a 2 CPU instance. Load seems to vary between 1 few percent to 180ish at times. Anyone else experiencing this? Are these just very high load times or is there anything else to consider?

top - 04:18:53 up 1 day, 13 min, 1 user, load average: 2.70, 2.66, 2.50
Tasks: 113 total, 3 running, 73 sleeping, 0 stopped, 0 zombie
%Cpu(s): 12.8 us, 7.6 sy, 0.0 ni, 28.1 id, 0.0 wa, 0.0 hi, 0.2 si, 51.3 st
KiB Mem : 4038200 total, 178468 free, 969180 used, 2890552 buff/cache
KiB Swap: 0 total, 0 free, 0 used. 2785284 avail Mem

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
6808 root 20 0 1304528 193892 12672 R 139.3 4.8 1920:16 node /usr/idexd
25845 root 20 0 1203384 50352 26400 S 1.0 1.2 8:41.80 containerd
7 root 20 0 0 0 0 S 0.3 0.0 5:47.48 ksoftirqd/0
5266 ubuntu 20 0 44552 3988 3376 R 0.3 0.1 0:00.89 top
1 root 20 0 159892 7236 4724 S 0.0 0.2 0:49.49 systemd
2 root 20 0 0 0 0 S 0.0 0.0 0:00.02 kthreadd

hi, any chances for rpi (armhf arm64) support in near future. cant get this thing to work with my noob programming skillz :(.

regards

Running node on AWS t2.medium (4GB RAM).

idex status
idexd-cli v0.2.1
Latest version: v0.2.1
Cold wallet: <>
Staked IDEX: 11654.77 IDEX 
Total Staked IDEX: 105472386.63 IDEX
Staking: offline [Sun Jul 14 2019 15:29:41 GMT+0000 (Coordinated Universal Time)]
Status: Your staker is out of sync with the blockchain

docker logs show that node is consistently 10 blocks behind:

15:31:41 0|worker  | STAKING OFFLINE: Your staker is out of sync with the blockchain
15:31:42 0|worker  | Error processing transactions, retry in 5 seconds
15:31:47 0|worker  | Processing blocks 8149190 to 8149199
15:31:52 0|worker  | Error processing transactions, retry in 5 seconds
15:31:57 0|worker  | Processing blocks 8149190 to 8149199
15:32:03 0|worker  | Error processing transactions, retry in 5 seconds
15:32:08 0|worker  | Processing blocks 8149190 to 8149199
15:32:12 0|worker  | STAKING OFFLINE: Your staker is out of sync with the blockchain
15:32:13 0|worker  | Error processing transactions, retry in 5 seconds
15:32:18 0|worker  | Processing blocks 8149190 to 8149199
15:32:33 0|worker  | Error processing transactions, retry in 5 seconds
15:32:38 0|worker  | Processing blocks 8149190 to 8149199

Not sure if this has anything to do with the fact that I still had AURA tokens in my wallet. Just swapped them, but figured I should still be able to sync...

Staking: offline [Wed May 08 2019 23:21:24 GMT+0000 (GMT)]
Status: Your staker is out of sync with the blockchain

1. nvm ls
   -> v10.15.0
   system
   default -> 10.15 (-> v10.15.0)
   node -> stable (-> v10.15.0) (default)
   stable -> 10.15 (-> v10.15.0) (default)
   iojs -> N/A (default)
   lts/* -> lts/dubnium (-> N/A)
   lts/argon -> v4.9.1 (-> N/A)
   lts/boron -> v6.17.1 (-> N/A)
   lts/carbon -> v8.16.0 (-> N/A)
   lts/dubnium -> v10.16.0 (-> N/A)

2. npm install -g @idexio/idexd-cli

npm WARN deprecated [email protected]: Use mz or fs-extra^3.0 with Promise Support
npm WARN deprecated [email protected]: ⚠️ WARNING ⚠️ tar.gz module has been deprecated and your application is vulnerable. Please use tar module instead: https://npmjs.com/tar

[email protected] preinstall /root/.nvm/versions/node/v10.15.0/lib/node_modules/@idexio/idexd-cli/node_modules/scrypt
node node-scrypt-preinstall.js

module.js:549
throw err;
^

Error: Cannot find module '/root/.nvm/versions/node/v10.15.0/lib/node_modules/@idexio/idexd-cli/node_modules/scrypt/node-scrypt-preinstall.js'
at Function.Module._resolveFilename (module.js:547:15)
at Function.Module._load (module.js:474:25)
at Function.Module.runMain (module.js:693:10)
at startup (bootstrap_node.js:188:16)
at bootstrap_node.js:609:3
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] preinstall: node node-scrypt-preinstall.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] preinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2019-06-19T05_52_37_758Z-debug.log

3. idex config

(node:27671) Error Plugin: @idexio/idexd-cli: files attribute must be specified in /usr/local/lib/node_modules/@idexio/idexd-cli/package.json
module: @oclif/[email protected]
plugin: @idexio/idexd-cli
root: /usr/local/lib/node_modules/@idexio/idexd-cli
See more details with DEBUG=*
(node:27671) Error Plugin: @oclif/plugin-help: files attribute must be specified in /usr/local/lib/node_modules/@idexio/idexd-cli/node_modules/@oclif/plugin-help/package.json
module: @oclif/[email protected]
plugin: @oclif/plugin-help
root: /usr/local/lib/node_modules/@idexio/idexd-cli/node_modules/@oclif/plugin-help
See more details with DEBUG=*
Error: The module '/usr/local/lib/node_modules/@idexio/idexd-cli/node_modules/scrypt/build/Release/scrypt.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 57. This version of Node.js requires
NODE_MODULE_VERSION 64. Please try re-compiling or re-installing
the module (for instance, using npm rebuild or npm install).
at Object. (/usr/local/lib/node_modules/@idexio/idexd-cli/node_modules/scrypt/index.js:3:20)
at Object. (/usr/local/lib/node_modules/@idexio/idexd-cli/node_modules/scrypt.js/node.js:1:76)
root@iZ0xiauhsvadcjl6e4wvdhZ:~/IDEXd# idex config
(node:27686) Error Plugin: @idexio/idexd-cli: files attribute must be specified in /usr/local/lib/node_modules/@idexio/idexd-cli/package.json
module: @oclif/[email protected]
plugin: @idexio/idexd-cli
root: /usr/local/lib/node_modules/@idexio/idexd-cli
See more details with DEBUG=*
(node:27686) Error Plugin: @oclif/plugin-help: files attribute must be specified in /usr/local/lib/node_modules/@idexio/idexd-cli/node_modules/@oclif/plugin-help/package.json
module: @oclif/[email protected]
plugin: @oclif/plugin-help
root: /usr/local/lib/node_modules/@idexio/idexd-cli/node_modules/@oclif/plugin-help
See more details with DEBUG=*
Error: The module '/usr/local/lib/node_modules/@idexio/idexd-cli/node_modules/scrypt/build/Release/scrypt.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 57. This version of Node.js requires
NODE_MODULE_VERSION 64. Please try re-compiling or re-installing
the module (for instance, using npm rebuild or npm install).
at Object. (/usr/local/lib/node_modules/@idexio/idexd-cli/node_modules/scrypt/index.js:3:20)
at Object. (/usr/local/lib/node_modules/@idexio/idexd-cli/node_modules/scrypt.js/node.js:1:76)

what can i do to fix this?

Running my staking node on an always-on computer with

• Core i5
• 4 physical, 8 virtual cores
• 32GB RAM
• Ubuntu 18.04
• Latest idexd release
  roughly 4GB RAM is used, CPU load is around 30%.

My node frequently loses synch with the ETH chain. What I am getting in the logs is constant:

19:10:09 0|worker | Warped to block 9677000
19:10:09 0|worker | Processing blocks 9677000 to 9677009
19:10:09 0|worker | STAKING OFFLINE: Your staker is out of sync with the blockchain
19:10:13 0|worker | Processing blocks 9677010 to 9677019
19:10:22 0|worker | Error processing transactions, retry in 5 seconds
19:10:27 0|worker | Processing blocks 9677010 to 9677019
19:10:33 0|worker | Processing blocks 9677020 to 9677029
19:10:39 0|worker | STAKING OFFLINE: Your staker is out of sync with the blockchain
19:10:47 0|worker | Error processing transactions, retry in 5 seconds
19:10:52 0|worker | Processing blocks 9677020 to 9677029
19:10:59 0|worker | Error processing transactions, retry in 5 seconds
19:11:04 0|worker | Processing blocks 9677020 to 9677029
19:11:09 0|worker | STAKING OFFLINE: Your staker is out of sync with the blockchain
19:11:10 0|worker | Error processing transactions, retry in 5 seconds

As you can see at 19:10:27, it sometimes processes a block (that would error before), but then errors on the next block. What kind of errors can even happen in processing blocks that are later recoverable? I don't quite understand what the issue is here.

Hello.
npm install -g @idexio/idexd-cli
npm WARN deprecated [email protected]: Use mz or fs-extra^3.0 with Promise Support
npm WARN deprecated [email protected]: ⚠️ WARNING ⚠️ tar.gz module has been deprecated and your application is vulnerable. Please use tar module instead: https://npmjs.com/tar

[email protected] preinstall /root/.nvm/versions/node/v10.15.3/lib/node_modules/@idexio/idexd-cli/node_modules/scrypt
node node-scrypt-preinstall.js

sh: 1: node: Permission denied
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! [email protected] preinstall: node node-scrypt-preinstall.js
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the [email protected] preinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2019-09-28T18_14_33_442Z-debug.log

I am not able to restart the staking because the Parity container exit just after the start with Exited (132)

sudo docker logs docker_parity_1

2019-11-13 15:18:03 UTC Starting Parity-Ethereum/v2.5.10-stable-9f94473-20191112/x86_64-linux-gnu/rustc1.39.0
2019-11-13 15:18:03 UTC Keys path /eth/keys/ethereum
2019-11-13 15:18:03 UTC DB path /eth/chains_light/ethereum/db/906a34e69aec8c0d
2019-11-13 15:18:03 UTC Running in experimental Light Client mode.
2019-11-13 15:18:05 UTC Debug API is not available in light client mode.
2019-11-13 15:18:05 UTC Debug API is not available in light client mode.
2019-11-13 15:18:06 UTC Removed existing file '/eth/jsonrpc.ipc'.

idex start

IDEXd v0.2.1
  ✔ Starting IDEXd
  ❯ Updating IDEX Trade History
    ⠋ Synchronizing Ethereum Node
      → [                                                                                                                                                                                                                  ] Waiting for RPC
    Writing IDEX Trades
    Serving IDEX Requests

Today I am getting this error:

aurad@aurad:~$ idex status
idexd-cli v0.2.1
Latest version: v0.2.1
Cold wallet: 0x....
StatusCodeError: 500 - {"message":"Internal server error"}
    at new StatusCodeError (~/.nvm/versions/node/v10.15.0/lib/node_modules/@idexio/idexd-cli/node_modules/request-promise-core/lib/errors.js:32:15)
    at Request.plumbing.callback (~/.nvm/versions/node/v10.15.0/lib/node_modules/@idexio/idexd-cli/node_modules/request-promise-core/lib/plumbing.js:104:33)
    at Request.RP$callback [as _callback] (~/.nvm/versions/node/v10.15.0/lib/node_modules/@idexio/idexd-cli/node_modules/request-promise-core/lib/plumbing.js:46:31)
    at Request.self.callback (~/.nvm/versions/node/v10.15.0/lib/node_modules/@idexio/idexd-cli/node_modules/request/request.js:185:22)
    at Request.<anonymous> (~/.nvm/versions/node/v10.15.0/lib/node_modules/@idexio/idexd-cli/node_modules/request/request.js:1161:10)
    at IncomingMessage.<anonymous> (~/.nvm/versions/node/v10.15.0/lib/node_modules/@idexio/idexd-cli/node_modules/request/request.js:1083:12)

The README should mention that the IDEX node runs a parity chain with flag --light and therefor 2GB+ memory with less 2Go ram is not enough to guarantee a smooth sync.
Reducing caching can help a little bit but the chain will not sync 100% of the time.

Hello,

Every few days, my idexd is going from the online to the offline staking status without any reasons, I have to rerun everything to make it work again (which is a bit annoying..).

Today, when I'm trying to restart it, I'm getting this error message:

$ idex start
IDEXd v0.2.1
Docker is required.

$ idex up
TypeError: (intermediate value) is not iterable
    at UpCommand.run (~/.nvm/versions/node/v10.15.3/lib/node_modules/@idexio/idexd-cli/src/commands/up.js:8:38)

Indeed, Docker is installed with the version Docker version 19.03.2, build 6a30dfc

When I'm doing a docker ps, everything is still running, but the staking status is still offline (see screenshot below)

$ idex version
@idexio/idexd-cli/0.2.1 linux-x64 node-v10.15.3

What should I do to resolve that please?

Regards