Debug.log file is increasing until hard drive is full

Support
1

Hi everyone,

I migrated Peercoin from Raspbian OS to Windows 10.

Now, the debug.log file is increasing in size until the hard drive is completely full.

It is writing this block again and again:

************************
EXCEPTION: St13runtime_error       
Error: Keypool ran out, please call keypoolrefill first.       
E:\Peercoin\peercoin-qt.exe in ThreadStakeMinter()       

2025-01-02T21:18:30Z CPUMiner started for proof-of-stake
2025-01-02T21:18:30Z

I already tried the command keypoolrefill in the console, but still the same error…

Thanks and best regards

1 Like
2

Any help is very appreciated. I´d like to take part on Minting again.

3

@backpacker69 is looking into it.

2 Likes
4

Looks like your wallet.dat is not writable by windows, either permission problem or bdb version difference. Try reimporting privkeys

1 Like
5

Hi, thanks for your reply.

I did not remove the already imported keys, because I did not find a suitable command in the console. So, I just did importprivkey and restarted the client. But the debug.log file is still increasing with the same error message…

6

can you try stopping the wallet, moving wallet.dat somewhere and restarting it again. it should create a new legacy wallet that you should be able to import privkeys to.

7

Stopped the wallet, removed wallet.dat and restarted. Peercoin quit with following error:

image
image1032Ă—314 19.6 KB

Uninstalled and installed Peercoin, created new blank encrypted wallet, imported private keys. Then, restarted wallet, decrypt wallet for minting only. Still the same problem…

1 Like
8

Anyone some idea?

9

Mismatching barkley db versions. 4 vs 5

10

Sorry, didnt saw your post. Okey, but how can i fix this?

I´ve updated to the newest version of peercoin, but still getting the error.

11

Well, I can’t figure out where does your wallet came from.

If it comes from Raspbian, it likely uses barkleydb 5. The windows build uses barkleydb 4.x.

If you really want to use that barkleydb (5) on Windows, you will need a QT client compiled with barkleydb 5. Which is, of course, possible, but not easy if you are not used to compiling complicated programs with plenty of dependencies on Windows. Perhaps this can be automated as a part of the new build process, but I am not sure. I can check with someone more familiar with this.

One alternative is to simply send the coins from Raspberry to a new wallet on Windows.

12

Oh. So, a private key out of Raspbian client cannot be imported to a Windows client?

Okey, please let me know if that could be fixed in your build pipeline.
Is there a reason, why not the same version is used for all your clients?

Otherwise, I will go with your suggested solution by sending the coins.

1 Like
13

Yes it can. Export it on raspberry and import it on windows. In the console of the qr client.

Yes. The raspberry build is built using Debian build system and standards. With goal of eventually getting into official Debian repositories.
Debian does not have Barkley db 4 in the repository. That package is like 15 years out of date, but is being used in Satoshi client based coins out of compatibility reasons.

Modern iterations do not use Barkley db at all but sqlite.

14

That´s actually what I did and after importing I get those errors…

I will create a new wallet on Windows and send the coins to it.
But now another question has appeared: how to export private keys of a descriptor wallet?

1 Like
15

Exported private keys with “listdescriptors true”. Is this sufficient for wallet recovery?

I downloaded arm-linux-gnu tar.gz, is this the correct one for raspbian OS?
And is there a tutorial how to install peercoin?

1 Like
16

On raspbian OS you can simply apt-get it.

But OK, you can also download the .tar.gz from Github. In which case, unpack the .tar.gz and double click the peercoin-qt binary.

You can also install it from flathub if you run Raspberry Pi 4 or 5. :slight_smile:

If installed with apt-get or flatpak, peercoin-qt will show up in the menu.

17

Thanks for your help!

Installed Peercoin on Raspberry Pi, created new blank non-descriptor wallet and imported private key.

When sending transaction I get the following error message:

image
image470Ă—142 15.1 KB

Executed keypoolrefill in console, still the same error.

1 Like
18

can you please run the client with debug=1 and send debug.log after getting this error to backpacker69@protonmail.com

19

Sure, but cannot find the .peercoin folder. Where is it located?

20

How did you install the client?

$HOME/.peercoin

Or, if flatpak:

$HOME/.var/app/net.peercoin.peercoin-qt/data/