 Show Posts
|
|
Pages: [1]
|
Update r362 to r371 worked fine  |
|
|
|
Hi Jon. Like BenD i have the same problem to update from r362 to r370 smartcoin Management System r362 Sa 9. Jul 09:31:22 CEST 2011
--------------------------------------------------------------------------------
Your current version is r362.
Are you sure that you wish to perform an update?
y
Bring update script up to current...
U /home/mono/smartcoin/smartcoin_update.sh
Aktualisiert zu Revision 370.
Preparing to do an Update...
Getting current revision...
Getting the current repo...
Getting the repo current revision number...
Checking stable update flag...
Update breakpoints have been detected! This means that you will have to run a partial update, restart smartcoin, then run an update again. You may have to repeat this several time to get fully up to date!
There are new experimental updates, but they aren't proven safe yet. Not updating.
Applying post update patches...
Applying r365 patch...
Update task complete.
Update is now complete! You should now restart smartcoin. Please hit any key to continue. Exited via 2) Starting smartcoin again ... still r362 smartcoin Management System r362 Sa 9. Jul 09:32:35 CEST 2011
--------------------------------------------------------------------------------
1) Reboot Computer
2) Kill smartcoin (exit)
3) Disconnect from smartcoin (leave running)
4) Edit Settings
5) Select Profile
6) Configure Miners
7) Configure Workers
8) Configure Profiles
9) Configure Devices
10) Configure Pools
11) Update Smartcoin
12) Set Failover Order Next try to Update smartcoin Management System r362 Sa 9. Jul 09:33:40 CEST 2011
--------------------------------------------------------------------------------
Your current version is r362.
Are you sure that you wish to perform an update?
y
Bring update script up to current...
Revision 370.
Preparing to do an Update...
Getting current revision...
Getting the current repo...
Getting the repo current revision number...
Checking stable update flag...
Update breakpoints have been detected! This means that you will have to run a partial update, restart smartcoin, then run an update again. You may have to repeat this several time to get fully up to date!
There are new experimental updates, but they aren't proven safe yet. Not updating.
Applying post update patches...
Applying r365 patch...
Update task complete.
Update is now complete! You should now restart smartcoin. Please hit any key to continue. Logfile output: mono@miner1:~$ cat .smartcoin/smartcoin.log
07/09/11 09:32:34 ******************* NEW SMARTCOIN SESSION STARTED *******************
07/09/11 09:32:34 Starting main smartcoin screen session...
07/09/11 09:32:34 Creating tab for each machine...
07/09/11 09:32:34 localhost
07/09/11 09:32:34 Starting status monitor for machine 1
07/09/11 09:32:34 NEW PROFILE DETECTED!
07/09/11 09:32:34 Switching from profile: to profile: -3
07/09/11 09:32:34 Killing Miners....
07/09/11 09:32:37 Starting miner Miner.1!
07/09/11 09:32:37 Launching miner with launch string: python /home/mono/phoenix/phoenix.py -v -u http://USER:PASS@de.btcguild.com:8332/ device=1 worksize=128 vectors aggression=11 bfi_int fastloop=false -k phatk
07/09/11 09:32:39 Starting miner Miner.2!
07/09/11 09:32:39 Starting miner Miner.3!
07/09/11 09:32:39 Starting miner Miner.4!
07/09/11 09:32:39 Launching miner with launch string: python /home/mono/phoenix/phoenix.py -v -u http://USER:PASS@de.btcguild.com:8332/ device=4 worksize=128 vectors aggression=11 bfi_int fastloop=false -k phatk
07/09/11 09:32:40 Launching miner with launch string: python /home/mono/phoenix/phoenix.py -v -u http://USER:PASS@de.btcguild.com:8332/ device=2 worksize=128 vectors aggression=11 bfi_int fastloop=false -k phatk
07/09/11 09:32:41 Launching miner with launch string: python /home/mono/phoenix/phoenix.py -v -u http://USER:PASS@de.btcguild.com:8332/ device=3 worksize=128 vectors aggression=11 bfi_int fastloop=false -k phatk
07/09/11 09:33:40 Update option selected
07/09/11 09:33:44 Preparing to do an Update...
07/09/11 09:33:51 There are new experimental updates, but they aren't proven safe yet. Not updating.
07/09/11 09:33:51 Applying post update patches...
07/09/11 09:33:51 No patches to apply to r363
07/09/11 09:33:51 No patches to apply to r364
07/09/11 09:33:51 Applying r365 patch...
07/09/11 09:33:51 Update task complete.
07/09/11 09:34:10 Exit option selected
07/09/11 09:34:10 Killing Miners.... Still r362  Or do i have to change to the experimental branch? |
|
|
|
Perhaps I'll just make a note in the post on page 4 that current instructions are to be found on the first post.
That should be the best solution! |
|
|
|
|
Just for a great praise and your info:
Update from r350 to r362 one minute ago without any problems.
|
|
|
|
Failover works like a charme  smartcoin Management System r350 Do 7. Jul 19:19:19 CEST 2011
--------------------------------------------------------------------------------
Host: localhost
GPU[0]: Temp: 43.50 load: 0%
GPU[1]: Temp: 44.50 load: 0%
GPU[2]: Temp: 38.50 load: 0%
GPU[3]: Temp: 39.50 load: 0%
CPU Load : 9,36%
Profile: Failover
--------BTCGuild--------
GPU[0]: <<<DOWN>>>
GPU[1]: <<<DOWN>>>
GPU[2]: <<<DOWN>>>
GPU[3]: <<<DOWN>>>
Total : [0 hash/sec] [0 Accepted] [0 Rejected]
--------Eligius--------
GPU[0]: [365.34 Mhash/sec] [0 Accepted] [0 Rejected] [RPC (+LP)]
GPU[1]: [395.47 Mhash/sec] [1 Accepted] [0 Rejected] [RPC (+LP)]
GPU[2]: [363.89 Mhash/sec] [0 Accepted] [0 Rejected] [RPC (+LP)]
GPU[3]: [365.66 Mhash/sec] [0 Accepted] [0 Rejected] [RPC (+LP)]
Total : [1490.36 MHash/sec] [1 Accepted] [0 Rejected]
Grand Total: [1490.36 Mhash/sec] [1 Accepted] [0 Rejected] [0% Rejected]
Thanks so much! |
|
|
|
Yes! I look at the logfile. Miners started with that command: python /home/mono/phoenix/phoenix.py -v -u http://USER:PASWORD@POOL:8332/ device=0 worksize=128 vectors aggression=11 bfi_int fastloop=false -k phatk When i start it directly from the console i get the following error: Could not locate the specified kernel! Ahh, my failure. After reinstall i have the edit the devices first. DEVICE=0 ist my CPU! Works again. Now i take a look at failover  |
|
|
|
Yes! I look at the logfile. Miners started with that command: python /home/mono/phoenix/phoenix.py -v -u http://USER:PASWORD@POOL:8332/ device=0 worksize=128 vectors aggression=11 bfi_int fastloop=false -k phatk When i start it directly from the console i get the following error: Could not locate the specified kernel! Ahh, my failure. After reinstall i have the edit the devices first. DEVICE=0 ist my CPU! |
|
|
|
Yes! I look at the logfile. Miners started with that command: python /home/mono/phoenix/phoenix.py -v -u http://USER:PASWORD@POOL:8332/ device=0 worksize=128 vectors aggression=11 bfi_int fastloop=false -k phatk When i start it directly from the console i get the following error: Could not locate the specified kernel! |
|
|
|
After r350 update, can't mine.
So, did a complete uninstall & re install.
Now even though already their is Automatic profile, its not running. Also new profile "Failover" i see.
I created a profile myself & it also not running.
Besides "Donation" pool is running with saying 351 minutes left.
Even though i gave 30 minutes donation & allow to select time itself, 400 minutes of donation is too much with current difficulty & also FORCING it is too much to my knowledge.
After i updated from 345 i got another problem. Hi, i updated from 345 and get following error: Your current version is r345.
Are you sure that you wish to perform an update?
y
Bring update script up to current...
U /home/mono/smartcoin/smartcoin_update.sh
Aktualisiert zu Revision 349.
Preparing to do an Update...
Preparing safe update from r345 to r349
Konflikt in »/home/mono/smartcoin/smartcoin.db« entdeckt.
Auswahl: (p) zurückstellen,
(mf) volle eigene Datei, (tf) volle fremde Datei,
(s) alle Optionen anzeigen: tf
G /home/mono/smartcoin/smartcoin.db
U /home/mono/smartcoin/smartcoin_control.sh
U /home/mono/smartcoin/smartcoin_ops.sh
U /home/mono/smartcoin/smartcoin_status.sh
U /home/mono/smartcoin/smartcoin_install.sh
U /home/mono/smartcoin
Aktualisiert zu Revision 349.
Applying post update patches...
Applying r346 patch...
Error: near "Q": syntax error
Error: near "Q": syntax error
Error: near "Q": syntax error
Update task complete.
Update is now complete! You should now restart smartcoin. Please hit any key to continue.
After restart SmartCoin and configure the profile, i get following error when i got to (12) Set Failover Order: 1) localhostPlease select the machine from the list above that you wish to edit Failover order on
1
Error: no such column: failover_order
The current profile failover order is listed above.
Do you want to change the failover order, (y)es or (n)o?
Seems the database was not updated. After i updated to r350: Same error in (12) Set Failover Order. Cause of that i deleted SmartCoin completly and reinstalled it. But no i can`t mine like dishwara. |
|
|
|
|
Is it possible to mine BTCGuild in first priority (with full power) and when they go down (like the last days because of DDOS) smartcoin switches completly to a backup like deepbit? If this is possible, where can i find this?
|
|
|
|
also, as a test of the update system patching, can those that ran the update let me know if:
A) ~/.smartcoin was created, and the smartcoin.db moved there
B) Go to the control tab-> 4) Edit Settings. Do you have an entry in the list " Development branch to follow (stable/experimental)?
thanks!
Awesome speed in fixing. Thank you. A) works B) works Everything is fine |
|
|
|
Ahh, when i start smartcoin directly like /home/$USERNAME/smartcoin/./smartcoin it works. But the symlink from /usr/bin is not working |
|
|
|
|
Hi,
i used the update function. after i killed smartcoin i get and error:
/usr/bin/smartcoin: Zeile 59: Goto: Command not found.
|
|
|
|
|
This can`t be a solution. I read most of the time. Now i want to post and not allowed. hmm.
|
|
|
|
|
I`m no happy to be a newbie. I think this is not a solution against spam.
|
|
|
|
|
