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.

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 · 200 comments
Open

Seednode Operator #15

cbeams opened this issue Sep 4, 2017 · 200 comments
Assignees
@wiz
Labels
team:ops https://bisq.wiki/Ops_Team

Comments

@cbeams
Copy link
Member

cbeams commented Sep 4, 2017 •
edited

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
Member

ManfredKarrer commented May 1, 2018 •
edited

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
Member

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
Member

mrosseel commented Jun 1, 2018 •
edited

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
Member

mrosseel commented Jun 29, 2018 •
edited

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
Member

ManfredKarrer commented Jun 30, 2018 •
edited

2018.06 report

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

@ManfredKarrer
Copy link
Member

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

@cbeams
Copy link
Member 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
Member

2018.07 report

Running 6 seednode instance.

/cc bisq-network/compensation#93

@jmacxx
Copy link

jmacxx commented May 13, 2023

Cycle 47 report

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

May-13 19:10:09.564 [SeedNodeMain] INFO  b.c.d.n.f.n.GetBlocksRequestHandler: Received GetBlocksRequest from Optional[zy7hnopqyzvv6gcejskc5cu2j3dod3dp6nrpzfvwondq6kpkh533tiad.onion:9999] for blocks from height 788838. Building GetBlocksResponse with 741 blocks took 30 ms. 
May-13 19:10:09.573 [NetworkNode:SendMessage-to-zy7hnopqyzvv...] INFO  b.c.d.n.m.GetBlocksResponse: Sending a GetBlocksResponse with 827.682 kB 
May-13 19:10:09.577 [NetworkNode:SendMessage-to-zy7hnopqyzvv...] INFO  b.c.d.n.m.GetBlocksResponse: Sending a GetBlocksResponse with 827.682 kB 
May-13 19:10:09.580 [SeedNodeMain] INFO  b.c.d.n.f.n.GetBlocksRequestHandler: Send DataResponse to Optional[zy7hnopqyzvv6gcejskc5cu2j3dod3dp6nrpzfvwondq6kpkh533tiad.onion:9999] succeeded. getBlocksResponse.getBlocks().size()=741 
May-13 19:10:09.584 [SeedNodeMain] INFO  b.c.d.n.m.GetBlocksResponse: Sending a GetBlocksResponse with 827.682 kB 
[REPEATS]

Apart from that, everything is as usual.

@jmacxx jmacxx mentioned this issue May 13, 2023
Closed
@devinbileck devinbileck mentioned this issue Jun 16, 2023
Closed
@devinbileck
Copy link
Member

Cycle 48 report

Running 3 instances.
Nothing to report.

/cc bisq-network/compensation#1318

@Emzy Emzy mentioned this issue Jun 17, 2023
Closed
@Emzy
Copy link

Emzy commented Jun 17, 2023

Cycle 48 report

Running 3 instances.

  • nothing to report

/cc bisq-network/compensation#1320

@jmacxx
Copy link

jmacxx commented Jun 17, 2023

Cycle 48 report

Running 3 instances.
Nothing to report.

@jmacxx jmacxx mentioned this issue Jun 17, 2023
Closed
@wiz wiz mentioned this issue Jun 18, 2023
Closed
@Emzy Emzy mentioned this issue Jul 17, 2023
Closed
@Emzy
Copy link

Emzy commented Jul 17, 2023

Cycle 49 report

Running 3 instances.

  • nothing to report

/cc bisq-network/compensation#1336

@jmacxx
Copy link

jmacxx commented Jul 17, 2023

Cycle 49 report

Running 3 instances.
Nothing to report.

@jmacxx jmacxx mentioned this issue Jul 17, 2023
Closed
@devinbileck devinbileck mentioned this issue Jul 19, 2023
Closed
@devinbileck
Copy link
Member

Cycle 49 report

Running 3 instances.
Nothing to report.

/cc bisq-network/compensation#1342

@wiz wiz mentioned this issue Jul 23, 2023
Closed
@devinbileck devinbileck mentioned this issue Aug 18, 2023
Closed
@devinbileck
Copy link
Member

Cycle 50 report

Running 3 instances.
Nothing to report.

/cc bisq-network/compensation#1354

@ghost ghost mentioned this issue Aug 19, 2023
Open
@ghost
Copy link

ghost commented Aug 21, 2023

Cycle 50 report

Running no instances yet.
I'm posting this comment to check visibility.

Ping @Emzy

@jmacxx
Copy link

jmacxx commented Aug 21, 2023

Cycle 50 report

Running 3 instances.
Nothing to report.

@jmacxx jmacxx mentioned this issue Aug 21, 2023
Closed
@Emzy Emzy mentioned this issue Aug 22, 2023
Closed
@Emzy
Copy link

Emzy commented Aug 22, 2023

Cycle 50 report

Running 3 instances.

  • nothing to report

/cc bisq-network/compensation#1363

@403State 403State mentioned this issue Sep 4, 2023
Open
@devinbileck devinbileck mentioned this issue Sep 19, 2023
Open
@jmacxx
Copy link

jmacxx commented Sep 20, 2023

Cycle 51 report

Running 3 instances.
Nothing to report.

@jmacxx jmacxx mentioned this issue Sep 20, 2023
Open
@Emzy Emzy mentioned this issue Sep 20, 2023
Open
@Emzy
Copy link

Emzy commented Sep 20, 2023

Cycle 51 report

Running 3 instances.

  • nothing to report

/cc bisq-network/compensation#1383

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

@wiz wiz

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

No branches or pull requests