Pages:
Author

Topic: [ANN] MemoryCoin | CPU Coin | Paid Dev Team | Limited Supply [MMC] - page 59. (Read 281387 times)

hero member
Activity: 910
Merit: 1000
Now it would be great to get any feedback from you guys: Stalled miners/wallets from you - do they have a public IP? Or are they NATted?
I have trouble with sync on my home NATed windows 8 computer. Reinstalling Windows is not helped. On the work memorycoin is installed on two Windows computers in the same network, one has a public address, the second behind NAT. Both work perfectly.
member
Activity: 111
Merit: 10
Delete many times memorycoin folder in appdata but still cant sync, omg any can tell me a f*king solution?

try "-reindex"
hero member
Activity: 690
Merit: 500
It finally synced. I just searched through the tread for some more nodes, added them, and it seems that some of them worked. Also I used the old MemoryCoin folder with block information that was created during my first sync. So I suppose it is all about the nodes, not some corrupt DB files. And yes, I am behind NAT.
newbie
Activity: 10
Merit: 0
Unable to import my old wallet.. yeah.. 280 MMC gone. Love that fork changes.

How are you unable to import? what's you specific details as to why?
hero member
Activity: 644
Merit: 500
I am selling 280 MMC, Please PM if interested.
newbie
Activity: 40
Merit: 0
Delete many times memorycoin folder in appdata but still cant sync, omg any can tell me a f*king solution?
newbie
Activity: 11
Merit: 0
Regarding the connection / synchronization problem I suspect an issue specially for people who are "NATted" and do not have a public IP address directly. I don't know much about it, but the source used the library libminiupnpc which seems to be necessary for having some sort of inbound connections from outside although there is no public IP...

Background is, that I have two MMC wallets/miners running on Debian root servers having public IP addresses and two other wallets/miners in my home office, one on VMware (ESXi), the other on VirtualBox. Both "external" servers with public IP addresses are fully synced and currently at block 724. Both "internal" servers do not succeed in fully connecting to the network. From what I see both "intern" servers occasionally establish connections from their side (1 or 2) but shortly after they do not have any connection again and are waiting forever.

One of those non-synchronizing miners/wallets were installed only a couple of minutes ago using the current Github sources (new VirtualBox for trial).

Now it would be great to get any feedback from you guys: Stalled miners/wallets from you - do they have a public IP? Or are they NATted?


I have 16 servers running here, 1 with an external IP at the gateway and 15 on the internal network.  I setup the "connect=" option in the memorycoin.conf file of the 15 internal ones to point to the one at the gateway.  I set it up this way to cut down on the traffic and increase performance, but I still had a lot of hangs, crashes, and block laggyness.  I then set the "rpcthreads=" option to 24 (it defaults to 4) on the one with the external IP.  So far, I have had zero hangs, crashes, or block laggyness on the 15 internal clients.
full member
Activity: 140
Merit: 100
My memorycoind just crashed with:

Code:
Dec 18 12:51:15 kernel: [1430299.393640] memorycoin-msgh[22896]: segfault at 50 ip 0000000000488dbf sp 00007ff4bdff89e0 error 4 in memorycoind[400000+2f5000]

This is why chainbrowser has not been updating.
member
Activity: 73
Merit: 10
Regarding the connection / synchronization problem I suspect an issue specially for people who are "NATted" and do not have a public IP address directly. I don't know much about it, but the source used the library libminiupnpc which seems to be necessary for having some sort of inbound connections from outside although there is no public IP...

Background is, that I have two MMC wallets/miners running on Debian root servers having public IP addresses and two other wallets/miners in my home office, one on VMware (ESXi), the other on VirtualBox. Both "external" servers with public IP addresses are fully synced and currently at block 724. Both "internal" servers do not succeed in fully connecting to the network. From what I see both "intern" servers occasionally establish connections from their side (1 or 2) but shortly after they do not have any connection again and are waiting forever.

One of those non-synchronizing miners/wallets were installed only a couple of minutes ago using the current Github sources (new VirtualBox for trial).

Now it would be great to get any feedback from you guys: Stalled miners/wallets from you - do they have a public IP? Or are they NATted?
full member
Activity: 238
Merit: 100
{
"blocks" : 658,
"currentblocksize" : 1384,
"currentblocktx" : 2,
"difficulty" : 0.00000118,
"errors" : "",
"genproclimit" : 8,
"hashespermin" : 1.89160325,
"pooledtx" : 2,
"testnet" : false
}


im still 60 or 70 blocks behind but i get hashes, do you think it works correctly or do i mine in the air?
full member
Activity: 140
Merit: 100
Bitcoin - love & hate
Unable to import my old wallet.. yeah.. 280 MMC gone. Love that fork changes.
member
Activity: 112
Merit: 10
terminate called after throwing an instance of 'boost::exception_detail::clone_impl >'
  what():  boost::thread_resource_error

Try the script created by FaSan. It will restart the daemon automatically: https://bitcointalksearch.org/topic/m.4030418
sr. member
Activity: 315
Merit: 250
ERROR: ConnectBlock() : Block 1 coinbase pays too much (actual=117154811 vs limit=117154811)

cant create chain ?  Huh
member
Activity: 100
Merit: 10
terminate called after throwing an instance of 'boost::exception_detail::clone_impl >'
  what():  boost::thread_resource_error
full member
Activity: 196
Merit: 100
anyone how do i setup miner for centOS?
member
Activity: 62
Merit: 10
I am getting "No block source available" for about 4 hours from now. Tried adding nodes suggested here and deleting the Memorycoin folder, doesn't help. Given that many are reporting the same issue here I think there is some general network problem that emerged several hours ago.

Mine just resolved itself after a few dozen tries at deleting everything!

Same here. Deleted the appdata folder (making sure to save my wallet.dat), then added the new nodes posted, and after 10 minutes I started getting connections. Up to 5 now.
newbie
Activity: 59
Merit: 0
Is there any way to see what the network hashes per min is? (sorry if that's a noobie question)
newbie
Activity: 17
Merit: 0
I am getting "No block source available" for about 4 hours from now. Tried adding nodes suggested here and deleting the Memorycoin folder, doesn't help. Given that many are reporting the same issue here I think there is some general network problem that emerged several hours ago.

Mine just resolved itself after a few dozen tries at deleting everything!
member
Activity: 112
Merit: 10
A script to restart the daemon when this happens would be very handy.


A very simple script, I hope can help you :


write it into the file /etc/crontab
Code:
*/1 * * * * root /bin/ps -ef|grep -v grep|grep memorycoind >/dev/null || /usr/local/bin/memorycoind -daemon

change name of process and/or path about your installation



FaSan

Thank you! The only problem is that I'm a linux newbie and don't know how to make that function. Will see if I can find a crontab newbie guide somewhere.

Edit: I think I got it working by following this guide.
hero member
Activity: 690
Merit: 500
I am getting "No block source available" for about 4 hours from now. Tried adding nodes suggested here and deleting the Memorycoin folder, doesn't help. Given that many are reporting the same issue here I think there is some general network problem that emerged several hours ago.
Pages:
Jump to: