Pages:
Author

Topic: Smartcoin Linux mining administration. [MULTI-MACHINE SUPPORT NOW IN!] - page 11. (Read 105029 times)

member
Activity: 84
Merit: 10
cable risers is best option if your going to mine with more than 2 cards generaly .   few motherboards have a good spacing for 3 cards .    with 4 cards its going to need fans at 100% and extra fans blowing to them to try and keep them cool.    with risers i have 5 video cards on a rack with high temp of 75c i think.

Jen

Thanks Jen.  I have the MSI 890FXA-GD70, so I can easily get 3 cards, each with 1 full PCI bay between them.  However, when I run 4 cards on the motherboard, they have zero space between them.  I also need to run them in a case.  I know, tons of "issues".  Anyone, don't want to hijack Jon's thread, I'll start a new one asking for some ideas.
full member
Activity: 167
Merit: 100
I know this is personal preference, but I don't worry at all until over 90 degrees - I think cards will run along just fine in the 80-degree range.

I also run two of my cards in the 80-83 range and things seem fine. I've successfully modified overclock and fan speed settings using the command-line option of AMDOverdriveCtrl while GPUs were mining.

My 5830s will lock up and stop mining if their temps are over 85C for more than a minute or two.  I think the problem is that the cards are so close together they just cannot vent properly and/or the fans aren't spinning.  It's hard to tell.

Someone else on the forums has the same setup as I do and he's stated that his cards run in the mid-to-upper 70s.  I just can't figure out how.  I just dropped that rig back down to 3 cards and they run in the high 60s with no external fans.  But I add the 4th card in and two of them run in the high 80s (other two are in mid-70s) with an external fan blowing into the back of the cards.  Very puzzling.

My rig only has 3 cards - I'm still amazed at the variance of temperature that I get. My coolest card is in the 50's  under full load, while the hottest one is in the low 80's.  The thing that helped my cooling the best was prying the top of the cards apart about 1/2" (I used plastic 2-liter bottle caps as spacers). Though, mine is not it a case, so prying the tops of the cards apart a little was very easy

cable risers is best option if your going to mine with more than 2 cards generaly .   few motherboards have a good spacing for 3 cards .    with 4 cards its going to need fans at 100% and extra fans blowing to them to try and keep them cool.    with risers i have 5 video cards on a rack with high temp of 75c i think.


Jen
full member
Activity: 238
Merit: 100
I know this is personal preference, but I don't worry at all until over 90 degrees - I think cards will run along just fine in the 80-degree range.

I also run two of my cards in the 80-83 range and things seem fine. I've successfully modified overclock and fan speed settings using the command-line option of AMDOverdriveCtrl while GPUs were mining.

My 5830s will lock up and stop mining if their temps are over 85C for more than a minute or two.  I think the problem is that the cards are so close together they just cannot vent properly and/or the fans aren't spinning.  It's hard to tell.

Someone else on the forums has the same setup as I do and he's stated that his cards run in the mid-to-upper 70s.  I just can't figure out how.  I just dropped that rig back down to 3 cards and they run in the high 60s with no external fans.  But I add the 4th card in and two of them run in the high 80s (other two are in mid-70s) with an external fan blowing into the back of the cards.  Very puzzling.

My rig only has 3 cards - I'm still amazed at the variance of temperature that I get. My coolest card is in the 50's  under full load, while the hottest one is in the low 80's.  The thing that helped my cooling the best was prying the top of the cards apart about 1/2" (I used plastic 2-liter bottle caps as spacers). Though, mine is not it a case, so prying the tops of the cards apart a little was very easy
full member
Activity: 238
Merit: 100
For the failover to work does every miner on the profile need to stop working .. ?

For failover, any single instance in the profile needs to go down for the specified number of iterations, it doesn't have to be all of the instances going down.
member
Activity: 84
Merit: 10
I know this is personal preference, but I don't worry at all until over 90 degrees - I think cards will run along just fine in the 80-degree range.

I also run two of my cards in the 80-83 range and things seem fine. I've successfully modified overclock and fan speed settings using the command-line option of AMDOverdriveCtrl while GPUs were mining.

My 5830s will lock up and stop mining if their temps are over 85C for more than a minute or two.  I think the problem is that the cards are so close together they just cannot vent properly and/or the fans aren't spinning.  It's hard to tell.

Someone else on the forums has the same setup as I do and he's stated that his cards run in the mid-to-upper 70s.  I just can't figure out how.  I just dropped that rig back down to 3 cards and they run in the high 60s with no external fans.  But I add the 4th card in and two of them run in the high 80s (other two are in mid-70s) with an external fan blowing into the back of the cards.  Very puzzling.
full member
Activity: 167
Merit: 100
For the failover to work does every miner on the profile need to stop working .. ?

