optiminer wont start after pimpup? Workaround for this problem!


  • Staff

    Some folks have reported issues with Optiminer refusing to start after a pimpup. The error normally looks like this:

    [/root]:# pimp --start 5
    Starting command line miner on localhost
    bin: optiminer-equihash 
    conf: optiminer.equihash.pcfg
    Using port 4032...
    Miner screen exited - the mining program failed to start.
    Please use 'pimp --test' or 'pimp --debug' to troubleshoot this error
    

    If you any miner has issues, its best to run it in debug mode, and you can see the issues pretty easy. For this problem, the issue shows up like this:

    [/root]:# pimp --debug 5
    Starting miner ID 5 without screen for debugging. 
    For normal operation, stop the miner using Control+C, 
    then start it using 'pimp --start 5' or the minerfarm agent console.
    Executing: /opt/miners/optiminer-equihash/optiminer-equihash -s us-east.equihash-hub.miningpoolhub.com:20570 -u anjin.pimp1 -p x  --nodevfee -a equihash200_9 -v
    [2018-03-03 14:59:34.215] [default] [info] Optiminer/Equihash 2.1.2 (C) Optiminer 2017
    [2018-03-03 14:59:34.216] [default] [info] Connecting to us-east.equihash-hub.miningpoolhub.com:20570.
    [2018-03-03 14:59:34.255] [default] [warning] Running in slower --nodevfee mode!
    [2018-03-03 14:59:34.255] [default] [info] Using 2 verifier threads.
    [2018-03-03 14:59:34.255] [default] [info] Using highly optimized kernel code for Baffin devices.
    [2018-03-03 14:59:34.255] [default] [info] Reading bianry kernel from bin-223600/Equihash200_9-Baffin.bin
    [2018-03-03 14:59:34.255] [default] [error] Failed to read bin-223600/Equihash200_9-Baffin.bin
    

    From the debug output, you can see the directory the miner application lives in. Simply cd to that directory, and then start the miner. In this case, the command would be cd /opt/miners/optiminer-equihash

    
    [/opt/miners/optiminer-equihash]:# pimp --debug 5
    Starting miner ID 5 without screen for debugging. 
    For normal operation, stop the miner using Control+C, 
    then start it using 'pimp --start 5' or the minerfarm agent console.
    Executing: /opt/miners/optiminer-equihash/optiminer-equihash -s us-east.equihash-hub.miningpoolhub.com:20570 -u anjin.pimp1 -p x  --nodevfee -a equihash200_9 -v
    [2018-03-03 15:01:55.171] [default] [info] Optiminer/Equihash 2.1.2 (C) Optiminer 2017
    [2018-03-03 15:01:55.171] [default] [info] Connecting to us-east.equihash-hub.miningpoolhub.com:20570.
    [2018-03-03 15:01:55.230] [default] [warning] Running in slower --nodevfee mode!
    [2018-03-03 15:01:55.230] [default] [info] Using 2 verifier threads.
    [2018-03-03 15:01:55.230] [default] [info] Using highly optimized kernel code for Baffin devices.
    [2018-03-03 15:01:55.230] [default] [info] Reading bianry kernel from bin-223600/Equihash200_9-Baffin.bin
    [2018-03-03 15:01:55.230] [default] [info] Autodetected '--intensity 4' for device 0.
    [2018-03-03 15:01:55.320] [default] [info] Extranonce is '0200106a'.
    [2018-03-03 15:01:55.390] [default] [info] Mining target is 0001000000000000000000000000000000000000000000000000000000000000
    [2018-03-03 15:01:55.390] [default] [info] Got new work.
    [2018-03-03 15:01:55.504] [default] [info] Connected to us-east.equihash-hub.miningpoolhub.com:20570.
    

    We will work with the developer to refix this bug, and deploy a new copy via pimpup as normal. Our apologies that this slipped past our beta testing. Hopefully this work around gets you back up and mining again quickly and with little effort.

    Once the miner is running, you can cd back to your home directory and carry on as normal.

    Good luck and happy mining!


  • Support

    Still no fix as of today.


  • Staff

    We did ask him over a year ago to fix it. He said no.


  • Support

    Simple fix: Use Claymore's ZCash AMD GPU Miner v12.6 instead. LOL


 



Want 10% more hash from your rigs?



We promise to keep your email safe and never spam you.



Copyright (c) 2017 PiMP LLC. All rights Reserved.

Looks like your connection to PiMP Forum was lost, please wait while we try to reconnect.