00:12:51 I installed libreadline-dev but the cmake says it doesn't find it 00:12:52 suspicious 00:13:33 ah I dropped the cmake cache and now it found it 00:13:37 bad bad cmake 00:14:03 yeah :\ 00:14:51 I suppose BUILD_GUI_DEPS is what I need to build the GUI? 00:16:08 sounds plausible. i've never built the GUI though, sorry 00:17:00 I'll give the cli wallet a try 00:17:18 the GUI makes my fan spin a lot for some reason, probably related to the deluge of weird errors in the log 00:18:44 that would be expected while syncing, but does it happen after it's fully up to date, too? 00:19:08 even from a remote node it would be syncing with lots of CPU usage? 00:19:17 yes, 00:19:19 well it's fully up to date and every now and then it spins up 00:19:41 for the fan to spin up the cpu usage of a few cores must be 100% for some time 00:19:41 a local node uses CPU while syncing because it needs to verify the incoming blocks, 00:20:04 a wallet (regardless of local or remote node) also uses CPU while syncing, because it needs to *scan* all the outputs in the new blocks 00:20:08 right 00:20:17 so if you use a remote node, you don't need the first half, but you always need the second half no matter what 00:20:26 yeah 00:21:09 unless it's the so called lightweight wallet I suppose 00:21:14 "every now and then" spinning up might just be when a new block first arrives? 00:21:20 which doesn't provide much security 00:21:32 right, with a lightweight wallet the server does the scanning 00:21:33 yes I suppose that's the case 00:21:56 my raspberry pi has a ssd, maybe I could try putting the node there if its cpu would be good enough 00:22:06 it's just as secure, the server never has access to your spend key. what you give up is privacy, since the server can see all your incoming transactions. 00:22:16 ah right yeah 00:22:25 which model pi? i use a rockpro64 for a monero node and it works great. i'd guess rpi4 would work just as well 00:22:31 it's a rpi4 yeah 00:22:40 already serving as a router, wifi AP and NAS 00:22:48 but none of these are CPU intensive 00:23:23 and it has a fan but I unplugged it because the noie was obnoxious, so there will be definitely no fan noise to annoy me there 00:24:12 i don't have a fan on my rockpro, just the passive sink. doesn't seem to have any issues. 00:25:33 it didn't seem to have issues when syncing from scratch either, more pertinently 00:25:58 i think running it 24/7 on a cheap ARM board like this is a pretty good choice. personally i'd be a little wary of running anything open to the internet on the same machine as my private NAS, however 00:26:25 yeah indeed 00:26:47 it's the router so it has a public IP 00:26:52 if you are confident you can isolate it properly (e.g. use firejail), it's probably fine, but i prefer to just spend the $50 and get a second one 00:27:13 public IP is one thing, but something actually accepting connections is another 00:27:13 but there's some firewall on it which should be good enough, unless monerod gets pwned then it's not good enough 00:28:08 for now it doesn't accept ingoing connections, and I'd just add the P2P ports of monerod and that should be good 00:28:23 the IP isn't static though, I don't know how much a problem it can be 00:28:39 when you add the p2p port, monerod will accept connections on that port 00:29:01 yeah 00:29:22 other nodes will know my ip, and just mark it as stale when they can't connect anymore? 00:29:44 yeah, dynamic IP is not a problem, i would bet the majority of nodes are on one 00:29:54 I see 00:30:27 if you believe in my abilities to do a proper firewall, you think it's fine to run monerod on the pi like this? or you would still be wary of a vulnerability in it and put it in a secure container thing 00:30:44 putting it in an unprivileged container would be an easy way to isolate it 00:31:18 and with systemd it's easy to do in a few lines of config 00:31:22 i don't think the firewall makes any difference since the relevant port would be open anyway 00:31:42 depends how sensitive the stuff on your NAS is? if it's just movies you downloaded then whatever :) 00:31:52 yeah just movies 00:32:02 but the pi is also the router 00:32:13 if it's a skilled attacker they could try to access my other computers with more sensitive stuff on it 00:32:33 otherwise, at a minimum, i'd make sure monerod has its own unprivileged user that doesn't have access to anything (e.g. your NAS files) 00:32:37 as computers tend to trust their LAN and especially their router 00:32:44 yeah 00:32:48 you can also add a firewall rule preventing that user from sending anything to your internal network 00:33:04 ah yes good point 00:33:12 unless it's RELATED,ESTABLISHED traffic 00:33:20 beyond that, i'd personally set it up under firejail, it's pretty easy to do 00:33:24 exactly 00:33:42 I've looked at firejail before it looks powerful indeed 00:33:57 but apart from the more exotic seccomp capabilities of firejail a container should be more or less the same result 00:34:08 firejail might be easier to use tho 00:36:41 thanks for the advice 00:36:48 yeah, you also don't need a whole separate chroot system with firejail. instead it provides a limited view of the host filesystem 00:37:20 so in this case you'd just give it read-only access to e.g. /usr/lib/whatever and /usr/local/bin, and write access to wherever your blockchain and log file are 00:37:37 yeah 01:09:02 maybe a stupid question but the p2p protocol is udp right? 01:32:10 I suppose 01:32:14 to get through NAT 01:32:34 is there a way to type a command into a remote node ndorf ? if it's unrestricted RPC for instance I should be allowed right? 01:32:51 otherwise I would have to like login on the pi and restart monerod in interactive mode to type the command 01:37:25 estimated time for syncing 2 days, with a ssd :( 01:37:31 I'll just let it run and see what happens 01:37:38 but it told me I'm on a rotating drive which is false 01:38:05 ah now it's 22 hours estimated 01:39:50 my own estimate would be 3-6h given the current speed 01:49:10 It slows down later in the chain due to larger blocks/more txs later 01:50:00 Also the first 40% of the chain was a different and faster format 01:51:24 Not sure but a sata ssd might take 22hrs 01:52:06 An nvme will be ~12hrs 02:03:33 mawk: you can send commands to a remote node like this: monerod --rpc-bind-ip node.whatever.com flush_txpool 02:03:51 --rpc-bind-port X if it's not 18081 02:53:21 are the large exchanges any worse, or better, than the smaller monero specific exchanges when trading fiat for monero? 07:03:35 TCP 07:06:42 so i'm trying to create a node, and it's been syncing for a few days...but it oscillates between syncing normally, and throwing stack traces. is that...normal behavior? 07:08:54 after Exception: it prints one of those diamond question mark characters which i think is a non-printable character 07:09:25 and then ultimately: src/common/stack_trace.cpp:149 Failed to find the next frame 07:09:38 but it seems to recover after a while 07:10:20 whatever is happening appears to be a recoverable error 07:10:48 but it will print pages and pages of stack traces before resuming normal sycning 07:13:56 Synced 2309456/2526760 (91%, 217304 left, 2% of total synced <--- this has also been confusing me 07:17:47 it appears to be 91% synced, and the other "total synced" number almost seems randomly generated. it jumps all over the place. 07:28:51 It's meant to be "total synced since you last started syncing again", while the 91% is the total from chain start. 07:29:17 If it jumps, possibly you're disconnecting all the time and it's restarting sync. 07:29:45 For the stack traces, they should appear in the log file only. Are you seeing them on the console ? 07:30:37 yeah 07:30:56 Very odd. Did you compile monerod yourself ? 07:31:04 but i'm doing tail -f logfile :P 07:31:09 ... 07:31:47 OK, I *was* imprecise, technically :) 07:32:18 Can you paste a sample stack on paste.debian.net ? It's most likely something uninteresting. 07:32:46 You can get rid of them with --log-level 0,*stack*:FATAL 07:37:21 http://paste.debian.net/1225335/ 07:39:19 Whee. Well, not helpful. I guess you did not biuld with libunwind. 07:39:26 But most likely innocuous anyway :) 07:39:48 The two things it's likely to be are: 07:40:47 - a bad weak_ptr in the net code: I'd fixed that (mostly) but it came back, but it's really innocuous, there's a check for it, it's just a noisy way to check whether an object has died 07:41:15 - failure from librandomx to use huge pages or the like: it'll fall back on normal allocs, it'll just be a bit slower 07:41:38 If it's another than these, it'd be interesting to know, but little chance of that. 07:49:34 yeah it seems innocuous because it looks bad, but I will check later and it's syncing totally normal. output is fine. 07:49:54 just keeps chugging along 07:51:12 if it's only supposed to appear in the logfile and not regular output, that makes me feel better. maybe next time I won't detach and run it in tmux or something 07:52:24 i guess i thought it was just standard output 12:58:58 h 14:52:09 any other small box recommendations? ima get rpi4, i have a pine64 from years ago... 14:54:42 beaglebone 14:55:53 wanted to get beagleboard-x15 15:16:54 rockpro64 15:17:00 avoid all rpi models 15:33:29 hyc: mind elaborating? 15:33:44 they all lack hardware AES 15:33:53 they all have shitty slow I/O subsystems 15:34:20 i will look into it, as im planning to get one more SBC soon and was rethinking what. 15:34:21 thanks 15:34:24 20MB/s max throughput, aggregate of all interfaces 15:35:12 waste of perfectly good silicon 15:46:49 even the pi 4 still lacks AES? damn 15:47:28 yeah 15:47:40 no clue why they don't use processors with crypto extensions 15:47:41 so stupid 15:48:47 almost but not quite unbelievable 15:57:38 cheapskates didn't want to pay for the extension license 15:58:41 That would be a license paid to ARM? AES itself does not require anything, right? 15:58:54 from broadcom to arm, yes 15:59:35 wtf. i have a different ARM SBC (NanoPi A64) that was $15 new and it has AES 16:00:40 broadcom makes all the pi CPU chips. either raspberry specifically asked for this, or this is what broadcom offered them and they took it 16:01:14 afaik broadcom makes the chips to raspberry's specification