Read-only forum archive. PROHASHING has closed. Posting, registration, and account access are unavailable. Preserved from the April 3, 2026 server backup.

Password Arguments

creiss
Archived posts: 3
Joined: Oct 07, 2017

Password Arguments

by creiss · · Post #10414

Hey folks,

I am unable to set the password arguments inside a Bitmain device. Using

Code:

n=myminer01
works like a charm. Adding more parameters fails, like

Code:

n=myminer01 m=solo c=litecoin
If I hit "Save & Apply" the config (/etc/config/cgminer) is being rewritten but the extra spaces in between make it fail. A start/restart does nothing (except trying to start the miner). Enabling "set -x" inside the script and launching it results in:

Code:

+ START=99
+ APP=cgminer
+ PID_FILE=/var/run/cgminer.pid
+ [ -n  ]
+ ALL_COMMANDS=start stop reload restart boot shutdown enable disable enabled depends 
+ list_contains ALL_COMMANDS start
+ local var=ALL_COMMANDS
+ local str=start
+ local val
+ eval val=" ${ALL_COMMANDS} "
+ val= start stop reload restart boot shutdown enable disable enabled depends  
+ [  !=  start stop reload restart boot shutdown enable disable enabled depends   ]
+ [ start = reload ]
+ start
+ [ ! -d /sys/class/gpio/gpio27 ]
+ echo out
+ echo 0
+ sleep 1
+ echo 1
+ local _pool1url
+ local _pool1user
+ local _pool2url
+ local _pool2user
+ local _pool3url
+ local _pool3user
+ local _freq
+ config_load cgminer
+ [ -n  ]
+ uci_load cgminer
+ local PACKAGE=cgminer
+ local DATA
+ local RET
+ local VAR
+ _C=0
+ [ -z  ]
+ export -n CONFIG_LIST_STATE=
+ export -n CONFIG_SECTIONS=
+ export -n CONFIG_NUM_SECTIONS=0
+ export -n CONFIG_SECTION=
+ /sbin/uci -P /var/state -S -n export cgminer
+ DATA=package cgminer

config cgminer 'default'
        option freq '600:300:0b83'
        option api_allow 'W:0/0'
        option pool1user 'antuser'
        option pool_balance '  '
        option pool1url 'stratum+tcp://prohashing.com:3333'
        option pool2user 'antuser'
        option pool2url 'stratum+tcp://proxy.prohashing.com:443'
        option pool1pw 'n=antrouter1 c=litecoin m=solo'
        option pool2pw 'n=antrouter2 c=litecoin m=solo'
+ RET=0
+ [ 0 != 0 -o -z package cgminer

config cgminer 'default'
        option freq '600:300:0b83'
        option api_allow 'W:0/0'
        option pool1user 'antuser'
        option pool_balance '  '
        option pool1url 'stratum+tcp://prohashing.com:3333'
        option pool2user 'antuser'
        option pool2url 'stratum+tcp://proxy.prohashing.com:443'
        option pool1pw 'n=antrouter1 c=litecoin m=solo'
        option pool2pw 'n=antrouter2 c=litecoin m=solo' ]
+ eval package cgminer

config cgminer 'default'
        option freq '600:300:0b83'
        option api_allow 'W:0/0'
        option pool1user 'antuser'
        option pool_balance '  '
        option pool1url 'stratum+tcp://prohashing.com:3333'
        option pool2user 'antuser'
        option pool2url 'stratum+tcp://proxy.prohashing.com:443'
        option pool1pw 'n=antrouter1 c=litecoin m=solo'
        option pool2pw 'n=antrouter2 c=litecoin m=solo'
+ package cgminer
+ return 0
+ config cgminer default
+ local cfgtype=cgminer
+ local name=default
+ export -n CONFIG_NUM_SECTIONS=1
+ name=default
+ append CONFIG_SECTIONS default
+ local var=CONFIG_SECTIONS
+ local value=default
+ local sep= 
+ eval export -n -- "CONFIG_SECTIONS=${CONFIG_SECTIONS:+${CONFIG_SECTIONS}${value:+$sep}}$value"
+ export -n -- CONFIG_SECTIONS=default
+ [ -n  ]
+ config_cb cgminer default
+ return 0
+ export -n CONFIG_SECTION=default
+ export -n CONFIG_default_TYPE=cgminer
+ option freq 600:300:0b83
+ local varname=freq
+ shift
+ local value=600:300:0b83
+ export -n CONFIG_default_freq=600:300:0b83
+ [ -n  ]
+ option_cb freq 600:300:0b83
+ return 0
+ option api_allow W:0/0
+ local varname=api_allow
+ shift
+ local value=W:0/0
+ export -n CONFIG_default_api_allow=W:0/0
+ [ -n  ]
+ option_cb api_allow W:0/0
+ return 0
+ option pool1user antuser
+ local varname=pool1user
+ shift
+ local value=antuser
+ export -n CONFIG_default_pool1user=antuser
+ [ -n  ]
+ option_cb pool1user antuser
+ return 0
+ option pool_balance   
+ local varname=pool_balance
+ shift
+ local value=  
+ export -n CONFIG_default_pool_balance=  
+ [ -n  ]
+ option_cb pool_balance   
+ return 0
+ option pool1url stratum+tcp://prohashing.com:3333
+ local varname=pool1url
+ shift
+ local value=stratum+tcp://prohashing.com:3333
+ export -n CONFIG_default_pool1url=stratum+tcp://prohashing.com:3333
+ [ -n  ]
+ option_cb pool1url stratum+tcp://prohashing.com:3333
+ return 0
+ option pool2user antuser
+ local varname=pool2user
+ shift
+ local value=antuser
+ export -n CONFIG_default_pool2user=antuser
+ [ -n  ]
+ option_cb pool2user antuser
+ return 0
+ option pool2url stratum+tcp://proxy.prohashing.com:443
+ local varname=pool2url
+ shift
+ local value=stratum+tcp://proxy.prohashing.com:443
+ export -n CONFIG_default_pool2url=stratum+tcp://proxy.prohashing.com:443
+ [ -n  ]
+ option_cb pool2url stratum+tcp://proxy.prohashing.com:443
+ return 0
+ option pool1pw n=antrouter1 c=litecoin m=solo
+ local varname=pool1pw
+ shift
+ local value=n=antrouter1 c=litecoin m=solo
+ export -n CONFIG_default_pool1pw=n=antrouter1 c=litecoin m=solo
+ [ -n  ]
+ option_cb pool1pw n=antrouter1 c=litecoin m=solo
+ return 0
+ option pool2pw n=antrouter2 c=litecoin m=solo
+ local varname=pool2pw
+ shift
+ local value=n=antrouter2 c=litecoin m=solo
+ export -n CONFIG_default_pool2pw=n=antrouter2 c=litecoin m=solo
+ [ -n  ]
+ option_cb pool2pw n=antrouter2 c=litecoin m=solo
+ return 0
+ unset DATA
+ config_cb
+ return 0
+ return 0
+ config_get _aa default api_allow
+ eval export -n -- _aa=${CONFIG_default_api_allow:-${4}}
+ export -n -- _aa=W:0/0
+ config_get _freq default freq
+ eval export -n -- _freq=${CONFIG_default_freq:-${4}}
+ export -n -- _freq=600:300:0b83
+ config_get _pool1url default pool1url
+ eval export -n -- _pool1url=${CONFIG_default_pool1url:-${4}}
+ export -n -- _pool1url=stratum+tcp://prohashing.com:3333
+ config_get _pool1user default pool1user
+ eval export -n -- _pool1user=${CONFIG_default_pool1user:-${4}}
+ export -n -- _pool1user=antuser
+ config_get _pool1pw default pool1pw
+ eval export -n -- _pool1pw=${CONFIG_default_pool1pw:-${4}}
+ export -n -- _pool1pw=n=antrouter1 c=litecoin m=solo
+ config_get _pool2url default pool2url
+ eval export -n -- _pool2url=${CONFIG_default_pool2url:-${4}}
+ export -n -- _pool2url=stratum+tcp://proxy.prohashing.com:443
+ config_get _pool2user default pool2user
+ eval export -n -- _pool2user=${CONFIG_default_pool2user:-${4}}
+ export -n -- _pool2user=antuser
+ config_get _pool2pw default pool2pw
+ eval export -n -- _pool2pw=${CONFIG_default_pool2pw:-${4}}
+ export -n -- _pool2pw=n=antrouter2 c=litecoin m=solo
+ config_get _pool3url default pool3url
+ eval export -n -- _pool3url=${CONFIG_default_pool3url:-${4}}
+ export -n -- _pool3url=
+ config_get _pool3user default pool3user
+ eval export -n -- _pool3user=${CONFIG_default_pool3user:-${4}}
+ export -n -- _pool3user=
+ config_get _pool3pw default pool3pw
+ eval export -n -- _pool3pw=${CONFIG_default_pool3pw:-${4}}
+ export -n -- _pool3pw=
+ [ stratum+tcp://prohashing.com:3333 !=  -a antuser !=  -a n=antrouter1 c=litecoin m=solo !=  ]
+ POOL1=-o stratum+tcp://prohashing.com:3333 -O antuser:n=antrouter1 c=litecoin m=solo
+ [ stratum+tcp://proxy.prohashing.com:443 !=  -a antuser !=  -a n=antrouter2 c=litecoin m=solo !=  ]
+ POOL2=-o stratum+tcp://proxy.prohashing.com:443 -O antuser:n=antrouter2 c=litecoin m=solo
+ [  !=  -a  !=  -a  !=  ]
+ source /etc/init.d/usr_bak
+ temp_file=/tmp/temp_usr.txt
+ user_mtd=/dev/mtdblock6
+ hexdump -v -n 3 -e 1/1 "%02x" /dev/mtdblock6
hexdump: /dev/mtdblock6: No such file or directory
+ magic_str=
+ magic=
+ usr_file=/etc/config/cgminer
+ [ != 97 ]
sh: 97: unknown operand
+ user_pos=
+ let user_pos=0x
/etc/rc.common: let: line 1: arithmetic syntax error
+ echo
+ user_pos=
+ dd of=/tmp/temp_usr.txt if=/dev/mtdblock6 bs=1 count=100 skip=
dd: invalid number ''
+ sed -n 1p /tmp/temp_usr.txt
sed: /tmp/temp_usr.txt: No such file or directory
+ fl_user=
+ echo

+ sed -n 2p /tmp/temp_usr.txt
sed: /tmp/temp_usr.txt: No such file or directory
+ fl_cg_ctrl=
+ [  !=  -o  !=  ]
+ AOPTIONS=--antrouter-options 115200:600:300:0b83
+ PARAMS=--antrouter-options 115200:600:300:0b83 -o stratum+tcp://prohashing.com:3333 -O antuser:n=antrouter1 c=litecoin m=solo -o stratum+tcp://proxy.prohashing.com:443 -O antuser:n=antrouter2 c=litecoin m=solo  --api-listen --scrypt --api-allow W:0/0  --version-file /usr/bin/compile_time --queue 50
+ cgminer --lowmem --bitmain-options 115200:600:300:0b83 -q
+ sleep 1
+ touch /tmp/cgminer-ntpd-done
+ cnt=0
+ [ ! -f /tmp/cgminer-ntpd-done ]
+ start-stop-daemon -S -x cgminer -p /var/run/cgminer.pid -m -- --antrouter-options 115200:600:300:0b83 -o stratum+tcp://prohashing.com:3333 -O antuser:n=antrouter1 c=litecoin m=solo -o stratum+tcp://proxy.prohashing.com:443 -O antuser:n=antrouter2 c=litecoin m=solo --api-listen --scrypt --api-allow W:0/0 --version-file /usr/bin/compile_time --queue 50
 [2017-10-07 12:10:15] Unexpected extra commandline arguments
The "-O antuser:n=antrouter2 c=litecoin m=solo" makes it fail;

It only works when I have exactly one password argument and no space in between it. I am using stock, unmodified Bitmain Software, testing on an Antrouter R1-LTC with current firmware.

What I tried:
- re-flashing the device with current firmware,
- replacing the spaces with other seperators like ".", ";"
- Adding single quotes to the $_pool1pw variables inside /etc/init.d/cgminer

I am out of my wits. Help. <3

-Chris.
Rabinovitch
Archived posts: 2
Joined: Oct 11, 2017

Re: Password Arguments

by Rabinovitch · · Post #10635

May be it's possible to change the password options format? For example an "U" character between password options instead of spaces? It that case any user (even with Bitmain miner, like me) will able to mine in solo. I also tried to set up Dash solo mining, and the firmware of my D3 replaced " with %20.
DaddyFreedom
Archived posts: 6
Joined: Oct 11, 2017

Re: Password Arguments

by DaddyFreedom · · Post #10642

I'm a new miner, and started mining with pro hashing with my L3+ Antminer the other day, and manage to figure out what to put in the password field, I used d=16384 and manage to mine for about 18 hours, until the Average Mining Efficiancy clock went to Zero, and from then on my miner was active, but it wasn't mining anything. Why did that happened? And now I don't know what to do to get it back up and running again mining with a 98% efficiency again. I've tried different things in the password field, even leaving it blank, but unsuccessfully still cannot make it run to mine.
Can anyone in this forum help me please? Thanks.
AppleMiner avatar
AppleMiner
Archived posts: 715
Joined: Sep 30, 2017

Re: Password Arguments

by AppleMiner · · Post #10653

When you were messing with settings trying to get it to work again, did you maybe enable the API key requirement?
If so, you have to add the k= password or it wont connect to your miner account's username.

try to change the username to: joejoe
on the miner and click apply, give it 2 mins and check the status. If you can connect in on the joejoe account someone setup for us to try testing on then the miner works fine on the pool, and you have settings on your account you need to disable or supply the info for to get them to work.

Hope that helps or gets you in the right direction.
DaddyFreedom
Archived posts: 6
Joined: Oct 11, 2017

Re: Password Arguments

by DaddyFreedom · · Post #10663

Thanks for your response AppleMiner. I just finished answering the other post comment you responded to. And yes that might be the problem, the API key requirement, as per memory I don't remember setting anything like that. I will have a look at that, once I'm back from work, later on the day.
Thank you. Cheers! :-)
berardo
Archived posts: 1
Joined: Jan 22, 2018

Re: Password Arguments

by berardo · · Post #15780

Did you ever figure this out? I'm having the same issue with my R1-LTC. I can enter single password arguments without issue, but as soon as I try to input multiple, I can not get to work. I've checked everything previously suggested in this post.