Everytime I try to open the Memorycoin-QT, I get a error which request to rebuild block database which takes extremely long.
When will this be solved?
When will this be solved?
this. happens every now and then
Topic: [ANN] MemoryCoin | CPU Coin | Paid Dev Team | Limited Supply [MMC] - page 72. (Read 281389 times)
December 17, 2013, 05:38:05 PM
this. happens every now and then
December 17, 2013, 05:34:19 PM
if someone still can't get sync here my memorycoin.conf
How to -> make a new file with editor then Ctrl+c & ctrl+v the code -> save file as -> memorycoin.info (save as ALL FILES and not as .TXT) in which directory? memory coin app data
(in win just search %appdata% directory then put in memorycoin folder)
Code:
rpcuser=x
rpcpassword=y
rpcport=1966
rpcallow=127.0.0.1
server=1
addnode=180.183.156.250:1968
addnode=76.24.94.154:1968
addnode=62.43.2.239:1968
addnode=82.52.177.81:1968
addnode=84.249.109.128:1968
addnode=78.239.107.25:49568
addnode=90.231.187.171:50251
addnode=70.112.30.253:26959
addnode=74.88.177.35:16511
addnode=54.200.207.220:49260
addnode=193.92.140.209:51570
addnode=95.89.105.134:1968
addnode=79.3.168.143:1968
addnode=91.157.155.98:1968
addnode=78.239.107.25:1968
addnode=87.49.126.92:1968
addnode=94.122.229.201:1968
addnode=94.3.149.107:1968
rpcpassword=y
rpcport=1966
rpcallow=127.0.0.1
server=1
addnode=180.183.156.250:1968
addnode=76.24.94.154:1968
addnode=62.43.2.239:1968
addnode=82.52.177.81:1968
addnode=84.249.109.128:1968
addnode=78.239.107.25:49568
addnode=90.231.187.171:50251
addnode=70.112.30.253:26959
addnode=74.88.177.35:16511
addnode=54.200.207.220:49260
addnode=193.92.140.209:51570
addnode=95.89.105.134:1968
addnode=79.3.168.143:1968
addnode=91.157.155.98:1968
addnode=78.239.107.25:1968
addnode=87.49.126.92:1968
addnode=94.122.229.201:1968
addnode=94.3.149.107:1968
How to -> make a new file with editor then Ctrl+c & ctrl+v the code -> save file as -> memorycoin.info (save as ALL FILES and not as .TXT) in which directory? memory coin app data
(in win just search %appdata% directory then put in memorycoin folder)
December 17, 2013, 05:33:13 PM
Freetrade, how much warning will we get for the fork? Can i suggest we get 12 hrs so people don't sleep with their miners mining the wrong fork all night?
Usually forks start with block X, not with the release of the new client. So both old and the new clients can mine until that block.
I didn't confirm this with with FreeTrade, but I think you can sleep well
December 17, 2013, 05:19:35 PM
Cant sync? Any good nodes, please?
Add me :
addnode 69.30.254.58:1968 add
FaSan
After hundreds of nodes yours finally worked. Thanks!
December 17, 2013, 05:12:18 PM
Freetrade, how much warning will we get for the fork? Can i suggest we get 12 hrs so people don't sleep with their miners mining the wrong fork all night?
December 17, 2013, 05:10:11 PM
maybe off-topic but relevant. FaSan after looking at your constant help to other users I think you could be a good candidate to apply for the CSO position of memorycoin https://bitcointalksearch.org/topic/the-memorycoin-blockchain-is-hiring-369487.
Thank you, I will look now :-)
FaSan
December 17, 2013, 05:08:50 PM
Ok finally clean.
Set the "rpcthreads" = number of CPUs Cores and set the "genproclimit" = the same value.
To me still to work fine from more of one hour.
FaSan
Set the "rpcthreads" = number of CPUs Cores and set the "genproclimit" = the same value.
To me still to work fine from more of one hour.
FaSan
I little update. With this setting, very sometimes can be a collision for filled rpc calls. I still to try now "rpcthreads" = number of CPUs Cores + 4
I will update
FaSan
December 17, 2013, 05:03:45 PM
Everytime I try to open the Memorycoin-QT, I get a error which request to rebuild block database which takes extremely long.
When will this be solved?
When will this be solved?
December 17, 2013, 05:03:39 PM
I don't think it is man. I haven't been able to get a connection yet. Don't take that as a failure on your part though, some coins just don't use UPNP well for some reason. i had the same problem with Nanotokens. When i get home in a little bit, i'm going to fork your repo, and investigate some small changes that should allow it to utilize upnp. i'll report back my findings.
Much obliged. uPNP has been a bugbear for me ever since I started with the Bitcoin codebase.
December 17, 2013, 04:56:36 PM
Cant sync? Any good nodes, please?
Add me :
addnode 69.30.254.58:1968 add
FaSan
maybe off-topic but relevant. FaSan after looking at your constant help to other users I think you could be a good candidate to apply for the CSO position of memorycoin https://bitcointalksearch.org/topic/the-memorycoin-blockchain-is-hiring-369487.
December 17, 2013, 04:53:34 PM
maybe build with UPNP support next time?
Actually managed to compile this one with UPNP, but haven't confirmed if it is working yet.
I don't think it is man. I haven't been able to get a connection yet. Don't take that as a failure on your part though, some coins just don't use UPNP well for some reason. i had the same problem with Nanotokens. When i get home in a little bit, i'm going to fork your repo, and investigate some small changes that should allow it to utilize upnp. i'll report back my findings.
December 17, 2013, 04:47:31 PM
Cant sync? Any good nodes, please?
Add me :
addnode 69.30.254.58:1968 add
FaSan
December 17, 2013, 04:45:04 PM
I can run the client under 32-bit (Windows 7), but I cannot run in mining mode since it crashes.
How much memory you got in those machines? what error are you getting?
The error just says to contact the dev team.
Just experienced again the error:
Quote
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information
Please contact the application's support team for more information
I have 3GB of RAM in ASUS F6Vseries notebook.
December 17, 2013, 04:44:32 PM
Add node increase chance to found a block ?
December 17, 2013, 04:42:51 PM
Cant sync? Any good nodes, please?
Add me :
addnode 69.30.254.58:1968 add
FaSan
December 17, 2013, 04:39:54 PM
Cant sync? Any good nodes, please?
December 17, 2013, 04:37:49 PM
I'm not sure I agree with you yet.
Albeit, writing yourself "payments" into the code for 6 officers, with two people filling two positions (twice the payments) is pretty sketchy.
Giving the right to vote on "job positions" to only a select few who already hold memorycoins from the previous coin is also sketchy. How can we be sure the devs didn't buy up all the old coins with the intention of holding the majority vote on the new coin? Why even hold a vote?
Writing a premine to "benefit previous memorycoin and protoshares holders" without outlining exactly how many coins would go to those people. We know the amount 1:10 memory coins. Does that mean there is 7,800,000 memory coins from 1.0? (nope, max 1 mill). So why the 780,000 MMC2 premine?
Let's say there was 500,000 memorycoins from 1.0
Shouldn't the premine be only 50,000 then?
What happens to all the MMC2 coins that aren't redeemed from MMC1 coins?
These questions need to be addressed going forward.
December 17, 2013, 04:29:19 PM
ok will update the config and restart the deamon see if it works.
thanks Fa
thanks Fa
December 17, 2013, 04:28:22 PM
Ok finally clean.
Set the "rpcthreads" = number of CPUs and set the "genproclimit" = the same value.
To me still to work fine from more of one hour.
FaSan
Set the "rpcthreads" = number of CPUs and set the "genproclimit" = the same value.
To me still to work fine from more of one hour.
FaSan
Hi Fa,
is that number of CPUs or number of core because genproclimit usually set to number of cores, not # of CPUs
You right, my mistake, sorry. Number of cores
December 17, 2013, 04:27:09 PM
Ok finally clean.
Set the "rpcthreads" = number of CPUs and set the "genproclimit" = the same value.
To me still to work fine from more of one hour.
FaSan
Set the "rpcthreads" = number of CPUs and set the "genproclimit" = the same value.
To me still to work fine from more of one hour.
FaSan
Hi Fa,
is that number of CPUs or number of core because genproclimit usually set to number of cores, not # of CPUs
Jump to: