Pages:
Author

Topic: [BOUNTY 5BTC] cgminer: add getwork proxy functionality (Read 8989 times)

sr. member
Activity: 284
Merit: 254
I always met a problem of "Segmentation fault (core dumped)" after running for a while, and the terminal closed automaticly. (ubuntu)

Any ideas?

Crashes happen with any miner now and then. You need to run bfgminer from a looping script to prevent your boards from idling.

I am using this one:
Code:
#!/bin/bash

ROOTDIR="$HOME/usr/bin"
MINER_BIN="$ROOTDIR/bfgminer"
CFG="$ROOTDIR/BEB-bfgminer.conf"
STARTLOG="$ROOTDIR/miner_startlog.txt"
LOG="$ROOTDIR/miner.log"

miner_run() {
MINER="$MINER_BIN --http-port 8332 -Q 50 -c $CFG"
echo "Starting '$MINER' at $(date)..." >> $STARTLOG
$MINER 2>> $LOG
echo "Terminated at $(date)" >> $STARTLOG
}

while true; do
miner_run
sleep 5
done

exit 0

Save this as $HOME/usr/bin/BEB-bfgminer.sh and adapt the related variables for your configuration. Run this script with screen and you have the perfect control over it for local and remote access. To have it started during boot-up, add this line to your /etc/rc.local:
Code:
sudo -u screen -dmS "BEB-bfgminer" /home//usr/bin/BEB-bfgminer.sh

To attach to the miner's screen session, run
Code:
screen -r BEB-bfgminer
to detach from the screen session press .

If you happened to forget detaching and want to attach from a different terminal / location, you can force detaching the previous session and take over with
Code:
screen -rd BEB-bfgminer

Finally, you can follow the log from local or remote sessions with
Code:
tail -f $HOME/usr/bin/miner.log


Happy mining Wink


Thank you zefir ,this is useful to me  Grin
legendary
Activity: 2576
Merit: 1186
ulimit -c unlimited #to enable core dumps Smiley
donator
Activity: 919
Merit: 1000
Crashes aren't a given, but I'd need at least a backtrace to try to debug it :/

Right, fighting the symptoms is always the second best choice.

Problem is, I never found a crash report or core dump while running bfgminer on my Ubuntu system, but from the startlog I know it restarts every now and then (in the order of once per week). Since this happens without interaction, I conclude those must be crashes - which might not be correct.
legendary
Activity: 2576
Merit: 1186
Crashes aren't a given, but I'd need at least a backtrace to try to debug it :/
donator
Activity: 919
Merit: 1000
I always met a problem of "Segmentation fault (core dumped)" after running for a while, and the terminal closed automaticly. (ubuntu)

Any ideas?

Crashes happen with any miner now and then. You need to run bfgminer from a looping script to prevent your boards from idling.

I am using this one:
Code:
#!/bin/bash

ROOTDIR="$HOME/usr/bin"
MINER_BIN="$ROOTDIR/bfgminer"
CFG="$ROOTDIR/BEB-bfgminer.conf"
STARTLOG="$ROOTDIR/miner_startlog.txt"
LOG="$ROOTDIR/miner.log"

miner_run() {
MINER="$MINER_BIN --http-port 8332 -Q 50 -c $CFG"
echo "Starting '$MINER' at $(date)..." >> $STARTLOG
$MINER 2>> $LOG
echo "Terminated at $(date)" >> $STARTLOG
}

while true; do
miner_run
sleep 5
done

exit 0

Save this as $HOME/usr/bin/BEB-bfgminer.sh and adapt the related variables for your configuration. Run this script with screen and you have the perfect control over it for local and remote access. To have it started during boot-up, add this line to your /etc/rc.local:
Code:
sudo -u screen -dmS "BEB-bfgminer" /home//usr/bin/BEB-bfgminer.sh

To attach to the miner's screen session, run
Code:
screen -r BEB-bfgminer
to detach from the screen session press .

If you happened to forget detaching and want to attach from a different terminal / location, you can force detaching the previous session and take over with
Code:
screen -rd BEB-bfgminer

Finally, you can follow the log from local or remote sessions with
Code:
tail -f $HOME/usr/bin/miner.log


Happy mining Wink
sr. member
Activity: 284
Merit: 254
I always met a problem of "Segmentation fault (core dumped)" after running for a while, and the terminal closed automaticly. (ubuntu)

Any ideas?
hero member
Activity: 728
Merit: 500
cryptoshark
yeah but i have 5 blades and solomining shitcoins for fun.

blades goes sick often and then i have to restart them, problem is to keep them in proper numbers i have to turn them on in order it is annoying Smiley

if instead SGW-0 would be SGW-0-workername (from the auth lan blade) it would be much easier for everybody Smiley
donator
Activity: 919
Merit: 1000
i found an error

should be --with-microhttpd
instead of --with-libmicrohttpd

now it works

but workers are SGW0 1 etc
not like in blade user configuration

Workers are just counted up incrementally based on their username - which is very useful since it allows you to partition your farm arbitrary. In my setup, I have 8 racks of blades operating. I give all blades within a rack the same username, resulting in bfgminer treating them as unit, i.e. I see SGW0-7 and immediately know which rack has problems.

In effect, you have a fine-grained statistics chain: each blade reports individual stats; bfgminer reports stats per rack; pool reports global stats. You could even add more intermediate stats layers by connecting bfgminer instances hierarchically, e.g. one main bfgminer serving over getwork server other bfgminers for your sub-domains.
hero member
Activity: 728
Merit: 500
cryptoshark
i found an error

should be --with-microhttpd
instead of --with-libmicrohttpd

now it works

but workers are SGW0 1 etc
not like in blade user configuration
hero member
Activity: 728
Merit: 500
cryptoshark
Are you aware of the build process required to follow (pre-reqs, autogen, configure, make)? If not, be sure to read the READMEs.
thx
yes I have done all pre-reqs

我也遇到了这个问题 ubuntu server ,恳请知道 如何解决?

 CC     bfgminer-httpsrv.o
In file included from httpsrv.c:15:0:
/usr/include/microhttpd.h:497:3: error: unknown type name ‘intptr_t’
/usr/include/microhttpd.h:830:5: error: unknown type name ‘uint64_t’
/usr/include/microhttpd.h:868:46: error: unknown type name ‘uint64_t’
/usr/include/microhttpd.h:893:55: error: unknown type name ‘va_list’
/usr/include/microhttpd.h:1085:57: error: unknown type name ‘uint64_t’
/usr/include/microhttpd.h:1087:57: error: unknown type name ‘MHD_ContentReaderCallback’
/usr/include/microhttpd.h:1197:54: error: unknown type name ‘MHD_PostDataIterator’
make[2]: *** [bfgminer-httpsrv.o] Error 1
make[2]: Leaving directory `/root/bfgminer'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/root/bfgminer'
make: *** [all] Error 2

I am working with Linux.
Code:
$ lsb_release -irc
Distributor ID: Ubuntu
Release: 13.04
Codename: raring

$ uname -a
Linux PC 3.8.0-27-generic #40-Ubuntu SMP Tue Jul 9 00:17:05 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

$ gcc --version
gcc (Ubuntu/Linaro 4.7.3-1ubuntu1) 4.7.3
Copyright (C) 2012 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Just tried with a fresh clone of the GIT repository and it worked.

Step-by-Step:
1. ensure you have the required libs installed
Code:
sudo apt-get install libjansson-dev libmicrohttpd-dev libncurses5-dev uthash-dev libcurl4-openssl-dev

2. clone the GIT repository
Code:
git clone https://github.com/luke-jr/bfgminer.git

3. prepare and build
Code:
cd bfgminer
./autogen.sh
./configure --disable-opencl --disable-bitforce --disable-adl --disable-modminer --disable-ztex --disable-avalon --disable-icarus --disable-modminer --disable-x6500
make

If this fails for you, and you have a different system, please post a bug report at https://github.com/luke-jr/bfgminer/issues




thanks for your post   but 。。。。

root@ubuntu:/home/enki/bfgminer# ./bfgminer -V
bfgminer 3.2.0
root@ubuntu:/home/enki/bfgminer# ./bfgminer --http-port
 [2013-09-10 00:05:35] ./bfgminer: --http-port: unrecognized option

./configure --disable-opencl --disable-bitforce --disable-adl --disable-modminer --disable-ztex --disable-avalon --disable-icarus --disable-modminer --disable-x6500 --with-microhttpd


hi i have newest rasbian and pi512
i have configured with microhttpd
but same result
unrecognized option

bfgminer 3.2.90

to reproduce

git clone https://github.com/luke-jr/bfgminer.git
./autogen.sh
 ./configure --disable-opencl --disable-bitforce --disable-adl --disable-modminer --disable-ztex --disable-avalon --disable-icarus --disable-modminer --disable-x6500 --with-microhttpd
make
./bfgminer --http-port 8332
 [2013-09-27 10:13:16] ./bfgminer: --http-port: unrecognized option

thanks




donator
Activity: 919
Merit: 1000
./configure --disable-opencl --disable-bitforce --disable-adl --disable-modminer --disable-ztex --disable-avalon --disable-icarus --disable-modminer --disable-x6500 --with-microhttpd


Must have been added only lately, was enabled by default initially.

Anyway, from numerous users I know that the getwork server is working quite well on Linux systems. There are / were some issues with specific OS / libmicrohttpd version combinations, but once solved, the efforts pay off immediately. To serve ~150 clients over stratum-proxy, I had to use a dual-Xeon machine - now a tiny netbook does the job.
sr. member
Activity: 284
Merit: 254
Are you aware of the build process required to follow (pre-reqs, autogen, configure, make)? If not, be sure to read the READMEs.
thx
yes I have done all pre-reqs

我也遇到了这个问题 ubuntu server ,恳请知道 如何解决?

 CC     bfgminer-httpsrv.o
In file included from httpsrv.c:15:0:
/usr/include/microhttpd.h:497:3: error: unknown type name ‘intptr_t’
/usr/include/microhttpd.h:830:5: error: unknown type name ‘uint64_t’
/usr/include/microhttpd.h:868:46: error: unknown type name ‘uint64_t’
/usr/include/microhttpd.h:893:55: error: unknown type name ‘va_list’
/usr/include/microhttpd.h:1085:57: error: unknown type name ‘uint64_t’
/usr/include/microhttpd.h:1087:57: error: unknown type name ‘MHD_ContentReaderCallback’
/usr/include/microhttpd.h:1197:54: error: unknown type name ‘MHD_PostDataIterator’
make[2]: *** [bfgminer-httpsrv.o] Error 1
make[2]: Leaving directory `/root/bfgminer'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/root/bfgminer'
make: *** [all] Error 2

