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.

Sign up for GitHub

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

Jump to bottom

No Miners Found! #204

Closed
MaynardMiner opened this issue Oct 31, 2019 · 2 comments
Closed

No Miners Found! #204

MaynardMiner opened this issue Oct 31, 2019 · 2 comments
Assignees
@MaynardMiner
Labels
single-user bug only 1 report of issue, can't reproduce.

Comments

@MaynardMiner
Copy link
Owner

I have a long time regular user who continues to experience this on a once-and-awhile basis. Going through the debug files they sent me, I noticed there was no bestminers.txt. The only time bestminers.txt is remove from build\txt, is at startup, which leads me to believe that his SWARM is restarting, and when it does- At that point it doesn't load miners (generate bestminers.txt debug file).

I have tried to reproduce with many different methods, but have been unable to do so.

I believe it may be a miner that is soft-crashing, and using up resources. I have seen miners that become zombies, and cause havoc as a result because it begins a backup of all software that ques the gpu drivers, but I am posting here in case anyone else experiences, so I can gather more data.

Normally SWARM should restart after enough times "No Miners Found!" is produced.

image
@MaynardMiner MaynardMiner added the single-user bug only 1 report of issue, can't reproduce. label Oct 31, 2019
@MaynardMiner MaynardMiner self-assigned this Oct 31, 2019
@MaynardMiner
Copy link
Owner Author

User supplied me with his logs, found error:

: Exception calling "Add" with "2" argument(s): "Item has already been added. Key in dictionary: 'Switch_Threshold'  Key being added: 'Switch_Threshold'"
At /hive/miners/custom/SWARM.2.7.8.linux/startup.ps1:40 char:21
+                     $parsed.Add($Com, "new")
+                     ~~~~~~~~~~~~~~~~~~~~~~~~
                    $parsed.Add($Com, "new")

Which means that his arguments had -Switch_threshold twice.

Solution is to output a warning that their is double arguments to the user.

MaynardMiner pushed a commit that referenced this issue Oct 31, 2019
@Embstj
#204
2568cd3 
Output warning that there is two of the same arguments in argument list, and only select 1 of them.
@MaynardMiner
Copy link
Owner Author

It was found this issue was miner related.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@MaynardMiner MaynardMiner

Labels
single-user bug only 1 report of issue, can't reproduce.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@MaynardMiner