Philemon Ukane
Philemon Ukane
> You have to be dropping the wrong data. How else would it report any db heights? I removed `~/.dcrdata/data` path and droped dcrdata db, so am starting afresh. Pm2...
First log output from dcrdata ``` 2022-01-19 20:59:07.531 [INF] PSQL: Empty database "dcrdata". Creating tables... 2022-01-19 20:59:07.532 [INF] PSQL: Creating the "meta" table. 2022-01-19 20:59:07.552 [INF] PSQL: Creating the "blocks"...
> So have you not been able to get a full sync of dcrdata so far because of this? Always panic during stage 1 of 5? yes.
>Do you know why this is not more like 870897? Is dcrd syncing at the same time? As of then, yes. dcrd finished syncing in less than 8hours.
>What did you mean by "fast forward"? Like this? Yeah, the "fast forward" loop runs in the main import loop instead of a panic. > Does it still panic even...
I am running a dev server with Ubuntu 20.04.3 LTS (GNU/Linux 5.4.0-96-generic x86_64) 154GB space.
> df -H says the drive is at 221G utilization with everything else. That's a lot of space, I might be able to add more space soon. But without the...
> I think you're out of disk space... Yeah, noticed it during setting spending info in addresses table.
`du -h` report: ``` udev 3.9G 0 3.9G 0% /dev tmpfs 796M 1.1M 795M 1% /run /dev/vda1 155G 143G 13G 93% / tmpfs 3.9G 16K 3.9G 1% /dev/shm tmpfs 5.0M...
dcrd is has been running smooth. For postgresql and stakeDB, space wasn't a concern during block import stage. Although, I will add more space soon since a complete sync would...