Pages:
Author

Topic: BAMT version 0.5 - Easy USB based mining Linux with farm wide management tools - page 35. (Read 324169 times)

hero member
Activity: 616
Merit: 506
Still looking for a proper fix to the networking thing, by proper I mean without reducing functionality.

Anyone that comes up with one, please let me know and we'll push out a fix.


I experienced the network issue for the last couple days. We fixed it by setting infinite leases for ip addresses. I know this doesn't fix the issue, but it at least keeps miners running.

well crap..  if i remove the network manager that seems to be causing this, the people with wireless devices will cry.  but atm thats the only "fix", besides setting static ips which sucks.

ps did anyone ever get a machine that does this that I can ssh into while it's broke (second nic that works)?


vip
Activity: 1358
Merit: 1000
AKA: gigavps
Still looking for a proper fix to the networking thing, by proper I mean without reducing functionality.

Anyone that comes up with one, please let me know and we'll push out a fix.


I experienced the network issue for the last couple days. We fixed it by setting infinite leases for ip addresses. I know this doesn't fix the issue, but it at least keeps miners running.
sr. member
Activity: 367
Merit: 250
I'm trying out BAMT right now. This far, it works great!
hero member
Activity: 616
Merit: 506
So someone was able to login to my box and create users.  I'm not sure how they did it as I have a rather long root password.  They made multiple users and then fetched a file "gosh.tgz" and extracted it in /tmp/ and /dev/shm/ and /home//.bash_history/

The location was different for each user.  gosh contains some scripts and BNC, an IRC bouncer.  They also stuck an entry in root's cron to run a script in /dev/shm/ to clear the user's history.

I'm going to build a new BAMT key, but for now I just looked at the histories of all of the new users (except the one that replaced .bash_history with a folder) to figure out where they stuck files and then deleted all the new users (easy to identify in /etc/passwd) and then edited /etc/sshd_config to only allow root without-password, so now my miner can only be logged into with a key.  

How much of the system was exposed to the internet? Like all ports or were you doing some port forwarding?
port 22 and 80 are all that are open. It's running ufw

I'm guessing they either cracked my root password or somehow broke in through munin.

It was clearly a person and not a script.  There were typos in .bash_history lol.  Things like ";s" instead of "ls"

Well the various scripts and whatnot are certainly not well audited for security flaws.  we don't have the budget for that type of thing Smiley

the good news is that short of disrupting your mining (which hopefully you would notice) there isn't really anything someone can do with a compromised box.  not like we store any actual btc or any credentials that matter on them.  bamt rigs are designed to be "disposable" not indestructible.
hero member
Activity: 742
Merit: 500
So someone was able to login to my box and create users.  I'm not sure how they did it as I have a rather long root password.  They made multiple users and then fetched a file "gosh.tgz" and extracted it in /tmp/ and /dev/shm/ and /home//.bash_history/

The location was different for each user.  gosh contains some scripts and BNC, an IRC bouncer.  They also stuck an entry in root's cron to run a script in /dev/shm/ to clear the user's history.

I'm going to build a new BAMT key, but for now I just looked at the histories of all of the new users (except the one that replaced .bash_history with a folder) to figure out where they stuck files and then deleted all the new users (easy to identify in /etc/passwd) and then edited /etc/sshd_config to only allow root without-password, so now my miner can only be logged into with a key.  

How much of the system was exposed to the internet? Like all ports or were you doing some port forwarding?
port 22 and 80 are all that are open. It's running ufw

I'm guessing they either cracked my root password or somehow broke in through munin.

It was clearly a person and not a script.  There were typos in .bash_history lol.  Things like ";s" instead of "ls"
hero member
Activity: 626
Merit: 500
Mining since May 2011.
So someone was able to login to my box and create users.  I'm not sure how they did it as I have a rather long root password.  They made multiple users and then fetched a file "gosh.tgz" and extracted it in /tmp/ and /dev/shm/ and /home//.bash_history/

The location was different for each user.  gosh contains some scripts and BNC, an IRC bouncer.  They also stuck an entry in root's cron to run a script in /dev/shm/ to clear the user's history.

I'm going to build a new BAMT key, but for now I just looked at the histories of all of the new users (except the one that replaced .bash_history with a folder) to figure out where they stuck files and then deleted all the new users (easy to identify in /etc/passwd) and then edited /etc/sshd_config to only allow root without-password, so now my miner can only be logged into with a key. 

How much of the system was exposed to the internet? Like all ports or were you doing some port forwarding?
hero member
Activity: 742
Merit: 500
So someone was able to login to my box and create users.  I'm not sure how they did it as I have a rather long root password.  They made multiple users and then fetched a file "gosh.tgz" and extracted it in /tmp/ and /dev/shm/ and /home//.bash_history/

The location was different for each user.  gosh contains some scripts and BNC, an IRC bouncer.  They also stuck an entry in root's cron to run a script in /dev/shm/ to clear the user's history.

I'm going to build a new BAMT key, but for now I just looked at the histories of all of the new users (except the one that replaced .bash_history with a folder) to figure out where they stuck files and then deleted all the new users (easy to identify in /etc/passwd) and then edited /etc/sshd_config to only allow root without-password, so now my miner can only be logged into with a key. 
hero member
Activity: 616
Merit: 506
Still looking for a proper fix to the networking thing, by proper I mean without reducing functionality.

Anyone that comes up with one, please let me know and we'll push out a fix.
full member
Activity: 205
Merit: 100
I got another problem,I am using powerline ,but after couple hours,the  network  disconnected, and it won't reconnect,I have to do it manually,anybody has anycode can check the connection and can reconnect automatically?
thanks everyone!


solved loss network problem by following this link:
http://www.bitcointrading.com/forum/index.php?topic=416.msg1235#msg1235

still testing
full member
Activity: 205
Merit: 100
I got another problem,I am using powerline ,but after couple hours,the  network  disconnected, and it won't reconnect,I have to do it manually,anybody has anycode can check the connection and can reconnect automatically?
thanks everyone!
sr. member
Activity: 476
Merit: 500
I just set static IPs. I was hoping a fix was up for a few near future rigs
hero member
Activity: 626
Merit: 500
Mining since May 2011.
Has there been a patch yet for the network issue?
No official BAMT patch, just this workaround:
https://bitcointalksearch.org/topic/m.932044
sr. member
Activity: 476
Merit: 500
Has there been a patch yet for the network issue?
sr. member
Activity: 476
Merit: 500
You really shouldn't mess with core_speed_0 or core_speed_1, though.

I know it's a no no, but I'm a control and order freak. I'd of deleted all the other crap if I knew fuxianhui888 wasn't going to use it too.

fuxianhui888, if you want just put # in front of core_speed_0-1 and mem_speed_0-1.
hero member
Activity: 742
Merit: 500
sr. member
Activity: 476
Merit: 500
Give her a shot, I think your clocks are either too high or you have a fussy GPU in there (probably GPU_0) that doesn't want to play nice.

Code:
# Big A Miner Thing configuration
# /etc/bamt/bamt.conf


---
settings:

  miner_id: bamt-miner
  miner_loc: unspecified location
  do_monitor: 0

  # if monitoring, how do we send email alerts?

  # these are required..

  # smtp_host: smtp.gmail.com
  # smtp_to: [email protected]
 
  # these are optional..

  # smtp_from: somefrom@address
  # smtp_subject: I wanted a custom subject in my alerts...
  # smtp_port: 587
  # smtp_auth_user: user@where
  # smtp_auth_pass: secret
  # smtp_tls: 1
  # smtp_ssl: 1

gpu0:
  disabled: 0
  # pre_oc_cmd:

  core_speed_0: 300
  core_speed_1: 800
  core_speed_2: 850
  mem_speed_0: 300
  mem_speed_1: 300
  mem_speed_2: 300
  # core_voltage_0: 1.125
  # core_voltage_1: 1.125
  # core_voltage_2: 1.125000
 
  fan_speed: 40

  # post_oc_cmd:

  kernel: phatk2
  kernel_params: BFI_INT VECTORS FASTLOOP=false AGGRESSION=9

  pool_file: /etc/bamt/pools
  pool_timeout: 180

  monitor_temp_lo: 45
  monitor_temp_hi: 80
  monitor_load_lo: 80
  monitor_hash_lo: 125
  monitor_fan_lo: 2000
  monitor_reject_hi: 2

gpu1:
  disabled: 0

  core_speed_0: 300
  core_speed_1: 800
  core_speed_2: 850
  mem_speed_0: 300
  mem_speed_1: 300
  mem_speed_2: 300
  # core_voltage_0: 1.125
  # core_voltage_1: 1.125
  # core_voltage_2: 1.125000

  fan_speed: 30

  kernel: phatk2
  kernel_params: BFI_INT VECTORS FASTLOOP=false AGGRESSION=11

  pool_file: /etc/bamt/pools
  pool_timeout: 180

  monitor_temp_lo: 45
  monitor_temp_hi: 80
  monitor_load_lo: 80
  monitor_hash_lo: 125
  monitor_fan_lo: 2000
  monitor_reject_hi: 1

gpu2:
  disabled: 0

  core_speed_0: 300
  core_speed_1: 800
  core_speed_2: 850
  mem_speed_0: 300
  mem_speed_1: 300
  mem_speed_2: 300
  # core_voltage_0: 1.125
  # core_voltage_1: 1.125
  # core_voltage_2: 1.125000

  fan_speed: 30

  kernel: phatk2
  kernel_params: BFI_INT VECTORS FASTLOOP=false AGGRESSION=11

  pool_file: /etc/bamt/pools
  pool_timeout: 180

  monitor_temp_lo: 45
  monitor_temp_hi: 80
  monitor_load_lo: 80
  monitor_hash_lo: 125
  monitor_fan_lo: 2000
  monitor_reject_hi: 1

gpu3:
  disabled: 0
 
  core_speed_0: 300
  core_speed_1: 800
  core_speed_2: 850
  mem_speed_0: 300
  mem_speed_1: 300
  mem_speed_2: 300
  # core_voltage_0: 1.125
  # core_voltage_1: 1.125
  # core_voltage_2: 1.125000

  fan_speed: 35

  kernel: phatk2
  kernel_params: BFI_INT VECTORS FASTLOOP=false AGGRESSION=11

  pool_file: /etc/bamt/pools
  pool_timeout: 180

  monitor_temp_lo: 45
  monitor_temp_hi: 80
  monitor_load_lo: 80
  monitor_hash_lo: 125
  monitor_fan_lo: 2000
  monitor_reject_hi: 1

gpu4:
  disabled: 0

  core_speed_0: 300
  core_speed_1: 800
  core_speed_2: 850
  mem_speed_0: 300
  mem_speed_1: 300
  mem_speed_2: 300
  # core_voltage_0: 1.125
  # core_voltage_1: 1.125
  # core_voltage_2: 1.125000

  fan_speed: 40

  kernel: phatk2
  kernel_params: BFI_INT VECTORS FASTLOOP=false AGGRESSION=11

  pool_file: /etc/bamt/pools
  pool_timeout: 180

  monitor_temp_lo: 45
  monitor_temp_hi: 80
  monitor_load_lo: 80
  monitor_hash_lo: 125
  monitor_shares_lo: 1

member
Activity: 546
Merit: 10
My thoughts are to uncomment the mem_0 and mem_1 lines, and then comment out the change in voltage.
full member
Activity: 205
Merit: 100
I tried to run 5 5870 with BAMT,but after couple minutes,OS would crashed(mouse doesn't move,keyboard doesn't work,stop mining,no network),anybody has any ideas?
Post your config.  Are you overclocking? If so, reduce your clocks.

Code:
# Big A Miner Thing configuration
# /etc/bamt/bamt.conf
#
# When done editing, restart mining to make changes here take effect
# If you're just setting up BAMT, be sure to edit pools as well.
#
# As of 0.5, many less common options have been removed from this
# default config to make it easier on the noobs.
#
# You will find a complete example with all options described
# at /opt/bamt/examples/bamt.conf
#
# Note: This is a YAML file.  Indentation is significant.
#
# If you break things badly, a backup of this file in it's original
# form can be found at /opt/bamt/examples/bamt.conf.simple
#


---
settings:

  # miner_id is used to set hostname and identify this rig to munin and
  # other processes
  # IMPORTANT! miner_id must be a valid hostname: all lower case, no weird
  # characters, underscores, periods, or spaces. Dash and numbers are ok.

  miner_id: bamt-miner

  # loc is any additional string you wish to use to identify or group this rig

  miner_loc: unspecified location

  # should we monitor the cards? 1 = yes, 0 = no

  do_monitor: 0

  # if monitoring, how do we send email alerts?

  # these are required..

  # smtp_host: smtp.gmail.com
  # smtp_to: [email protected]
 
  # these are optional..

  # smtp_from: somefrom@address
  # smtp_subject: I wanted a custom subject in my alerts...
  # smtp_port: 587
  # smtp_auth_user: user@where
  # smtp_auth_pass: secret
  # smtp_tls: 1
  # smtp_ssl: 1

 
 
# GPU Configurtation

# You'll need one gpuX: section per GPU installed.  Not sure what's installed,
# or the order?  Open a root shell and type:  aticonfig --list-adapters
#
# You can delete gpu sections if you don't have that many cards.. or add more
# if you find a way to run them



gpu0:

  # remove disabled: or set it to 0 to actually use this card..

  disabled: 0

 
  # overclocking.. all are optional 

  # optional command to execute prior to overclocking
  # any valid command (or the path to a script) is fine

  # pre_oc_cmd:


  # (core/mem)_X = the value to set for this profile (0-2)
  # Profile 2 is used while mining, but setting values
  # in profile 2 that are *lower* than the values in the other
  # profiles is not allowed on some GPUs, so you have to adjust
  # the other profiles as well.
  # For instance, to get 300Mhz mem clock on my 5830s, I have
  # to set all 3 profiles to 300.


  # core_speed_0: 300
  # core_speed_1: 800
  # core_speed_2: 980
  core_speed_2: 900
  # mem_speed_0: 300
  # mem_speed_1: 300
  # mem_speed_2: 300
  mem_speed_2: 300
  # core_voltage_0: 1.125
  # core_voltage_1: 1.125
  # core_voltage_2: 1.125000
  core_voltage_2: 1.05
  # recommend to set and forget fan, preferably at 100
 
  fan_speed: 40

  # optional command to execute after overclocking
  # post_oc_cmd:


  # Phoenix mining setup (see full example for how to use cgminer instead)
  # We strongly recommend you use phoenix at, least until you are familiar
  # with BAMT

  # kernel to use.. one of:  phatk phatk2 poclbm
  # if in doubt, use phatk2

  kernel: phatk2

  # phoenix style kernel params.  *do not* include DEVICE=x, otherwise
  # exactly same as any phoenix setup. 
  # if in doubt: BFI_INT VECTORS AGGRESSION=11
  # (though 9 on GPU0 often makes using the GUI more pleasant)

  kernel_params: BFI_INT VECTORS FASTLOOP=false AGGRESSION=9


  # Pool file

  # IMPORTANT: pool_file must contain a list of pool URLs.. one at least, more if
  # you like.  You can share the same file for all GPUs, or have one for each.
  # Miner will start with first URL in file, however if no shares are accepted
  # for any reason in (pool_timeout) seconds, the miner will move to next URL
  # in the file.  Wraps around to first URL when last one fails.
  # You can also set pool specific values, see the example pools file.
  # if in doubt: /etc/bamt/pools

  pool_file: /etc/bamt/pools

  # max time to allow phoenix to run without finding a share..
  # exceed this and we kill phoenix, start a new instance with
  # next line in pools file

  pool_timeout: 180



  # monitoring limits, used by email alerts and gpumon
  # an alert is generated if the current value goes below a 'lo'
  # or above a 'hi'.

  # GPU temp sensor reading (in C)
  monitor_temp_lo: 45
  monitor_temp_hi: 80

  # GPU load (in %)
  monitor_load_lo: 80

  # average hashrate (in mh/s)
  monitor_hash_lo: 125

  # fam rpm (in rpm)
  monitor_fan_lo: 2000

  # effective reject rate (in % of total)
  monitor_reject_hi: 2



# OK.. hopefully you get the idea.  Stubs for additional GPUs below.
# There are many additional paramters to help you deal with various
# scenarios, see /opt/bamt/examples and the docs (if we write some)


gpu1:
  disabled: 0
  # core_speed_0: 300
  # core_speed_1: 800
  # core_speed_2: 1060
  core_speed_2: 900
  # mem_speed_0: 300
  # mem_speed_1: 300
  # mem_speed_2: 1120
  mem_speed_2: 300
  # core_voltage_0: 1.125
  # core_voltage_1: 1.125
  # core_voltage_2: 1.125000
  core_voltage_2: 1.05
  fan_speed: 30

  kernel: phatk2
  kernel_params: BFI_INT VECTORS FASTLOOP=false AGGRESSION=11

  pool_file: /etc/bamt/pools
  pool_timeout: 180

  monitor_temp_lo: 45
  monitor_temp_hi: 80
  monitor_load_lo: 80
  monitor_hash_lo: 125
  monitor_fan_lo: 2000
  monitor_reject_hi: 1


gpu2:
  disabled: 0

  # core_speed_0: 300
  # core_speed_1: 800
  # core_speed_2: 980
  core_speed_2: 900
  # mem_speed_0: 300
  # mem_speed_1: 300
  # mem_speed_2: 300
  mem_speed_2: 300
  # core_voltage_0: 1.125
  # core_voltage_1: 1.125
  # core_voltage_2: 1.125000
  core_voltage_2: 1.05
  fan_speed: 30

  kernel: phatk2
  kernel_params: BFI_INT VECTORS FASTLOOP=false AGGRESSION=11

  pool_file: /etc/bamt/pools
  pool_timeout: 180

  monitor_temp_lo: 45
  monitor_temp_hi: 80
  monitor_load_lo: 80
  monitor_hash_lo: 125
  monitor_fan_lo: 2000
  monitor_reject_hi: 1



