Command terminates with "Killed"

[vertex]

So, running poclbm on Ubuntu Sever 11.4, and everything runs fine, but like an hour in it'll terminate the process with the line "Killed".  Anyone else encounter this?

[1713577429]

1713577429

[1713577429]

1713577429

[1713577429]

1713577429

[lowlevel]

Quit mining, I'm trying to download porn! 

[haydent]

So, running poclbm on Ubuntu Sever 11.4, and everything runs fine, but like an hour in it'll terminate the process with the line "Killed".  Anyone else encounter this?

is it your own box or a server ?


theres is a command to get the exit code which can give you more info

sometimes it has to do with resources running out or in my case (rtorrent on vps) it was banned and killed by a higher up level cron job

[vertex]

So, running poclbm on Ubuntu Sever 11.4, and everything runs fine, but like an hour in it'll terminate the process with the line "Killed".  Anyone else encounter this?

is it your own box or a server ?


theres is a command to get the exit code which can give you more info

sometimes it has to do with resources running out or in my case (rtorrent on vps) it was banned and killed by a higher up level cron job

My own box.... hmmm, I hadn't thought of that, but it is the only thing the box is doing, IDK what could be eating resources

[infofront]

I'm encountering this same problem using phoenix miner on linuxcoin. I have a machine running 4 x 5850, and each one will terminate after submitting around 7000-8000 shares, with the word "Killed" at the end of the command line. I'm still trying to find some sort of solution.

[Stalin-chan]

Are you running linux?

Can you show the exact error?

[infofront]

Yes, I'm running linuxcoin. There's no error message to speak of. The process just stops abruptly, with the word "Killed" at the end of the command line. I just restart the process again, and it gets killed again after another 6000-8000 shares are submitted.

[infofront]

Any ideas? I'd be grateful

[infofront]

Just an update, in case anyone else has the same problem. I switched mining pools from eclipse to btcguild and I no longer have this problem.