01:53:17 <m-relay> <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:
01:53:18 <m-relay> <o​xetn:matrix.org> Error: {"status":500,"code":-4,"message":"transaction was rejected by daemon"}
01:53:20 <m-relay> <o​xetn:matrix.org> and this from the docker logs:
01:53:22 <m-relay> <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
01:53:28 <m-relay> <o​xetn:matrix.org> i've tried changing nodes and tweaking some configs but no luck yet
04:01:37 <m-relay> <s​iren:kernal.eu> MoneroPay relays the error from monero-wallet-rpc and also this is seen repeating in the logs
04:01:37 <m-relay> <s​iren:kernal.eu> ```
04:01:37 <m-relay> <s​iren:kernal.eu> 2024-11-19 17:55:39.689 W Requested ring size 9 too low, using 16
04:01:38 <m-relay> <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: ...
04:01:40 <m-relay> <s​iren:kernal.eu> ```
04:04:39 <m-relay> <s​iren:kernal.eu> This happens on mainnet, wallet-rpc version v0.18.3.3
13:28:05 <m-relay> <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:
13:28:06 <m-relay> <d​aborg69:matrix.org> 2024-11-20 13:26:02.420	3268	INFO	global	src/daemon/core.h:64	Initializing core...
13:28:08 <m-relay> <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
13:28:10 <m-relay> <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
13:28:12 <m-relay> <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 ...
13:28:14 <m-relay> <d​aborg69:matrix.org> 2024-11-20 13:26:02.423	3268	DEBUG	cn	src/cryptonote_core/cryptonote_core.cpp:551	option: safe
13:28:16 <m-relay> <d​aborg69:matrix.org> 2024-11-20 13:26:02.423	3268	DEBUG	cn	src/cryptonote_core/cryptonote_core.cpp:551	option: sync
13:28:18 <m-relay> <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
13:28:20 <m-relay> <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
13:28:22 <m-relay> <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
13:28:24 <m-relay> <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
13:28:26 <m-relay> <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
13:34:22 <m-relay> <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.
13:54:24 <m-relay> <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.
16:30:20 <m-relay> <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
17:22:44 <zzz123> summoning moneromooo - https://i.imgur.com/R46Wxfw.png
17:30:10 <moneromooo> 99% probably it's the OOM killer. Free more memory. See dmesg if you want to double check.
17:30:22 <zzz123> 16gb mem
17:30:45 <zzz123> 100% memory on the monerod process. how do i boost mem for the process?
17:31:02 <moneromooo> 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...
17:31:10 <zzz123> yea burner vps
17:31:50 <moneromooo> 16 GB ought to be way more than enough, assuming it's not used up by something else.
17:31:56 <zzz123> 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
17:32:08 <zzz123> hats off
17:32:33 <moneromooo> Found a... bug ?
17:32:39 <zzz123> yezzir
17:33:02 <zzz123> remote p2p crash - not releasing details publicly, naturally. going to go for a bug bounty this time
17:33:32 <zzz123> i should've specified - you probably just thought i had a random oom from running a node
17:33:40 <moneromooo> I did.
17:33:45 <zzz123> my b
17:34:10 <moneromooo> Is it running in in restricted mode ?
17:34:19 <zzz123> ./monerod
17:34:28 <moneromooo> Oh. Yes. Forgot.
17:34:31 <zzz123> log levels above 0 crash way faster
17:34:47 <moneromooo> Then try with restricted mode first.
17:35:09 <zzz123> i hate irc
17:35:14 <zzz123> how do i run restricted mode
17:35:27 <zzz123> love/hate. efnet 1999 :']
17:35:31 <moneromooo> --restricted-rpc IIRC
17:35:43 <zzz123> it's not an rpc issue it's p2p - does that matter?
17:36:02 <moneromooo> It does not. I just have a very very short attention span.
17:36:11 <zzz123> i hear ya
17:37:22 <zzz123> and yes it does appear to be '--restricted-rpc'
17:37:27 <zzz123> will lyk
17:37:41 <zzz123> will work against it - testing regardless
17:38:11 <moneromooo> Anyway, best is to file a report on hackerone I think.
17:38:21 <zzz123> yeah i was wondering if that was still active
17:38:31 <zzz123> forgot to ask - jumped right into the meat and potatoes
17:38:48 <moneromooo> It is still active.
17:39:06 <zzz123> 10-4. do you analyze bugs on there still?
17:39:37 <moneromooo> Only when i'm prodded, I'm hacker emeritus now.
17:40:04 <zzz123> fml teach me
17:40:13 <zzz123> ok i'll make contact on h1 thanks moo
17:40:23 <moneromooo> Thanks for finding/reporting.
18:32:48 <rbrunner> Test test test please ignore