New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Seednode Operator #15
Comments
2018.04 reportRunning 6 Bitcoin and 2 LTC instances. Digital ocean updates their servers frequently with security patches and that causes restarts which kills the seed node (no crone job for autostart). I am following the old email notifications and got alerted soon to start the seed node in such cases. |
2018.05 reportRunning 6 Bitcoin and 2 LTC instances. |
2018.05 reportRunning 1 Bitcoin instance. |
2018.05 reportRunning 1 Bitcoin instance |
2018.06 reportRunning 1 seednode instance
|
2018.06 reportRunning 1 Bitcoin instance
|
2018.06 reportRunning 6 seednode instance |
I've updated the description of this role issue and updated the @bisq-network/seednode-operators team to reflect current status. |
2018.07 reportRunning 6 seednode instance. |
Cycle 47 reportRunning 3 instances. As mentioned by devin above, block height 788837 something triggered all Bisq clients to continuously download blocks. It has subsided quite a bit, but still ongoing and fills the 20 logs quickly. I saved the seednode log at the time of the incident in case it is needed. It seems some bisq clients still have not rebooted and continue to download.
Apart from that, everything is as usual. |
Cycle 48 reportRunning 3 instances. |
Cycle 48 reportRunning 3 instances.
|
Cycle 48 reportRunning 3 instances. |
Cycle 49 reportRunning 3 instances.
|
Cycle 49 reportRunning 3 instances. |
Cycle 49 reportRunning 3 instances. |
Cycle 50 reportRunning 3 instances. |
Cycle 50 reportRunning no instances yet. Ping @Emzy |
Cycle 50 reportRunning 3 instances. |
Cycle 50 reportRunning 3 instances.
|
Cycle 51 reportRunning 3 instances. |
Cycle 51 reportRunning 3 instances.
|
This role is responsible for operating one or more Bisq seednodes.
See: btc_mainnet.seednodes
Docs: none, other than the above
Team: @bisq-network/seednode-operators
The text was updated successfully, but these errors were encountered: