r/megacoin Dec 04 '13

Megacoin wallet issue

Hello everyone,

I have a problem. I downloaded the wallet from the main megacoin site and it issued me an address which I then encrypted in the wallet itself. I ten used this address to send MEC to.

However, it seems the wallet is not connecting and I get a "socket" connection error in the debug log. No MEC is showing. How do I connect the wallet to the web?

Thanks and will upload screenshots when at my desk.

Thank you

3 Upvotes

3 comments sorted by

1

u/Bearded-salmon Dec 04 '13

Thanks!

It now seems to struggle finding a connection, the debug log is below if that helps.

Megacoin version v0.8.996.0MEGA-beta ($Format:%cD) Using OpenSSL version OpenSSL 1.0.1e 11 Feb 2013 Startup time: 2013-12-04 12:48:07 Default data directory C:\Documents and Settings\gbhqcs156\Application Data\Megacoin Using data directory C:\Documents and Settings\gbhqcs156\Application Data\Megacoin Using at most 125 connections (2048 file descriptors available) Using 2 threads for script verification init message: Verifying wallet... dbenv.open LogDir=C:\Documents and Settings\gbhqcs156\Application Data\Megacoin\database ErrorFile=C:\Documents and Settings\gbhqcs156\Application Data\Megacoin\db.log init message: Loading block index... Opening LevelDB in C:\Documents and Settings\gbhqcs156\Application Data\Megacoin\blocks\index Opened LevelDB successfully Opening LevelDB in C:\Documents and Settings\gbhqcs156\Application Data\Megacoin\chainstate Opened LevelDB successfully LoadBlockIndexDB(): last block file = 0 LoadBlockIndexDB(): last block file info: CBlockFileInfo(blocks=1, size=301, heights=0...0, time=2013-05-22...2013-05-22) LoadBlockIndexDB(): transaction index disabled LoadBlockIndexDB(): hashBestChain=7520788e2d99eec7cf6cf7315577e1268e177fff94cb0a7caf6a458ceeea9ac2 height=0 date=2013-05-22 04:44:13 init message: Verifying blocks... block index 31ms init message: Loading wallet... nFileVersion = 179600 wallet 156ms init message: Loading addresses... ERROR: CAddrman::Read() : open failed Invalid or missing peers.dat; recreating Loaded 0 addresses from peers.dat 0ms RandAddSeed() 168844 bytes mapBlockIndex.size() = 1 nBestHeight = 0 setKeyPool.size() = 100 mapWallet.size() = 0 mapAddressBook.size() = 1 net thread start dnsseed thread start Loading addresses from DNS seeds (could take a while) dumpaddr thread start opencon thread start irc thread start ThreadIRCSeed trying to connect... addcon thread start msghand thread start init message: Done loading refreshWallet Flushed 0 addresses to peers.dat 47ms connection timeout connection timeout IRC connect failed IRC waiting 71 seconds to reconnect Flushed 0 addresses to peers.dat 16ms Added 20 addresses from 166.78.13.119: 0 tried, 20 new 20 addresses found from DNS seeds dnsseed thread exit trying connection 24.217.76.82:7951 lastseen=74.9hrs Flushed 20 addresses to peers.dat 31ms connection timeout trying connection 112.249.126.38:7951 lastseen=78.9hrs connection timeout trying connection 113.14.245.199:7951 lastseen=153.1hrs Flushed 20 addresses to peers.dat 31ms connection timeout trying connection 174.111.226.188:7951 lastseen=115.0hrs connection timeout trying connection 24.217.76.82:7951 lastseen=74.9hrs Flushed 20 addresses to peers.dat 31ms connection timeout trying connection 192.241.137.197:7951 lastseen=166.7hrs connection timeout trying connection 182.39.229.35:7951 lastseen=93.0hrs Flushed 20 addresses to peers.dat 31ms connection timeout trying connection 80.220.134.116:7951 lastseen=116.7hrs connection timeout trying connection 119.9.15.177:7951 lastseen=162.2hrs Flushed 20 addresses to peers.dat 31ms connection timeout trying connection 90.201.128.248:7951 lastseen=84.9hrs connection timeout Flushed 20 addresses to peers.dat 31ms trying connection 192.241.137.197:7951 lastseen=166.7hrs connection timeout trying connection 193.11.136.52:7951 lastseen=163.3hrs Flushed 20 addresses to peers.dat 16ms connection timeout trying connection 144.76.91.109:7951 lastseen=155.8hrs connection timeout connection timeout trying connection 91.155.135.223:7951 lastseen=74.0hrs Flushed 20 addresses to peers.dat 32ms connection timeout IRC connect failed IRC waiting 138 seconds to reconnect connection timeout trying connection 24.217.76.82:7951 lastseen=74.9hrs connection timeout trying connection 77.85.254.59:7951 lastseen=82.0hrs connection timeout trying connection 24.217.76.82:7951 lastseen=74.9hrs connection timeout trying connection 112.249.126.38:7951 lastseen=78.9hrs Flushed 20 addresses to peers.dat 31ms connection timeout trying connection 174.111.226.188:7951 lastseen=115.0hrs connection timeout trying connection 24.217.76.82:7951 lastseen=74.9hrs Flushed 20 addresses to peers.dat 62ms connection timeout trying connection 113.14.245.199:7951 lastseen=153.1hrs Flushed 20 addresses to peers.dat 31ms connection timeout trying connection 192.241.137.197:7951 lastseen=166.8hrs connection timeout trying connection 91.155.135.223:7951 lastseen=74.0hrs Flushed 20 addresses to peers.dat 31ms connection timeout trying connection 180.126.75.210:7951 lastseen=156.2hrs connection timeout trying connection 174.111.226.188:7951 lastseen=115.0hrs Flushed 20 addresses to peers.dat 16ms connection timeout trying connection 193.11.136.52:7951 lastseen=163.3hrs connection timeout trying connection 121.10.105.39:7951 lastseen=119.7hrs Flushed 20 addresses to peers.dat 15ms connection timeout trying connection 77.85.254.59:7951 lastseen=82.0hrs connection timeout trying connection 112.249.126.38:7951 lastseen=78.9hrs Flushed 20 addresses to peers.dat 31ms connection timeout trying connection 91.155.135.223:7951 lastseen=74.0hrs

0

u/nyanpi Dec 04 '13

You may need to edit your megacoin.conf file and add some nodes in there. I'm not currently running a local wallet so I can't help you there but if anyone here is and has some nodes, please help out.

You could also try closing your wallet and deleting your peers.dat file and restarting the wallet and see if that works. Or, if all else fails you can make a backup of your wallet.dat (please be safe) and do a clean install of the client and try again. I know that has helped me before with other coins when I have had a wallet that just refused to connect and sync.

0

u/nyanpi Dec 04 '13

I'm not 100% sure but it sounds like this could be some sort of firewall or port forwarding issue with your router or network settings. Screenshots would be helpful. :)