-
Notifications
You must be signed in to change notification settings - Fork 441
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
WARN: Messy shutdown... Killed. TREX: T-Rex instance wasn't validated #26
Comments
Possibly related to #20 Protocol dump:
Any ideas? |
Turns out I was missing one GPU, and it may have thrown the miner off ? Running a dump with the 11th GPU. [UPDATE] similar output... @trexminer any ideas? |
I found the issue. Leaving ticket open for @trexminer to notice & close issue. It is related to #20 (comment)
When I read all the tickets, this stuck in the back of my mind. It turns out my /etc/resolv.conf is blank after rebooting, and I figure when it hits the dev fee session it is unable to resolve the DNS and mine the dev session, thus the miner shuts down. Thanks! [Edit] Yeah, it actually is related because " ... the miner stops hashing after a dev fee session" just like #20 |
Yep, that's right. It shuts down if unable to fetch dev fee pools from our server. However, #20 is a separate issue not related to this one. |
Hi
I have a 10 GPU rig...
I get the following in my logs after submitting a bunch of successful shares:
LOGS IN NEXT REPLY
Any ideas?
Why is there no more detail? I tried --no-watchdog but doesn't fix it :-/
Thanks
The text was updated successfully, but these errors were encountered: