Transisto
Donator
Legendary
 Offline
Activity: 1731
Merit: 1008
|
 |
May 27, 2012, 04:01:44 PM |
|
Debian connection lost problem, Is there a bug report for this on debian's forums ? I would say this has happened / happening on 2/5 of my rigs, It basically just boils down the network-manager package. This software has a bug that seems to effect some systems, just google around and you'll find lots of ubuntu users with the exact same issue. I didn't find any clear explanations or what the proper fix is in a quick search. It does seem to be limited to certain network cards.
rather than removing the network manager entirely (as suggested by the external link), if someone finds an actual fix that would be preferable.
removing the network manager will remove the issue, but it will take away your ability to configure wireless networks (and wired) using the easy gui, so you'll have to edit the network config files by hand. not a big deal if you know how to do that, but not an ideal "fix" in any case. |
|
|
|
|
|
|
|
|
|
Bitcoin mining is now a specialized and very risky industry, just like gold mining. Amateur miners are unlikely to make much money, and may even lose money. Bitcoin is much more than just mining, though!
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
|
|
|
|
bulanula
|
|
May 27, 2012, 07:31:01 PM |
|
Debian connection lost problem, Is there a bug report for this on debian's forums ? I would say this has happened / happening on 2/5 of my rigs, It basically just boils down the network-manager package. This software has a bug that seems to effect some systems, just google around and you'll find lots of ubuntu users with the exact same issue. I didn't find any clear explanations or what the proper fix is in a quick search. It does seem to be limited to certain network cards.
rather than removing the network manager entirely (as suggested by the external link), if someone finds an actual fix that would be preferable.
removing the network manager will remove the issue, but it will take away your ability to configure wireless networks (and wired) using the easy gui, so you'll have to edit the network config files by hand. not a big deal if you know how to do that, but not an ideal "fix" in any case. Remove the network-manager. It is dead simple to change IP config in Debian using CLI. Not worth having this damn bug IMHO |
|
|
|
|
|
abracadabra
|
|
May 28, 2012, 05:32:56 PM |
|
I believe I've been able to find a solution to the rigs losing network connection. I had a few rigs that would disconnect/drop network connection after 6-12 hours. With my fix, the rigs have been running for a bit over 14 hours and they are still running. I want to test for a couple more days and then I'll post something up in this thread. Removing network-manager did not solve the problem for me. Neither was setting a static IP and neither the "fix" detailed here: http://www.bitcointrading.com/forum/index.php?PHPSESSID=528oms2jquas75afn1t6fp45n5&topic=416.msg1235#msg1235This is not a problem due to the rig hardware. I have exact duplicate rigs deployed in multiple locations. I believe it has something to do with the router/dhcp server. I only have this problem when I bring the rigs home to troubleshoot a gpu. When the rigs are deployed offsite to networks with different network hardware, the loss of network connection does not occur. |
|
|
|
|
|
abracadabra
|
|
May 31, 2012, 03:26:41 AM
Last edit: February 25, 2013, 06:16:19 PM by abracadabra |
|
Ok... here's what i've put together with some help from some friends (thx C) - create a check_network.sh in /etc/bamt this script will check for internet connection. if there is none, it will bring the ethernet interface down, wait a bit, then bring it back up.
#! /bin/sh
ping -c1 -W5 google.com > /dev/null || (
echo "down"
ifdown eth0
sleep 5
ifup eth0
) - create a file called crontab in /etc/bamt - this will be a file used to create a crontab entry that will run the check_network.sh script every minute.
* * * * * /etc/bamt/check_network.sh - edit /etc/rc.local to add the following line just before the "exit 0" - upon bootup this will add a crontab entry.
crontab /etc/bamt/crontab - at this point you can reboot, or simply type "crontab /etc/bamt/crontab"
I've been running rigs for over 2 days straight now that would have normally lost connection after only 12 hours. |
|
|
|
|
david113
Member
Offline
Activity: 63
Merit: 10
|
|
May 31, 2012, 04:03:44 PM |
|
Yes please donate to the 7970 & 64bit BAMT fund!!!!
How much BTC´s left to support 7970s?? |
|
|
|
|
|
fuxianhui888
|
|
June 01, 2012, 12:13:21 AM |
|
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?
|
|
|
|
|
|
Red Emerald
|
|
June 01, 2012, 01:01:51 AM |
|
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. |
|
|
|
|
fuxianhui888
|
|
June 01, 2012, 01:21:39 AM |
|
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. # 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: you@yourmail.com
# 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
|
|
|
|
|
ModusPwnd
Member
Offline
Activity: 546
Merit: 10
|
|
June 01, 2012, 04:23:31 AM |
|
My thoughts are to uncomment the mem_0 and mem_1 lines, and then comment out the change in voltage.
|
|
|
|
|
|
likuidxd
|
|
June 01, 2012, 03:22:59 PM |
|
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. # 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: you@yourmail.com
# 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
|
|
|
|
|
Red Emerald
|
|
June 01, 2012, 11:07:33 PM |
|
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. # 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: you@yourmail.com
# 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
You really shouldn't mess with core_speed_0 or core_speed_1, though. |
|
|
|
|
likuidxd
|
|
June 01, 2012, 11:47:40 PM |
|
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. |
|
|
|
|
likuidxd
|
|
June 02, 2012, 10:13:37 PM |
|
Has there been a patch yet for the network issue?
|
|
|
|
|
|
|
likuidxd
|
|
June 03, 2012, 01:39:55 AM |
|
I just set static IPs. I was hoping a fix was up for a few near future rigs
|
|
|
|
|
fuxianhui888
|
|
June 05, 2012, 02:16:19 AM |
|
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!
|
|
|
|
|
|
|
|
lodcrappo (OP)
|
|
June 07, 2012, 06:31:01 PM |
|
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.
|
|
|
|
|
|
Red Emerald
|
|
June 07, 2012, 06:36:18 PM |
|
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/<their user>/.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.
|
|
|
|
|
BitMinerN8
|
|
June 07, 2012, 06:41:15 PM |
|
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/<their user>/.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? |
|
|
|
|
|
