Bitcoin Forum

Autominer 0.3.2.6 - New Interface Baby!

I decided to redo the thread from scratch to better explain Autominer. I felt that the old thread rambled a bit and didn't explain enough, so this one should be better designed to take care of the users' needs.

About Donate Mode

A few people were saying they'd like to donate but have no BTC up front, so if you want to, just edit common.lib (on v0.3.2.3 or above) and put the following line at the bottom:

donateMode=1

It will automatically give me 1 out of every 200 mining cycles (0.5% of your mining time). I will implement an option later so you can decide how much to donate.

This option is off by default, it's purely optional, and thanks if anyone decides to use it.

Download Autominer v0.3.2.6 (http://dl.dropbox.com/u/23460903/Autominer-0.3.2.6.tar.gz)

http://dl.dropbox.com/u/23460903/amm-0.3.2.3.png


What is Autominer?
Autominer is a bash script (technically, a set of bash scripts) written to automate the process of mining on a Linux rig. After a relatively short configuration time, you can just type a single command to start mining on all of your GPUs, in screen sessions for remote monitoring, with a temperature monitor and automatic pool monitoring and swapping in the case of downtime. Interested? Good.

And some history...

v0.3.2.6
- Bug fix of the checkphoenix.sh script (it was connecting to the wrong pool)
- Bug fix in screen settings

v0.3.2.5
- Added a 'countTarget' variable to change the frequency of 'successfully mining' updates
- Added a checkphoenix.sh script for diagnostic purposes
- Added better output to configure.sh when no workers are chosen
- Fixed a bug that was causing configure.sh to ask about donateMode for each GPU

v0.3.2.4
- Fixed a bug in configure.sh where it was writing Worksize variable to queuesize.
- Cleaned up configure.sh

v0.3.2.3
- Fixed a bug with the 'kill process' function.
- Cleaned up some text outputs.
- Added getting the CHANGELOG when using an outdated version.
- Fixed the loop function in the main program.
- Added 'donation mode' (optional, of course). To donate 0.5% of your mining to aid Autominer
development, just add 'donateMode=1' to common.lib. This will cause one in every two hundred cycles
to be donated.

v0.3.2.2
- Added support for PLATFORM in Phoenix.

v0.3.2.1
- Fixed a bug which caused pool switching not to work on machines with both monitoring modes enabled
if the downtime was picked up by GPU load first.

v0.3.2
- Added support for hashrate-based pool downtime detection in addition to GPU-load based, works even
if overdrive won't report GPU load (it's an issue for some people with risers) - needs XML RPC enabled
- Fixed a bug with downloading 'LATEST' file

v0.3.1
- Added experimental support for thejfk's getRate.py hack to display hashrate in miner window
- Rewrote the entire interface to use a single screen window, takes some getting used to

v0.3
- Added defaults files in order to avoid overriding a user's config upon update
- Added warning and disabled pool monitoring if GPU load can't be found (previously caused error spew)
- Added a stopmining.sh script which should look through screens and kill all Autominer screens
- Added detection for obsolete versions
- Added an experimental configuration script
- Removed version numbers from several script headers
- Moved opening the temps window to the main script
- Changed the temps window so that height corresponds to number of GPUs

v0.2
- Added status update to monitor where cards are mining and if cards are mining
- Added timestamps to output in main window

v0.1b
- Added support for phoenix failures, added workers

v0.1
- Got it working


What does Autominer need?
Autominer needs a relatively standard set of Linux tools, plus a mining program, those are:
tar - To extract the archive in the first place
wget - To check for updates to the package
screen - For monitoring sessions
xterm - To load the terminal windows themselves
phoenix-miner - To mine delicious coins!

To get this short list of tools (other than Phoenix, that's here in the forum) in the main distros is easy, fire up a command line and type:

Ubuntu Natty: sudo apt-get install screen tar wget xterm
Debian: sudo apt-get install screen tar wget xterm
Arch Linux: pacman -S screen tar wget xterm
Gentoo: emerge screen tar wget xterm

In addition, you need to be running X11 in order to take advantage of ATI Overdrive & multiple Xterm windows, and you need a few minutes to go through configuration the first time you run it.


So, how do I install it?

Well, download the tar.gz file at the top, then go to your favourite command line and navigate to where you put it. Do:

tar xvfz Autominer-x.x.tar.gz (where x.x is the version number)
cd Autominer
./configure.sh

Follow the instructions in the configuration script, assuming it works it will spit out two files called cards.lib and common.lib, with all the information you put into the script contained in them.


I'm running Autominer, how do I update it?

If your existing version is 0.3 or above, follow these instructions. If you're on 0.1, 0.1b or 0.2, you'll need to remove your existing Autominer & follow the install instructions as above. This is because 0.3 changed the file structure and the variable names, and is fairly incompatible with lte v0.2 config files.

Assuming you're running v0.3 already, simply download the .tar.gz and extract the files into your Autominer directory. This will not overwrite cards.lib or common.lib, as I have modified the file structure to preserve these files which contain your settings.


How do I *RUN* this beast?

First of all kill any miners you have open, then go to the Autominer directory and run ./startmining.sh /path/to/Autominer

Controls for the window:
F1-F6 = Windows 0-5
F7 = Previous window
F8 = Next window
Ctrl-a then a number = That number window
Ctrl-a then d = Detach screen (keeps miner running)


You have MH/S in your 'amm' window... how do I get that?

This technique relies upon a patch to Phoenix developed by thejfk, but it's relatively easy.

1. Open up a command line
2. cd to your phoenix directory
3. wget http://robertlacroix.com/files/phoenix-xmlrpc.diff
4. patch -p0 < phoenix-xmlrpc.diff
5. Send thejfk a tip: 1EhQ1dbeZnxs7wZKngegsHLheAjUK37k7m
6. cd to your Autominer directory
7. Edit common.lib, at the bottom write on a new line:
xmlRPCEnabled=1;
8. Start up your miner, the rest should happen automatically


And how do I monitor it over ssh?

If you want to open over ssh, do DISPLAY=:0 ./startmining.sh /path/to/Autominer

Connect to the screen using screen -x amm -p 0


So, what happened to the file structure?

Previously, whenever you updated Autominer, it came with a new cards.lib and common.lib, this meant you had to re-configure everything every time. Now, I've created files called cards.defaults.lib and common.defaults.lib.

These files allow me to define new variables without overwriting the variables you've saved in your configuration scripts. Obviously, you shouldn't edit the defaults files (they'll be overwritten when you update) but if you want to change something in there, simply copy the variable into cards.lib or common.lib and change it there.

Variables in cards.lib and common.lib OVERRIDE those in cards.defaults.lib and common.defaults.lib. The only time the defaults will be used is if something isn't defined in YOUR config settings.


Can I still manually modify the .lib files?

Sure can. Just copy cards.sample.lib to cards.lib and common.sample.lib to common.lib and modify. Don't edit the defaults, they will be overwritten when you update again.


Common Problems & Troubleshooting

Computer clearly mining but autominer won't connect to the display - Often caused by starting an identifier name with a number. Check your identifier names start with a letter.

Nice work, I made some similar scripts myself but never incorporated pool detection/switching.

Start the miners each in their own GNU Screen sessions and set this to run at start up in your DE of choice (and set automatic log in of course) and bam, this script is now ideal for headless mining. The screen sessions will allow users to view the miners though SSH. I like to start an extra session as well just so i can run aticonfig if i need to check my temps/adjust fan speed/what have you.

I've been working on a way to detect locked up miners, I'll let you know if I find anything interesting.

I'm just detecting GPU load via aticonfig --adapter=X --odgc and killing GPUs which aren't under load.

Also, yeah this works for headless I guess, screens are named $identifier-MINER so if you set an identifier to 'Radeon5850' the screen would be called 'Radeon5850-MINER'. Temp screen is called 'temps'.

Oops, I some how missed that you used screen already. Script skimming comprehension fail. Its early (for me at least), ignore my blather.

I'm beating my head against the wall for not thinking about checking for bum miners with gpu load. I was using wget and grep to check deepbit's api for statuses, which is fine i guess, but not good for solo miners or pools without an api like db's.

I use tmux for my miner(s), as:
- it can be split horizontally/vertically, so I can have a number of miners in one "window"
- its launch can be scripted, so you can have one .sh script launch a number of miners each with their own details *and* detach the whole
- it can be scripted and the buffer saved somewhere, to be later handled via other GNU tools

For example: on screen 0, window 1, pane 0 I have a miner; on pane 1 another.



I also modify the miners to report found/rejected blocks on STDERR, then munge it with some Perl and display the graph on a site, but having only one graphics card I'm not sure how useful the thing is to you guys ;)

Yeah I'm just doing a check for GPU load below 90%, then sleeping 15 sec to make sure it's not an anomoly, then killing the miner and changing to backup pool if it's not fixed.

Also, version 0.2 should be up soon, with regular status reports to the main window so that you can see everything is mining, removing the annoying 'All seems fine' message every 2 minutes, and timestamps in the main window.

Great! Thank you.
I'm also using a much more "simpler" bash script, nice to have a backup server now.
This also helps me to learn more about script writing, so thumbs up for you. :)

Glad to be helping people out, I'm uploading v0.2 right now and adding it to first post.

Cool script :)

Am I the only one that uses a single screen session for all my miners? :-/

I do on ssh, this loads the miners into screen sessions so you can load them up via SSH on $identifier[0]-miner, $identifier[1]-miner etc. You can do the same with temperatures, screen is called temps.

So just ssh in and hit:

screen -x temps

OR

screen -x Radeon5850-1-miner (assuming one of your identifiers is Radeon5850-1).

No like, i have one screen session called miners, and then i have windows in each. Like window 1 is for GPU 1, window 2 for GPU 2, and window 0 is for my monitoring script. I just reattach the screen session and then hit ctrl-a 1 to see the miner for gpu 1, ctrl-a 2 for the second, etc. That way i can quickly check all miners without having to attach and detach sessions all the time.

Oh OK, I do this instead on my laptop to monitor everything:

http://img695.imageshack.us/img695/7922/itermscreensnapz006.th.png (http://imageshack.us/photo/my-images/695/itermscreensnapz006.png/)

+1 for using E17 for your miner's desktop. I'm doing the same thing ;).

maybe a dumb question, but is xfce (xubuntu) going to work for this x11, or are they different?

Also, I've been using amdoverdrive for temp/OCing, would I need to change anything to switch to the commandline OCing and temp control?

XFCE is X11 based, as are (I think) all Linux desktop environments.

If AMDOverdriveCtrl is working, you shouldn't need to change anything.

If you're unsure, go to command line and type 'aticonfig --adapter=all --odgc'.

It might come back telling you to enable Overdrive, in which case type 'aticonfig --adapter=all --od-enable'. Then this will work fine.

Tested working in Debian Squeeze and Ubuntu Natty.

For anyone having trouble with screen terminating repeatedly, add this to your ~/.screenrc

Plus one of the following:

For 64-bit SDK 2.4:

For 32-bit SDK 2.4:

For 64-bit SDK 2.1:

For 32-bit SDK 2.1:


Reikoku, is 4 GPUs just where you decided to stop or is there some limitation in the script that make more a problem?

You can go past 4 GPUs, I think I removed the checker for >4. I just didn't add more than 4 to cards.lib because 4 is the most I run in one machine.

You will need to set the geometry for the 5th Xterm though in cards.lib otherwise it'll spawn over the 4th one. You'll also need to add 3 rows to temps window in startmining.sh.

Also, thanks for testing.

I got it working, but I changed it to start from device 1 (not 0), so, 1,2,3,4 for all the numbers in the card file that were under 0,1,2,3 sections.
also, not sure how screen works, but closing seems to be an issue, only ghosts the programs.
After the necessary edits, this looks like a great program.

You mean closing the main loop? It doesn't kill all the screens, I will have to write a closing script at some point, for now assuming you run no other screens, 'killall screen' will give you a clean close.

I had to make some changes to your files like I said before:
This is great for linux, after you get the system set up because for me the pools go down or if a miner stalls, this fixes it. . .

here is my working version of the files (replaced/created the following files with text editor in autominer folder):
cards.lib: http://pastebin.com/AD6ugg4x
common.lib: http://pastebin.com/ZSNb2KzZ
otherwise using the files you have listed, works great!

You must really dislike zero indexing. :P

Nice clean scripting.  A lot to learn from you!

Will this work with 7 cards?
I didn't check the code too carefully, but it just increments everything to scale up, then I just add more entries in the cards file, right?

Yes it will work with 7 cards, you will have to edit cards.lib and specify geometry for phoenix windows for cards 5-7 however, or they'll spawn on top of existing ones.

Basically take these:

# You probably don't need to touch these
xtermGeometry[4]="61x10+730+11";
xtermTitle[4]="Mining on Card 0";

And modify to:

# You probably don't need to touch these
xtermGeometry[4]="61x10+XPOSITION+YPOSITION";
xtermTitle[4]="Mining on Card CARD NUMBER";


Thanks.

Version 0.2.1 should be up soon with a few changes. Trying to find a way for you guys to download new versions without having to rewrite your configs over and over. :P

Version 0.3(!!) is up with auto-configuration script.

Easier than ever.

Will this work with poclbm?

Only works with phoenix, but phoenix supports poclbm mining kernel so if you want to try it, install phoenix & just select poclbm kernel.

Up to 0.3.1 now with screen-based interface, finally starting to look something like the product I wanted!

EDIT: Nearly instantly released 0.3.2 as well, has hashrate-based pool monitoring.

0.3.2.1 is up, I found a pretty major bug for people with GPU Based & XML-RPC based monitoring enabled (tl;dr: pool switching didn't work).

Get this update to fix it.

Was working great for me until 0.3.2.1 update today.

It's not detecting my hashrate and killing and restarting the miners over and over again. I can verify in the miner windows that they are working correctly until killed by the script. Any help would be greatly appreciated. I have really enjoyed using this.

Log:
[28-Jun-2011 15:23.42] Checking for updated versions...
[28-Jun-2011 15:23.42] You are running the latest version of Autominer already.
[28-Jun-2011 15:23.42] GPU-load pool monitoring for card0 could not be enabled. ATI Overdrive is not loaded.
[28-Jun-2011 15:23.42] GPU-load pool monitoring for card1 could not be enabled. ATI Overdrive is not loaded.
[28-Jun-2011 15:23.42] Hashrate-based pool monitoring for card0 enabled.
[28-Jun-2011 15:23.42] Hashrate-based pool monitoring for card1 enabled.
[28-Jun-2011 15:23.42] Firing up the miner on card card0 using pool 1!
[28-Jun-2011 15:23.42] Connecting to XXX@uswest.btcguild.com:8332...
[28-Jun-2011 15:23.42] Firing up the miner on card card1 using pool 1!
[28-Jun-2011 15:23.42] Connecting to XXX@uswest.btcguild.com:8332...
[28-Jun-2011 15:23.42] Rechecking status...
[28-Jun-2011 15:24.03] card0 is not hashing, waiting 15 seconds and deciding whether to change pools.
[28-Jun-2011 15:24.18] The hash rate after 15 seconds is
[28-Jun-2011 15:24.18] Still not hashing, pool or net has dropped...
[28-Jun-2011 15:24.18] Killing PID: 5153
[28-Jun-2011 15:24.18] Trying to kill 5153: 0 (should be 0)
[28-Jun-2011 15:24.18] card1 is not hashing, waiting 15 seconds and deciding whether to change pools.
[28-Jun-2011 15:24.33] The hash rate after 15 seconds is
[28-Jun-2011 15:24.33] Still not hashing, pool or net has dropped...
[28-Jun-2011 15:24.33] Killing PID: 5164
[28-Jun-2011 15:24.33] Trying to kill 5164: 0 (should be 0)
[28-Jun-2011 15:24.38] Card card0 is not currently mining.
[28-Jun-2011 15:24.38] Card card1 is not currently mining.
[28-Jun-2011 15:24.38] Rechecking status...

Was 0.3.2 monitoring your hashes correctly?

It could be that for some reason it thinks hashrate monitoring is working, but it's not.

Actually went from 0.3 to 0.3.2.1 so never tried it...

Definitely seems to not be detecting correctly - I went back to the 0.3 I made a backup of and it runs fine, yet still with the  "ATI Overdrive is not loaded" error line. That error started showing up after I upgraded the ATI drivers to 11.6 yesterday and I haven't been able to get rid of it. (ran the -od -enable commands, etc. maybe there is more I need to do)

Anyways figured with the new version today with hashrate monitoring this wouldn't matter, but having the issue as I described above. Thanks

OD not enabled issue is when aticonfig --adapter=all --odgc doesn't work, so it can't work out your GPU load.

When you fire up 0.3.2.1 does it say 'Hashrate-based pool monitoring is enabled', or not?

If so, can you give me the contents of your common.defaults.lib and common.lib (blank out passwords if you use them)?

Yes from the log above:

[28-Jun-2011 15:23.42] Hashrate-based pool monitoring for card0 enabled.
[28-Jun-2011 15:23.42] Hashrate-based pool monitoring for card1 enabled.

I'll get you copies of those files in a bit. Thanks for the help!

No problem, it looks like you've enabled xmlRPC monitoring somewhere, or I've fucked up the code somewhere and done that.

Edit: Just tried setting my xmlRPCEnabled to 0 and it didn't enable it, so it looks like somehow you've set it in common.lib OR my tarfile includes common.lib... checking the tarfile.

Nope, it's not in there. Did you try to enable hashrate monitoring? If so, is your Phoenix kernel patched?

Yeah updated my phoenix-1.50 per your directions and added the xmlRPCEnabled=1; line to common.lib.
If I set this back to =0 the miners stay working, although they won't switch to the backup pool under this setup of course.

OK, did you patch your Phoenix binary or not?

Try starting Phoenix manually like this:

./phoenix.py -v -x 2500 -u http://username:password@server:port -k phatk DEVICE=0

If that loads without an issue, go to Autominer directory and do:

./getrates.sh

And tell me what comes out of that.

It looks like either your Phoenix didn't patch properly, or your getrates.sh for some reason isn't pulling the right rates.

Yes phoenix is patched. Directly launching it works fine (as in the command you provided).

running ./getrates.sh however, produces the following:

./getrates.sh: ./getRate.py: /usr/bin/python2: bad interpreter: No such file or directory
./getrates.sh: line 42: /1000: syntax error: operand expected (error token is "/1000")

OK, do ls -l /usr/bin/python*

If that doesn't work try sudo ls -l /usr/bin/python*

(Basically, getRate script can't find Python, so we need to set up a symbolic link to it).

I get:

lrwxrwxrwx 1 root root       9 2011-06-12 01:27 /usr/bin/python -> python2.7
-rwxr-xr-x 1 root root 2375356 2011-04-11 12:14 /usr/bin/python2.7
-rwxr-xr-x 1 root root    1652 2011-04-11 12:07 /usr/bin/python2.7-config
lrwxrwxrwx 1 root root      16 2011-06-12 01:41 /usr/bin/python-config -> python2.7-config

OK, easy enough, just do (either sudo or as root):

ln -s /usr/bin/python2.7 /usr/bin/python2

Then retry autominer.

I was having the same issue with the quick timeout/die and this symbolic link fixed it just right! Thanks!

No problem, enjoy!

I have a linux pc whit 3 card, i used phoenix(1 for each card) miner and sometimes phoenix crash(only a proccess),.
whit this script "auto start"  a phoenix proccess if proccess stop?

thx  ;)

This depends, as there are two types of Phoenix crash.

In one it reduces to 0 khash and your card stops doing anything - for this one, as long as you apply the Phoenix patch and enable XML-RPC reporting, the script will see when Phoenix crashes and restart it.

In the other type of Phoenix crash, it keeps reporting full hashrate. Unfortunately this script can't prevent this but I'm working on a way around it (will involve being able to grab JSON reports from your pool and parse to see when they last accepted a share from a worker).

My crash its 0kh/s proccess kill and only see

"Killed"

will try appling the Phoenix patch

Up with a new version.

A few people were saying they'd like to donate but have no BTC up front, so if you want to, just edit common.lib (on v0.3.2.3 or above) and put the following line at the bottom:

donateMode=1

It will automatically give me 1 out of every 200 mining cycles (0.5% of your mining time). I will implement an option later so you can decide how much to donate.

This option is off by default, it's purely optional, and thanks if anyone decides to use it.

Ok up and running on the current version with no issues!  :)

Thanks for your help and the sym link fixed the problems I was having with getrates.sh.

After I had that fixed I was still having a whole host of problems that must have been a result of improperly installing the 11.6 CCC and 2.4 SDK the day before. (I was seeing multiple platforms listed, -getclocks stopped working, my 2nd card would only hash at like 10% of what it should do)

I uninstalled all the drivers and reinstalled and now everything is as it should be.

I appreciate all the time and help - I'm still relatively new to linux so the simplest things can be baffling at times!

No problem. If you need any help with Autominer, or with Linux, let me know and I'll try to help.

I can't make it work.

http://img263.imageshack.us/img263/6038/dwefwef.jpg

http://paste.ubuntu.com/635996/

Any ideas what's wrong?

Cyper, can you give me the contents of common.lib and cards.lib?

http://paste.ubuntu.com/636029/
http://paste.ubuntu.com/636030/

Also during setup it said that if I use workers I should enter anything in the username/password fields and so I did.
But then where do I enter my real username/passwords? I use 4x Ati 5870 and 4x workers = 1 for each card.

Change phoenixQueueSize to 1 for each card in cards.lib, then try again.

I think that parameter only supports values from 1-10.

Also, unless you removed them, your cards don't have workers attached in this cards.lib file.

It will ask you during configuration something like "Do you use workers for this card on main pool?"
Just type yes, then it'll take you through questions to set up usernames and passwords. Same for backup pool.

Don't use a password which matters for workers, they are sent across the net in plaintext.

I'm also not sure why it's put donateMode=0 four times instead of once, but that won't be causing the issue.

Thank you for your reply, but I think the problem is somehow related to screen judging by this image:

http://img263.imageshack.us/img263/6038/dwefwef.jpg

Also missing XML-RPC - is that a problem?

I've fixed the 4 instances of phoenixQueueSize to 1

Should I run the configure script again?

It's not related to screen, that just means phoenix didn't work, probably because you have no workers set up.

I suggest running the configure script again, don't power through it, look out for the part where it asks if you have workers and type 'yes'.

Not having XML-RPC wouldn't cause this issue, but enabling it allows you to see all your hash rates in the main window (see post 1 for details). I'd suggest ignoring this until everything else is working.

During setup with ./configure.sh I used "y" instead of "yes" to answer the questions.

Is that a problem?

Ok so this is the question where I just wrote some random stuff:



It asks the same questions for the main and backup pools.

Do I leave that blank?

Yes, it only accepts 'yes' or 'no'. Anything else will go to the default (whichever is in caps).

With re: the first user/pass prompt: You can put anything in that part because those usernames and passwords will never be used by Autominer if you specify workers.

It first looks for worker details, then if it can't find those, it looks for common usernames & passwords.

Wow that you for your quick replies. I'm make sure to send you some coins when I mine some :)

Btw is this relevant to me? My rig will be in the next room in headless mode (no monitor) and I'll control it using Ubuntu Remote Desktop + Windows VNC Viewer.

Additionally on my initial setup I answer 0 to this question:


But now when I though about it I think it should be 1, as phoenix sees my CPU as device 0 and my 4 cards as 1,2,3,4

You might find it easier to control it with screen. Just install sshd on Ubuntu (http://www.cyberciti.biz/faq/ubuntu-linux-openssh-server-installation-and-configuration/), then download Putty (http://www.chiark.greenend.org.uk/~sgtatham/putty/) on Windows and open a terminal session. Type:

ssh username@ipaddressofminer

Once you're logged in, you can just do screen -x amm -p 0 to open up your screen session.

The reason why I say this is because Phoenix really reduces your computer's graphical responsiveness, and this can make it very slow over VNC. However, if you want to use VNC, you probably want Xterm to keep opening. It won't prevent you working headlessly if xterm does open, but it makes the screens look a bit uglier (they're restricted to the size of your xterm in terms of amount of space they can take up).

If you want to donate, feel free to test donateMode. :P It gives me 0.5% of your mining capability.

On the device, if Phoenix sees your GPUs as 1/2/3/4 you should choose 1/2/3/4. My phoenix sees my CPU as 3, GPUs as 0/1/2.

Ok I got them working then I closed the console, but they continued working. Well I used stopmining.sh which worked. Is that the only way to stop them?

And the main problem - the speeds are half of what I should get. ~210 Mhash/s compared to 435 Mhash/s

I just found out phoenixQueueSize[0]="256" and I'm absolutely certain I pressed 1 as default during setup.

Try changing it to 1 and retry. That bit was an issue with the code which I will fix now and upload a new version, thanks.

Edit: Fixed in 0.3.2.4.

Running stopmining.sh is the only way to get them to stop, this is by design intent, because it means if you're remote monitoring and your ssh session dies, your miners keep working.

Well I fixed it and now it does not want to start mining:

http://img24.imageshack.us/img24/2840/rgrc.jpg

http://img221.imageshack.us/img221/4479/sdfdsgfdsg.jpg

Latest cards.lib file: http://paste.ubuntu.com/636058/

Also which part of the GUI/Desktop Environment do I need to stop when using SSH? Is it Gnome and then I just login in the console?

Your GPU load is 0 apparently.

Can you grab the latest version and run the new checkphoenix.sh script?

Edit: Issue with Dropbox's server right now apparently. Joy. :D

Edit2: Apparently they're migrating data and should be about 1 hour of downtime. This is where I really need a mirror. :P

Can you try Phoenix with the following options from the command line? (you need to be in phoenix dir)

./phoenix.py -q 1 -v  -u http://CYPER_GPU1:password@nl.btcguild.com:8332 -k phatk PLATFORM=0 DEVICE=1 WORKSIZE=256 AGGRESSION=11 BFI_INT FASTLOOP=false VECTORS

If this works, double check your phoenix directory (in common.lib) is correct, as that's the exact command the script is sending.

Well I got it working and now I'm fighting the SSH thing.

Also I managed to start it and then running stopmining.sh does not seem to kill all instances - one card continued working no matter how many times and executed the stopmining script.

Regarding SSH am I supposed to see the same fancy window as when ran locally?

I ran: sudo DISPLAY=:0 ./startmining.sh /home/cyper/Autominer

And get this:
Autominer Initialization...
Starting in /home/cyper/Autominer
If this is the wrong directory, run "./startmining /path/to/Autominer" instead!
If the script fails, check the log file (default: /var/log/Autominer.log) for details of why.
Most likely, you haven't configured Autominer correctly.
If you can't work it out, don't give up, post at http://forum.bitcoin.org/index.php?topic=19861.0 and I'll try to help!

Re: stopmining.sh not killing, try running the following:

killall screen
killall phoenix.py

It could be that when you changed a card identifier, it lost one or something. Usually it kills everything.

On ssh, you should get the exact same screen, when you do 'screen -x amm -p 0'. The screenshot in the first post (which is down thanks to Dropbox) was taken in ssh.

Any chance of a download mirror for the file?

I'd sorely like to, but I don't have anywhere to ftp dump it to right now. Check back in 30 mins or so and Dropbox should be back up (they're migrating to another datacentre).

I'll try these commands next time I can't stop it.

I haven't forgotten 'screen -x amm -p 0 but it says:
There is no screen to be attached matching amm.

The first command does not work, cause I can hear when it starts mining :)

Locally everything works great apart from the information row where it does not display all GPUs.

Have you successfully connected via ssh, or are you in a local terminal?

Try doing 'screen -x amm -p 0' on your local machine (the one running the miner), as that's the exact command that's being run on the terminal which you say works by this code:

# Load Xterm if not running headless
if [ "$autoOpenXterm" -eq "1" ]; then
        xterm -T "Autominer" -e screen -x amm -p 0 &
fi

As long as this works, your ssh is probably not connected.

If by the information row you mean where it shows the hashes on my screenshot, you have to enable xmlRPC to make that work. See first post for details.

Yes I have successfully connected to the machine.

And yes the xmlRPC was enabled and working, apart from not showing all GPUs screens, but it was correctly showing the total speed.

I just restarted and it tries to connect to dropbox to check for newer version but as the site is down it won't. Will it start mining in that case?

Should do after some failed attempts.

Can you show me what it looks like when it doesn't show all GPUs? Is it because your xterm is too small?

If so, try stopmining.sh, then change common.lib and set autoOpenXterm=0, then startmining.sh, then open a terminal, make it big and do screen -x amm -p 0.

On a second attempt it connected immediately.

Here is what I mean by missing GPUs (the black line at the bottom):

http://img21.imageshack.us/img21/1902/grfsdgfr.jpg

and cycling through the screens does not show the missing GPUs.

Oh, that's an issue with screen, I get the same sometimes when on my 3 GPU machine, the only fix I've found is restarting startmining.sh but it's in my bugs to fix list.

I did that and my machine started mining without the fancy window popping out.

then screen -x amm -p 0 said:

There is no screen to be attached matching amm

Do screen -ls

cyper@Woody:~/Autominer$ screen -ls
No Sockets found in /var/run/screen/S-cyper.

Also this is my attempt at running it via SSH:

http://img62.imageshack.us/img62/7248/fdgfl.jpg

I connect, enter my username, then password and then I can change directories, so I'm definitely connected.

screen -x amm -p 0 will produce There is no screen to be attached matching amm and I can hear the machine does not start mining.

try sudo screen -x amm -p 0

I'm not an expert on sudo but I think it would attach the screen to root's session so you might have to be root to use it.

Ok, got the fancy screen under SSH, but it does not connect + F7-F8 doesn not work so how do I change screens?

http://img718.imageshack.us/img718/4213/fgdfgf.jpg

Try ctrl-a, then the screen number (will be 0,1,2,3 etc).

The next release will really help you as it has a dedicated Phoenix diagnostic tool, but Dropbox is being a nightmare.

This SSH thing is driving me crazy, maybe I should stick with running it locally using Gnome even if it eats some resources.

It does not want to connect + Ctrl+A + numbers works erratically or just using Ctrl+A switches between 2 screens.

Ctrl-A then number should work flawlessly. :/

You have to press Ctrl-A every time you want to press a number.

Is it Ctrl + A + Number all simultaneously
or
Ctrl + A then release and press the number

Btw I'm going for a shower and something to eat after that. If you are still around later on I will write again :)

Thank you again for being so helpful :)

Ctrl-A then release and press the number.

This was a lifesaver! Thank you.

@Reikoku: the .screenrc has a small typo on -k k6: it says "kindkey" instead of "bindkey".

Phoenix 1.50 gives me 13Mhash/sec less than the r101 i used with the same settings... i wonder if the XML-RPC is worth the speed decrease...

Are you on SDK 2.1 or 2.4? If you're on 2.1 modify back to poclbm kernel instead of phatk.

I'll fix .screenrc for the next release, thanks.

can this gr8 script be run on mac/windows? As I have 2 computers (1 PC-now upgraded to radeon HD 6950 GPU and my macBook Pro used for backup mining).

Can a GUI version be made as well for these 2 platforms (Win/Mac)?

Is it possible for there to be a feature where the GUI loads initially until you start mining and then it goes to terminal so as to kill overhead running a GUI all day long would create?

Thank you

With effort this could run on Mac, as Mac is compatible with bash script, you'd just have to get screen working.

I'm not sure if Phoenix runs on Mac though.

As far as I know, to make it run on Windows would require switching to another programming language and forgoing the core of the program (GNU Screen).

2.4.
Tried both 2.1 and 2.4. I now consider the speed decrease a deserved "price" for a so-handy script. Nicely done! :)


I confirm Phoenix runs on Mac, and screen is easily installed through MacPorts.

Do you think you can help with THIS (http://forum.bitcoin.org/index.php?topic=25057.msg310922#msg310922)?

I left my machine running during the night using your script and when I woke up it has stopped mining.
I tried connecting using VNC but I couldn't, so I connected via SSH and did sudo reboot.
So the machine was responsive, but it stopped mining for some reason.

Any ideas?

Usually that issue is related to running out of free memory. :S

Did you leave a VNC on overnight?

Hm, good question.

I closed the VNC Viewer window and then put the machine to sleep.
But this morning I found 2 vnc processes in the Task Manager, which apparently did not close. Would that matter when the machine is sleeping? Is it still maintaining a connection to the Ubuntu machine?

Also when using putty and after screen -x amm -p 0 how do I get back to the terminal so I can write commands?

Also is this a bug with Putty, screen or your script?
It was fine 2 minutes ago, but now it does not show the temp of the 4th card.

http://img24.imageshack.us/img24/5541/sdfdsflw.jpg

That's a bug with aticonfig, I assume, since all the script is doing is passing 'aticonfig --adapter=all --odgt' every 15 seconds.

To get out of screen, just hit Ctrl-A, then D.

I'm not sure about the VNC windows, even having the VNC server open may be a memory issue if it's caching.

First of all, thanks for the Autominer. It's really great! I have a (small) problem with it though:

http://bit.ly/lXqgdQ

The GPU* screens do not attach correctly, as shown above. The miner is working and it mines fine, but the status windows don't work. Any ideas why?

Try changing card identifier names in cards.lib to start with a letter instead of a number.

It's an awkward convention of screen that session names must start with a letter.

@Reikoku: You were right. It works now. I have one bug report though:

The startmining.sh script works from any directory and this is good. But the stopmining.sh works only from Autominer dir. I just copied and pasted the lines that get directory from paratemer and sets it to current directory to stopmining.sh and now it works ok :). I need that, because for some reason when I want to start my miners at boot, this doesn't work:

cd ~/Autominer
sh startmining.sh

But this works:

cp ~/Autominer/startmining.sh /usr/bin/startmining
...
startmining

Not sure why the first doesn't work. Try cd ~/Autominer && ./startmining.sh instead.

I've noticed that when the terminal or any other windows are open at the Ubuntu machine then the speed is playing, but when I close all windows the speed is rock solid, so I disabled xterm. That is not a problem/bug, just an observation on my part :)

But I do have a problem:

When I start the miner locally everything is fine, but it does not start via SSH.
I connect and then I write:

http://img832.imageshack.us/img832/6360/dsfgd.jpg
http://img546.imageshack.us/img546/7119/dsgfg.jpg
http://img51.imageshack.us/img51/9633/sderftr.jpg

So for now I connect using VNC, start it locally, close the Terminal and any other windows, close the VNC viewer and then connect using SSH and proceed with sudo screen -x amm -p 0
But I would like to be able to start it remotely via SSH and not use VNC if possible.

Any ideas?

Works well, saved me hacking one together myself.

Flawless so far.

Is it very difficult to implement manual switching between pools?
Currently I have created different common.lib and cards.lib files for each set of pools such as:

Deepbit and Slush
Deepbit and BTC Guild
Slush and BTC Guild

But it would be awesome if there is an easy way to quickly switch to a different pool manually when desired and not just when the pool is down.

Thank you.

Try doing sudo DISPLAY=:0 ./startmining.sh (or that might be DISPLAY=:0 sudo ./startmining.sh). It can only open over ssh if you set DISPLAY variable.


I don't think it would be very difficult to do this if you know some bash script. You'd just make a new script that cycles through all devices, kills active processes then starts new miners up on the pool passed to it as an argument.

Thank you for your script, everything I read it is wonderful.  I have tried several different ways to start this but I keep getting the same error, I check for a log and no log exists.  Cany you help me...btw I am very new at this so please be patient.
 
This is a copy of the message I get:  I have 2 Radeon 6950, connecting to bitcoinpool.com, my miners work fine and that part I know works. 

miningrig3@miningrig3-MS-7599:~/Autominer$ sudo ./startmining.sh
Autominer Initialization...
Starting in /home/miningrig3/Autominer/
If this is the wrong directory, run "./startmining /path/to/Autominer"                                                        instead!
If the script fails, check the log file (default: /var/log/Autominer.log) for details of why.
Most likely, you haven't configured Autominer correctly.
If you can't work it out, don't give up, post at http://forum.bitcoin.           org/index.php?topic=19861.0 and I'll try to help!

The text you are getting doesn't indicate an error as it appears everytime, even if everything works fine :)

When you write sudo ./startmining.sh does an additional window open?

Also did you configure autoOpenXterm=1 or autoOpenXterm=0 in common.lib?

Thank you for your responese,

autoOpenXterm=1, I am running this via ssh, is there another screen I need activate?

First try to run it locally to make sure everything is working as it should. Can you do that?

I am on the local machine and it popped up the Autominer screen and is mining, I checked the cores both are running 99%,  I guess it most be the way I display in ssh?  Thank you, I am glad the software is running....if you could help me with the ssh part that would be great...

The important thing is that it works :)

Try

or

I'm not sure of the exact structure.

I have the same problem, but it does not bother me, as I'm using VNC to connect to the machine and start the miner locally and then I just connect via SSH to monitor it using sudo screen -x amm -p 0

I'd prefer mining instead of troubleshooting it ;)

That did it, thank you for the help.... :)

Which command is the correct one?

I did it just like you said, I had it started on the local machine, and used sudo screen -x amm -p 0
to start the screen via ssh.  I will try it on the other 2 machines I have, I need to install the autominer on those also.  Thanks again for all the help, I feel much better seeing the miners running.

Nice job.

Sigh. . .

With the DDOS's hitting the good pools, I need more than 2 pools to cycle through.

I'm using one of your original versions, because the newer ones never worked with the autosetup.

Can I just add pool 3, 4 etc. in the common file and corresponding entries in the cards file?

I'll probably just try this anyways, since it's kinda necessary, unless I go back to solomining as backup. . .

If there's anything extra I need to modify, PLMK.
Thanks!

I did donate a little something to you, btw, if that matters.

when i start mining, i just get a bunch of "Rechecking status..." and no mining is going on.  i have a 4850.  if i start phoenix manually (python ./phoenix.py -u http://X@pit.deepbit.net:8332/ -k poclbm VECTORS FASTLOOP=false AGGRESSION=9 DEVICE=1) it works fine.


no further info is in Autominer.log

Connecting to http://X@pit.deepbit.net:8332... which I guess is Connecting to http://X:X@pit.deepbit.net:8332... right?

Also do you run sudo ./startmining locally or via SSH?

yes by X i meant my user:pass.

i am running through ssh:

First try locally to make sure everything is working as it should.
If it does I can't help you with starting it remotely as I usually start it locally and then just monitor it via SSH.

i tried running locally and the same thing is happening.  using sudo doesn't change anything and should not be required.  i also tried adding `setenv DISPLAY ":0"` and `setenv LD_LIBRARY_PATH "/opt/ati-stream-sdk-v2.1-lnx64/lib/x86_64/"` to my ~/.screenrc.

Well, I think without sudo the log file can't be created.

Use sudo and then check on Autominer.log

i set the log file to be in my home directory so it gets created either way, and there isn't any extra info in there:

Try doing ./checkphoenix.sh

thanks.  after i ran that i noticed that it's trying to run `./phoenix.py` whereas i was using `python ./phoenix.py`.  `chmod +x phoenix.py` has solved the issue and Autominer is now mining!

Makes sense, glad to know it's working now.

is there a way to send a command to phoenix/Autominer to change the aggression? like via RPC for example?  or will i need to use ./stopmining, edit the lib file, and then ./startmining, whenever i want to watch a video, then repeat when i am finished watching a video?

also, is there a way to switch back to my main pool once Autominer has started using the seondary pool?  or do i again just have to restart Autominer?

or maybe a way for Autominer to periodically check the main pool and automatically switch back to it once it determines it's reachable again?  sorry i'm not a coder at all but these might be good features to implement....

thanks

You can edit the lib file, then do stopmining then startmining to change aggression. Active phoenix sessions won't take a command to change aggression. I suggest making two copies of the libfile, say:

cards.lib.7 - Aggression 7
cards.lib.11 - Aggression 11

Then just do:

cp cards.lib.7 cards.lib && ./stopmining.sh && DISPLAY=:0 ./startmining.sh

With re: changing back to your main pool, all of the pools seem to have different ways to tell that they're online. This is something planned for the long term future of autominer (probably via a python script) but isn't likely to come anytime soon. Right now it'd just be ./stopmining.sh && DISPLAY=:0 ./startmining.sh

Hi,

im trying to use autominer... set up all configurations to my cards an workers.
But when i start i don't get a new window.
Somehow the cards are fired up and doing their work.

says "There is no screen to be attached matching amm."

Any suggestions?

EDIT:
- autoOpenXterm is set to 1
- also tried wrote
to my ~/.screenrc

I believe you have an extra /lib on the end of your LD_LIBRARY_PATH, and if you set your autominer directory in your startmining.sh or the configure script you shouldn't need to include /opt/miners/autominer when running the script.

Thanks for reply, but still no new window.

How can I check if "screen" is working properly?

Which .screenrc do I have to edit? (I created this file on /home/user/.screenrc because there wasn't one)

There is a file called .screen_Autominer in the Autominer directory. What is it for? It's empty.

Have you installed screen? - sudo apt-get install screen

And always use sudo to make sure everything runs with elevated privileges.

I installed screen, yes.
And I'm using a root terminal.

anything useful in the Autominer.log?  you can list the active screen sessions with `screen -ls` there should be a 'miner', 'amm', and 'temps' at least, and then a 'cardX-miner' for each of your cards.

screen -ls is showing the following:

Log file (stopped it mysef with ./stopminer.sh)
(*** replacing my account data. the connection to the pool is working.)

no more ideas?
would really like to use this script... :(

For some reason it looks like everything is working but the main 'amm' screen isn't connecting.

The screenrc is in the Autominer directory, do ls -a, it's .screenrc_Autominer I think (don't have a box to hand).

If that file is empty, you need to redownload autominer and re-untar it.

If you copied or moved the directory, it could be that it didn't move the invisible file.

Well, something happened now. You were right, the .screen_Autominer file was not copied.

When i start the script now using VNC, the CPU runs with 100% and nothing else happens... there is still no xterm opening.
(Had real hard problems to get the control back)

I will recheck this when I have more time and be able to control the machine physically without VNC.

Stay tuned ;)

For me now works really good  :).

I`ve a suggestion.

When change to 2nd pool, check status of pool 1 every 10 minutes and if its ok, put mining on 1st pool again.

Sometimes have connection problems and miner change pool and no back to pool 1, keep on pool 2.

this's a great idea

It is only a good idea if the script can check the connection to Pool 1 without interrupting the mining process, because otherwise if Pool 1 still has connection issues then the script will disconnect from Pool 2 every 10 minutes to check Pool 1 = not very efficient.

No need kill te pool 2 proccess(can start 2 phoenix whit same card), if connect pool 1 and start mining, kill pool 2 process.

So I'm still trying to start the script via SSH and it does not work. I type:

sudo DISPLAY=:0 ./startmining.sh /home/cyper/Autominer
or
DISPLAY=:0 sudo ./startmining.sh /home/cyper/Autominer
or
sudo DISPLAY=:0 ./startmining.sh

All I get is this:

http://img24.imageshack.us/img24/6875/aefedf.jpg
http://img803.imageshack.us/img803/3070/sdfd.jpg
http://img810.imageshack.us/img810/675/wsfgert.jpg

Also here is the log from Autominer.log:

since X isn't running then i think you need to have it start xterm, which is `autoOpenXterm="1"` in common.lib. 

I still have problems starting autominer. after i copied the .screen_Autominer, the starting window appears for a millisecond. the miner is working, but still no window. screen -list also shows no screen called "amm".

Any ideas?

I tried, but that is not the problem.
Any other suggestions?

Btw I also tried:

export DISPLAY=:0
sudo DISPLAY=:0 ./startmining.sh

But it didn't work too.

OK for anyone struggling to start the script at reboot this is the best way I've found:

In Gnome  go to System/Preferences/Startup Application or just find Startup Applications and add the script there.

Then when you connect via SSH just type:

screen -r to get the info screen.

For anyone having this problem just edit getRate.py

change

#!/usr/bin/python2

to

#!/usr/bin/python

This may not work on legacy systems which have python 1 and 2 installed, you would be better off going into /usr/bin, finding out the name of your python executable and creating a symlink to it.

For example, if it's called python26 (many are), do:

ln -s /usr/bin/python26 /usr/bin/python2

I'm getting the "There is no screen to be attached matching miner-1" message when starting the Autominer. I'm on ubuntu 11.07. Got x running and everything installed that I'm supposed to.

Is there any chance you could make the older version available? I had no problem running the one before the new interface.

Is it possible to run this on LinuxCoin?

I ran the config script, and have everything setup, but I get an error whe I run the startmining.sh script:


There ISN'T a directory "/var/run/screen" there IS "/run/screen"

Do I have to install anything over the basic setup of LinuxCoin?

Why isn't this stickied yet?

Works very nicely except requires modding "miner.sh" file to avoid the even card failure toggle back bug which prevents switching pools when an even number of cards is attempting to switch.
Email me if you want the version of miner.sh to prevent this.


This needs upgrade for more than 2 pools and also timed switch back to main pool after failure, but those aren't necessary.