I officially give up on BAMT =(
Sorry to hear. Please let me know how much you donated towards BAMT so I can refund you.
Topic: BAMT version 0.5 - Easy USB based mining Linux with farm wide management tools - page 42. (Read 324185 times)
May 07, 2012, 04:32:42 PM
Sorry to hear. Please let me know how much you donated towards BAMT so I can refund you.
May 07, 2012, 04:31:43 PM
I officially give up on BAMT =(
May 07, 2012, 02:22:36 PM
Also, this appears to happen every minute:
Code:
May 7 19:21:01 kraken stop_mining[11391]: stopping mining processes...
May 7 19:21:01 kraken stop_mining[11391]: failed to get socket for cgminer api
May 7 19:21:05 kraken start_mining[11397]: starting mining processes
May 7 19:21:06 kraken start_mining[11397]: generating munin config, stopping munin-node
May 7 19:21:06 kraken start_mining[11397]: replace hostname in munin.conf
May 7 19:21:06 kraken start_mining[11397]: generating munin summary plugins...
May 7 19:21:06 kraken start_mining[11397]: generating per gpu munin plugins for template gpuhash...
May 7 19:21:06 kraken start_mining[11397]: generating per gpu munin plugins for template gpushares...
May 7 19:21:06 kraken start_mining[11397]: generating per gpu munin plugins for template gputemp...
May 7 19:21:06 kraken start_mining[11397]: done generating munin config, starting munin-node
May 7 19:21:09 kraken start_mining[11793]: starting cgminer with cmd: cd /opt/miners/cgminer;/usr/bin/screen -d -m -S cgminer /opt/miners/cgminer/cgminer --api-listen --api-port 4028 -o http://pit.deepbit.net:8332 -u user -p pass
May 7 19:22:02 kraken stop_mining[11852]: stopping mining processes...
May 7 19:22:02 kraken stop_mining[11852]: failed to get socket for cgminer api
May 7 19:22:06 kraken start_mining[11858]: starting mining processes
May 7 19:22:06 kraken start_mining[11858]: generating munin config, stopping munin-node
May 7 19:22:06 kraken start_mining[11858]: replace hostname in munin.conf
May 7 19:22:06 kraken start_mining[11858]: generating munin summary plugins...
May 7 19:22:06 kraken start_mining[11858]: generating per gpu munin plugins for template gpuhash...
May 7 19:22:06 kraken start_mining[11858]: generating per gpu munin plugins for template gpushares...
May 7 19:22:06 kraken start_mining[11858]: generating per gpu munin plugins for template gputemp...
May 7 19:22:06 kraken start_mining[11858]: done generating munin config, starting munin-node
May 7 19:22:09 kraken start_mining[12254]: starting cgminer with cmd: cd /opt/miners/cgminer;/usr/bin/screen -d -m -S cgminer /opt/miners/cgminer/cgminer --api-listen --api-port 4028 -o http://pit.deepbit.net:8332 -u user -p pass
May 07, 2012, 01:26:01 PM
Why does BAMT give up on X? More importantly, why can't it find it?
Code:
May 8 02:22:01 kraken start_mining[2802]: pre mining tasks
May 8 02:22:02 kraken start_mining[2802]: wait 30 seconds for X to start...
May 8 02:22:03 kraken mother[2822]: #011autoconf client doesn't seem to be running, spawning one
May 7 18:24:00 kraken start_mining[2802]: still waiting for X after 30 seconds...
May 7 18:24:30 kraken start_mining[2802]: still waiting for X after 60 seconds...
May 7 18:25:00 kraken start_mining[2802]: still waiting for X after 90 seconds...
May 7 18:25:30 kraken start_mining[2802]: gave up on X after 120 seconds
May 06, 2012, 06:40:02 PM
My http://bit.ly/IOdhFArig keeps hanging up on me. Have to restart it every few days. Just logged in via Putty, and saw this error:
How do I fix it?
Code:
xauth: (argv):1: merge: unable to open file /home/user/.Xauthority
How do I fix it?
Reduce your overclocking.
bad hardware then. nothing in software will fix that.
I sent a little something for the help. I am using BAMT on all my rigs and have become profitable over a short period of time. Thanks!
May 06, 2012, 06:35:15 PM
My http://bit.ly/IOdhFArig keeps hanging up on me. Have to restart it every few days. Just logged in via Putty, and saw this error:
How do I fix it?
Code:
xauth: (argv):1: merge: unable to open file /home/user/.Xauthority
How do I fix it?
Reduce your overclocking.
bad hardware then. nothing in software will fix that.
May 06, 2012, 06:33:43 PM
My http://bit.ly/IOdhFArig keeps hanging up on me. Have to restart it every few days. Just logged in via Putty, and saw this error:
How do I fix it?
Code:
xauth: (argv):1: merge: unable to open file /home/user/.Xauthority
How do I fix it?
Reduce your overclocking.
May 06, 2012, 06:17:15 PM
My http://bit.ly/IOdhFArig keeps hanging up on me. Have to restart it every few days. Just logged in via Putty, and saw this error:
How do I fix it?
Code:
xauth: (argv):1: merge: unable to open file /home/user/.Xauthority
How do I fix it?
Reduce your overclocking.
Also, what are the commands to restart, and also shutdown linux? I found this command online:
That seems to restart, but I can't find a Shut Down command.
Code:
shutdown -r now
http://bit.ly/IOdhFA
May 06, 2012, 06:13:18 PM
My rig keeps hanging up on me. Have to restart it every few days. Just logged in via Putty, and saw this error:
How do I fix it? Also, what are the commands to restart, and also shutdown linux? I found this command online:
That seems to restart, but I can't find a Shut Down command.
Code:
xauth: (argv):1: merge: unable to open file /home/user/.Xauthority
How do I fix it? Also, what are the commands to restart, and also shutdown linux? I found this command online:
Code:
shutdown -r now
May 05, 2012, 01:28:47 AM
Well i ran into a problem and still noob at linux..
one of my miner stop working after 2 months no problems..
I tryed to restart miners..
And i get error message saying i ran out of disk space
I'm guessing this from web logs filling up...
it wont even let me delete something
i get error no space for trash can
Any idea's..
or should i just wipe the 2g flash with clean copy?
jay
Your USB key may have crapped out. Try a new install, if it still does it, your key is borked. one of my miner stop working after 2 months no problems..
I tryed to restart miners..
And i get error message saying i ran out of disk space
I'm guessing this from web logs filling up...
it wont even let me delete something
i get error no space for trash can
Any idea's..
or should i just wipe the 2g flash with clean copy?
jay
May 04, 2012, 11:01:26 PM
Well i ran into a problem and still noob at linux..
one of my miner stop working after 2 months no problems..
I tryed to restart miners..
And i get error message saying i ran out of disk space
I'm guessing this from web logs filling up...
it wont even let me delete something
i get error no space for trash can
Any idea's..
or should i just wipe the 2g flash with clean copy?
jay
one of my miner stop working after 2 months no problems..
I tryed to restart miners..
And i get error message saying i ran out of disk space
I'm guessing this from web logs filling up...
it wont even let me delete something
i get error no space for trash can
Any idea's..
or should i just wipe the 2g flash with clean copy?
jay
May 04, 2012, 03:08:48 PM
I've perused this thread, searched, and messed up my BAMT configs a few times now. I've succumbed to asking here, so... Is there any documentation on how to get the whole farm's status showing on one machine? I can't seem to get all of my machines to show up on a single machine's web status page... Giga, I know you've somehow managed to get your farm showing, any tips/tricks/info on how you did this?
https://bitcointalksearch.org/topic/m.864059
that what you need?
That helped, thank-you. I needed to do to this, as well I had to change the cidr_allow from 192.168.0.0/16 to 192.168.2.0/16 in munin-node.conf
that doesn't make any sense, 192.168.0.0/16 and 192.168.2.0/16 are exactly the same thing.
ps - also, mgpumon doesn't use munin at all, so I sincerely doubt changing the munin config made any difference.
May 04, 2012, 02:55:31 PM
I've perused this thread, searched, and messed up my BAMT configs a few times now. I've succumbed to asking here, so... Is there any documentation on how to get the whole farm's status showing on one machine? I can't seem to get all of my machines to show up on a single machine's web status page... Giga, I know you've somehow managed to get your farm showing, any tips/tricks/info on how you did this?
https://bitcointalksearch.org/topic/m.864059
that what you need?
That helped, thank-you. I needed to do to this, as well I had to change the cidr_allow from 192.168.0.0/16 to 192.168.2.0/16 in munin-node.conf
May 04, 2012, 11:56:50 AM
Playing around with BAMT, I found a strange bug.
When I have a monitor plugged in, and I'm fooling around in BAMT, if I unplug the monitor, it makes BAMT crash. Here's what munin shows when I connect to the rig:
If I never plug a monitor in BAMT and I boot the rig, everything's fine. It only occurs when BAMT is started and I plug and unplug the monitor. If I want to plug back the monitor to check what happens in BAMT, it start working again without problems.
I use the 0.5c version of BAMT.
When I have a monitor plugged in, and I'm fooling around in BAMT, if I unplug the monitor, it makes BAMT crash. Here's what munin shows when I connect to the rig:
Quote
__.....__ .' ':, / __ _ __ \\ | |_)) || |_))|| | | \\ || | || | || _, | status.pl ||.-(_{} | |/ ` | ,_ (;|/) \\| {}_)-,||` \\;/,,;;;;;;;,\\|//, .;;;;;;;;;;;;;;;;, ,;;;;;;;;;;;;;;;;,// \\;;;;;;;;;;;;;;;;,// ,';;;;;;;;;;;;;;;;' One of the BAMT tools has suffered a fatal error. Can't use an undefined value as a HASH reference at /usr/lib/cgi-bin/status.pl line 88. Defiled: Unable to record this travesty in the deathlog! Why?: Permission denied
If I never plug a monitor in BAMT and I boot the rig, everything's fine. It only occurs when BAMT is started and I plug and unplug the monitor. If I want to plug back the monitor to check what happens in BAMT, it start working again without problems.
I use the 0.5c version of BAMT.
Yeah, many of us have had this problem and, as you found out, you mustn't unplug a monitor while BAMT is running. Actually I think it may be a driver issue.
What you may not grok is what that string of punctuation symbols is all about. So I checked through the author's perl scripts. It turns out that if you put appropriate line breaks in and use a fixed width font (which your average web browser does not do, hence the garbling), that's actually a tombstone rendered in ascii art. Because status.pl has died. Geddit?
If you are using the shell, you see something like:
__.....__
.' ':,
/ __ _ __ \\
| |_)) || |_))||
| | \\ || | ||
| || _,
| mother ||.-(_{}
| |/ `
| ,_ (;|/)
\\| {}_)-,||`
\\;/,,;;;;;;;,\\|//,
.;;;;;;;;;;;;;;;;,
,;;;;;;;;;;;;;;;;,//
\\;;;;;;;;;;;;;;;;,//
,';;;;;;;;;;;;;;;;'
One of the BAMT tools has suffered a fatal error.
anyway, don't plug/unplug monitors. it breaks things. nobody knows why, but everybody knows you should never plug a monitor into bamt anyway. you're wasting your time doing that.
May 04, 2012, 11:00:16 AM
sounds like you overclocked them too much... and your rig/bamt doesn't like it.
reduce your clocks, typically 800/300 works best for all my 5970's...
then try removing the noOCGPUx file:
Quote
: cd /live/image/BAMT/CONTROL/ACTIVE
: ls
(it will display the files needed to be removed, n then you follow by typing for each one)
: rm noOCGPUx
: ls
(it will display the files needed to be removed, n then you follow by typing for each one)
: rm noOCGPUx
once done editing your .config, and removing each one of those files...
go back to gpumon, stop mining, start mining.
hope that helps, as it did for me from. (thanks to Spilrow for schoolin me on that :-) ).
I don't OC my cards, 800/300 is a fairly high OC. It was just one of those weird things that happens every once in a while with no reason or explanation. Started with fresh images across the farm today.
May 04, 2012, 09:12:09 AM
Playing around with BAMT, I found a strange bug.
When I have a monitor plugged in, and I'm fooling around in BAMT, if I unplug the monitor, it makes BAMT crash. Here's what munin shows when I connect to the rig:
If I never plug a monitor in BAMT and I boot the rig, everything's fine. It only occurs when BAMT is started and I plug and unplug the monitor. If I want to plug back the monitor to check what happens in BAMT, it start working again without problems.
I use the 0.5c version of BAMT.
When I have a monitor plugged in, and I'm fooling around in BAMT, if I unplug the monitor, it makes BAMT crash. Here's what munin shows when I connect to the rig:
Quote
__.....__ .' ':, / __ _ __ \\ | |_)) || |_))|| | | \\ || | || | || _, | status.pl ||.-(_{} | |/ ` | ,_ (;|/) \\| {}_)-,||` \\;/,,;;;;;;;,\\|//, .;;;;;;;;;;;;;;;;, ,;;;;;;;;;;;;;;;;,// \\;;;;;;;;;;;;;;;;,// ,';;;;;;;;;;;;;;;;' One of the BAMT tools has suffered a fatal error. Can't use an undefined value as a HASH reference at /usr/lib/cgi-bin/status.pl line 88. Defiled: Unable to record this travesty in the deathlog! Why?: Permission denied
If I never plug a monitor in BAMT and I boot the rig, everything's fine. It only occurs when BAMT is started and I plug and unplug the monitor. If I want to plug back the monitor to check what happens in BAMT, it start working again without problems.
I use the 0.5c version of BAMT.
Yeah, many of us have had this problem and, as you found out, you mustn't unplug a monitor while BAMT is running. Actually I think it may be a driver issue.
What you may not grok is what that string of punctuation symbols is all about. So I checked through the author's perl scripts. It turns out that if you put appropriate line breaks in and use a fixed width font (which your average web browser does not do, hence the garbling), that's actually a tombstone rendered in ascii art. Because status.pl has died. Geddit?
May 04, 2012, 05:21:03 AM
Playing around with BAMT, I found a strange bug.
When I have a monitor plugged in, and I'm fooling around in BAMT, if I unplug the monitor, it makes BAMT crash. Here's what munin shows when I connect to the rig:
If I never plug a monitor in BAMT and I boot the rig, everything's fine. It only occurs when BAMT is started and I plug and unplug the monitor. If I want to plug back the monitor to check what happens in BAMT, it start working again without problems.
I use the 0.5c version of BAMT.
When I have a monitor plugged in, and I'm fooling around in BAMT, if I unplug the monitor, it makes BAMT crash. Here's what munin shows when I connect to the rig:
Quote
__.....__ .' ':, / __ _ __ \\ | |_)) || |_))|| | | \\ || | || | || _, | status.pl ||.-(_{} | |/ ` | ,_ (;|/) \\| {}_)-,||` \\;/,,;;;;;;;,\\|//, .;;;;;;;;;;;;;;;;, ,;;;;;;;;;;;;;;;;,// \\;;;;;;;;;;;;;;;;,// ,';;;;;;;;;;;;;;;;' One of the BAMT tools has suffered a fatal error. Can't use an undefined value as a HASH reference at /usr/lib/cgi-bin/status.pl line 88. Defiled: Unable to record this travesty in the deathlog! Why?: Permission denied
If I never plug a monitor in BAMT and I boot the rig, everything's fine. It only occurs when BAMT is started and I plug and unplug the monitor. If I want to plug back the monitor to check what happens in BAMT, it start working again without problems.
I use the 0.5c version of BAMT.
Yeah, many of us have had this problem and, as you found out, you mustn't unplug a monitor while BAMT is running. Actually I think it may be a driver issue.
What you may not grok is what that string of punctuation symbols is all about. So I checked through the author's perl scripts. It turns out that if you put appropriate line breaks in and use a fixed width font (which your average web browser does not do, hence the garbling), that's actually a tombstone rendered in ascii art. Because status.pl has died. Geddit?
May 04, 2012, 05:08:27 AM
I've perused this thread, searched, and messed up my BAMT configs a few times now. I've succumbed to asking here, so... Is there any documentation on how to get the whole farm's status showing on one machine? I can't seem to get all of my machines to show up on a single machine's web status page... Giga, I know you've somehow managed to get your farm showing, any tips/tricks/info on how you did this?
https://bitcointalksearch.org/topic/m.864059
that what you need?
May 04, 2012, 12:32:54 AM
Having a strange issue with my rigs today.
Card clocks seem to randomly change, in both directions.
Each rig houses 3 5970s running at 725/250, I noticed to my clocks are jumping all over the board. I randomly have on GPU clocked at 820/300 on one rig and on another, 5 GPUs clocked to 725/1000 and the sixth at 750/250. I did not change these clocks and they have never been set to that.
Card clocks seem to randomly change, in both directions.
Each rig houses 3 5970s running at 725/250, I noticed to my clocks are jumping all over the board. I randomly have on GPU clocked at 820/300 on one rig and on another, 5 GPUs clocked to 725/1000 and the sixth at 750/250. I did not change these clocks and they have never been set to that.
sounds like you overclocked them too much... and your rig/bamt doesn't like it.
reduce your clocks, typically 800/300 works best for all my 5970's...
then try removing the noOCGPUx file:
Quote
: cd /live/image/BAMT/CONTROL/ACTIVE
: ls
(it will display the files needed to be removed, n then you follow by typing for each one)
: rm noOCGPUx
: ls
(it will display the files needed to be removed, n then you follow by typing for each one)
: rm noOCGPUx
once done editing your .config, and removing each one of those files...
go back to gpumon, stop mining, start mining.
hope that helps, as it did for me from. (thanks to Spilrow for schoolin me on that :-) ).
May 04, 2012, 12:20:49 AM
I've perused this thread, searched, and messed up my BAMT configs a few times now. I've succumbed to asking here, so... Is there any documentation on how to get the whole farm's status showing on one machine? I can't seem to get all of my machines to show up on a single machine's web status page... Giga, I know you've somehow managed to get your farm showing, any tips/tricks/info on how you did this?
In putty, connect to one of your rigs and type mgpumon
I've got do_mgpumon: 1 set in bamt.conf on one miner. If I browse to each machine's individual IP, the web interface works as expected, but the one running do_mgpumon: 1 isn't listing anything but it's own stats. I should mention that the IP's are statically set on the 192.168.2.x subnet vs the std. 192.168.0.x
Jump to: