Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

proxy job timeout loop #3

Open
ludovicbret opened this issue Mar 26, 2016 · 6 comments
Open

proxy job timeout loop #3

ludovicbret opened this issue Mar 26, 2016 · 6 comments

Comments

@ludovicbret
Copy link

Hi !

Just reporting an issue that appears 2 days ago. My proxy is running for quite some times without any troubles until that happened :

WARNING proxy # Job timeout. Proxy is waiting for an updated job. Please restart proxy!

It loops over and over again without any clear reasons and obviously stopped my rigs from minning.
It happens twice a day now.

@benjaminpratt
Copy link

Ended up finding out that this was related to just nanopool. It's not happening on any other. Hope this helps.

@thiagolimaaurea
Copy link

I'm getting this same problem and i'm not using nanopool

@perpeer
Copy link

perpeer commented Jul 20, 2017

@thiagolimaaurea I'm getting this problem from ubiqpool.io. This is not about nanopool.

@hung135
Copy link

hung135 commented Aug 12, 2017

I am getting same problem a ubiqpool.io and dbix.pool.sexy. I don't get this error when my miners connect directly to any of the pools.

@teotikalki
Copy link

teotikalki commented Nov 20, 2017

I set up eth-proxy yesterday night on dwarfpool and got:

Job timeout. Proxy is waiting for an updated job. Please restart proxy!

about 14 hours later.

I am unsure if it is related, but the proxy had switched to FAILOVER_POOL_1 for some time. Restarting it in response to the error caused it to reconnect to the MAIN_POOL.

@maxlam79
Copy link

I've encountered this issue with dwarfpool today, with the same message (I'm running this on Ubuntu Linux)

"Proxy is waiting for an updated job. Please restart proxy!"

I wonder if it is possible to have a command line option to restart the proxy every time when it encounters this message? instead of doing it manually?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants