Update the install instructions a bit with a note about $LD_LIBRARY_PATH
Updated the installer file to prompt for mysql password as well as report the error messages so we can track bugs (I had them going silently do /dev/null, which I guess isn't a great idea for a beta where I'm trying to find and track down bugs)
Topic: Smartcoin Linux mining administration. [MULTI-MACHINE SUPPORT NOW IN!] - page 39. (Read 105030 times)
June 25, 2011, 10:33:57 PM
June 25, 2011, 08:21:37 PM
Quote
For suggestions, i recommend a return to upper menu option.
Yes, I know a graceful way of returning to the main menu is needed. For now, what I do is ctrl+c to kill the script, then o to open it back up.I'll probably add "x" as an option in the near future.
Quote
I strongly suggest there be a configuration file so that I can point to compiled libs.
This should be handled by your environmental variables. If set up correctly, they should already be in you LD_Library_Path. I could see smartcoin failing if LD_Library_Path wasn't set properly. Alternatively, you could also create symlinks in /usr/lib that point to the library files. Eventually, I'd like to have the installer do this automatically, but didn't have the time to get it in before beta. Now that I think about it, i expect a lot of problems related to this, as a casual user probably won't know if its set, and under many circumstances, it would go un-noticed. Here is an example of how to pull it off with symlinks:Code:
cd /usr/lib
sudo ln -s /home/user/AMD-APP-SDK-v2.4-lnx32/lib/x86/libOpenCL.so libOpenCL.so
sudo ln -s /home/user/AMD-APP-SDK-v2.4-lnx32/lib/x86/libOpenCL.so.1 libOpenCL.so.1
sudo ln -s /home/user/AMD-APP-SDK-v2.4-lnx32/lib/x86/libamdocl32.so libamdocl32.so
sudo ln -s /home/user/AMD-APP-SDK-v2.4-lnx32/lib/x86/libGLEW.so libGLEW.so
sudo ln -s /home/user/AMD-APP-SDK-v2.4-lnx32/lib/x86/libglut.so libglut.so
Code:
export LD_LIBRARY_PATH=/home/user/AMD-APP-SDK-v2.4-lnx32/lib/x86/:$LD_LIBRARY_PATH
(both assuming the AMD sdk installation is correct)
Quote
The mysql database creation doesn't work. I need to specify -p to manually enter password even though it's performed under sudo
I think I see the bug in this.. Most people leave the root user with no password, so I didn't include the -p switch in the mysql command in the installer. I guess I have to find a graceful way to deal with that situation, as mysql sees users with and without passwords as two separate entities reallyAs far as any ATIconfig errors, smartcoin does nothing other than call aticonfig its self, it doesn't mess with any paths so I'm not sure why you're having that problem
June 25, 2011, 08:02:30 PM
The program caused weird problem for me. I used this guide (http://forum.bitcoin.org/index.php?topic=9239.0) to setup my miner originally, so most of the stuff were compiled directly.
I strongly suggest there be a configuration file so that I can point to compiled libs.
There were quite a few errors: The mysql database creation doesn't work. I need to specify -p to manually enter password even though it's performed under sudo
The program seemed to have crashed the ATI driver installation. After reboot, I can no longer run aticonfig, it says command not found. I tried to force remove using dpkg purge and apt-get remove --purge and reinstalled the debian ATI driver compiled using with no luck. Not sure what happened.
For suggestions, i recommend a return to upper menu option.
I strongly suggest there be a configuration file so that I can point to compiled libs.
There were quite a few errors: The mysql database creation doesn't work. I need to specify -p to manually enter password even though it's performed under sudo
The program seemed to have crashed the ATI driver installation. After reboot, I can no longer run aticonfig, it says command not found. I tried to force remove using dpkg purge and apt-get remove --purge and reinstalled the debian ATI driver compiled using
Code:
sudo sh ati-driver-installer-11-5-x86.x86_64.run --buildpkg Ubuntu/natty
For suggestions, i recommend a return to upper menu option.
Dang you having loads of problems, I had a default ubuntu installation with the extra neccesary steps for ATI drivers and miner etc.
All my machines installed without hassle, on some I had to just doublecheck the detected gpu's and miner. The one machine I mentioned in this thread was related to my own usb stick data corruption.
June 25, 2011, 07:25:57 PM
sudo rm /usr/bin/smartcoin
sudo mysql smartcoin -e "DROP DATABASE smartcoin;"
sudo rm -r ~/smartcoin
... should wipe everything clean for a fresh install
sudo mysql smartcoin -e "DROP DATABASE smartcoin;"
sudo rm -r ~/smartcoin
... should wipe everything clean for a fresh install
June 25, 2011, 07:17:55 PM
thanks for the report - that would definitely be good news (for me anyways) if it was caused by data corruption. (though I admit, the installer needs some attention yet as it doesn't actually verify any of the data integrity yet)
Also, since you did have concerns, here is a simple way to test the AutoDonate:
1) On the status screen, note the current time.
2) Goto the control screen, edit settings.
3) Change the start time to be a few minutes ahead of the current time you noted
4) Change the donation minutes to 1 or 2 (anything small)
5) Sit back and watch the status screen - you should see the autodonate kick in, and shut its self back off based on the parameters you entered.
6) the only reason a random time is entered initially, is so that every machine with the feature on didn't all try to do it at once and bog down any pools in the process.
Also, since you did have concerns, here is a simple way to test the AutoDonate:
1) On the status screen, note the current time.
2) Goto the control screen, edit settings.
3) Change the start time to be a few minutes ahead of the current time you noted
4) Change the donation minutes to 1 or 2 (anything small)
5) Sit back and watch the status screen - you should see the autodonate kick in, and shut its self back off based on the parameters you entered.
6) the only reason a random time is entered initially, is so that every machine with the feature on didn't all try to do it at once and bog down any pools in the process.
I had no concern, I verified that the donation works just as advertised without any backhanded tactics
ps. do you have any elegant way to completely uninstall the symlinks / and installation itself in case I want to do a clean reinstall ?
June 25, 2011, 07:08:21 PM
thanks for the report - that would definitely be good news (for me anyways) if it was caused by data corruption. (though I admit, the installer needs some attention yet as it doesn't actually verify any of the data integrity yet)
Also, since you did have concerns, here is a simple way to test the AutoDonate:
1) On the status screen, note the current time.
2) Goto the control screen, edit settings.
3) Change the start time to be a few minutes ahead of the current time you noted
4) Change the donation minutes to 1 or 2 (anything small)
5) Sit back and watch the status screen - you should see the autodonate kick in, and shut its self back off based on the parameters you entered.
6) the only reason a random time is entered initially, is so that every machine with the feature on didn't all try to do it at once and bog down any pools in the process.
Also, since you did have concerns, here is a simple way to test the AutoDonate:
1) On the status screen, note the current time.
2) Goto the control screen, edit settings.
3) Change the start time to be a few minutes ahead of the current time you noted
4) Change the donation minutes to 1 or 2 (anything small)
5) Sit back and watch the status screen - you should see the autodonate kick in, and shut its self back off based on the parameters you entered.
6) the only reason a random time is entered initially, is so that every machine with the feature on didn't all try to do it at once and bog down any pools in the process.
June 25, 2011, 06:59:19 PM
Bit to late 
Im redoing the 2nd machine, seems my usb stick went apeshit and seems like it may be data corruption related.
Will report back if fresh install on different stick still have same issue
Im redoing the 2nd machine, seems my usb stick went apeshit and seems like it may be data corruption related.
Will report back if fresh install on different stick still have same issue
June 25, 2011, 06:55:46 PM
if you want, do a dump on the database (removing the worker table if you want to) and I'll see if there is anything obvious there. I'm sure we'll find what is causing it on your 2nd machine.
June 25, 2011, 06:52:37 PM
Just finished installing on 2 more machines, no hassles just like on 1st machine.
Only the damn second machine giving me those crappy errors :p
Only the damn second machine giving me those crappy errors :p
June 25, 2011, 06:43:53 PM
Quote
I haven't reviewed the donating feature but I do not have a good feeling with it.
Processing time is controlled from your script only and the normal user can't check, if it works correctly.
Your wallet address for donating your hard work would be more fair for myself.
Processing time is controlled from your script only and the normal user can't check, if it works correctly.
Your wallet address for donating your hard work would be more fair for myself.
Donation choices are completely yours - however, I do invite anyone and everyone to look over the code - I can assure you that there is nothing backhanded at all here. The user definitely can check if its working, as the status screen will show when it goes into, and leaves the AutoDonation mode. Also realize, that variance aside, that with a 1% donation, a user would make aprox. 100 bitcoins before 1 full bitcoin would be donated - not a bad deal and that should be anough to show i\I'm not trying to get rich off of anything.
I will look into the disconnect/exit reports and see what I can find locally. I will also check on the backend script, as I though I disabled it, as its there for future improvements and currently doesn't do anything but listen to a pipe.
Thanks for the reports
June 25, 2011, 06:30:53 PM
I did a quick install because I am very tired - will look for it tomorrow.
- I had to create the database and import the smartcoin_schema.sql by myself.
- detection of miners root path did not work correctly:
- Disconnect from smartcoin (leave running) seems working correctly but when I start smartcoin again, it does not attach the running screen session so I have to do it manually via screen -r
I haven't reviewed the donating feature but I do not have a good feeling with it.
Processing time is controlled from your script only and the normal user can't check, if it works correctly.
Your wallet address for donating your hard work would be more fair for myself.
- I had to create the database and import the smartcoin_schema.sql by myself.
- detection of miners root path did not work correctly:
Quote
install-path = /home//phoenix (phoenix is a softlink to phoenix-1.50)
you detected = /home//phoenix-1.48/something wired I can't remember because its too late
- Kill smartcoin (exit) does not kill all smartcoin processes (smartcoin_backend.sh ist still running)you detected = /home/
- Disconnect from smartcoin (leave running) seems working correctly but when I start smartcoin again, it does not attach the running screen session so I have to do it manually via screen -r
I haven't reviewed the donating feature but I do not have a good feeling with it.
Processing time is controlled from your script only and the normal user can't check, if it works correctly.
Your wallet address for donating your hard work would be more fair for myself.
On my first machine where Im having no hassles the following worked right:
-killing smartcoin (exit) : no problem here, no extra process remaining
-disconnect from smartcoin (leave running) : no problem here, starting smartcoin connects to the screen as it should.
I checked the donation settings and it all checks out, if disabled nothing is processed on that.
June 25, 2011, 06:27:46 PM
What is the value for the start time setting? Maybe that's where the problem is. I'd like to reproduce it locally if I can
Tried various start times, dont think its related.
I did however see the miner2 machine having the issues did detect phoenix installation at wrong dir , I then pointed it to the proper one and still same error so atleast it seems that wasnt the reason for error.
My first machine did detect all correctly with no hassles, both setups are the same installation of ubuntu which is weird.
June 25, 2011, 06:22:45 PM
What is the value for the start time setting? Maybe that's where the problem is. I'd like to reproduce it locally if I can
June 25, 2011, 06:16:59 PM
I did a quick install because I am very tired - will look for it tomorrow.
- I had to create the database and import the smartcoin_schema.sql by myself.
- detection of miners root path did not work correctly:
- Disconnect from smartcoin (leave running) seems working correctly but when I start smartcoin again, it does not attach the running screen session so I have to do it manually via screen -r
I haven't reviewed the donating feature but I do not have a good feeling with it.
Processing time is controlled from your script only and the normal user can't check, if it works correctly.
Your wallet address for donating your hard work would be more fair for myself.
- I had to create the database and import the smartcoin_schema.sql by myself.
- detection of miners root path did not work correctly:
Quote
install-path = /home//phoenix (phoenix is a softlink to phoenix-1.50)
you detected = /home//phoenix-1.48/something wired I can't remember because its too late
- Kill smartcoin (exit) does not kill all smartcoin processes (smartcoin_backend.sh ist still running)you detected = /home/
- Disconnect from smartcoin (leave running) seems working correctly but when I start smartcoin again, it does not attach the running screen session so I have to do it manually via screen -r
I haven't reviewed the donating feature but I do not have a good feeling with it.
Processing time is controlled from your script only and the normal user can't check, if it works correctly.
Your wallet address for donating your hard work would be more fair for myself.
June 25, 2011, 06:08:03 PM
Ok, found the problem
Your donation time is blank in the database, where it should be 0
I've updated the scripts to check for this now.
You can either kill smartcoin, svn update, then restart it. Or even easier, from the control screen, edit settings - then edit the donation minutes per day to be 0
(Sanitizing input is something that I'm going to be working on next )
Your donation time is blank in the database, where it should be 0
I've updated the scripts to check for this now.
You can either kill smartcoin, svn update, then restart it. Or even easier, from the control screen, edit settings - then edit the donation minutes per day to be 0
(Sanitizing input is something that I'm going to be working on next
)Allright I saw that the value was 0(and not empty) allready but I tried different values still gave error.
I then tried updating svn, still getting same error.
Weirdness.
BTW - have you gotten around to making any manual profiles yet, and/or switching them on the fly?
I am still playing around, will let you know about manual profiles (I did create one but nothing special yet)
June 25, 2011, 06:00:45 PM
Ok, found the problem
Your donation time is blank in the database, where it should be 0
I've updated the scripts to check for this now.
You can either kill smartcoin, svn update, then restart it. Or even easier, from the control screen, edit settings - then edit the donation minutes per day to be 0
(Sanitizing input is something that I'm going to be working on next )
Your donation time is blank in the database, where it should be 0
I've updated the scripts to check for this now.
You can either kill smartcoin, svn update, then restart it. Or even easier, from the control screen, edit settings - then edit the donation minutes per day to be 0
(Sanitizing input is something that I'm going to be working on next
)Weird, I set it to 100 maybe overlooked like a donkey and 1 didnt register lol
June 25, 2011, 05:31:16 PM
BTW - have you gotten around to making any manual profiles yet, and/or switching them on the fly?
June 25, 2011, 05:29:59 PM
Ok, found the problem
Your donation time is blank in the database, where it should be 0
I've updated the scripts to check for this now.
You can either kill smartcoin, svn update, then restart it. Or even easier, from the control screen, edit settings - then edit the donation minutes per day to be 0
(Sanitizing input is something that I'm going to be working on next )
Your donation time is blank in the database, where it should be 0
I've updated the scripts to check for this now.
You can either kill smartcoin, svn update, then restart it. Or even easier, from the control screen, edit settings - then edit the donation minutes per day to be 0
(Sanitizing input is something that I'm going to be working on next
) June 25, 2011, 05:01:30 PM
Made installation on second machine and it didnt go as smoothly when starting up miners
Getting these errors:
Getting these errors:
Code:
expr: syntax error
/home/miner2/smartcoin/smartcoin_ops.sh: line 384: +0 0: syntax error in expression (error token is "0")
/home/miner2/smartcoin/smartcoin_ops.sh: line 420: [[: 0 0: syntax error in expression (error token is "0")
/home/miner2/smartcoin/smartcoin_ops.sh: line 384: +0 0: syntax error in expression (error token is "0")
/home/miner2/smartcoin/smartcoin_ops.sh: line 420: [[: 0 0: syntax error in expression (error token is "0")
June 25, 2011, 03:57:13 PM
sexy stuff, easy and straight forward setup.
Will let it run on my one box for now, good job, cant wait for the final release
Will let it run on my one box for now, good job, cant wait for the final release
Jump to: