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"

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

Get a stack trace for the crash (using gdb) if you can. You bump log level up with --log-level 1 (or 2).

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

If it's really crashing, you can run with gdb that way:

gdb /path/to/monerod

run insert-your-usual-monerod-arguments-here

Then after it crashes: bt

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

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 ...

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

@spigfis on telegram

@spigfish *

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.

moneromooo: I will start again tomorrow with a more consistent troubleshooting methodolgy with fresh eyes, to see if I can consistently replicate the crash

when mooo locks my cli wallet for being inactive, pressing ctrl+c and ctrl+d randomly makes the wallet segfault

the flex

can only seem to reproduce it with the inactive lock, not the lock command. paste.debian.net/hidden/ab7be583

shit on my idea please

nevermind, it happens with the lock command too

did you find anything interesting probing me acth2004

endogenic, bitcointalk.org/index.php?topic=583449.msg54169169#msg54169169

i dont know what telegram option he's talking about

we dont have one

he needs to hit our support - i wonder if thats what he means

i wonder if he has a pre rct output of some sort. should be fine tho

could be a stuck daemon

on a wrong chain

dunno, just thought I'd forward

totally

i was working my way towards saying a big thanks :)

you all holding up there?

ya, I am not a fan of being stuck at home, but things certainly could be worse

assuming you have vacated the area by this point?

<\​x> gary

<\​x> valid.x86.fr/19sgv2