Missed Ticket

Discussion in 'Proof-of-stake Mining' started by Btu, Jul 5, 2016.

  1. 2017/12/15 - Decred v1.1.2 released! → Release Notes  → Downloads
  1. Btu

    Btu New Member

    Jan 1, 2016
    27
    2
    Male
    #1 Btu, Jul 5, 2016
    Last edited: Jul 24, 2016
    A few weeks ago I had bought 13 tickets when the price was about 25dcr with the default fee. I have been checking once in a while and this is the msg I get when I enter:
    dcrclt -u [username] -P [password] --wallet getstakeinfo


    "revoked": 0
    "proportionmissed": 1,
    "missed": 1,
    "totalsubsidy": 0,
    "voted": 0,
    "proportionlive": 0.0002886766580865549,
    "live": 12,
    "immature": 0,
    "ownmempooltix": 0,
    "allmempooltix": 6,
    "difficulty": 26.10253614,
    "poolsize": 41569,

    Is there a reason why I missed a ticket? If I did, is it now lost. Also could it be because every 60 blocks or so I get this message:
    "Failed to purchase tickets this round: Wallet not connected to daemon"

    Also what does allmempooltix mean? It used to be less.


    ERROR FIXED. ALL GOOD. I wasn't running wallet with --enablestakemining and the error message fixed when I upgraded the server a bit.
     
  2. Halestorm

    Halestorm Jr. Member

    Jan 22, 2016
    83
    32
    Male
    Data Center
    Texas, USA
    That would indeed be the root of your problem. dcrd is either not running, froze up, or for some reason dcrwallet isn't connecting to it properly. Check the status of dcrd and restart if necessary, then restart dcrwallet to get it reconnected to dcrd. Read the messages as each program starts up to watch for errors. Also don't forget to unlock your wallet, otherwise it can't vote.

    It's the number of all tickets purchased by decred users awaiting being mined into a block. If you had just purchased tickets they would show up under "ownmempooltix" until they got mined, then you'd see them as "immature" for 256 blocks until they go live.
     
  3. Btu

    Btu New Member

    Jan 1, 2016
    27
    2
    Male
    I restarted everything, and now I get 1 error message and inside it it said it might be temporary(in deamon):
    18:10:37 2016-07-06 [INF] DISC: DNS discovery failed on seed mainnet-seed.decred
    .org: lookup mainnet-seed.decred.org: getaddrinfow: This is usually a temporary
    error during hostname resolution and means that the local server did not receive
    a response from an authoritative server.

    Also now when I do stake info I get:
    {
    "poolsize": 41209,
    "difficulty": 32.62765338,
    "allmempooltix": 0,
    "ownmempooltix": 0,
    "immature": 0,
    "live": 12,
    "proportionlive": 0.00029119852459414205,
    "voted": 0,
    "totalsubsidy": 0,
    "missed": 1,
    "proportionmissed": 1,
    "revoked": 0
    }

    (The previous post was reversed order(the stake info))
     
  4. Btu

    Btu New Member

    Jan 1, 2016
    27
    2
    Male
    I still seem to get the same error: "Failed to purchase tickets this round: Wallet not connected to daemon" after some time.

    When it does happen I get these messages(all at same time):

    In deamon:
    02:33:29 2016-07-07 [ERR] RPCS: Websocket receive error from [::1]:57057: websoc
    ket: close 1006 unexpected EOF
    02:33:29 2016-07-07 [INF] RPCS: Disconnected websocket client [::1]:57057
    02:33:30 2016-07-07 [INF] RPCS: New websocket client [::1]:57944
    02:33:32 2016-07-07 [INF] RPCS: Beginning rescan for 71 addresses

    In wallet:
    02:33:29 2016-07-07 [ERR] CHNS: Timeout waiting for session RPC
    02:33:29 2016-07-07 [WRN] RPCS: Ping failed on connected daemon client: the clie
    nt has been shutdown
    02:33:29 2016-07-07 [INF] DCRW: Attempting RPC client connection to localhost:91
    09
    02:33:30 2016-07-07 [INF] CHNS: Established connection to RPC server localhost:9
    109
    02:33:30 2016-07-07 [INF] WLLT: Beginning a rescan of active addresses using the
    daemon. This may take a while.
    02:33:30 2016-07-07 [INF] WLLT: The last used account was 0. Beginning a rescan
    for all active addresses in known accounts.
    02:33:30 2016-07-07 [INF] WLLT: Successfully synchronized the address manager to
    external address DsYah8zNPrqc54oEgwWnp8wqU2zcKFyXDfS (key index 1) for account
    0
    02:33:32 2016-07-07 [INF] WLLT: Successfully synchronized the address manager to
    internal address DsT5XntZWKUFTYTZHBLdd7FUbNj16h6qZiD (key index 28) for account
    0
    02:33:32 2016-07-07 [INF] WLLT: Successfully synchronized wallet accounts to acc
    ount number 0.
    02:33:32 2016-07-07 [INF] WLLT: Started rescan from block 0000000000000b2686b4a0
    041784fb09e2f913ba80cad732a3861f455796532a (height 43389) for 71 addresses
    02:33:33 2016-07-07 [INF] WLLT: Syncing the transaction store blockchain to the
    most recent blocks.
    02:34:02 2016-07-07 [INF] WLLT: Blockchain sync completed, wallet ready for gene
    ral usage.
    02:34:02 2016-07-07 [INF] WLLT: The client has successfully connected to dcrd an
    d is now handling websocket notifications
    02:34:02 2016-07-07 [INF] WLLT: Finished rescan for 71 addresses (synced to bloc
    k 00000000000011f8723611da18f9737c9ea2f98ced88d52bf56419ab63441ed2, height 43390
    )

    Dcrticketbuyer:
    "Failed to purchase tickets this round: Wallet not connected to daemon"

    Any ideas how I can fix this? It only happens once in a while. I tried restarting everything, but it still happens.
     
  5. root

    root Member

    Feb 3, 2016
    381
    76
    I have never seen such error in weeks long dcrticketbuyer testing (testnet), I'd guess slow PC, slow wallet<->daemon connection, slow / broken connection to the net, old version.
    See my signature.
     
  6. Btu

    Btu New Member

    Jan 1, 2016
    27
    2
    Male
    Now its 2 missed tickets... It could be because of a slow PC because I am currently hosting this in a very very slow server. Ill also look into the version now.
     
  7. Btu

    Btu New Member

    Jan 1, 2016
    27
    2
    Male
    The network connection is good, the version I am using is the latest, and Ill try upgrading the server and see if it still happens.
     
  8. chappjc

    chappjc Full Member
    Developer Pool Operator (PoS)

    @Btu Unfortunately there are still issues with the PoW miners and the mining pools, specifically, they have trouble propagating updated work to the miners. Usually it is for the 4th or 5th vote that comes in a fraction of a second later than the others. Even the PoS pools have missed tickets because of this, and we use upwards of 5 wallets globally distributed (although western Europe seems to be the most important for mining pools.).

    Regarding the state where missed > revoked in getstakeinfo output, that can be resolved automatically by restarting your wallet, which will rebroadcast the revoke to so you can get your DCR back.
     
  9. Btu

    Btu New Member

    Jan 1, 2016
    27
    2
    Male
    Everything is fixed, I forgot to post it here. Ill update the first post saying it was fixed. Thanks for all the help
     

Share This Page