<o​xetn:matrix.org> hello, i'm developing a monero dicing telegram bot with MoneroPay integration for receiving and transfering XMR, the thing is, i'm having some trouble transfering XMR after a bet is won, could somebody help me? i keep getting this error:

<o​xetn:matrix.org> Error: {"status":500,"code":-4,"message":"transaction was rejected by daemon"}

<o​xetn:matrix.org> and this from the docker logs:

<o​xetn:matrix.org> 2024-11-19 17:55:43.932 E daemon_send_resp.status != CORE_RPC_STATUS_OK. THROW EXCEPTION: error::tx_rejected

<o​xetn:matrix.org> i've tried changing nodes and tweaking some configs but no luck yet

<s​iren:kernal.eu> MoneroPay relays the error from monero-wallet-rpc and also this is seen repeating in the logs

<s​iren:kernal.eu> ```

<s​iren:kernal.eu> 2024-11-19 17:55:39.689 W Requested ring size 9 too low, using 16

<s​iren:kernal.eu> 2024-11-19 17:55:43.445 W amount=0.010971960000, real_output=12, real_output_in_tx_index=0, indexes: ...

<s​iren:kernal.eu> ```

<s​iren:kernal.eu> This happens on mainnet, wallet-rpc version v0.18.3.3

<d​aborg69:matrix.org> Hi. I have been trying to get a local node running. Tried 3x from scratch. They all seem to die around 91% complete. If I restart then it just stops. Log Level at 4 and it provides no info. Just exits the program. Seems like maybe the DB is not resizing... I have 100+GB free on the drive. This is the complete log from the last start:

<d​aborg69:matrix.org> 2024-11-20 13:26:02.420 3268 INFO global src/daemon/core.h:64 Initializing core...

<d​aborg69:matrix.org> 2024-11-20 13:26:02.421 3268 TRACE blockchain.db.lmdb src/blockchain_db/lmdb/db_lmdb.cpp:1307 BlockchainLMDB::BlockchainLMDB

<d​aborg69:matrix.org> 2024-11-20 13:26:02.422 3268 TRACE blockchain.db.lmdb src/blockchain_db/lmdb/db_lmdb.cpp:1686 BlockchainLMDB::get_db_name

<d​aborg69:matrix.org> 2024-11-20 13:26:02.422 3268 INFO global src/cryptonote_core/cryptonote_core.cpp:523 Loading blockchain from folder E:\BlockChain\BlockChainData\lmdb ...

<d​aborg69:matrix.org> 2024-11-20 13:26:02.423 3268 DEBUG cn src/cryptonote_core/cryptonote_core.cpp:551 option: safe

<d​aborg69:matrix.org> 2024-11-20 13:26:02.423 3268 DEBUG cn src/cryptonote_core/cryptonote_core.cpp:551 option: sync

<d​aborg69:matrix.org> 2024-11-20 13:26:02.423 3268 TRACE blockchain.db.lmdb src/blockchain_db/lmdb/db_lmdb.cpp:1329 BlockchainLMDB::open

<d​aborg69:matrix.org> 2024-11-20 13:26:02.769 3268 TRACE blockchain.db.lmdb src/blockchain_db/lmdb/db_lmdb.cpp:620 BlockchainLMDB::need_resize

<d​aborg69:matrix.org> 2024-11-20 13:26:02.770 3268 DEBUG blockchain.db.lmdb src/blockchain_db/lmdb/db_lmdb.cpp:636 DB map size: 73992683520

<d​aborg69:matrix.org> 2024-11-20 13:26:02.771 3268 DEBUG blockchain.db.lmdb src/blockchain_db/lmdb/db_lmdb.cpp:637 Space used: 66175582208

<d​aborg69:matrix.org> 2024-11-20 13:26:02.771 3268 DEBUG blockchain.db.lmdb src/blockchain_db/lmdb/db_lmdb.cpp:638 Space remaining: 7817101312

<d​aborg69:matrix.org> Okay. I literally restarted this thing like 25x with no success. Same error. I post here and I changed log level to 2. Restarted and it started running for a minute. Looks like it did do something with the DB and it pruned it. Processed a couple of blocks and exited again. Now same error as above, and the DB is no larger.

<d​aborg69:matrix.org> Hmm. I checked EventVwr and I had not checked the System logs. It appears there is some write error. So may be an issue on my side.

<d​aborg69:matrix.org> So after further research there is some issue with the drive not allowing writes for this process. Not exactly sure what is going on as I can write other large files to this drive. But I will research this further. thx

summoning moneromooo - i.imgur.com/R46Wxfw.png

99% probably it's the OOM killer. Free more memory. See dmesg if you want to double check.

16gb mem

100% memory on the monerod process. how do i boost mem for the process?

You might also want not to run it as root. Though I guess if it's a VM just for this you might not care...

yea burner vps

16 GB ought to be way more than enough, assuming it's not used up by something else.

i found another one years ago. we had a hilarious back and forth for a week. i declined the bounty because it's xmr community funded, then you did the same shortly after

hats off

Found a... bug ?

yezzir

remote p2p crash - not releasing details publicly, naturally. going to go for a bug bounty this time

i should've specified - you probably just thought i had a random oom from running a node

I did.

my b

Is it running in in restricted mode ?

./monerod

Oh. Yes. Forgot.

log levels above 0 crash way faster

Then try with restricted mode first.

i hate irc

how do i run restricted mode

love/hate. efnet 1999 :']

--restricted-rpc IIRC

it's not an rpc issue it's p2p - does that matter?

It does not. I just have a very very short attention span.

i hear ya

and yes it does appear to be '--restricted-rpc'

will lyk

will work against it - testing regardless

Anyway, best is to file a report on hackerone I think.

yeah i was wondering if that was still active

forgot to ask - jumped right into the meat and potatoes

It is still active.

10-4. do you analyze bugs on there still?

Only when i'm prodded, I'm hacker emeritus now.

fml teach me

ok i'll make contact on h1 thanks moo

Thanks for finding/reporting.

Test test test please ignore