[HiveOS] Ne récupérer que les logs sur les " incorrect share "

  • -

    Salut à tous,

    J’aimerais récupérer en ligne de commande sur Hiveos l’ensemble des erreurs des GPU afin de vérifier si je dois agir ou pas, car de temps à autre j’ai un message d’erreur.

    GPU #1 got incorrect share. If you see this warning often, make sure you did not overclock it too much!

    Merci d’avance pour votre aide.

    maccoin 1 Reply
  • -

    @maccoin

    tail -n 1000 incorrect share* /var/log/miner/claymore/lastrun_noappend.log

    J’y suis presque…😵

  • -

    cat /var/log/miner/claymore/lastrun_noappend.log | grep “incorrect”

    maccoin 1 Reply
  • -

    @impassenet
    Merci🙂

  • -

    Du coup j’ai des erreurs… 1 par heure env. et toujours sur le meme GPU ! c’est passable à ton avis ?

    root@rig:~# cat /var/log/miner/claymore/lastrun_noappend.log | grep “incorrect share”
    22:09:33:796 eec15700 GPU #1 got incorrect share. If you see this warning often, make sure you did not overclock it too much!
    23:18:42:005 ef416700 GPU #1 got incorrect share. If you see this warning often, make sure you did not overclock it too much!
    00:48:57:941 ef416700 GPU #1 got incorrect share. If you see this warning often, make sure you did not overclock it too much!
    01:26:06:688 ef416700 GPU #1 got incorrect share. If you see this warning often, make sure you did not overclock it too much!
    02:29:46:257 eec15700 GPU #1 got incorrect share. If you see this warning often, make sure you did not overclock it too much!
    05:39:55:846 eec15700 GPU #1 got incorrect share. If you see this warning often, make sure you did not overclock it too much!
    07:36:12:425 ef416700 GPU #1 got incorrect share. If you see this warning often, make sure you did not overclock it too much!
    08:15:37:539 eec15700 GPU #1 got incorrect share. If you see this warning often, make sure you did not overclock it too much!
    08:54:43:754 eec15700 GPU #1 got incorrect share. If you see this warning often, make sure you did not overclock it too much!
    root@rig:~#

  • -

    Baisse juste la MEM de 10 ou 20 sur cette GPU.

  • -

    Merci 😉 et bonne journée.

  • -

    À votre avis c’est normal que les devfee aillent sur dwarfpool alors que je mine sur Nanopool ?

    09:51:09:743 6b7fe700 DevFee: ETH: Stratum - connecting to ‘eth-eu.dwarfpool.com’ <188.165.34.183> port 8008
    09:51:09:768 6b7fe700 DevFee: ETH: Stratum - Connected (eth-eu.dwarfpool.com:8008)
    09:51:32:074 6b7fe700 DevFee: ETH: 02/27/18-09:51:32 - New job from eth-eu.dwarfpool.com:8008
    09:51:46:025 6b7fe700 DevFee: ETH: 02/27/18-09:51:46 - New job from eth-eu.dwarfpool.com:8008
    10:51:09:914 6b7fe700 DevFee: ETH: Stratum - connecting to ‘eth-eu.dwarfpool.com’ <164.132.140.111> port 8008
    10:51:09:937 6b7fe700 DevFee: ETH: Stratum - Connected (eth-eu.dwarfpool.com:8008)
    11:51:10:094 6b7fe700 DevFee: ETH: Stratum - connecting to ‘eth-eu.dwarfpool.com’ <91.134.112.222> port 8008
    11:51:10:117 6b7fe700 DevFee: ETH: Stratum - Connected (eth-eu.dwarfpool.com:8008)
    11:51:23:053 6b7fe700 DevFee: ETH: 02/27/18-11:51:23 - New job from eth-eu.dwarfpool.com:8008
    11:51:30:723 6b7fe700 DevFee: ETH: 02/27/18-11:51:30 - New job from eth-eu.dwarfpool.com:8008
    11:51:44:035 6b7fe700 DevFee: ETH: 02/27/18-11:51:44 - New job from eth-eu.dwarfpool.com:8008
    12:51:10:263 6b7fe700 DevFee: ETH: Stratum - connecting to ‘eth-eu.dwarfpool.com’ <87.98.182.61> port 8008
    12:51:10:297 6b7fe700 DevFee: ETH: Stratum - Connected (eth-eu.dwarfpool.com:8008)
    12:51:18:003 6b7fe700 DevFee: ETH: 02/27/18-12:51:17 - New job from eth-eu.dwarfpool.com:8008
    12:51:20:586 6b7fe700 DevFee: ETH: 02/27/18-12:51:20 - New job from eth-eu.dwarfpool.com:8008
    12:51:43:182 6b7fe700 DevFee: ETH: 02/27/18-12:51:43 - New job from eth-eu.dwarfpool.com:8008
    12:51:45:881 6b7fe700 DevFee: ETH: 02/27/18-12:51:45 - New job from eth-eu.dwarfpool.com:8008

  • -

    Ça commence à rentrer … manque plus qu’à pouvoir archiver et mettre en forme.

    cat /var/log/miner/claymore/lastrun_noappend.log | grep “SHARE FOUND”

    cat /var/log/miner/claymore/lastrun_noappend.log | grep “incorrect share”

    cat /var/log/miner/claymore/lastrun_noappend.log | grep “Total Shares”

    cat /var/log/miner/claymore/lastrun_noappend.log | grep “DevFee”

  • -

    impassenet 1 Reply
  • -

    @maccoin Pour les devfee oui il a ses propres pool de configurés dans le miner.
    Sinon claymore a une api aussi au lieu de regarder les logs.

Log in to reply