for failover to work primary pool has to go down then it goes to next one etc , from my understanding


Jen
newbie
Activity: 42
Merit: 0
For the failover to work does every miner on the profile need to stop working .. ?
full member
Activity: 238
Merit: 100
One of my miner updated to the lastest 495e but doesn't have lockup threshold settings in the settings. It keep rebooting (using the custom lockup.sh).
Is there anyway to backup profile/miners and reinstall the smartcoin clean?

They should have been added at r490..  Did you use the built-in update system? I ask, because simply running svn update can cause this behavior, as the patch system won't get executed (and why I advise to only use the built-in update mechanism)


Do you have the fialover threshold or failover rejection rate settings?

You can fix your database by running these from the terminal for the missing settings:
Code:
sqlite3 ~/.smartcoin/smartcoin.db "INSERT INTO settings (data,value,description) VALUES ('failover_threshold','10','Failover Threshold');"

sqlite3 ~/.smartcoin/smartcoin.db "INSERT INTO settings (data,value,description) VALUES ('failover_rejection','10','Failover on rejection % higher than');"

sqlite3 ~/.smartcoin/smartcoin.db "INSERT INTO settings (data,value,description) VALUES ('lockup_threshold','50','Lockup Threshold');"

full member
Activity: 238
Merit: 100
I just installed SmartCoin today and after playing with it, I have to say that it looks really great. You've really put a lot of polish on it.

Unfortunately I'm not having any luck getting my lockups detected. There's no relevant information in the SmartCoin logs, and the SmartCoin console just seems to stop running altogether. However, I can disconnect from screen and issue other commands so I know the machine isn't completely unresponsive. I can also run ./lockup.sh manually and it works fine.

What should I look at? Is there any troubleshooting information I can provide? Thanks!

A lot depends on what revision you are running.  There have been several fixes and improvements in the last few revisions.  If I were you, I would first switch to the experimental branch (4) Edit Settings->Development Branch to Follow.  Then run an update (11) Update Smartcoin). Then reboot smartcoin by first killing smartcoin (2) Kill smartcoin) then restarting it.  That will bring you to the most current revision (r495e at this time)


Ok, once we know you are current, lets review what a lockup is so that we are on the same page. A lockup almost always is caused by either loss of Internet, or stability problems from an over aggressive overclock.  A locked GPU in this case still reports aticonfig commands, but you will notice that the miner will just hang without ever changing (you can view the miners individually if you want by typing
Code:
screen -r miner
. Another thing to point out is that at default settings, it can take 5-10 minutes before the lockup is detected.   You can accelerate your testing by giong to Edi Settings, and edit the Lockup Threshold value to something lower (a value of 10 will take about a minute or two)

Let me know how things work out for you
newbie
Activity: 19
Merit: 0
I just installed SmartCoin today and after playing with it, I have to say that it looks really great. You've really put a lot of polish on it.

Unfortunately I'm not having any luck getting my lockups detected. There's no relevant information in the SmartCoin logs, and the SmartCoin console just seems to stop running altogether. However, I can disconnect from screen and issue other commands so I know the machine isn't completely unresponsive. I can also run ./lockup.sh manually and it works fine.

What should I look at? Is there any troubleshooting information I can provide? Thanks!
full member
Activity: 238
Merit: 100
Update r495e now available
- Failed sql queries will now wait 1/100 of a second between retries
- --reload command line argument addition. 'smartcoin --reload' run from the commandline will now reload all the miner instances. The underlying reload structure will also be used soon to reload miners whenever configurations are changed from the control screen.  Another way to use this from your own script is the create a file /tmp/smartcoin.reload with a message contained within to display. For example:
Code:
echo "Reloading because I have the power to do so!" > /tmp/smartcoin.reload
- Started refactoring some code to make reinitialization of global variables possible (as many of these values are grabbed live from the database as needed.  Once this refactor is complete,  these values will be read in only once from the database unless I choose to reinitialize them at some point in the code.

Basically just some framework changes to facilitate future features and upcoming optimizations
full member
Activity: 238
Merit: 100
Update r491e now available:
- Removed injected delay in the status loop - this pretty much doubles the refresh rate.  Future optimizations will probably increase the refresh rate even more.


If everything looks stable for the next day or so, I'll trip the stable update flag
full member
Activity: 238
Merit: 100
Update r490e now available:
- Fixed a small bug in the lockup.sh custom script execution
- There are 3 new settings that can be fine-tuned:
* Lockup threshold (default is 50 iterations). The smaller the number, the faster the lockup detection will trip.
* Failover threshold (default is 10 iterations). The smaller the number, the faster the failover detection will trip.
* Failover Rejection (default is 10%) Increments the failover detection counter each iteration if the rejection percentage is above this number (INTEGER NUMBER ONLY!)

NOTE:  A restart of smartcoin is required after changing these before the new values will take effect.
full member
Activity: 238
Merit: 100
I was getting stale shares from 9%-38% with SmartCoin w/ my 4 rigs/workers - now back hooked up to pool straight, I'm at 0.10% ...is this a known side-effect of running SmartCoin? I don't know how much extra is going on behind the scenes with processes, etc. I do know how much I dig SmartCoin though - will keep updating.

This isn't a known side effect of smartcoin.  I run 3 instances per card normally with less than 0.05% rejected shares.  Its normal for rejection percent to start a little higher and then settle out sometimes though.  Can you give me some information on how you have things set up?
How many instances are you running per card? And to how many different pools? Which miner? etc.

I kept things running for over 8 hours with only 1 instance per card to 1 pool, phoenix - and was getting those high numbers w/ 3, 2-card rigs and 1, 1-card rig. Open to suggestions for multi-instance/pool..can anyone elaborate on how stales form? Could it be from other (home) network load/usage, computer system processes, pool, other?

Can you compare the launch string that you use manually (when you got decent rejection rates) to the launch string defined in Configure Miners->Edit->Phoenix?
Perhaps you need to edit the launch string so that you use the same phoenix options that you normally use (the default options may not be playing nice on your setup)
jl
newbie
Activity: 10
Merit: 0
I was getting stale shares from 9%-38% with SmartCoin w/ my 4 rigs/workers - now back hooked up to pool straight, I'm at 0.10% ...is this a known side-effect of running SmartCoin? I don't know how much extra is going on behind the scenes with processes, etc. I do know how much I dig SmartCoin though - will keep updating.

This isn't a known side effect of smartcoin.  I run 3 instances per card normally with less than 0.05% rejected shares.  Its normal for rejection percent to start a little higher and then settle out sometimes though.  Can you give me some information on how you have things set up?
How many instances are you running per card? And to how many different pools? Which miner? etc.

I kept things running for over 8 hours with only 1 instance per card to 1 pool, phoenix - and was getting those high numbers w/ 3, 2-card rigs and 1, 1-card rig. Open to suggestions for multi-instance/pool..can anyone elaborate on how stales form? Could it be from other (home) network load/usage, computer system processes, pool, other?
full member
Activity: 167
Merit: 100
smartcoin is very much fun , just turned up aggression to 12

now things are looking much better


Jen
full member
Activity: 238
Merit: 100
I was getting stale shares from 9%-38% with SmartCoin w/ my 4 rigs/workers - now back hooked up to pool straight, I'm at 0.10% ...is this a known side-effect of running SmartCoin? I don't know how much extra is going on behind the scenes with processes, etc. I do know how much I dig SmartCoin though - will keep updating.

This isn't a known side effect of smartcoin.  I run 3 instances per card normally with less than 0.05% rejected shares.  Its normal for rejection percent to start a little higher and then settle out sometimes though.  Can you give me some information on how you have things set up?
How many instances are you running per card? And to how many different pools? Which miner? etc.
jl
newbie
Activity: 10
Merit: 0
I was getting stale shares from 9%-38% with SmartCoin w/ my 4 rigs/workers - now back hooked up to pool straight, I'm at 0.10% ...is this a known side-effect of running SmartCoin? I don't know how much extra is going on behind the scenes with processes, etc. I do know how much I dig SmartCoin though - will keep updating.
member
Activity: 79
Merit: 10
Quote
I also run two of my cards in the 80-83 range and things seem fine. I've successfully modified overclock and fan speed settings using the command-line option of AMDOverdriveCtrl while GPUs were mining. Whatever you do for temp functions, I think you should use hook scripts that are user customizable. At least those are my thoughts...
Yeah, I'm thinking along the same lines, as there is just an incredible amount of variance to deal with, and each user will probably have a unique set of needs.

Also, the hook scripts are going to get a nice overhaul soon, such as having parameters passed into them when they are launched
(For instance, passing the machine number as an argument to the lockup.sh script so you can have different cases for different machines when multi-machine support is in..  Or having the GPU temperatures passed in to a temperature.sh script to make things easier)


Yeah that would be awesome.

Btw, I've noticed a trailing "t" on the header line (example: "-----------------t"). Not sure if this is my terminal version or a side effect of turning of line wrap. Just thought I'd mention it.
brand new
Activity: 0
Merit: 0
@jondecker76

Problem fixed!! Awesome!
Pages:
Jump to: