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

WARNING: No miners available: disabled by Watchdog #2752

Open
vstrong-info opened this issue Apr 29, 2024 · 21 comments
Open

WARNING: No miners available: disabled by Watchdog #2752

vstrong-info opened this issue Apr 29, 2024 · 21 comments
Assignees

Comments

@vstrong-info
Copy link

vstrong-info commented Apr 29, 2024

I have a few HP DL360/380 servers that I would like to use for CPU mining. None of them have a GPU. CPU mining is enabled. All servers are running in Client mode and report to Server correctly.
RainbowMiner: RainbowMiner v4.9.2.4
OS: Clean Ubuntu 20.04 build.
Additional software: Tailscale client and Docker.
CPU mining is enabled.

What may be a problem?
Thank you.

@RoyCRoderickIII
Copy link

Just disable watchdog, it will disable miners for various reasons and not all bad.

@vstrong-info
Copy link
Author

Watchdog is already disabled:
image

@RoyCRoderickIII
Copy link

And your server has a wallet/pool configured to mine to?

@vstrong-info
Copy link
Author

Of course. Verus, Zephyr, herominers, viper and luck pool are enabled.

@RoyCRoderickIII
Copy link

Only thing i can think of off the top of my head is check the console page and see if they are not paused on start.

@vstrong-info
Copy link
Author

All good but still not working.
image
image

@RoyCRoderickIII
Copy link

You may just have to wait for watchdog timer to finish and then should be ok

@vstrong-info
Copy link
Author

Have been sitting like this for the last 24 hours. Never worked from the moment I installed it. :(

@RoyCRoderickIII
Copy link

Try running repair.sh and restart something ist right, ive only ever seen it do that if some dependencies or something was missing etc

@vstrong-info
Copy link
Author

Thank you. I tried running repair.sh but unfortunately it did not help. I did not install any GPU drivers as I do not have any GPUs installed in this system.

@RoyCRoderickIII
Copy link

You should not need to, did you make sure to enable cpu mining? During setup cpu mining is disabled be default. That is the only other reason i can think of cpus wouldn't mine

@vstrong-info
Copy link
Author

I did enable CPU mining during setup as that was the whole purpose of using those servers.
I take Ubuntu 20.04 is fully supported, right?

@RoyCRoderickIII
Copy link

Yes ofcourse you may need to create a debug file at the bottom of the menu on the gui, cause if sll you say is true something else is wrong

@vstrong-info
Copy link
Author

debug_2024-04-29.zip
Would you be able to check it out please? Thank you

@RoyCRoderickIII
Copy link

I am at work currently, once i get home can take a look

@RoyCRoderickIII
Copy link

okay I am by far an expert on RBM, but the only thing i see that catches my attention because i have never seen it before is here in the startup

"Detecting devices ..
1 CPU found
Initialize configuration ..
Re-installing libraries and binaries ..
Checking last shutdown ..
crashed
Read configuration ..
Starting sysinfo ..
ok"
i have never on any of my CPU only systems seen it try and reinstall libraries or binaries. if repair did not work, maybe try update.sh? something is definitely off . i know on the arm versions we have to run the install script directly, could give that a try

sudo pwsh ./Scripts/Install.ps1
thats from the RainbowMiner directory.

@vstrong-info
Copy link
Author

Thank you but unfortunately it did not help. :(
debug_2024-04-29-2.zip

@RainbowMiner RainbowMiner self-assigned this Apr 30, 2024
@RainbowMiner
Copy link
Owner

You seem to have made a mistake with your wallets inside the pools.config.txt - could you please send me your current pools.config.txt file to info@rbminer.net so that I can have a look?
At the moment, it looks like you have setup your ZEPH wallet address as a coin symbol. It should be "ZEPH" as coin symbol and "$ZEPH" as wallet address.

@whitindllc
Copy link

i see this as an issue
"ZEPHYR35YYc6wkhNBcMuxP6aWoQeV7SC8bBr7ytKmSRAc9eXcqWzC7xAqkKH1yz18CJUpuB2jsHwCh4fSQDdD8V1EZXfDzk22433u": "",
"ZEPHYR35YYc6wkhNBcMuxP6aWoQeV7SC8bBr7ytKmSRAc9eXcqWzC7xAqkKH1yz18CJUpuB2jsHwCh4fSQDdD8V1EZXfDzk22433u-Params": "",

should look like this

"PYI": "pyrin:blahblahblah",
"PYI-Params": "",
"ZEPH": "zepBlahblahblah",
"ZEPH-Params": "",  

i stopped there.... fix them and it should fix the issue

@vstrong-info
Copy link
Author

Thank you gentlemen, I will double check ZEPH address.
Strangely enough, ZEPH, worked well on RM client installed on Windows, before I stopped it.
image

@whitindllc
Copy link

whitindllc commented May 1, 2024

what payments do you have to ZEPHYR35YYc6wkhNBcMuxP6aWoQeV7SC8bBr7ytKmSRAc9eXcqWzC7xAqkKH1yz18CJUpuB2jsHwCh4fSQDdD8V1EZXfDzk22433u

when the pool cant pay these it just keeps them... so it doesnt care if enter the wrong address

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

4 participants