An error occurred at task: MakerSendSignOfferRequest - Exception at handleSignOfferRequest Failed to submit tx to daemon:

[slrslr]

This repeats when I try to "Review: place offer ..." in Retoswap 1.0.17 on Linux

An error occurred at task: MakerSendSignOfferRequest
Error signing offer idhereee: Arbitrator nacked SignOfferRequest for offer idhereee: Exception at handleSignOfferRequest Failed to submit tx to daemon: {"isGood":false,"isRelayed":true,"isDoubleSpend":true,"isFeeTooLow":false,"isMixinTooLow":false,"isOverspend":false,"isTooBig":false,"sanityCheckFailed":false,"credits":0,"isTxExtraTooBig":false,"isNonzeroUnlockTime":false,"hasInvalidInput":false}

In the past under same Retoswap app version, I have already placed this cryptocurrency sale offer.

After restarting RetoSwap, it worked to publish this offer (i have used duplicate offer function on history tab).

[woodser]

Can you share your logs prior to when that happened for further debugging? Guessing funds must have been spent from your wallet just prior to posting the new offer, which your wallet was attempting to re-use until the previous tx was confirmed and your wallet synced.

Also it's best to update to v1.0.18.

[slrslr]

It happened again under same session for which it worked earlier (but maybe for different funds/outputs). Log is here (pa$$. is your username).

No recent unconfirmed transaction found.. For details, you may also contact me in private.

Also it's best to update to v1.0.18.

You have not answered this retoaccess1#62

[woodser]

I will need more logs prior to when the error occurs to better understand what your application was doing. The more context the better. Feel free to DM me on Matrix if you want to send logs privately.

You have not answered this

The admins of that network would need to send a notification to their users. We're not associated in any way so you'd have to ask them directly.

[slrslr]

I do not know how to connect you on matrix, it says user is offline entering "woodser". I have already given you contact on myself in previous post and the log lines prior to ones I have provided are older several minutes prior oldest line I have provided, meaning:
Mar-01 20:44:48.292 - oldest mine provided log entry
several minutes delay before that:

Mar-01 20:39:58.746 [InputHandler-y3ur6ixrovey...] WARN  haveno.network.p2p.network.Connection: proto is null because protoInputStream.read()=-1 (EOF). That is expected if client got stopped without proper shutdown.
Mar-01 20:41:57.295 [InputHandler-vjblmzyskeu3...] WARN  haveno.network.p2p.network.Connection: Shut down caused by exception Read timed out on

[woodser]

I've sent you a note. Thanks.

[woodser]

After investigating further, it's not clear what caused the double spend error you were experiencing over a period of about 2.5 hours when trying to post offers, but it seems the arbitrator may have had a problem on their end, where your reserve tx for verification became stuck in their local tx pool. I've added a guard to help prevent txs from potentially getting stuck in the arbitrator's tx pool: #1625

For now I think since this issue has resolved itself, and it's not being reported by anyone else, we can write this off as an unlikely fluke with protection added, but please let me know if you see this problem again for awareness.

[slrslr]

let me know if you see this problem again

thank you