You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I then went into the "single" container (stellar/stellar-core) and ran stellar-core self-check
What did you expect to see?
I am not sure but not failure.
What did you see instead?
root@proxmox103:/# stellar-core self-check
2021-02-23T14:32:08.567 [default INFO] Config from stellar-core.cfg
2021-02-23T14:32:08.568 [default INFO] Using QUORUM_SET: {
"t" : 1,
"v" : [ "GD5KD" ]
}
2021-02-23T14:32:08.573 GD5KD [Database INFO] Connecting to: postgresql://dbname=stellar user=postgres host=/postgresql-unix-sockets
2021-02-23T14:32:08.587 GD5KD [SCP INFO] LocalNode::LocalNode@GD5KD qSet: 3bdc92
2021-02-23T14:32:08.588 GD5KD [default INFO] Application destructing
2021-02-23T14:32:08.589 GD5KD [default INFO] Application destroyed
2021-02-23T14:32:08.590 GD5KD [default FATAL] Got an exception: unable to flock file: /data/buckets/stellar-core.lock (Resource temporarily unavailable). This can be caused by access rights issues or another stellar-core process already running
2021-02-23T14:32:08.590 GD5KD [default FATAL] Please report this bug along with this log file if this was not expected
What version are you using?
Stellar-core version 15.3.0 from the docker image
What did you do?
I installed the stellar-core and stellar-core-state docker images following the guide at https://github.com/stellar/docker-stellar-core#single-node-local-network-with-monitoring. I used the supplied single.env file unaltered and ran the first two docker images as in the document. I didn't run the optional container.
I then went into the "single" container (stellar/stellar-core) and ran
stellar-core self-checkWhat did you expect to see?
I am not sure but not failure.
What did you see instead?
Log file: single.log
FWIW, the command
stellar-core testalso gets a lot of failures: