creepMiner-1.6.0 on linux - best DL?



  • Hi,
    Any way to configure creepMiner to only submit best deadline? Pool doesn't seem to accept second DL submitted:
    Thanks!

    @Creepsky45 ? (Is it OK to tag you like that or is it rude?)

    20:23:54: K886-EGY9-8ANY-7UX3K: nonce found (1d 17:38:09)
    20:23:54: nonce: 403077822
    20:23:54: in: /mnt/8t2/plots/6379272334720145604_400000000_3550000_3550000
    20:23:54: K886-EGY9-8ANY-7UX3K: nonce on the way (1d 17:38:09)
    20:23:54: Submit-loop 1 (1d 17:38:09)
    20:23:54: K886-EGY9-8ANY-7UX3K: nonce submitted (1d 17:38:09)
    20:23:54: nonce: 403077822
    20:23:54: in /mnt/8t2/plots/6379272334720145604_400000000_3550000_3550000
    20:23:54: JSON confirmation (1d 17:38:09)
    20:23:54: {"result":"success","block":375714,"deadline":149889,"deadlineString":"1 day, 17 hours, 38 mins, 9 secs","targetDeadline":15400,"requestProcessingTime":0}
    20:23:54: K886-EGY9-8ANY-7UX3K: nonce confirmed (1d 17:38:09)
    20:23:54: nonce: 403077822
    20:23:54: in /mnt/8t2/plots/6379272334720145604_400000000_3550000_3550000
    [skip]
    20:24:09: K886-EGY9-8ANY-7UX3K: nonce found (14:52:03)
    20:24:09: nonce: 407844958
    20:24:09: in: /mnt/8t2/plots/6379272334720145604_405000000_3550000_3550000
    20:24:09: K886-EGY9-8ANY-7UX3K: nonce on the way (14:52:03)
    20:24:09: Submit-loop 1 (14:52:03)
    20:24:09: K886-EGY9-8ANY-7UX3K: nonce submitted (14:52:03)
    20:24:09: nonce: 407844958
    20:24:09: in /mnt/8t2/plots/6379272334720145604_405000000_3550000_3550000
    [skip]
    20:24:14: Submit-loop 2 (14:52:03)
    20:24:14: WAITING......................
    [skip]
    20:24:27: Submit-loop 3 (14:52:03)
    20:24:27: WAITING......................
    20:24:43: JSON confirmation (14:52:03)
    20:24:43:
    20:24:43: K886-EGY9-8ANY-7UX3K: got no confirmation from server! busy? (14:52:03)



  • @laydeals you can tag me, its ok :D
    Is your pool only accepting 1 deadline? That would be really strange.
    By default, creepminer is sending all deadlines that are better than the last best one (or the target deadline).

    Is it always - 1 deadline and after that no confirmations anymore by pool? Maybe it was just a temporary pool downtime.



  • @Creepsky45 I think it might have been a one off. But I keep having some fun with double DLs (below). "Your deadline was good... for the previous block! " :) OK, I now understand that this is good behaviour to submit DLs as soon as they found and not wait till scans finished.

    21:02:14: Submit-loop 1 (4d 23:15:28)
    21:02:14: K886-EGY9-8ANY-7UX3K: nonce submitted (4d 23:15:28)
    21:02:17: Submit-loop 2 (4d 23:15:28)
    21:02:17: WAITING......................
    21:02:21: K886-EGY9-8ANY-7UX3K: nonce found (1d 05:26:48)
    21:02:21: K886-EGY9-8ANY-7UX3K: nonce on the way (1d 05:26:48)
    21:02:21: Submit-loop 1 (1d 05:26:48)
    21:02:21: K886-EGY9-8ANY-7UX3K: nonce submitted (1d 05:26:48)
    21:02:22: JSON confirmation (4d 23:15:28)
    21:02:22: Better deadline in pipeline, stop submitting! (4d 23:15:28)
    21:02:27: Submit-loop 2 (1d 05:26:48)
    21:02:27: WAITING......................
    21:02:39: Submit-loop 3 (1d 05:26:48)
    21:02:39: WAITING......................
    21:02:47: Error: Your deadline was good... for the previous block! You submitted your nonce too late.
    21:02:47: JSON confirmation (1d 05:26:48)
    21:02:47: {"errorCode":1006,"errorDescription":"Your deadline was good... for the previous block! You submitted your nonce too late."}
    21:02:47: K886-EGY9-8ANY-7UX3K: error on submitting nonce! (1d 05:26:48)
    21:02:48: --------------------------------------------------
    21:02:48: block# 376086
    21:02:48: scoop# 864
    21:02:48: baseTarget# 409282
    21:02:48: --------------------------------------------------


Log in to reply
 

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