01:10:57 <duso> more crash errors, this time on monero-wallet-cli "2020-04-06 00:56:04.341     7f2759142380        INFO    logging contrib/epee/src/mlog.cpp:273   New log categories: *:WARNING,net:FATAL,net.http:FATAL,net.ssl:FATAL,net.p2p:FATAL,net.cn:FATAL,global:INFO,verify:FATAL,serialization:FATAL,daemon.rpc.payment:ERROR,stacktrace:INFO,logging:INFO,msgwriter:INFO"
01:21:12 <duso> it seems whenever I try to connect to my vm running my monerod from my laptop with monero-wallet-cli using set_daemon it crashes
02:03:24 <moneromooo> Get a stack trace for the crash (using gdb) if you can. You bump log level up with --log-level 1 (or 2).
02:19:13 <duso> moneromooo: <-- Not a developer =/, just a lowly sysadmin that does shell scripts at best. I will try --log-level 2 and tail the log file and hope to get some more info
02:28:02 <moneromooo> If it's really crashing, you can run with gdb that way:
02:28:07 <moneromooo> gdb /path/to/monerod
02:28:18 <moneromooo> run insert-your-usual-monerod-arguments-here
02:28:23 <moneromooo> Then after it crashes: bt
02:38:01 <duso> ok, still futzing. trying to pass --log-level=2 to the rc.conf. I restarted the wallet with command line options of --daemon-address instead of set_daemon within the wallet and it seems to be working ok
02:52:26 <duso> I have been unable to replicate the first 2 crashes. The first time it crashed I did not have the RPC bound to the IP:port it was trying to connect to. I will play with this a bit more later, but have to actually do some work from home ...
10:07:41 <spigfish> Hello guys, Is there any admin from the official Monero Telegram channel here?  I got banned is seems, Cant access the channal anymore. No idea why
10:08:20 <spigfish> @spigfis on telegram
10:08:39 <spigfish> @spigfish *
10:23:23 <duso> moneromooo: still futzing with my monerod and monero-wallet-cli, trying to set up rpc-pay now but still getting inconsistencies that is baffling me. Now I can't even connect to my daemon and I can't figure out why but I am going to call it a night, I am going around in circles.
10:24:38 <duso> moneromooo: I will start again tomorrow with a more consistent troubleshooting methodolgy with fresh eyes, to see if I can consistently replicate the crash
11:25:47 <asymptotically> when mooo locks my cli wallet for being inactive, pressing ctrl+c and ctrl+d randomly makes the wallet segfault
11:32:15 <azy> https://youtu.be/diiuHfPkn9s?t=216
11:32:17 <azy> the flex
11:33:51 <asymptotically> can only seem to reproduce it with the inactive lock, not the lock command. http://paste.debian.net/hidden/ab7be583/
11:49:09 <azy> https://old.reddit.com/r/Monero/comments/fvw8gw/maam_monero_ask_anything_monday_april_06_2020/fmkx87n/
11:49:11 <azy> shit on my idea please
12:21:12 <asymptotically> nevermind, it happens with the lock command too
14:55:30 <Bill48105> did you find anything interesting probing me acth2004
16:44:27 <jwinterm> endogenic, https://bitcointalk.org/index.php?topic=583449.msg54169169#msg54169169
16:45:10 <endogenic> i dont know what telegram option he's talking about
16:45:12 <endogenic> we dont have one
16:45:24 <endogenic> he needs to hit our support - i wonder if thats what he means
16:45:48 <endogenic> i wonder if he has a pre rct output of some sort. should be fine tho
16:45:54 <endogenic> could be a stuck daemon
16:45:57 <endogenic> on a wrong chain
16:46:11 <jwinterm> dunno, just thought I'd forward
16:46:17 <endogenic> totally
16:46:30 <endogenic> i was working my way towards saying a big thanks :)
16:46:40 <endogenic> you all holding up there?
16:47:43 <jwinterm> ya, I am not a fan of being stuck at home, but things certainly could be worse
16:47:51 <jwinterm> assuming you have vacated the area by this point?
17:49:52 <hv-bridge> <\​x> gary
17:49:53 <hv-bridge> <\​x> https://valid.x86.fr/19sgv2