I have built
horizon instances from source on Ubuntu 18.04 LTS.
I managed to make them work for the test-net, yet now, whilst trying to configure
stellar-core.cfg for the public network, I am unable to connect to peers.
I have tried multiple
.cfg specifications, but always end up with issues related to the Overlay component of
By using the following
I get the following log output:
[Overlay WARNING] 2018-06-21T13:34:44.778 GCZGU [Overlay ERROR] TCPPeer::drop shutdown socket failed: Transport endpoint is not connected [TCPPeer.cpp:195]
What could be the issue here? I looked int othe
TCPPeer.cpp file, and that was not as well documented as I had expected since line 195 only referred to printing an error message without explaining where the error was generated.
With an alternative
stellar-core.cfg I ended up with the following log:
2018-06-21T12:11:35.429 GDMPG [Overlay TRACE] OverlayManagerImpl tick [OverlayManagerImpl.cpp:288]
What am I doing wrong?
horizon run for a while with the first configuration (prior to Edit, in other words the Container solution), eventually bucket entries where added. Yet, after a while
horizon asked me to re-create the horizon PSQL database since I had not done this prior to evolving to the public network.
After re-creating the PSQL database for Horizon, and re-initializing it with
horizon db init, the
stellar-core database with
stellar-core --newdb I am unable to fetch the History buckets from the Stellar core history bucket repository available at:
I am not sure why this happens, since it appeared to be just fine yesterday. As is noticeable, the URL gives a 404 error. Anyone got some advice on defining the bucket directories correctly? Or are the history repositories down during certain time periods?