pi-node / instructions

254 stars 154 forks source link

Your computer is not running the blockchain #84

Open cy6886 opened 3 years ago

cy6886 commented 3 years ago

Why does my computer prompt Your computer is not running the blockchain? when everything is normal?

ihatejam commented 3 years ago

please post a picture of your troubleshooting screen as well as your Docker Dashboard

cy6886 commented 3 years ago

Starting Stellar Quickstart

mode: persistent

network: testnet (Pi Testnet)

postgres user: stellar

using POSTGRES_PASSWORD

finalize-pgpass: ok

init-postgres: ok

Waiting for postgres to be available...

postgres: up

create-horizon-db: ok

create-core-db: ok

stellar-postgres-user: ok

chown-core: ok

finalize-core-config-pgpass: ok

finalize-core-config-run-standalone: ok

finalize-core-config-manual-close: ok

set-private-key: ok

init-core-db: ok

chown-horizon: ok

init-horizon-db: ok

postgres: down

starting supervisor

2021-03-07 13:26:09,221 CRIT Supervisor running as root (no user in config file)

2021-03-07 13:26:09,239 INFO RPC interface 'supervisor' initialized

2021-03-07 13:26:09,240 CRIT Server 'unix_http_server' running without any HTTP authentication checking

2021-03-07 13:26:09,240 INFO supervisord started with pid 1

2021-03-07 13:26:10,250 INFO spawned: 'postgresql' with pid 178

2021-03-07 13:26:10,267 INFO spawned: 'stellar-core' with pid 179

2021-03-07 13:26:10,276 INFO spawned: 'horizon' with pid 180

2021-03-07 13:26:10,277 INFO reaped unknown pid 175

2021-03-07 13:26:11,384 INFO success: postgresql entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2021-03-07 13:26:11,389 INFO success: stellar-core entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2021-03-07 13:26:11,390 INFO success: horizon entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2021-03-07 13:58:47,786 WARN received SIGTERM indicating exit request

2021-03-07 13:58:47,788 INFO waiting for stellar-core, postgresql, horizon to die

2021-03-07 13:58:47,798 INFO stopped: horizon (exit status 0)

2021-03-07 13:58:48,885 INFO stopped: stellar-core (exit status 0)

2021-03-07 13:58:49,509 INFO stopped: postgresql (exit status 0)

Starting Stellar Quickstart

mode: persistent

network: testnet (Pi Testnet)

postgres: config directory exists, skipping copy

supervisor: config directory exists, skipping copy

stellar-core: config directory exists, skipping copy

horizon: config directory exists, skipping copy

postgres: already initialized

chown-core: ok

core: already initialized

horizon: already initialized

starting supervisor

2021-03-08 13:06:17,869 CRIT Supervisor running as root (no user in config file)

2021-03-08 13:06:17,898 INFO RPC interface 'supervisor' initialized

2021-03-08 13:06:17,899 CRIT Server 'unix_http_server' running without any HTTP authentication checking

2021-03-08 13:06:17,899 INFO supervisord started with pid 1

2021-03-08 13:06:18,905 INFO spawned: 'postgresql' with pid 21

2021-03-08 13:06:18,911 INFO spawned: 'stellar-core' with pid 22

2021-03-08 13:06:18,916 INFO spawned: 'horizon' with pid 23

2021-03-08 13:06:20,186 INFO success: postgresql entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2021-03-08 13:06:20,186 INFO success: stellar-core entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2021-03-08 13:06:20,186 INFO success: horizon entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) (93O _IWI$KQ}(4}Q9$W%99 77CTH2N6N J_SFB3U5VP3 }%05Y{}%LB33BCJI26B1JMP ![8VH0@ %0MYEF9@0PTDH(Starting Stellar Quickstart

mode: persistent

network: testnet (Pi Testnet)

postgres user: stellar

using POSTGRES_PASSWORD

finalize-pgpass: ok

init-postgres: ok

Waiting for postgres to be available...

postgres: up

create-horizon-db: ok

create-core-db: ok

stellar-postgres-user: ok

chown-core: ok

finalize-core-config-pgpass: ok

finalize-core-config-run-standalone: ok

finalize-core-config-manual-close: ok

set-private-key: ok

init-core-db: ok

chown-horizon: ok

init-horizon-db: ok

postgres: down

starting supervisor

2021-03-07 13:26:09,221 CRIT Supervisor running as root (no user in config file)

2021-03-07 13:26:09,239 INFO RPC interface 'supervisor' initialized

2021-03-07 13:26:09,240 CRIT Server 'unix_http_server' running without any HTTP authentication checking

2021-03-07 13:26:09,240 INFO supervisord started with pid 1

2021-03-07 13:26:10,250 INFO spawned: 'postgresql' with pid 178

2021-03-07 13:26:10,267 INFO spawned: 'stellar-core' with pid 179

2021-03-07 13:26:10,276 INFO spawned: 'horizon' with pid 180

2021-03-07 13:26:10,277 INFO reaped unknown pid 175

2021-03-07 13:26:11,384 INFO success: postgresql entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2021-03-07 13:26:11,389 INFO success: stellar-core entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2021-03-07 13:26:11,390 INFO success: horizon entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2021-03-07 13:58:47,786 WARN received SIGTERM indicating exit request

2021-03-07 13:58:47,788 INFO waiting for stellar-core, postgresql, horizon to die

2021-03-07 13:58:47,798 INFO stopped: horizon (exit status 0)

2021-03-07 13:58:48,885 INFO stopped: stellar-core (exit status 0)

2021-03-07 13:58:49,509 INFO stopped: postgresql (exit status 0)

Starting Stellar Quickstart

mode: persistent

network: testnet (Pi Testnet)

postgres: config directory exists, skipping copy

supervisor: config directory exists, skipping copy

stellar-core: config directory exists, skipping copy

horizon: config directory exists, skipping copy

postgres: already initialized

chown-core: ok

core: already initialized

horizon: already initialized

starting supervisor

2021-03-08 13:06:17,869 CRIT Supervisor running as root (no user in config file)

2021-03-08 13:06:17,898 INFO RPC interface 'supervisor' initialized

2021-03-08 13:06:17,899 CRIT Server 'unix_http_server' running without any HTTP authentication checking

2021-03-08 13:06:17,899 INFO supervisord started with pid 1

2021-03-08 13:06:18,905 INFO spawned: 'postgresql' with pid 21

2021-03-08 13:06:18,911 INFO spawned: 'stellar-core' with pid 22

2021-03-08 13:06:18,916 INFO spawned: 'horizon' with pid 23

2021-03-08 13:06:20,186 INFO success: postgresql entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2021-03-08 13:06:20,186 INFO success: stellar-core entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2021-03-08 13:06:20,186 INFO success: horizon entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) (93O _IWI$KQ}(4}Q9$W%99 77CTH2N6N J_SFB3U5VP3 }%05Y{}%LB33BCJI26B1JMP N](https://user-images.githubusercontent.com/66433347/110326165-400a7480-8053-11eb-908f-e4350450e055.png) YFZVAZ _GF(G%3~7U%4%1(S

cy6886 commented 3 years ago

After the promotion of administrator privileges

Consensus container enabled: Yes

Node switch on: Yes

PortsChecker container: exited

Consensus container: running

ihatejam commented 3 years ago

Without seeing a picture of your troubleshooting screen (which summarizes the state of your node), I'm guessing that your node is now fine since the Consensus container is now running (and has stayed up since the last message in your log about it being in a running state).

cy6886 commented 3 years ago

G%OPA6@ZEMJHL~EO31$9AAJ

) 1VWJJ%Z L`BW5OSFG2W0V

ihatejam commented 3 years ago

yes - this is normal.