And therefore have to redownload all the blockchain stuff? . . I think this is as far as I can go at this stage . . thanks.biolizard89 wrote:I think this usually is indicative of a mismatched BerkeleyDB version, probably because the FreeSpeechMe distributed namecoind binary was using a different version than the official packages. There are probably ways to recover this, but they're complicated. The easiest workaround is probably to rename your ~/.namecoin/ folder and let it regenerate a profile.philip_rhoades wrote:OK, I used 8335 for convenience . . now I get:biolizard89 wrote:Port 8334 is the Namecoin peer port. I'm guessing that the namecoind packaged in FreeSpeechMe grabbed that port. The current GitHub code fixes that. I believe you can work around it by placing the following line in ~/.namecoin/namecoin.conf
port=xxx
Where xxx is a port that isn't in use. Incoming connections don't have to be allowed by your firewall, although doing so will help the network.
Let us know if that helps you load the GUI.
Cheers.
Code: Select all
libpng warning: iCCP: Not recognizing known sRGB profile that has been edited libpng warning: iCCP: Not recognizing known sRGB profile that has been edited EXCEPTION: 22DbRunRecoveryException DbEnv::open: DB_RUNRECOVERY: Fatal error, run database recovery namecoin in Runaway exception QMetaObject::invokeMethod: No such method QObject::message(QString,QString,unsigned int,bool*)
Next step - registering a domain
-
- Posts: 12
- Joined: Mon Mar 23, 2015 1:31 pm
- os: linux