19:18:38 <vthor_> is there a way to resubmit a transaction? seems like monerod swallowed the tx, not in mempool, but spend....
19:21:59 <sech1> just rescan your wallet and try again
19:22:40 <vthor_> I rescanned now in cli, but still ony in my wallet
19:24:13 <vthor_> sorry, made refresh not rescan...
19:26:41 <sech1> refresh command doesn't reset anything, it just scans for new transactions
19:26:47 <sech1> you need to rescan
19:29:47 <vthor_> thank you sech1 that resoved the issue
21:19:50 <m-relay> <o​frnxmr:monero.social> Vthor, were you using a remote node?
22:46:19 <vthor_> no, in this case local on the machine. But normally I have a home server where I have a note running and one on a vps, why?
22:48:43 <vthor_> o​frnxmr, was the first time ever it happend to me but also my inet is bad and it was aso first time that I had two or three tx on the same wallet at a time. But I was sending the whole day coins in circe to test XmrSigner and companion app, so I could have caused that also with something there, will probably never figure out the real cause, but I started to sweat :D
22:49:16 <m-relay> <o​frnxmr:monero.social> If local node, it should be in your nodes txpool
22:49:32 <m-relay> <o​frnxmr:monero.social> When you say "not in mempool" did you check your local pool, or a block explorer?
22:50:13 <m-relay> <o​frnxmr:monero.social> The only way i could see it being "swallowed" by your local pool would be if you ran flush_txpool on it
22:55:39 <vthor_> "When you say "not in mempool" did you check your local pool, or a block explorer?" block explorer after tx didn't get confirmations, and the other tx 2 min earlier hat already 5ish, how it was very urgent and important I got stressed out :D
22:58:45 <vthor_> Well, I restarted monerod first, then I made flash_tx (I think) and flush_cache, and nothing changed, then I closed monero-gui twice and my stress level grew even more :D this is when I made the question, I was already worried the tx_will be simply stuck forever. Can also not think clear with migrane and blurry vision, so I was simply searching for an hammer
22:59:47 <vthor_> "The only way i could see it being "swallowed" by your local pool would be if you ran flush_txpool on it" of course in my panic I made exactly that.... :D But luckily a rescan resent the transaction, next minute 1 confirmation....
23:09:28 <m-relay> <o​frnxmr:monero.social> 👍👍. Yeah, flush tx removed the tx from your mempool. It should have attempted to broadcast the tx automatically if left alone (even after restarting monerod)
23:17:10 <vthor_> yeah, but it didn't said only something can't be sent, letme see if I still find it in the terminal
23:18:10 <vthor_> 2024-08-11 19:26:24.809 W Unable to send transaction(s), no available connections
23:18:40 <vthor_> but sync_info told it had 5 peers.....