creepMiner - C++ Burst Miner (based on Uray's Miner)



  • @Creepsky45

    Thank you Creepsky!

    Can I ask another question, I'm CPU mining with an i7 and 3 drives (2 internal) 1 external (usb2).

    I have forged 2 blocks in just over 2 weeks but most of my deadlines are being found at 20+ days or longer.

    Would faster drives help or am I going to need a GPU?

    Does CreepMiner use the GPU automatically? or is there a setting I missed?

    Cheers!


  • admin

    @scprv55 To forge more blocks you need more capacity - ie more drives.



  • @haitch

    Thanks Haitch, I'm going to buy a new drive (maybe today), but I'm trying to figure out if it is just drive capacity that I'm lacking or if its also a speed thing.

    Should I get a USB 3 port upgrade or is USB2 enough?

    Should I not bother with external drive (USB2 is all my PC has) and instead hook them up using Sata 2

    Is it worth upgrading my motherboard to one that has SATA 3?

    Appreciate everyone's help!


  • admin

    @scprv55 How long does it take you to mine all the drives? USB3 is more desirable than USB2, but if it's what you have - it's what you have.

    My latest rig has SATA2, for 20 drives. it's not as fast as I'd like, but it's fast enough.



  • @haitch

    500 GB USB 3 drive but on a USB port

    read (3 files, 460.00 GB total) in 3.870s (~29.71 MB/s)

    1 TB internal on SATA
    read (4 files, 870.00 GB total) in 4.013s (~54.19 MB/s)

    2TB internal on SATA
    read (6 files, 1.49 TB total) in 4.886s (~78.03 MB/s)

    All plots (except 2) are optimized


  • admin

    @scprv55 You're reading them all in less than 5 seconds, mine take around 60 seconds. You cpu/gpu is not your bottleneck, just continue to add capacity.



  • @haitch

    Thanks Haitch, that clears things up.

    Basically I didn't want to spend on drives if there was something else I could do to speed things up first.

    Better go out this afternoon and buy myself at least 4TB of extra space.


  • admin

    @scprv55 When you mining time goes over 60 seconds, consider looking at better mining processing power.



  • Hello @Creepsky45,

    Just joined the burst mining ranks and chose to give a go to creepminer.
    Thanks for all the work and time you put in it.

    I have a couple of questions, which I'm hoping you guys will be able to clear up for me:

    1. Is it normal that in the lower part of the miner window I constantly see a lot of +++ followed by 66% ? I mean, the miner seems to be working (timestamps get updated and I get nonce confirmations) but that percentage never increases. Does it have any particular meaning or is it just my miner acting out?
      Here's a snapshot of it:
    23:41:59: Dir /media/minertux/Burst4 read (2 files, 7.28 TB total) in 0.000s (~35.52 TB/s)
    23:41:59: minertux: nonce found (10d 18:47:50)                                  
    23:41:59:       nonce: 614466                                                   
    23:41:59:       in: /media/minertux/Burst2/13492061662977583734_0_30457856_30457856
    23:41:59: minertux: nonce on the way (10d 18:47:50)                             
    23:41:59: minertux: nonce submitted (10d 18:47:50)                              
    23:41:59:       nonce: 614466                                                   
    23:41:59:       in /media/minertux/Burst2/13492061662977583734_0_30457856_30457856
    23:42:14: Dir /media/minertux/Burst1 read (2 files, 7.27 TB total) in 15.195s (~122.54 MB/s)
    23:42:15: Dir /media/minertux/Burst2 read (1 files, 7.26 TB total) in 15.936s (~116.65 MB/s)
    23:42:22: minertux: nonce confirmed (10d 18:47:50)                              
    23:42:22:       nonce: 614466                                                   
    23:42:22:       in /media/minertux/Burst2/13492061662977583734_0_30457856_30457856
    23:42:22: [+++++++++++++++++++++++++++++++-----------------] 66%
    
    
    1. If I add another plotted drive to config file paths, do I need to restart the miner before it start to be read by the miner?
    2. From what I understand, once plotted the drives only need to be read (assuming dedicated disk drives of course). Am I correct to assume that I can mount the disks as read-only (to prevent any accidental deletion of plotfiles) or would that impede the miner somehow?

    Specs:

    • HW platform: Z270 Extreme4 + i3 7100 + 16 GB RAM
    • GPU: Nvidia GTX 1060
    • OS: Ubuntu 17.04
    • GPU driver in use: Nvidia proprietary 375.66
    • Primary graphics adapter: Intel CPU integrated --> output to monitor

    Not sure what else might be of use.
    Thanks for any input.



  • Hi @Creepsky45, thanks a lot for this miner!!!

    Total mining noob here :)

    I install/configured creepminer on Centos 7, compiled using these instructions: https://github.com/Creepsky/creepMiner/wiki/Compilation-&-Installation-on-CentOS. I have a 537GB plot. Everything seems to be working fine except the GUI.

    I configured the gui to be available on localhost, port 8080, this is a headless server so to connect to the gui for security reasons I do port forwarding using ssh like this:

    ssh -L 8081:localhost:8080 [email protected]

    Then type localhost:8081 on my browser, which works (displays the page). However, the page comes up with just the blue bar, the creepminer logo and no info at all (every box is blank). Here is a reference screenshot: http://prntscr.com/ft2r7c

    To run the miner, I run: "nohup ./run.sh &" that way I can see the output on nohup.out on the same folder I have the creepminer compiled binary in (and creepminer won't exit when I close my shell).

    Is there a reason for the lack of data on the gui?

    Here is my mining.conf (feel free to make other suggestions as well :D ):

    {
        "logging" : {
            "config" : "information",
            "general" : "information",
            "miner" : "information",
            "nonceSubmitter" : "information",
            "output" : {
                "dirDone" : true,
                "lastWinner" : true,
                "nonceConfirmed" : true,
                "nonceFound" : true,
                "nonceOnTheWay" : true,
                "nonceSent" : true,
                "plotDone" : false
            },
            "path" : "/var/log/",
            "plotReader" : "information",
            "plotVerifier" : "information",
            "server" : "fatal",
            "session" : "error",
            "socket" : "off",
            "wallet" : "information"
        },
        "mining" : {
            "intensity" : 3,
            "maxBufferSizeMB" : 700,
            "maxPlotReaders" : 0,
            "passphrase" : {
                "algorithm" : "aes-256-cbc",
                "decrypted" : "",
                "deleteKey" : false,
                "encrypted" : "",
                "iterations" : 0,
                "key" : "",
                "salt" : ""
            },
            "plots" : [
                "/burst/plots"
            ],
            "submissionMaxRetry" : 3,
            "targetDeadline" : "0",
            "timeout" : 45,
            "urls" : {
                "miningInfo" : "http://pool.burstcoin.ml:8124",
                "submission" : "http://pool.burstcoin.ml:8124",
                "wallet" : "http://localhost:8125"
            }
        },
        "webserver" : {
            "credentials" : {
                "hashed-pass" : "",
                "hashed-user" : "",
                "plain-pass" : "",
                "plain-user" : ""
            },
            "start" : true,
            "url" : "http://localhost:8080"
        }
    

    Another thing I just noticed:
    for some reason after ~1:45 hours of the miner running, It just stops sending nonces and only shows this output:

    01:16:42: Dir /burst/plots read (1 files, 500.39 GB total) in 9.187s (~13.62 MB/s)
    01:17:43: --------------------------------------------------
    01:17:43: block#      379480
    01:17:43: scoop#      1061
    01:17:43: baseTarget# 219645
    01:17:43: --------------------------------------------------
    01:17:43: --------------------------------------------------
    01:17:43: last block winner:
    01:17:43: block#             379479
    01:17:43: winner-numeric     11057109464612582920
    01:17:43: winner-address     HFJA-H8EF-ESC5-BYPWL
    01:17:43: --------------------------------------------------
    01:17:52: Dir /burst/plots read (1 files, 500.39 GB total) in 8.893s (~14.07 MB/s)
    01:17:59: --------------------------------------------------
    01:17:59: block#      379481
    01:17:59: scoop#      2485
    01:17:59: baseTarget# 191737
    01:17:59: --------------------------------------------------
    01:17:59: --------------------------------------------------
    01:17:59: last block winner:
    01:17:59: block#             379480
    01:17:59: winner-numeric     10276640676891941155
    01:17:59: winner-address     LQB5-9XM9-9WGY-AQH9X
    01:17:59: winner-name        Kanzas
    01:17:59: --------------------------------------------------
    01:18:08: Dir /burst/plots read (1 files, 500.39 GB total) in 9.565s (~13.08 MB/s)
    

    Software info:

    [[email protected] bin]# head -100 /var/log/creepMiner_20170707_205158.157623.log
    07.07.2017 20:51:58 (0, src/main.cpp, 47, Information): creepMiner 1.5.2 Unix x64
    07.07.2017 20:51:58 (0, src/main.cpp, 48, Information): ----------------------------------------------
    07.07.2017 20:51:58 (0, src/main.cpp, 49, Information): Github:   https://github.com/Creepsky/creepMiner
    07.07.2017 20:51:58 (0, src/main.cpp, 50, Information): Author:   Creepsky [[email protected]]
    07.07.2017 20:51:58 (0, src/main.cpp, 51, Information): Burst :   BURST-JBKL-ZUAV-UXMB-2G795
    07.07.2017 20:51:58 (0, src/main.cpp, 52, Information): ----------------------------------------------
    07.07.2017 20:51:58 (0, src/main.cpp, 53, Information): Based on http://github.com/uraymeiviar/burst-miner
    07.07.2017 20:51:58 (0, src/main.cpp, 54, Information): author : uray meiviar [ [email protected] ]
    07.07.2017 20:51:58 (0, src/main.cpp, 55, Information): please donate to support developments :
    07.07.2017 20:51:58 (0, src/main.cpp, 56, Information):  [ Burst   ] BURST-8E8K-WQ2F-ZDZ5-FQWHX
    07.07.2017 20:51:58 (0, src/main.cpp, 57, Information):  [ Bitcoin ] 1UrayjqRjSJjuouhJnkczy5AuMqJGRK4b
    07.07.2017 20:51:58 (0, src/main.cpp, 58, Information): ----------------------------------------------
    07.07.2017 20:51:58 (0, src/main.cpp, 72, Information): using config file mining.conf
    07.07.2017 20:51:59 (0, src/MinerConfig.cpp, 314, Information): Changing path for log file to
    	/var/log/creepMiner_20170707_205158.157623.log
    07.07.2017 20:52:02 (0, src/MinerConfig.cpp, 597, Debug): Reading passphrase...
    07.07.2017 20:52:02 (0, src/Miner.cpp, 51, Information): Total plots size: 500.39 GB
    07.07.2017 20:52:02 (0, src/Miner.cpp, 53, Information): Submission Max Retry : 3
    07.07.2017 20:52:02 (0, src/Miner.cpp, 55, Information): Buffer Size : 700 MB
    07.07.2017 20:52:02 (0, src/Miner.cpp, 58, Information): Pool Host : http://pool.burstcoin.ml:8124 (173.212.236.124)
    07.07.2017 20:52:02 (0, src/Miner.cpp, 61, Information): Mininginfo URL : http://pool.burstcoin.ml:8124 (173.212.236.124)
    07.07.2017 20:52:02 (0, src/Miner.cpp, 64, Information): Wallet URL : http://localhost:8125 (::1)
    07.07.2017 20:52:02 (0, src/Miner.cpp, 67, Information): Server URL : http://192.168.0.23:8080 (186.176.50.117)
    07.07.2017 20:52:02 (0, src/Miner.cpp, 70, Information): Mining intensity : 3
    07.07.2017 20:52:02 (0, src/Miner.cpp, 71, Information): Max plot readers : 1
    07.07.2017 20:52:02 (0, src/Miner.cpp, 73, Information): Log path : /var/log/creepMiner_20170707_205158.157623.log
    07.07.2017 20:52:06 (0, src/Miner.cpp, 174, Debug): Verification queue cleared.
    07.07.2017 20:52:06 (0, src/Miner.cpp, 194, Notice): --------------------------------------------------
    

    Killing the process (pkill creepMiner) and starting it again solves it, but we all know it sucks having to babysit a process :)

    Hope you can look into this!


Log in to reply
 

Looks like your connection to Burst - Efficient HDD Mining was lost, please wait while we try to reconnect.