Great post by jh00

windows 7 64bit binary?

Quote from: marlowbg on December 26, 2013, 06:16:05 am

Why threads 12 is invalid? There are many cpus out there with 12 cores, please fix this...

For now, just run one instance with 8 and one with 4.

this is what I also plan to do I hope a fix will come as well.

hash generated - 2805 / 1968 / 2228977017
submit: 036d3929486b4ba07dbc68f6a172a5456216c3b82cc5e87d83a589d68c8e8113
hash generated - 13053 / 1968 / 3171305550


I think there is still some pools issue - with Submits,

the response from the server is missing after "submit" message

EDIT: down again

system:111
connecting to 162.243.216.74:1339
system:111
connecting to 162.243.216.74:1339

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.

any ideas on the buffer overflow message?

Quote

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

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

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