pretty sure the pool is down right now

problem miner stop running on all 3  centos 6.4 servers

Quotesystem:111
submit: 09608ec60edcc1a5a4a026ec55bba36d8d4f559bd69fc94450fe4a5dd80f18be
hash generated - 4074 / 1968 / 3352696207
Segmentation fault (core dumped)

how to fix ?

i take it main_poolminer is the actual miner? I'm looking to start fiddling. Which line has the memory limit?

Quote from: chida on December 25, 2013, 09:12:13 PM
if i use different mining pc is necessary different pooluser? i prefer only one, but you add? is problem different ip?

no, not at all.

if i use different mining pc is necessary different pooluser? i prefer only one, but you add? is problem different ip?

Quote from: KillerByte on December 25, 2013, 08:56:52 PM

Quote from: duck on December 25, 2013, 08:53:46 PM
I have a question. After being mining almost a day during the uptime I checked my stats and see that I had 0,03 MMC confirmed and 0,07 MMC unconfirmed.

Are those stats correct, if it is I don't think that worth the effort :/

Mining with 40 Cores in 6 computers...

only 0.03, 0.07?

what is your normal hashrate for one of those machines when you mine solo?

I have 4 8core machines at 1hpm and 2 4 core machines at .5 hpm each one more or less.

Quote from: KillerByte on December 25, 2013, 08:45:35 PM

Quote from: marlowbg on December 25, 2013, 08:42:28 PM
what is the OS (linux flavour) used?

arch linux, updated

I am going to focus on getting those payouts going... get your wallets ready.

Waiting.. MAQ5SK33KVcDrAmWHHEAGJ35uTv8wkcWJy

Quote from: duck on December 25, 2013, 08:53:46 PM
I have a question. After being mining almost a day during the uptime I checked my stats and see that I had 0,03 MMC confirmed and 0,07 MMC unconfirmed.

Are those stats correct, if it is I don't think that worth the effort :/

Mining with 40 Cores in 6 computers...

Dude, I have also issue with the rate, I have more cores. With this difficulty and comp power we should have definitely more coins

Quote from: duck on December 25, 2013, 08:53:46 PM
I have a question. After being mining almost a day during the uptime I checked my stats and see that I had 0,03 MMC confirmed and 0,07 MMC unconfirmed.

Are those stats correct, if it is I don't think that worth the effort :/

Mining with 40 Cores in 6 computers...

only 0.03, 0.07?

what is your normal hashrate for one of those machines when you mine solo?

I have a question. After being mining almost a day during the uptime I checked my stats and see that I had 0,03 MMC confirmed and 0,07 MMC unconfirmed.

Are those stats correct, if it is I don't think that worth the effort :/

Mining with 40 Cores in 6 computers...

The crash always happens on net.cpp, line 980 on the standard memorycoind...

bug in memorycoind?

Quote from: I_M on December 25, 2013, 08:48:20 PM
From the error, at a google-glance, are you running out of memory or temp space?

nope, the temp memory isnt even used and there is plenty enough RAM...

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

Quote from: KillerByte on December 25, 2013, 08:36:04 PM
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.

One thing you can check is the 'SystemMaxUse' in '/etc/system/systemd-journald.conf' to see how much memory journald has allocated.

(taken from https://bbs.archlinux.org/viewtopic.php?id=150704)

From the error, at a google-glance, are you running out of memory or temp space?

Quote from: marlowbg on December 25, 2013, 08:42:28 PM
what is the OS (linux flavour) used?

arch linux, updated

I am going to focus on getting those payouts going... get your wallets ready.