Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Seednode Operator #15

Open
cbeams opened this issue Sep 4, 2017 · 236 comments
Open

Seednode Operator #15

cbeams opened this issue Sep 4, 2017 · 236 comments
Assignees
@devinbileck @runbtc @jester4042
Labels
team:ops https://bisq.wiki/Ops_Team

Comments

@cbeams
Copy link
Contributor

cbeams commented Sep 4, 2017 •
edited
Loading

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
@cbeams cbeams added the role:op label Sep 4, 2017
@cbeams cbeams changed the title seednode operator Seednode Operator Jan 2, 2018
@cbeams cbeams added role and removed role:op labels Jan 3, 2018
@ManfredKarrer
Copy link

ManfredKarrer commented May 1, 2018 •
edited
Loading

2018.04 report

Running 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.

@ManfredKarrer ManfredKarrer mentioned this issue May 1, 2018
Closed
@cbeams cbeams removed the a:role label May 4, 2018
This was referenced May 8, 2018
Closed
Closed
@ManfredKarrer
Copy link

2018.05 report

Running 6 Bitcoin and 2 LTC instances.

@ManfredKarrer ManfredKarrer mentioned this issue May 30, 2018
Closed
@Emzy Emzy mentioned this issue May 30, 2018
Closed
@Emzy
Copy link

Emzy commented May 30, 2018

2018.05 report

Running 1 Bitcoin instance.

bisq-network/compensation#76

@mrosseel
Copy link

mrosseel commented Jun 1, 2018 •
edited
Loading

2018.05 report

Running 1 Bitcoin instance
hosting: Linode in docker container

bisq-network/compensation#80

@mrosseel mrosseel mentioned this issue Jun 1, 2018
Closed
@mrosseel mrosseel mentioned this issue Jun 29, 2018
Closed
@mrosseel
Copy link

mrosseel commented Jun 29, 2018 •
edited
Loading

2018.06 report

Running 1 seednode instance
hosting: Linode in docker container

  • fixed a docker bug where the linux had no language setup which crashed the container.
  • Manfred found a restart bug, this was not noticed on my node because the docker container restarts automatically so it seems this is not relevant for my node.

bisq-network/compensation#83

@Emzy Emzy mentioned this issue Jun 30, 2018
Closed
@Emzy
Copy link

Emzy commented Jun 30, 2018

2018.06 report

Running 1 Bitcoin instance

  • Update to new Version

bisq-network/compensation#88

@ManfredKarrer ManfredKarrer mentioned this issue Jun 30, 2018
Closed
@ManfredKarrer
Copy link

ManfredKarrer commented Jun 30, 2018 •
edited
Loading

2018.06 report

Running 6 seednode instance
Updated to new Version
bisq-network/compensation#92

@ManfredKarrer
Copy link

@Emzy @mrosseel You mixed that role up with the bitcoin operator role...

@cbeams
Copy link
Contributor Author

cbeams commented Jul 9, 2018

I've updated the description of this role issue and updated the @bisq-network/seednode-operators team to reflect current status.

@ManfredKarrer ManfredKarrer mentioned this issue Jul 26, 2018
Closed
@ManfredKarrer
Copy link

2018.07 report

Running 6 seednode instance.

/cc bisq-network/compensation#93

@jester4042
Copy link

Cycle 61

- Running 3 bisq 1 seed nodes with no issues to report
- Checked internal monitor 2x day to ensure proper operation
- Checked each machine daily for updates and applied as needed

@jester4042 jester4042 mentioned this issue Aug 5, 2024
Open
@devinbileck devinbileck mentioned this issue Aug 5, 2024
Open
@devinbileck
Copy link
Member

Cycle 61 report

My 3 nodes are still running, though will be removed in a subsequent Bisq release, as per bisq-network/bisq#7137. Once sufficient time has elapsed after that has been released, I will decommission the nodes.

/cc bisq-network/compensation#1594

@runbtc runbtc mentioned this issue Aug 8, 2024
Open
@runbtc
Copy link

runbtc commented Aug 8, 2024

Cycle 61 report

Running 3 instances.
Nothing to report.

/cc bisq-network/compensation#1599

@jester4042
Copy link

Cycle 62

- Running 3 bisq 1 seed nodes with no issues to report
- Checked internal monitor 2x day to ensure proper operation
- Checked each machine daily for updates and applied as needed

@jester4042 jester4042 mentioned this issue Sep 4, 2024
Open
@devinbileck devinbileck mentioned this issue Sep 5, 2024
Open
@devinbileck
Copy link
Member

Cycle 62 report

My 3 nodes are still running, though will be removed in a subsequent Bisq release, as per bisq-network/bisq#7137. Once sufficient time has elapsed after that has been released, I will decommission the nodes.

/cc bisq-network/compensation#1611

@runbtc runbtc mentioned this issue Sep 5, 2024
Open
@runbtc
Copy link

runbtc commented Sep 5, 2024

Cycle 62 report

Running 3 instances.
Nothing to report.

/cc bisq-network/compensation#1615

@jester4042
Copy link

Cycle 63

- Running 3 bisq 1 seed nodes with no issues to report
- Checked internal monitor 2x day to ensure proper operation
- Checked each machine daily for updates and applied as needed

@jester4042 jester4042 mentioned this issue Oct 8, 2024
Open
@runbtc runbtc mentioned this issue Oct 8, 2024
Open
@runbtc
Copy link

runbtc commented Oct 8, 2024

Cycle 63 report

Running 3 instances.
Nothing to report.

/cc bisq-network/compensation#1632

@devinbileck devinbileck mentioned this issue Oct 9, 2024
Open
@devinbileck
Copy link
Member

Cycle 63 report

My 3 nodes are still running, though will be removed in a subsequent Bisq release, as per bisq-network/bisq#7137. Once sufficient time has elapsed after that has been released, I will decommission the nodes.

/cc bisq-network/compensation#1635

@jester4042
Copy link

Cycle 64

- Running 3 bisq 1 seed nodes with no issues to report
- Checked internal monitor 2x day to ensure proper operation
- Checked each machine daily for updates and applied as needed

@jester4042 jester4042 mentioned this issue Nov 7, 2024
Open
@devinbileck devinbileck mentioned this issue Nov 8, 2024
Open
@devinbileck
Copy link
Member

Cycle 64 report

My 3 nodes are still running, though will be removed in a subsequent Bisq release, as per bisq-network/bisq#7137. Once sufficient time has elapsed after that has been released, I will decommission the nodes.

/cc bisq-network/compensation#1654

@runbtc runbtc mentioned this issue Nov 8, 2024
Open
@runbtc
Copy link

runbtc commented Nov 8, 2024

Cycle 64 report

Running 3 instances.
Nothing to report.

/cc bisq-network/compensation#1657

@jester4042
Copy link

Cycle 65

- Running 3 Bisq 1 seed nodes which were all updated to v1.9.18. There are no issues to report.
- Checked internal monitor 2x day to ensure proper operation
- Checked each machine daily for updates and applied as needed

@jester4042 jester4042 mentioned this issue Dec 7, 2024
Closed
@devinbileck devinbileck mentioned this issue Dec 8, 2024
Open
@devinbileck
Copy link
Member

devinbileck commented Dec 8, 2024 •
edited
Loading

Cycle 65 report

My 3 nodes are still running, and were recently updated to 1.9.18. Though they will be decommissioned soon since they have been removed in the recent 1.9.18 release, as per bisq-network/bisq#7137. Once sufficient time has elapsed, I will decommission the nodes.

/cc bisq-network/compensation#1671

@runbtc runbtc mentioned this issue Dec 9, 2024
Open
@runbtc
Copy link

runbtc commented Dec 9, 2024

Cycle 65 report

Running 3 instances.
My nodes were upgraded to 1.9.18.

/cc bisq-network/compensation#1676

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@devinbileck devinbileck

@runbtc runbtc

@jester4042 jester4042

Labels
team:ops https://bisq.wiki/Ops_Team
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
15 participants
@ripcurlx @wiz @cbeams @devinbileck @freimair @Emzy @ManfredKarrer @mrosseel @KanoczTomas @alexej996 @17331yas @runbtc @403State @jester4042 and others