Smartcoin Linux mining administration. [MULTI-MACHINE SUPPORT NOW IN!]

[Clipse]

mmm errors from hell

before this it kept spewing, lockfile : command not found

Code:

./smartcoin_install.sh: line 162: syntax error near unexpected token `('
./smartcoin_install.sh: line 162: `     Q="INSERT INTO device (fk_machine,name,device,auto_allow,type,disabled) VALUES (1,'$devName',$id,1,'$devType',$devDisable);"'

[1713507142]

1713507142

[1713507142]

1713507142

[jondecker76]

What distro are you running?  Sounds like yours doesn't come with the lockfile command preinstalled (its part of the procmail package for some goofy reason)

I just did an update that adds the dependency and should install procmail package automatically (if your distro uses apt-get anyways), and fixes a quoting issue that caused the other error.

Let me know how it turns out

[Clipse]

Ok it worked, but I had to manually apt-get procmail for the lockfile issue.

New svn installer didnt install procmail, other than that it all went smooth

[jondecker76]

install instructions updated on pages 1 and 4. Includes new procmail dependency, as well as listing Failover support as implemented.

[mono]

Just for a great praise and your info:
Update from r350 to r362 one minute ago without any problems.

[jondecker76]

mono:
thanks for the report!  Must be my lucky day

[BenD]

Ok I went from 323 to 362 using the internal update function.
It definitely gave me an "ERROR" in capital letters, but it was so fast that I could not read the rest.
Afterwards, it asked if I want to take smartcoin.db and I answered tf, for getting your db.

Although I thought that it won't work anymore, it just works like a charm. And since the update I have a rejected of 0.00 %. This is weird. Normally, after starting smartcoin, I got ~12 % rejected, falling slowly to 3.25%.

[Fletch]

install instructions updated on pages 1 and 4. Includes new procmail dependency, as well as listing Failover support as implemented.

Suggestion: Merge all instructions into one post/place.

[jondecker76]

Ok I went from 323 to 362 using the internal update function.
It definitely gave me an "ERROR" in capital letters, but it was so fast that I could not read the rest.
Afterwards, it asked if I want to take smartcoin.db and I answered tf, for getting your db.

Although I thought that it won't work anymore, it just works like a charm. And since the update I have a rejected of 0.00 %. This is weird. Normally, after starting smartcoin, I got ~12 % rejected, falling slowly to 3.25%.

The issue with having to accept "mine" or "theirs" on files should be remedied in future updates.  I know it isn't exactly intuitive

It is possible to have no rejections at startup, though its rare.  If you're lucky enough that your work is not yet out of date when you start mining, then you can see this happen.  You should see this come back up to normal though with some time.

Suggestion: Merge all instructions into one post/place.

The instructions on page 1 and 4 are exactly the same. I normally update post 1, then copy/paste it into the post on page 4. I do it this way so that the information is available on the very first post of this thread, and the post where the beta release was announced.  Perhaps I'll just make a note in the post on page 4 that current instructions are to be found on the first post.

[mono]

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!

[jondecker76]

Update to r367 available

- The Update/Patching system just got a pretty major update.  There are now "update breakpoints".  This means, that in some cases you will have to run a partial update, restart smartcoin, then run subsequent updates.  This allows me to be sure that smartcoin is restarted at key points between doing updates (in fact, r365 will be a partial update, after which you will need to restart smartcoin then update to r367)  A message will be displayed letting you know this, and in the future I will likely make a routine that restarts smartcoin for you, then goes back to continuing the update automatically.

- The stable/experimental update system goes live. By default, everyone is put into the stable updates. If you want to do experimental updates, go to 4) Edit Settings and change the "Development branch to follow" setting to 'experimental' after you've reached r367.
How future updates will work, is they will be available to the experimental people first. Once I can get a few reports back from them, then I will set a flag that will let the stable people grab the updates.

[dishwara]

Dishwara:
It is possible that you saw donation mining because the current time happened to be somewhere between the randomly generated start time and starttime+donation_minutes.  You can verify this by going to 4)Edit Settings, and check the settings for "Hashpower donation minutes per day", and "Time to start hashpower donation each day".  These can also be changed to your liking, but the start time is randomly generated at install time and my best guess was just by pure chance, the donation cycle just happened to be during the time you were first running it. (This would be normal)

In fact, I would appreciate it if you could post both of those settings here, just so I can double-check that there is no issue.
[edit]
I think its likely that your donation minutes per day is set to 3030 instead of 30...  On install, its already defaultly filled out to 30, so if you typed '30' again without backspacing over the 30 that was already there, then it probably got stored as '3030', which would pretty much cause it to be in autoDonate all the time.  Can you confirm this in your settings entries?


Also, ragarding miners that hang. I used to have the problem, but started overclocking just a few mhz less and my miner hasn't hiccupped in over a month.  I would try to make sure that you're not being too aggressive on the overclocking, as it is a very likely cause of the hangs

I use default 30 minutes not 3030, also now i manually change timing to 535.
can you tell how the time is set?
I mean, is 535 means 5:35 AM & 1455 means 2:55 PM? or some other way.
I am using v350 so far, seems you have added many features. Have to try.

EDIT:
Find out about timing setting in 1st post.

[BenD]

I try to update from 362 to 370.
However I am stuck at the update breakpoint to 365. It says it will update to 365 now, succeeds, tells me to kill smartcoin and start it again. I will do, but printouts say it is still 362. When I start the update, it will again update from 362 to 365.

Edit: Just removed the whole directory and got it fresh from svn. I do not have to delete $HOME/.smartcoin/smartcoin.db?

[jondecker76]

Are you sure you completely exited (shut down) smartcoin, and not just detached?


You shouldn't have to remove ~/.smartcoin in your case, there were no schema changes in between those versions, so you should be fine

[BenD]

Are you sure you completely exited (shut down) smartcoin, and not just detached?

Left it everytime with strg + a, "0" + "2" Enter.
No problem. Everything works fine with the freshly grabbed version (+ the "old" database from ~/.smartcoin)

[mono]

Hi Jon.

Like BenD i have the same problem to update from r362 to r370

Code:

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

Code:

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

Code:

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:

Code:

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?

[jondecker76]

Yes, moving to the experimental branch will get you to r370.
I'm going to increment the stable update counter (its a file called update.ver)
This is what will signal the stable update to happen, so if you want to try a stable update again in a little while, that's fine also. [EDIT:  I just incremented the stable update counter, which will make r371 the next available stable update)

I still have a little more work to do on the stable/experimental updates. I should get to it sometime later today (work has taken a lot of my time this week). Basically, the update patches should not have run, as the update its self was skipped.   I'm also working on better display and feedback (showing your current version, the current stable version and the current experimental version) which will make the update system more clear.

[mono]

Update r362 to r371 worked fine 

[jondecker76]

Update r383 now available (for both stable and experimental).
This should pretty much complete the update system, along with full stable/experimental support. The output is changed significantly and it is much easier to understand and follow. It is now impossible to do a 2nd update without a restart after an update breakpoint also.

[plantucha]

fresh install r383

if I change profile or try to kill 2
can't kill mining workers
always some zombies:

mchal    3158  0.9  0.0      0     0 ?        Zl   10:27   2:01 [python] <defunct>
michal    3363  0.8  0.0      0     0 ?        D    10:27   1:54 [python]
michal    3468  0.9  0.0      0     0 ?        Zl   10:27   2:05 [python] <defunct>
michal    3601  0.9  0.0      0     0 ?        D    10:27   2:04 [python]


then new profile cant start, just hanging there:

smartcoin Management System r383(stable) Sat Jul 9 14:01:42 EDT 2011
--------------------------------------------------------------------------------
A configuration change has been detected.  Loading the new profile....
Starting miner Miner.1!
Starting miner Miner.2!
Starting miner Miner.3!
Starting miner Miner.4!

I cant kill zombies even with root, have to restart.

anybody idea what I can do?