I am working with Linux.
Code:
$ lsb_release -irc
Distributor ID: Ubuntu
Release: 13.04
Codename: raring

$ uname -a
Linux PC 3.8.0-27-generic #40-Ubuntu SMP Tue Jul 9 00:17:05 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

$ gcc --version
gcc (Ubuntu/Linaro 4.7.3-1ubuntu1) 4.7.3
Copyright (C) 2012 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Just tried with a fresh clone of the GIT repository and it worked.

Step-by-Step:
1. ensure you have the required libs installed
Code:
sudo apt-get install libjansson-dev libmicrohttpd-dev libncurses5-dev uthash-dev libcurl4-openssl-dev

2. clone the GIT repository
Code:
git clone https://github.com/luke-jr/bfgminer.git

3. prepare and build
Code:
cd bfgminer
./autogen.sh
./configure --disable-opencl --disable-bitforce --disable-adl --disable-modminer --disable-ztex --disable-avalon --disable-icarus --disable-modminer --disable-x6500
make

If this fails for you, and you have a different system, please post a bug report at https://github.com/luke-jr/bfgminer/issues




thanks for your post   but 。。。。

root@ubuntu:/home/enki/bfgminer# ./bfgminer -V
bfgminer 3.2.0
root@ubuntu:/home/enki/bfgminer# ./bfgminer --http-port
 [2013-09-10 00:05:35] ./bfgminer: --http-port: unrecognized option

./configure --disable-opencl --disable-bitforce --disable-adl --disable-modminer --disable-ztex --disable-avalon --disable-icarus --disable-modminer --disable-x6500 --with-libmicrohttpd
newbie
Activity: 46
Merit: 0
Are you aware of the build process required to follow (pre-reqs, autogen, configure, make)? If not, be sure to read the READMEs.
thx
yes I have done all pre-reqs

我也遇到了这个问题 ubuntu server ,恳请知道 如何解决?

 CC     bfgminer-httpsrv.o
