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

[pvp1982]

what is the OS (linux flavour) used?

[KillerByte]

agreed... but there is nothing online about how to fix it.

the backtrace does not show anything useful either... maby its a bug in the memorycoin client that only comes from great stress?

[pvp1982]

dmesg -T | tail

[Wed Dec 25 20:17:24 2013] systemd-journald[101]: Failed to write entry (25 items, 211571354 bytes) despite vacuuming, ignoring: Argument list too long
[Wed Dec 25 20:19:02 2013] systemd-journald[101]: Deleted empty journal /var/log/journal/bb9d0a52a41243829ecd729b40ac0bce/user-1000@c4ef46c298b543f9ab9fbe27625479c4-0000000000000000-0000000000000000.journal (3735552 bytes).
[Wed Dec 25 20:19:02 2013] systemd-journald[101]: Vacuuming done, freed 3735552 bytes
[Wed Dec 25 20:19:02 2013] systemd-journald[101]: Failed to write entry (25 items, 237032090 bytes) despite vacuuming, ignoring: Argument list too long

... and that message is repeated many times.

Hmm I don't think it's related to the software buffer overflow error.

[KillerByte]

dmesg -T | tail

[Wed Dec 25 20:17:24 2013] systemd-journald[101]: Failed to write entry (25 items, 211571354 bytes) despite vacuuming, ignoring: Argument list too long
[Wed Dec 25 20:19:02 2013] systemd-journald[101]: Deleted empty journal /var/log/journal/bb9d0a52a41243829ecd729b40ac0bce/user-1000@c4ef46c298b543f9ab9fbe27625479c4-0000000000000000-0000000000000000.journal (3735552 bytes).
[Wed Dec 25 20:19:02 2013] systemd-journald[101]: Vacuuming done, freed 3735552 bytes
[Wed Dec 25 20:19:02 2013] systemd-journald[101]: Failed to write entry (25 items, 237032090 bytes) despite vacuuming, ignoring: Argument list too long

... and that message is repeated many times.

[pvp1982]

what is there in kernel log?

dmesg -T | tail

or only

dmesg

?

[KillerByte]

any ideas on the buffer overflow message?

*** buffer overflow detected ***: memorypool terminated

some attack directed to the port on which the pool is running?

I doubt... I think it is another system limit or something...

I just backtraced it and it was not from any of my pool functions...

[pvp1982]

any ideas on the buffer overflow message?

*** buffer overflow detected ***: memorypool terminated

some attack directed to the port on which the pool is running?

[KillerByte]

is this normal? i mean the duplicates... what does the first number actually mean?

hash generated - 7502 / 1968 / 3640808312
hash generated - 10725 / 1968 / 3757984692
hash generated - 13317 / 1968 / 2492638785
hash generated - 12666 / 1968 / 2015562052
hash generated - 12666 / 1968 / 2015562052
hash generated - 14294 / 1968 / 3536542128
hash generated - 14294 / 1968 / 3536542128
hash generated - 13666 / 1968 / 1088440815
hash generated - 13666 / 1968 / 1088440815
hash generated - 13666 / 1968 / 1088440815
hash generated - 12510 / 1968 / 3560445581

I have never seen that before... do you hash quickly?

are you submitting double shares?

hmm, probably around 10 hpm.
regarding submitting double shares, it sometimes happens that the miner submits one or two shares and right after that tries to submit another one or two shares which then get rejected...

maby that is the cause of those rejects?

that is an issue I could fix with the miner.

[KillerByte]

any ideas on the buffer overflow message?

*** buffer overflow detected ***: memorypool terminated

[agnostik_one]

is this normal? i mean the duplicates... what does the first number actually mean?

hash generated - 7502 / 1968 / 3640808312
hash generated - 10725 / 1968 / 3757984692
hash generated - 13317 / 1968 / 2492638785
hash generated - 12666 / 1968 / 2015562052
hash generated - 12666 / 1968 / 2015562052
hash generated - 14294 / 1968 / 3536542128
hash generated - 14294 / 1968 / 3536542128
hash generated - 13666 / 1968 / 1088440815
hash generated - 13666 / 1968 / 1088440815
hash generated - 13666 / 1968 / 1088440815
hash generated - 12510 / 1968 / 3560445581

I have never seen that before... do you hash quickly?

are you submitting double shares?

hmm, probably around 10 hpm.
regarding submitting double shares, it sometimes happens that the miner submits one or two shares and right after that tries to submit another one or two shares which then get rejected...

[aorith]

Also, we have 25k shares without a block

there are a lot of solo miners i think

[KillerByte]

stats for 64 core and 64 threads

[STATS] 2013-12-25 19:23:21 | SHARES: 5 (100.0% | 5.4/h), VL: 5 (62.5%), RJ: 3 (37.5%), ST: 0 (0.0%)

I think you have to keep it running for some time to get proper stats, because there is some luck involved also... as far as I know.

Otherwise REJECTS are not good to have... it happens to me also.

yes, most likely because the server crashes. Thanks for the report though.

My computer at home has 0 rejects when the server works...

[pvp1982]

EDIT: 1000+ clients connecting. That is probobly part of why. I have the debugger running. ready for another error.

Good problem to have actually

[KillerByte]

is this normal? i mean the duplicates... what does the first number actually mean?

hash generated - 7502 / 1968 / 3640808312
hash generated - 10725 / 1968 / 3757984692
hash generated - 13317 / 1968 / 2492638785
hash generated - 12666 / 1968 / 2015562052
hash generated - 12666 / 1968 / 2015562052
hash generated - 14294 / 1968 / 3536542128
hash generated - 14294 / 1968 / 3536542128
hash generated - 13666 / 1968 / 1088440815
hash generated - 13666 / 1968 / 1088440815
hash generated - 13666 / 1968 / 1088440815
hash generated - 12510 / 1968 / 3560445581

I have never seen that before... do you hash quickly?

are you submitting double shares?

system:111
hash generated - 10273 / 1968 / 992674184
connecting to 162.243.216.74:1339
system:111
hash generated - 988 / 1968 / 732418756

this is what happens with my node

yeah, thats because it just crashed... again debugging....

EDIT: 1000+ clients connecting. That is probobly part of why. I have the debugger running. ready for another error.

EDIT: *** buffer overflow detected ***: memorypool terminated

I think I know the fix... but any ideas while I am at it?

[pvp1982]

system:111
hash generated - 10273 / 1968 / 992674184
connecting to 162.243.216.74:1339
system:111
hash generated - 988 / 1968 / 732418756

this is what happens with my node