Closed steeveee100 closed 3 years ago
Please check Docker Desktop to make sure that the consensus is running well. You may need to look into the log of the consensus container.
Thanks lehboi! I wonder if you could help me by having a look at this log (part) and help me to understand?
much obliged.
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-04-14 05:23:41,971 CRIT Supervisor running as root (no user in config file) Unlinking stale socket /var/run/supervisor.sock 2021-04-14 05:23:42,702 INFO RPC interface 'supervisor' initialized 2021-04-14 05:23:42,703 CRIT Server 'unix_http_server' running without any HTTP authentication checking 2021-04-14 05:23:42,704 INFO supervisord started with pid 1 2021-04-14 05:23:43,902 INFO spawned: 'postgresql' with pid 20 2021-04-14 05:23:43,914 INFO spawned: 'stellar-core' with pid 21 2021-04-14 05:23:43,927 INFO spawned: 'horizon' with pid 22 2021-04-14 05:23:44,930 INFO success: postgresql entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2021-04-14 05:23:44,931 INFO success: stellar-core entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2021-04-14 05:23:44,932 INFO success: horizon entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2021-04-14 05:25:19,174 INFO exited: stellar-core (exit status 1; not expected) 2021-04-14 05:25:20,195 INFO spawned: 'stellar-core' with pid 1840 2021-04-14 05:25:20,395 INFO exited: stellar-core (exit status 1; not expected) 2021-04-14 05:25:21,414 INFO spawned: 'stellar-core' with pid 1864 2021-04-14 05:25:21,607 INFO exited: stellar-core (exit status 1; not expected) 2021-04-14 05:25:24,152 INFO spawned: 'stellar-core' with pid 1896 2021-04-14 05:25:24,401 INFO exited: stellar-core (exit status 1; not expected) 2021-04-14 05:25:28,183 INFO spawned: 'stellar-core' with pid 1938 2021-04-14 05:25:28,460 INFO exited: stellar-core (exit status 1; not expected) 2021-04-14 05:25:29,139 INFO gave up: stellar-core entered FATAL state, too many start retries too quickly
Hi steeveee100, The last line of logs said that your consensus is not running well. I don't know how to fix this problem, sorry. You may try to delete this container and restart Pi Node, it will reinitialize the container. If you are lucky, It may be better than last time. I also had problem when initializing postgresql database and I deleted container several times.
Hey guy, for a temporary fix, give the solution on the bottom of this issue a go: https://github.com/pi-node/instructions/issues/89 Restarting postgresql seems to do the trick (temporarily).
Thanks Zantiki. I gave it a go but received an error report that postgresql was already running on a port no.xxxx
Interestingly, I fiddled around and started up a new container which seems to be working fine at the moment!
Hey success at last! I went to the Developers Chat group in the Pi App and got immediate help! I'm now up and running - main problem was that I had downloaded Ubuntu apparently. Now running blockchain successfully!
Hi. Could someone please check my setup and let me know if all ok? The consensus container has been enabled for 24 hours, but it just seems that the blockchain is still starting!