Altcoin QT wallet won't sync

[wingless]

Hey guys,

I'm trying to sync my slimcoin QT wallet, but reading the debug file I get something like this:

mapBlockIndex.size() = 1
nBestHeight = 0
setKeyPool.size() = 100
mapWallet.size() = 0
mapAddressBook.size() = 1
Bound to port 41682
addrLocalHost = 192.168.1.109:41682
addrLocalHost = 0.0.0.0:41682
DNS seeding disabled
IRC seeding/communication disabled
ThreadOpenAddedConnections started
trying connection 78.46.37.209:41682 lastseen=-410459.7hrs
ThreadOpenConnections started
ThreadStakeMinter started
CPUMiner started for proof-of-stake
ThreadSocketHandler started
ThreadAfterBurner started
CPUMiner started for proof-of-burn
ThreadMessageHandler started
trying connection 81.207.93.95:41682 lastseen=-438237.5hrs
connection timeout
trying connection 145.239.189.106:41682 lastseen=-410459.7hrs
connection timeout
trying connection 5.9.38.137:41682 lastseen=-438237.5hrs
connection timeout
trying connection 85.10.208.71:41682 lastseen=-410459.8hrs
connection timeout
trying connection 5.105.63.14:41682 lastseen=-438237.5hrs
connection timeout
trying connection 37.187.100.75:41682 lastseen=-410459.8hrs
connection timeout


I'm particularly wondering about this portion of the debug file:

addrLocalHost = 192.168.1.109:41682
addrLocalHost = 0.0.0.0:41682

why are there two local host addresses? Shouldn't there only be one? To test this, I ran this same wallet on a different computer and saw that the debug showed only one local host address. Can it be possible that the wallet is getting confused at these two addresses? If so, how can I remove the bottom address (addrLocalHost = 0.0.0.0:41682)?

I'd appreciate any help! Thank you!

[jackg]

Try pinging both hosts if you're used to the command line. It might just be a problem with the network configuration...

But I'm assuming that if it is your machine might identify by that or it could be an interface piece or something.

Can you conntect to the Internet on the machine? Do you have a firewall on the PC and or router, how are they configured or what are you using... If its set on supersafe for the router, chances are your node won't run because the router will block connections...

[wingless]

thanks for your reply! I tried pinging both local hosts. Pinging 192.168.109 worked. when I tried to ping 0.0.0.0, I got a "general failure" error. I so think you are right, this is a network/connection related issue. I got the same error with the firewall on and off.

I'm not sure if this information will help, but I created a new user account on the same computer, and was able to successfully get the wallet to sync. So perhaps the problem may be in a setting that is on the other account, preventing the wallet from syncing?

I found the on wikiepdia when searching "what is 0.0.0.0?":

In the Internet Protocol Version 4, the address 0.0.0.0 is a non-routable meta-address used to designate an invalid, unknown or non-applicable target. This address is assigned specific meanings in a number of contexts, such as on clients or on servers.

In the context of servers, 0.0.0.0 can mean "all IPv4 addresses on the local machine". If a host has two IP addresses, 192.168.1.1 and 10.1.2.1, and a server running on the host is configured to listen on 0.0.0.0, it will be reachable at both of those IP addresses.

here is the link:

https://en.wikipedia.org/wiki/0.0.0.0

As I'm sure you can tell, I'm not very well versed in troubleshooting these kinds of problems. What next would you suggest in trying to find out what the cause of 0.0.0.0 is and how to remove it?

thanks again for your reply!

[jackg]

What operating system is it you're running? If it's Linux it's worth opening the command line and running cat on /etc/network/interfaces. The file might not exist, or it might not say much but if it does it should djust say something about dhcp but it's probably better to send the output here so I can take a look.

If it's in Windows you can probably run netstat to see if anything else is connected to it or if you have a connection with it.


I imagine your router probably takes those packets and sends them you but your computer doesn't pick it up... It could always just be shoddy programming with the wallet software, in which case you might be able to assign yourself 0.0.0.0

[wingless]

I'm using windows 7. I ran netstat and being its my first time looking at this I hope I'm not making a mistake, but I don't think I saw the wallet app on there. By that, I mean I looked for the port the app should be using and saw it was not listed on there.

Also, when you say assign myself 0.0.0.0, do you mean assign my IP as that?

Please let me know if you can think of anything else to do. Thanks again for replying.

[jackg]

Just pulled out my windows 7 laptop and my netstat gives internal connections from 127.0.0.1 and external ones from the 192.*.*.* address (aka 10.*.*.* on some networks).

https://kb.netgear.com/27476/How-do-I-set-a-static-IP-address-in-Windows is what I found for trying to change an IP address, there are potentially some settings that will say what address your computer sinks it has - just look at the router and make sure the first three numbers are the same (some are 192.168.0.1 and some are 192.168.1.1, go with a static ip like 192.168.0.145 if you wantt o set one and try this again).

If that deosn't work this wallet software isn't covered very much on the internet so I'm not sure there's much I can offer, you could try contacting the developer on the git repo to see if they have a solution (I know you mentioned it on stackoverflow).


Generally a lot of packets are sent with something so that your machine can identify it's for them even if they share an ip address with another machine so I'm not sure why this isn't working in this instance (maybe the program trying to save cpu time).

[wingless]

Just pulled out my windows 7 laptop and my netstat gives internal connections from 127.0.0.1 and external ones from the 192.*.*.* address (aka 10.*.*.* on some networks).
 
/quote]

thanks for explaining that, because I just realized I wasn't reading netstat correctly. So, the PC in question already has a static IP in the form of 192.168.*.*.* When running netstat, I do see the internal connections listed as 127.0.0.1 and I also see the static IP address listed under local connections. Is that normal? Or could that cause a conflict?

I'll look at the link you posted and try and reset my static IP, maybe that's the problem. I contacted the Dev, and he gave me a list of things to try and unfortunately they didn't work. Whatever the issue is, I think it has to do with my network configuration.

Thank you again for your help, I really appreciate it! I'll let you know if I make any progress.

[jackg]

No, the 127 and 192 afgeeases are local addresses... As long as the 192.168 one is a number above 1... I guess 0.0.0.0 is not listed anywhere there then?

[wingless]

yeah, unfortunately, I couldn't find 0.0.0.0 anywhere on the list net stat produced    I wish there was a way I could just remove the 0.0.0.0 but I it's listed no where, so I have no idea how to locate where it is coming from.