02:00:59 fiuuuu 02:00:59 Server decided that it would remove one nvme drive by surprise :D 02:00:59 While compiling monero pool stuff :D 02:00:59 [... more lines follow, see https://mrelay.p2pool.observer/e/07Huz9oKdElPN2JI ] 02:01:22 md0 : active (auto-read-only) raid1 nvme0n1p1[0] 02:01:22 4189184 blocks super 1.2 [2/1] [U_] 02:01:22 md2 : active raid1 nvme0n1p3[0] 02:01:22 10476544 blocks super 1.2 [2/1] [U_][... more lines follow, see https://mrelay.p2pool.observer/e/-ervz9oKeTZNcXI1 ] 02:21:25 Why do big host provide Samsung nvme drive in there dedicated server, they arent reliable. 02:21:25 It got the same exact issue on my other server (the one that run ma other monero node), two times.. Drive vanish... Rebooting dont bring the drive back, only a power cycle do. 02:24:05 On that later server I replaced the samsung drives for Kyoxia drives. But I dont think I get get provider I can't control to replace the drive with non-samsung one.. 02:24:05 Maybe I have to relocate 03:06:26 <321bob321> Check probably 03:06:32 <321bob321> Cheap* 03:08:44 I have 3 samsung SSDs with the oldest running a node for 5.5 years 03:08:54 none have had a problem 03:13:23 I never had issue on my samsung drive in com various consumer PC. Even the want that I used down to 100% still work fine. 03:13:23 But its the second server on where a samsung drive vanish from the pcie bus. Both of them, the drive would now show up after a reboot, only a power cycle brought it back 03:13:46 Not show up* 03:14:27 The slop told me it was common on samsung drives 03:17:02 The drive literally vanish without logging anything in smart. It's like if there controller hang and don't even obey the reset signal 03:21:17 ah 03:21:37 slop never tells me anything 03:22:03 rabbit holes are nice 03:22:07 yeah, but still, theses drive have serious reliability issues if they can vanish from the bus just like that for fun 03:27:45 Seam to have to most recent firmware... 03:30:14 Hardest part will be to find replacement dedicated server that don't contain that Samsung crap 03:52:11 <321bob321> You can ask them what drives they use 04:27:44 That being said, no data has been lost (like at all). 04:27:44 Every time a drive Samsung vanished, LVM2 was fast enough to catch it and shutoff the affected LVs. The VM all complain about IO errors but then once your back it's nothing more than en unexpected shutdown. 04:27:44 On my other server on where that issue occured, KVM even automatically "paused" the affected VM before they began to IO error. (I just did not have space on / here to suspend 60GB worth of VM because well, I did not plan to pause VMs 😂) 04:27:44 [... more lines follow, see https://mrelay.p2pool.observer/e/uOaH1NoKclBibllr ] 09:05:55 future donations should appear under https://blocks.p2pool.observer/payments automatically > <@ravfx:xmr.mx> xmr.mx now accept donations finally! : https://xmr.mx/donate.html 09:15:54 hello, im from asia 09:21:42 Touch some grass jeez. Who is this loser? > <@dumb_of_ass.:matrix.org> ^ who the fuck even is gonna donate to you aside from actual feds? yall already on the feds payroll 14:36:41 i got confused by bounties.monero.social's UI lol 14:36:54 when a comment is older than a year, it displays it by " " 14:36:59 instead of " months ago" 14:37:09 i actually thought those comments happened this year 14:46:52 /exit 19:26:30 Alright, so I want to run a Monero node via I2P, using i2pd. why does monerod --proxy=127.0.0.1:4447 --daemon-address=http://asdfgasdfgasdfgasdfgasdfgasdfgasdfgasdfgasdfgasdfgas.b32.i2p:18283 --trusted-daemon executed as the monero user, not start the daemon, but instead print the help options? 19:26:30 I've checked the b32 address and ensured it's tunnel type is http. 19:28:15 --daemon-address is not a real argument 19:28:27 That's for wallet cli and rpc 19:28:35 neither is --trusted-daemon 19:28:42 Yeah, same 19:28:46 did you get the command from chatgpt? 19:29:04 https://docs.getmonero.org/running-node/monerod-tori2p/#wallet-setup 19:29:22 that's for wallet cli 19:29:25 not monerod 19:29:28 at the very bottom select I2P and Monero CLI 19:29:36 Maybe what you want is --add-exclusive-node ? 19:29:38 that page talks about the wallet programms 19:34:00 I guess the Node Configuration section is the only relevant one. 19:34:34 Thanks for noticing the error, I didn't notice. 19:43:29 Can the same user run multiple monero nodes easily? 19:44:16 it seems I need to modify ~/.bitmonero/bitmonero.conf, which makes me think, I have to create another user for the I2P monerod 19:45:01 kinda non trivial running two nodes on the same machine. 19:45:04 @everchange000:matrix.org: It's not difficult. You just need to specify different p2p, RPC, and ZMQ ports. 19:45:36 Because two programs can't use the same ports on the same machine. 19:45:39 * br-m looks up ZMQ port 19:46:17 It's probably easier to just disable ZMQ on the 2nd node 19:47:29 You can add these flags. I use flags instead of config files. --rpc-bind-port --p2p-bind-port --no-zmq 19:48:34 @rucknium: thanks 19:50:00 @everchange000:matrix.org: You also need to specify a different directory for the second copy of the blockchain. Make sure you have enough storage space 19:50:21 --data-dir 19:51:31 @rucknium: can't I just symlink? 19:52:15 Storage is not an issue. But the last symc was like 6days 19:52:49 so two monerod instances with the same data dir clash? 19:53:55 @everchange000:matrix.org: Yes. Only one monerod instance per blockchain database file. 19:54:17 You can stop monerod and make a copy of the database file. That would skip the sync. 19:55:45 @rucknium: Amen 🙏 19:56:22 @rucknium: You can use the same db 19:56:38 Just dont allow connections on one of them 19:57:00 No p2p connections? 19:57:15 Yeah 19:58:15 I have one node mining via p2pool. The other node is for the community. 19:59:11 https://github.com/monero-project/monero/pull/1982#issuecomment-295025270 19:59:11 > I've found that when running two daemons on the same DB 19:59:22 @everchange000:matrix.org: Why not use the same node for both? 20:00:18 @ofrnxmr: how would that work? 20:00:34 can I just pass additional ports? 20:01:34 not sure i understand why it wouldnt work 20:01:47 The i2p and the p2pool configs dont conflict 20:02:14 I'll test that tomorrow. I'm sleepy. Thanks for the input everyone. 20:03:58 P2pool config: zmq-pub=tcp://ip:port 20:03:58 i2p config: tx-proxy=i2p,ip:port[,max_conmections][,disable_noise] 20:03:58 anonymous-inbound=hiddenservice.b32.i2p,[ip:]port[,max_connections]