Help with "Could not get mining infos" errors in creepMiner 1.5.2


  • Mod



  • @groupthug sometimes (for example at the beginning of a new block) the pool server is under heavy load and can't process your mining info request.
    If you get deadlines, everything is ok and you don't need to worry about it :)
    But if you get a lot of "Could not get mining infos 5/5 times..." messages, something is not working properly.



  • @Creepsky45 Unfortunately my log files are filled with these messages right now. Any suggestions? Should I turn up the level of debug in the miner.conf file?



  • I got a similar

    16:47:48: Could not get block infos!
    16:51:49: Could not get block infos!
    16:55:49: Could not get block infos!
    16:59:50: Could not get block infos!
    17:03:51: Could not get block infos!
    17:07:52: Could not get block infos!
    17:11:52: Could not get block infos!
    17:15:53: Could not get block infos!
    17:19:54: Could not get block infos!
    17:23:54: Could not get block infos!
    17:27:55: Could not get block infos!
    
    


  • @bugduino if youre pool mining your pool could be down.

    @groupthug sorry for not answering, lost this thread out of my eyes. Do you still have this problem? This could also be a problem of the pool (ddos).



  • yeah probably i'm mining at http://pool.burstcoin.eu and it seems down.


  • admin

    @bugduino was down - back up now.



  • @Creepsky45 Hi, I am getting these (below), every few seconds, always 1/5 never even 2/5. 1.6.0 downloaded off github as binary. Pool seems alive and fine otherwise.

    Something is wrong with mining.conf?

            "miningInfo" : "http://pool.burstmining.club:8124",
            "submission" : "http://pool.burstmining.club:8124",
    

    Thaaanks! :)

    16:54:39: Dir /mnt/8t1/plots read (6 files, 6.20 TB total) in 5.988s (~264.99 MB/s)
    16:54:42: Could not get mining infos 1/5 times...
    16:54:48: Could not get mining infos 1/5 times...
    16:54:55: Could not get mining infos 1/5 times...
    16:55:01: Could not get mining infos 1/5 times...
    16:55:07: Could not get mining infos 1/5 times...
    16:55:13: Could not get mining infos 1/5 times...
    16:55:19: Could not get mining infos 1/5 times...
    16:55:25: Could not get mining infos 1/5 times...
    16:55:32: Could not get mining infos 1/5 times...
    16:55:38: Could not get mining infos 1/5 times...
    16:55:44: Could not get mining infos 1/5 times...
    16:55:50: Could not get mining infos 1/5 times...
    16:55:56: Could not get mining infos 1/5 times...
    16:56:02: Could not get mining infos 1/5 times...
    16:56:09: Could not get mining infos 1/5 times...
    16:56:15: Could not get mining infos 1/5 times...
    16:56:21: Could not get mining infos 1/5 times...
    16:56:27: Could not get mining infos 1/5 times...
    16:56:33: Could not get mining infos 1/5 times...
    16:56:39: Could not get mining infos 1/5 times...
    16:56:46: Could not get mining infos 1/5 times...
    16:56:52: Could not get mining infos 1/5 times...
    16:56:58: Could not get mining infos 1/5 times...
    16:57:04: Could not get mining infos 1/5 times...
    16:57:10: Could not get mining infos 1/5 times...
    16:57:16: Could not get mining infos 1/5 times...
    16:57:23: Could not get mining infos 1/5 times...
    16:57:29: Could not get mining infos 1/5 times...
    16:57:35: Could not get mining infos 1/5 times...
    16:57:41: Could not get mining infos 1/5 times...
    16:57:47: Could not get mining infos 1/5 times...
    16:57:53: Could not get mining infos 1/5 times...
    16:58:00: Could not get mining infos 1/5 times...
    16:58:06: Could not get mining infos 1/5 times...
    16:58:12: Could not get mining infos 1/5 times...
    16:58:18: Could not get mining infos 1/5 times...
    16:58:24: Could not get mining infos 1/5 times...
    16:58:30: Could not get mining infos 1/5 times...
    16:58:37: Could not get mining infos 1/5 times...
    16:58:43: Could not get mining infos 1/5 times...



  • @laydeals That is a good question, thats something i noticed some time ago while testing a bugfix on this pool.
    Somehow the server decides not to respond on every get mining info request - it just closes the connection.

    My theory is that there is an anti-flood-algorithm, that blocks requests that have not a particular amount of time between them.

    I will look at it and report back.



  • I changed pool from "ninja" to "club" 25 min ago - with there min DL I only had two confirmed DLs in two days on a different miner (earned 4!!!), so never really seen any confirmed DLs in creepminer. Two minutes ago - first confirmed DL in Creep! It works despite these messages! Thanks for the comment! @Creepsky45


Log in to reply
 

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