gpu3:
  disabled: 0
 
  # core_speed_0: 300
  # core_speed_1: 800
  # core_speed_2: 980
  core_speed_2: 900
  # mem_speed_0: 300
  # mem_speed_1: 300
  # mem_speed_2: 300
  mem_speed_2: 300
  # core_voltage_0: 1.125
  # core_voltage_1: 1.125
  # core_voltage_2: 1.125000
  core_voltage_2: 1.05
  fan_speed: 35

  kernel: phatk2
  kernel_params: BFI_INT VECTORS FASTLOOP=false AGGRESSION=11

  pool_file: /etc/bamt/pools
  pool_timeout: 180

  monitor_temp_lo: 45
  monitor_temp_hi: 80
  monitor_load_lo: 80
  monitor_hash_lo: 125
  monitor_fan_lo: 2000
  monitor_reject_hi: 1


gpu4:
  disabled: 0

  # core_speed_0: 300
  # core_speed_1: 800
  # core_speed_2: 980
  core_speed_2: 900
  # mem_speed_0: 300
  # mem_speed_1: 300
  # mem_speed_2: 300
  mem_speed_2: 300
  # core_voltage_0: 1.125
  # core_voltage_1: 1.125
  # core_voltage_2: 1.125000
  core_voltage_2: 1.05
  fan_speed: 40

  kernel: phatk2
  kernel_params: BFI_INT VECTORS FASTLOOP=false AGGRESSION=11

  pool_file: /etc/bamt/pools
  pool_timeout: 180

  monitor_temp_lo: 45
  monitor_temp_hi: 80
  monitor_load_lo: 80
  monitor_hash_lo: 125
  monitor_shares_lo: 1


gpu5:
  disabled: 1

  # core_speed_0: 300
  # core_speed_1: 800
  # core_speed_2: 980
  core_speed_2: 900
  # mem_speed_0: 300
  # mem_speed_1: 300
  # mem_speed_2: 300
  mem_speed_2: 300
  # core_voltage_0: 1.125
  # core_voltage_1: 1.125
  # core_voltage_2: 1.125000
  core_voltage_2: 1.05
  fan_speed: 50

  kernel: phatk2
  kernel_params: BFI_INT VECTORS FASTLOOP=false AGGRESSION=11

  pool_file: /etc/bamt/pools
  pool_timeout: 180

  monitor_temp_lo: 45
  monitor_temp_hi: 80
  monitor_load_lo: 80
  monitor_hash_lo: 125
  monitor_shares_lo: 1


gpu6:
  disabled: 1

  # core_speed_0: 300
  # core_speed_1: 800
  # core_speed_2: 980
  # mem_speed_0: 300
  # mem_speed_1: 300
  # mem_speed_2: 300
  # core_voltage_0: 1.125
  # core_voltage_1: 1.125
  # core_voltage_2: 1.125000

  fan_speed: 100

  kernel: phatk2
  kernel_params: BFI_INT VECTORS FASTLOOP=false AGGRESSION=11

  pool_file: /etc/bamt/pools
  pool_timeout: 180

  monitor_temp_lo: 45
  monitor_temp_hi: 80
  monitor_load_lo: 80
  monitor_hash_lo: 125
  monitor_shares_lo: 1


gpu7:
  disabled: 1

  # core_speed_0: 300
  # core_speed_1: 800
  # core_speed_2: 980
  # mem_speed_0: 300
  # mem_speed_1: 300
  # mem_speed_2: 300
  # core_voltage_0: 1.125
  # core_voltage_1: 1.125
  # core_voltage_2: 1.125000

  fan_speed: 100

  kernel: phatk2
  kernel_params: BFI_INT VECTORS FASTLOOP=false AGGRESSION=11

  pool_file: /etc/bamt/pools
  pool_timeout: 180

  monitor_temp_lo: 45
  monitor_temp_hi: 80
  monitor_load_lo: 80
  monitor_hash_lo: 125
  monitor_shares_lo: 1

hero member
Activity: 742
Merit: 500
I tried to run 5 5870 with BAMT,but after couple minutes,OS would crashed(mouse doesn't move,keyboard doesn't work,stop mining,no network),anybody has any ideas?
Post your config.  Are you overclocking? If so, reduce your clocks.
full member
Activity: 205
Merit: 100
I tried to run 5 5870 with BAMT,but after couple minutes,OS would crashed(mouse doesn't move,keyboard doesn't work,stop mining,no network),anybody has any ideas?
Pages:
Jump to: