[ANN] [STABLE!] mmc.xpool.xram.co - First Memorycoin Pool

Started by KillerByte, December 24, 2013, 07:01:03 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

balthazr

hi Killer,

how long does the upgrade take? it's only upgrade the front web server or also mining server? will minging will stop while upgrading?


KillerByte

#171
Quote from: Firefly on December 25, 2013, 04:51:14 AM
Well, I also have another question. Is this coin can utilize much more memory than 1 GB? If I have 32 GB could I use them all?

It should only use 1GB no matter how many threads you have.

I will now address the maximum threads limit problem... do my best to fix it. Stay tuned!

EDIT: Pool just crashed. I will fix!!!

Firefly

Well, I also have another question. Is this coin can utilize much more memory than 1 GB? If I have 32 GB could I use them all?

KillerByte

Quote from: balthazr on December 25, 2013, 04:47:52 AM
killerbyte, this is GREAT Xmas's present ever!

tks

well, there will still be bugs to fix, so dont get TOO excited... :)

balthazr

killerbyte, this is GREAT Xmas's present ever!

tks

KillerByte


Firefly

#166
Quote from: balthazr on December 25, 2013, 04:32:06 AM
you guys may try to compile on windows with mingw, i;ve done before with compile bitcoin and litecoin on windows, just for practice only.
google for compile bitcoin/litecoin on windows, it may be the same with this

>src/main.cpp:1925: error: integer constant is too large for 'long' type
>src/main.cpp:5723: error: integer constant is too large for 'long' type
> 1925    if(vtx[0].GetValueOut()!=73366415666531){
> 5723    int64 bottomOfThePollAmount=9223372036854775807;

That's what I mean. Excuse me, I'm not a programmer.

balthazr

you guys may try to compile on windows with mingw, i;ve done before with compile bitcoin and litecoin on windows, just for practice only.
google for compile bitcoin/litecoin on windows, it may be the same with this

Firefly

Quote from: rambo on December 25, 2013, 04:18:53 AM
We Need Windows Version!!!!!
Really it's so. We don't want to assemble/compile, make/install, errors with missing libs and other linux brainfu*king stuff.

rambo

PTS:PiGpn2feczAyyzQiBCNrd7aMCTMmWFqGqg
MMC:MBJdzcauFmMTeB7JMsrsJeR9vKDQENuoBC
PPC:PQPZRkbYnPsPPQDFT9ahEvdpBM7BpSYBkS

balthazr

tks moutujan,

still have some errors, but i give up, will ask the provider to re-install to ubuntu one, that one i'm familiar with.  :-[

tks for your support

mutoujian

Quote from: balthazr on December 25, 2013, 04:01:15 AM
@moutain: makefile.my:150: *** missing separator  :'(

which version of centos are you using, i'm currently on centos 5.10, that's bad  :'(

you cat get it from  http://pan.baidu.com/s/1o64mIqI 

balthazr

@moutain: makefile.my:150: *** missing separator  :'(

which version of centos are you using, i'm currently on centos 5.10, that's bad  :'(

KillerByte

Quote from: doxymoron on December 25, 2013, 02:18:33 AM
Immediately after I start the miner it works for about 2 minutes.  Here's an example:

submit: 020d527e6d7ae2dbe41fdcb2ac1892ed349ef426356a2680fbac1d5ff371d2ea
[MASTER] submitted share -> SHARE
[STATS] 2013-12-25 02:07:28 | SHARES: 1 (100.0% | 52.9/h), VL: 1 (100.0%), RJ: 0 (0.0%), ST: 0 (0.0%)
hash generated - 8206 / 1968 / 3410774748
hash generated - 3065 / 1968 / 3346170544
hash generated - 1418 / 1968 / 4147674291
[MASTER] work received
connecting to 162.243.216.74:1339
system:111

It submits a couple of shares within the first minute or 2 then seems to get disconnected.  After that it will submit more shares, but won't receive any response, and won't work until I start again.  Checking if anyone else has this issue.

Thanks for your insight on this.

Quote from: milkmeat on December 25, 2013, 02:42:02 AM
Hi, KillerByte, Thanks for you effort for the pool

I got following output in my miner, it looks like it's sending the same share within a short time. The first is accepted and the second is rejected. Does that mean some duplicate work is in different threads? Maybe you can fix it to make the miner more efficient.


hash generated - 1921 / 1968 / 4265226673
hash generated - 5552 / 1968 / 3603954008
submit: 0c4102809f907d3fc6e995f020e7dbd2fdda66f26f87ecbfa63815c3c0f281ed
[MASTER] submitted share -> SHARE
[STATS] 2013-12-25 02:32:58 | SHARES: 2 (100.0% | 144.0/h), VL: 2 (100.0%), RJ:
0 (0.0%), ST: 0 (0.0%)
hash generated - 9188 / 1968 / 1831948737
hash generated - 9578 / 1968 / 3607491106
hash generated - 8598 / 1968 / 811137229
hash generated - 1921 / 1968 / 4265226673
hash generated - 5552 / 1968 / 3603954008
submit: 0c4102809f907d3fc6e995f020e7dbd2fdda66f26f87ecbfa63815c3c0f281ed
[MASTER] submitted share -> REJECTED
[STATS] 2013-12-25 02:33:16 | SHARES: 2 (100.0% | 105.9/h), VL: 2 (66.7%), RJ: 1
(33.3%), ST: 0 (0.0%)
hash generated - 2666 / 1968 / 3113632687
hash generated - 13359 / 1968 / 3249895379

Different keys are aupposed to be sent to each client, maybe there is a problem with the key pool for memorycoin?

smokim11

Quote from: balthazr on December 25, 2013, 02:54:15 AM
pool down again?

It seems that way.

Guys the System:111 error means that the pool is down but also means everything is working correctly except a valid connection to the pool.

I think this should be solved after server migration in a few hours so sit tight and wait until the new server comes in.
If I helped you and want to show your appreciation donate any amount:
Pjem2V2FDPGZa6yAvpL2fN5yZKXYUNLSv5