libbitcoin and bitcoind servers

bobinson commented

2023-03-30 14:22:22 +00:00

(Migrated from gitlab.com)

Provide libitcoin and bitcoind servers which are fully synced with Bitcoin Mainnnet

bobinson commented

2023-03-30 14:22:22 +00:00

(Migrated from gitlab.com)

assigned to @rilesdun

bobinson commented

2023-03-30 14:22:35 +00:00

(Migrated from gitlab.com)

assigned to @robert.hedler

bobinson commented

2023-03-30 14:32:40 +00:00

(Migrated from gitlab.com)

changed title from libitcoin and bitcoind servers to lib{+b+}itcoin and bitcoind servers

changed title from **libitcoin and bitcoind servers** to **lib{+b+}itcoin and bitcoind servers**

rilesdun commented

2023-04-03 16:59:00 +00:00

(Migrated from gitlab.com)

Bitcoind full node is available for @vampik

Libbitcoin is taking time to restart as original chainstore corrupted, database is redownloading and resyncing

Bitcoind full node is available for @vampik Libbitcoin is taking time to restart as original chainstore corrupted, database is redownloading and resyncing

rilesdun commented

2023-04-12 13:32:08 +00:00

(Migrated from gitlab.com)

Libbitcoin bs server is running - block 774k out of 785k

bs config is setup with only one peer to ensure multi-threading bug doesn't corrupt database

Libbitcoin main VM has two backups available:

One periodically backing up changes on the running VM
One complete clone of the VM, database is synced upto 765k blocks

cc: @bobinson @vampik @hirunda

Libbitcoin `bs` server is running - block 774k out of 785k `bs` config is setup with only one peer to ensure multi-threading bug doesn't corrupt database Libbitcoin main VM has two backups available: - One periodically backing up changes on the running VM - One complete clone of the VM, database is synced upto 765k blocks cc: @bobinson @vampik @hirunda

bobinson commented

2023-04-26 08:04:26 +00:00

(Migrated from gitlab.com)

changed due date to April 06, 2023

rilesdun commented

2023-04-27 19:13:43 +00:00

(Migrated from gitlab.com)

marked this issue as related to #483

rilesdun commented

2023-04-27 19:13:52 +00:00

(Migrated from gitlab.com)

mentioned in issue #483

rilesdun commented

2023-05-05 19:07:17 +00:00

(Migrated from gitlab.com)

@vampik @bobinson

Sync has slowed down slightly, but is nearing complete and will finish sometime over the weekend..

19:05:10.104222 INFO [blockchain] Block [780888] 3072 txs 6811 ins   21 wms 5173 vms  759 vµs    6 rµs    3 cµs  707 pµs    7 aµs   36 s
µs 1476 dµs 0.000000

8k~ blocks to go!

@vampik @bobinson Sync has slowed down slightly, but is nearing complete and will finish sometime over the weekend.. ``` 19:05:10.104222 INFO [blockchain] Block [780888] 3072 txs 6811 ins 21 wms 5173 vms 759 vµs 6 rµs 3 cµs 707 pµs 7 aµs 36 s µs 1476 dµs 0.000000 ``` 8k~ blocks to go!

rilesdun commented

2023-05-08 11:43:12 +00:00

(Migrated from gitlab.com)

Libbitcoin bs server has been fully synced and given to @vampik and @hirunda for testing

cc: @tai.sama @bobinson

Libbitcoin `bs` server has been fully synced and given to @vampik and @hirunda for testing cc: @tai.sama @bobinson

bobinson commented

2023-05-10 13:12:04 +00:00

(Migrated from gitlab.com)

As per @hirunda the libbitcoin server has crashed again - db is corrupt.

rilesdun commented

2023-05-10 13:24:37 +00:00

(Migrated from gitlab.com)

Yes, @hirunda was going to upload the fully synced chain he has locally - to avoid 2~ days of syncing required after the backup is restored.

I have provided him with the appropriate command, but commented that the 1.6TBs available on this server is not suffficent

Yes, @hirunda was going to upload the fully synced chain he has locally - to avoid 2~ days of syncing required after the backup is restored. I have provided him with the appropriate command, but commented that the 1.6TBs available on this server is not suffficent

bobinson commented

2023-05-10 21:16:33 +00:00

(Migrated from gitlab.com)

Hi @rilesdun - Why is that you are not having a reliable back up ? A copy of the file is not yet available AWS EBS or S3 ?

rilesdun commented

2023-05-16 23:12:03 +00:00

(Migrated from gitlab.com)

We have a reliable backup, though it is only 745K/790K blocks. Any time it has fully synced, it is unable to stop and corrupts.

We now have four copies - The backup, @hirunda local copy, and two on the VPS.

We have a reliable backup, though it is only 745K/790K blocks. Any time it has fully synced, it is unable to stop and corrupts. We now have four copies - The backup, @hirunda local copy, and two on the VPS.

tai.sama commented

2023-06-14 13:11:58 +00:00

(Migrated from gitlab.com)

assigned to @hirunda and unassigned @robert.hedler and @rilesdun

tai.sama commented

2023-06-14 13:15:29 +00:00

(Migrated from gitlab.com)

assigned to @rilesdun

tai.sama commented

2023-06-14 13:25:57 +00:00

(Migrated from gitlab.com)

change assignee to Davor

hirunda commented

2023-06-14 14:21:59 +00:00

(Migrated from gitlab.com)

@tai.sama Why assigned to me? I am not DevOps. Yes I am maintaining the libbitcoin (only) server on my local PC and we are using currently for testing the mainnet, but the final libbitcoin server should be maintained by DevOps.

hirunda commented

2023-06-14 14:34:15 +00:00

(Migrated from gitlab.com)

OK, I just talked with @rilesdun and he explained to me that I am going to maintain the libbitcoin server until we finish mainnet testing. No need for clarification @tai.sama.

Thanks,
Davor

OK, I just talked with @rilesdun and he explained to me that I am going to maintain the libbitcoin server until we finish mainnet testing. No need for clarification @tai.sama. Thanks, Davor

tai.sama commented

2023-07-26 13:08:05 +00:00

(Migrated from gitlab.com)

Close this one since we're tracking on another ticket

tai.sama (Migrated from gitlab.com) closed this issue

2023-07-26 13:08:09 +00:00

libbitcoin and bitcoind servers #525