search

Snipa22 / nodejs-pool

Other
481 stars 421 forks source link

pokracovaní po instalaci change as config.json #467

Open Kimajs opened 5 years ago

Kimajs commented 5 years ago

where is the error? I'm confused wrong config.json how to change it?

I did not understand the assignment: Once it's complete, change as config.json is appropriate. It is pre-loaded for a local install of everything running on 127.0.0.1. This will work fine if you're using a single node setup. You will also want to set bind_ip to the external IP of the pool server, and hostname to the resolvable hostname for the pool server. pool_id is mostly used for multi-server installations to provide unique identifiers in the backend. You will also want to run: source ~ / .bashrc This will activate NVM and get things working for the following pm2 steps. where can I find config.json?

the installation proceeded according to "https://raw.githubusercontent.com/Snipa22/nodejs-pool/master/deployment/deploy.bash" in what precise steps continue to continue my statement from the windows that I have open, I'm noob

$ tail -f ~ / .bitmonero / bitmonero.log where is between 0 (no details) and 4 (very verbose), or custom category based levels (eg *: WARNING)

Use the "help" command to see the list of available commands.

2019-02-11 11: 49: 22.215 [P2P1] WARN global src / cryptonote_core / cryptonote_core.cpp: 1276 ** **** 2019-02-11 11: 49: 22.215 [P2P1] WARN global src / cryptonote_core / cryptonote_core.cpp: 1277 Last scheduled hard fork is too far in the past. 2019-02-11 11: 49: 22.215 [P2P1] WARN global src / cryptonote_core / cryptonote_core.cpp: 1278 We are most likely forked from the network. Daemon update needed now. 2019-02-11 11: 49: 22.215 [P2P1] WARN global src / cryptonote_core / cryptonote_core.cpp: 1279 *** **** 2019-02-11 11: 49: 22.578 [P2P1] WARN net.dns src / common / dns_utils.cpp: 487 WARNING: No two valid MoneroPulse DNS checkpoints were received ./monerod --help

$ pm2 restart all Use -update-env to update environment variables [PM2] Applying action restartProcessId on app [all] (ids: 1,2) [PM2] [api] (1) ✓ [PM2] [init] (2) ✓ ┌─────────────────────────────────────────────────────────────────────────── ──────────────────────────────────── │ Name │ id │ mode │ status │ │ │ cpu │ memory │ ├───────────────────────────────────────────────────────── ────────────────────────────── │ api │ 1 │ 0.0.1 │ fork │ online │ 9 │ 0% │ 31.9 MB │ │ init │ 2 │ 0.0.1 │ fork │ online │ 1 │ 0% │ 19.4 MB │ └───────────────────────────────────────────────────────────────────────────────── ────────────────────────────────── Modules ┌─────────────────────────────────────────────────────────── │ Modules │ id │ status │ cpu │ mem │ ├──────────────────────────────────────────────────────────── │ pm2-logrotate │ 0 │ online │ 0% │ 55.5 MB │ └──────────────────────────────────────────────────────────── Use `pm2 show <id | name> 'to get more details about an app

$ /usr/local/src/monero/build/release/bin/monerod --rpc-bind-ip 127.0.0.1 --restricted-rpc 2019-02-11 11:49:18.868 7f729ac61780 INFO global src/daemon/main.cpp:279 Monero 'Helium Hydra' (v0.11.1.0-793bc973) 2019-02-11 11:49:18.868 7f729ac61780 INFO global src/daemon/protocol.h:55 Initializing cryptonote protocol... 2019-02-11 11:49:18.868 7f729ac61780 INFO global src/daemon/protocol.h:60 Cryptonote protocol initialized OK 2019-02-11 11:49:18.868 7f729ac61780 INFO global src/daemon/p2p.h:63 Initializing p2p server... 2019-02-11 11:49:20.063 7f729ac61780 INFO global src/daemon/p2p.h:68 P2p server initialized OK 2019-02-11 11:49:20.063 7f729ac61780 INFO global src/daemon/rpc.h:58 Initializing core rpc server... 2019-02-11 11:49:20.063 7f729ac61780 INFO global contrib/epee/include/net/http_server_impl_base.h:70 Binding on 127.0.0.1:18081 2019-02-11 11:49:20.064 7f729ac61780 INFO global src/daemon/rpc.h:63 Core rpc server initialized OK on port: 18081 2019-02-11 11:49:20.064 7f729ac61780 INFO global src/daemon/core.h:73 Initializing core... 2019-02-11 11:49:20.064 7f729ac61780 INFO global src/cryptonote_core/cryptonote_core.cpp:323 Loading blockchain from folder /home/server/.bitmonero/lmdb ... 2019-02-11 11:49:20.065 7f729ac61780 WARN blockchain.db.lmdb src/blockchain_db/lmdb/db_lmdb.cpp:72 Error attempting to retrieve a hard fork version at height 0 from the db: MDB_NOTFOUND: No matching key/data pair found 2019-02-11 11:49:20.852 7f729ac61780 INFO global src/cryptonote_core/cryptonote_core.cpp:421 Loading checkpoints 2019-02-11 11:49:21.213 7f729ac61780 WARN net.dns src/common/dns_utils.cpp:487 WARNING: no two valid MoneroPulse DNS checkpoint records were received 2019-02-11 11:49:21.214 7f729ac61780 INFO global src/daemon/core.h:78 Core initialized OK 2019-02-11 11:49:21.214 7f729ac61780 INFO global src/daemon/rpc.h:68 Starting core rpc server... 2019-02-11 11:49:21.214 [SRV_MAIN] INFO global src/daemon/rpc.h:73 Core rpc server started ok 2019-02-11 11:49:21.214 [SRV_MAIN] INFO global src/daemon/p2p.h:78 Starting p2p net loop... 2019-02-11 11:49:22.215 [P2P1] INFO global src/cryptonote_core/cryptonote_core.cpp:1258

The daemon will start synchronizing with the network. This may take a long time to complete.

You can set the level of process detailization through "set_log <level|categories>" command, where is between 0 (no details) and 4 (very verbose), or custom category based levels (eg, *:WARNING)

Use the "help" command to see the list of available commands.

2019-02-11 11:49:22.215 [P2P1] WARN global src/cryptonote_core/cryptonote_core.cpp:1276 ** 2019-02-11 11:49:22.215 [P2P1] WARN global src/cryptonote_core/cryptonote_core.cpp:1277 Last scheduled hard fork is too far in the past. 2019-02-11 11:49:22.215 [P2P1] WARN global src/cryptonote_core/cryptonote_core.cpp:1278 We are most likely forked from the network. Daemon update needed now. 2019-02-11 11:49:22.215 [P2P1] WARN global src/cryptonote_core/cryptonote_core.cpp:1279 ** 2019-02-11 11:49:22.578 [P2P1] WARN net.dns src/common/dns_utils.cpp:487 WARNING: no two valid MoneroPulse DNS checkpoint records were received

thanks

Kimajs commented 5 years ago

monero.service - Monero Daemon Loaded: loaded (/lib/systemd/system/monero.service; enabled; vendor preset: e Active: failed (Result: start-limit-hit) since Mon 2019-02-11 11:51:52 UTC; 2 Process: 10975 ExecStart=/usr/local/src/monero/build/release/bin/monerod --rpc

úno 11 11:51:52 server-user systemd[1]: monero.service: Service hold-off time ov úno 11 11:51:52 server-user systemd[1]: monero.service: Scheduled restart job, r úno 11 11:51:52 server-user systemd[1]: Stopped Monero Daemon. úno 11 11:51:52 server-user systemd[1]: monero.service: Start request repeated t úno 11 11:51:52 server-user systemd[1]: monero.service: Failed with result 'star úno 11 11:51:52 server-user systemd[1]: Failed to start Monero Daemon. lines 1-11/11 (END)

shigutso commented 5 years ago

You downloaded a very old version of Monero. The deploy script is outdated, you have to fix the download link of Monero.

Kimajs commented 5 years ago

Will I find some other script that is current? or how to fix this intall?

shigutso commented 5 years ago

The script is old and needs many manual adjustments, maybe there's a fork with a updated deploy script, but other than that you'll have to fix it yourself by downloading the script file and changing what is needed.

Kimajs commented 5 years ago

and is there some current trend on the monero pool?

Kimajs commented 5 years ago

I thought this script is always up to date

Kimajs commented 5 years ago

when there is no instruction, there is no pool ...