In file included from httpsrv.c:15:0:
/usr/include/microhttpd.h:497:3: error: unknown type name ‘intptr_t’
/usr/include/microhttpd.h:830:5: error: unknown type name ‘uint64_t’
/usr/include/microhttpd.h:868:46: error: unknown type name ‘uint64_t’
/usr/include/microhttpd.h:893:55: error: unknown type name ‘va_list’
/usr/include/microhttpd.h:1085:57: error: unknown type name ‘uint64_t’
/usr/include/microhttpd.h:1087:57: error: unknown type name ‘MHD_ContentReaderCallback’
/usr/include/microhttpd.h:1197:54: error: unknown type name ‘MHD_PostDataIterator’
make[2]: *** [bfgminer-httpsrv.o] Error 1
make[2]: Leaving directory `/root/bfgminer'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/root/bfgminer'
make: *** [all] Error 2

I am working with Linux.
Code:
$ lsb_release -irc
Distributor ID: Ubuntu
Release: 13.04
Codename: raring

$ uname -a
Linux PC 3.8.0-27-generic #40-Ubuntu SMP Tue Jul 9 00:17:05 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

$ gcc --version
gcc (Ubuntu/Linaro 4.7.3-1ubuntu1) 4.7.3
Copyright (C) 2012 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Just tried with a fresh clone of the GIT repository and it worked.

Step-by-Step:
1. ensure you have the required libs installed
Code:
sudo apt-get install libjansson-dev libmicrohttpd-dev libncurses5-dev uthash-dev libcurl4-openssl-dev

2. clone the GIT repository
Code:
git clone https://github.com/luke-jr/bfgminer.git

3. prepare and build
Code:
cd bfgminer
./autogen.sh
./configure --disable-opencl --disable-bitforce --disable-adl --disable-modminer --disable-ztex --disable-avalon --disable-icarus --disable-modminer --disable-x6500
make

If this fails for you, and you have a different system, please post a bug report at https://github.com/luke-jr/bfgminer/issues




thanks for your post   but 。。。。

root@ubuntu:/home/enki/bfgminer# ./bfgminer -V
bfgminer 3.2.0
root@ubuntu:/home/enki/bfgminer# ./bfgminer --http-port
 [2013-09-10 00:05:35] ./bfgminer: --http-port: unrecognized option
full member
Activity: 126
Merit: 100
ok thx for explanation all clear now Wink
donator
Activity: 919
Merit: 1000
ye from what i can see on bitminter site in "latest shifts" speed is the same like with stratum proxy
only one whats bothering me is blade stats page
with stratum total speed = 13xxx and 99 efficiency but with bfgminer its 12600-12800 with 96 efficiency ;p

Ah, that you mean.

Look into the source code: in driver-getwork.c:handle_getwork() you see how results are processed. The blades sometimes send submit request with empty work field (unclear why this happens), which are counted as HW errors and rejected as 'unknown-work'. Then there are those 'H-not-zero' rejects with a wrong nonce, plus the 'stale' ones.

I assume that the stratum-proxy does not reject some of them (e.g. the empty ones) and since the efficiency provided by the blades is the ratio of accepted to requested work items it differs between bfgminer and stratum-proxy (with bfgminer being more accurate).

My long term values for efficiency reported by blades is 96.4% and matches the expected numbers quite well.
full member
Activity: 126
Merit: 100
ye from what i can see on bitminter site in "latest shifts" speed is the same like with stratum proxy
only one whats bothering me is blade stats page
with stratum total speed = 13xxx and 99 efficiency but with bfgminer its 12600-12800 with 96 efficiency ;p
donator
Activity: 919
Merit: 1000
with --queue 10 had many rejected shares too (3%)
i think its ok now with --no-submit-stale option.
it still shows at bfgminer stats A:1733 R:0+87(2.2%) but at least im not sending that shares to the mine
whats strange with that option stats on blade config panel showing normal stats like total mhz 13k and efficency 99

My blades settled at 2.3% after running for a week, and to me it seems perfectly accurate.

Since the blades do not support LP, each time a block is found you get up to 32 stales (since each chip processes its own full nonce range). At 336 MHz, each chip needs 12.8 seconds for a full nonce range, so on average wastes 6.4 seconds per block change. With currently one block found every 440s, the theoretical loss is somewhere at 1.5% already - not too far from the measured stats.
full member
Activity: 126
Merit: 100
with --queue 10 had many rejected shares too (3%)
i think its ok now with --no-submit-stale option.
it still shows at bfgminer stats A:1733 R:0+87(2.2%) but at least im not sending that shares to the mine
whats strange with that option stats on blade config panel showing normal stats like total mhz 13k and efficency 99

edit: after like 2h its again same as before 12700-12800 ;p so no diference too

dont know why so many stales on bfgminer but not with stratum proxy
donator
Activity: 919
Merit: 1000
it works almost perfect Wink
but i have much more rejected shares than on stratum proxy and blades stats page shows speed like 12600-12700 when on stratum proxy it was 13xxx
and efficiency is 96.5 now, on stratum proxy it was like 99 Wink
i think maybe its bcouse 2 blades im getting much rejected shares (stale)
im trying same user on both blades

edit: yes with same user on both blades it works ok no more rejected shares

edit2: yes confirmed

again 2 diferent users = again some rejected (stale) shares

for now it works perfect only if u set same user/pw on all blades (no stale rejected shares)

Hm, sounds like an issue I observed when debug log displays work-item queue underruns.

In my case it helped to increase the the work-item queue, you could try adding e.g.
Code:
--queue 10
to the parameter list or put it into the config file.
full member
Activity: 126
Merit: 100
it works almost perfect Wink
but i have much more rejected shares than on stratum proxy and blades stats page shows speed like 12600-12700 when on stratum proxy it was 13xxx
and efficiency is 96.5 now, on stratum proxy it was like 99 Wink
i think maybe its bcouse 2 blades im getting much rejected shares (stale)
im trying same user on both blades

edit: yes with same user on both blades it works ok no more rejected shares

edit2: yes confirmed

again 2 diferent users = again some rejected (stale) shares

for now it works perfect only if u set same user/pw on all blades (no stale rejected shares)
Pages:
Jump to: