03:21:17 <gingeropolous> oh yay its just doin what its sposed to on ubuntu 18
03:21:34 <gingeropolous> yummy copypasta
04:46:24 <DeanGuss> Is there a monero equivalent of `bitcoin-cli getpeerinfo`?
04:47:32 <DeanGuss> I'm trying to diagnose why I keep seeing this in the log:WARNING	net.p2p.tx	src/cryptonote_protocol/levin_notify.cpp:349	Unable to send transaction(s) to tor - no available outbound connections
04:47:44 <DeanGuss> Seems very odd because I am keeping up with new blocks just fine
07:27:49 <alive> I mined some monero up to the 0.07 payout fee. The pool sent me the coin. I can see the transaction in the blockhain, and I can decrypt it with my private view key. The transaction has not arrived in my wallet at the most recent block height. It's been two weeks. Is it still possible I ihad the wrong wallet address in my miner? Is the coin gone? Will it ever come?
07:30:35 <alive> 8157 confirmations on the block so far.
07:30:38 <sech1> If you can decrypt it with your view key, it's in your wallet
07:30:53 <sech1> rescan it starting from before the height when this tx was mined
07:31:03 <sech1> and use the official CLI or GUI wallet
07:31:03 <alive> Thanks
07:31:17 <alive> I use Monerujo on android
07:31:28 <sech1> good enough
07:31:32 <sech1> rescan the wallet
07:31:41 <alive> Thanks ,will do.
07:40:58 <jovvana> hi
07:41:41 <jovvana> I'm doing some test  with new chain but nodes cant connect
07:42:39 <jovvana> Dandelion is stopping nodes to connect or because i deleted dns there is no connections
07:42:46 <jovvana> 3nodes
07:43:15 <jovvana> allways "Starting new Dandelion++ epoch: stem"
07:43:41 <jovvana> Myabe dandelion prices need 1 on all config.h file
07:44:00 <alive> sech1: thanks! It now seems like I am no longer missing any funds. But now my wallet glitched out and I can't see any of the tx's 
09:24:26 <user85> hello
09:24:27 <user85> :)
09:27:11 <user85> heatwave in uk
09:27:25 <user85> maybe i should come for a few days to enjoy it
12:41:48 <tinybronca[m]> Hi all, so I am going to sync a new blockchain which I havenot done in a while... I want the data on a specific directory where I have SSD space, so I run monderod --data-dir /path/to/ssd  ??
12:43:00 <tinybronca[m]> also I will probably want --prune-blockchain
12:49:59 <sech1> yes
12:50:17 <sech1> --data-dir /path/to/bitmonero/dir
12:52:36 <tinybronca[m]> thanks ok
12:52:48 <tinybronca[m]> I wonder how long this takes now
13:00:05 <sech1> if your connection and SSD are fast, 8-12 hours
13:06:13 <tinybronca[m]> I am not convinced my SSD is that fast, not NVMe
13:14:19 <sech1> Anyway, if it's an SSD you will probably be limited by your CPU and network speed, not by disc access when you sync
13:45:05 <DeanGuss> Is there a monero equivalent of `bitcoin-cli getpeerinfo`?
13:49:29 <selsta> what does that print?
15:56:50 <DeanGuss> selsta: it prints info about the peers you're connected to
15:57:02 <selsta> right but what kind of info?
15:57:14 <selsta> there is `sync_info`, there is also `print_cn`
15:58:33 <DeanGuss> ip address info, network info, peer capabilities, bytes sent/recieved etc
15:59:08 <DeanGuss> I'm trying to diagnose why I keep seeing this in the log: WARNING	net.p2p.tx	src/cryptonote_protocol/levin_notify.cpp:349	Unable to send transaction(s) to tor - no available outbound connections
15:59:19 <DeanGuss> Even though I'm receiving new blocks just fine
16:12:21 <selsta> DeanGuss: this is with tx-proxy?
16:12:52 <selsta> blocks are sent over clearnet, only transactions are sent over tor
16:13:15 <selsta> print_cn will show you the amount of incoming and outgoing tor peers you have
16:13:27 <selsta> also which version are you running?
16:15:55 <DeanGuss> 0.17.3.2
16:16:11 <DeanGuss> I have this stuff turned on in the config:
16:16:30 <DeanGuss> #Tor stuff
16:16:30 <DeanGuss> # Tor: broadcast transactions originating from connected wallets over Tor (does not concern relayed transactions)
16:16:30 <DeanGuss> tx-proxy=tor,127.0.0.1:9050,16
16:16:30 <DeanGuss> # Tor for p2p traffic
16:16:30 <DeanGuss> proxy=127.0.0.1:9050
16:16:37 <selsta> v0.18 has multiple fixes so that this message will show up less often
16:16:39 <DeanGuss> as well as anonymous-inbound
16:17:49 <hyc> definitely, upgrade to v0.18.0.0, tor / i2p are much more stable there
16:18:18 <selsta> there were two bugs that caused tor / i2p connections to get dropped
16:19:03 <DeanGuss> I see no v0.18 @ https://www.getmonero.org/downloads/
16:19:09 <DeanGuss> Did it just come out or something?
16:19:11 <selsta> it will be up the next hours
16:19:16 <DeanGuss> k
16:21:49 <DeanGuss> forgive me, I'm monero stupid so I don't recall.  How do I get to the shell to enter this print_cn command?  Doesn't seem to be monero-wallet-rpc or monero-wallet-cli or monerod
16:22:09 <selsta> ./monerod print_cn
16:22:18 <selsta> if your node isn't restricted
16:22:29 <selsta> otherwise you have to run monerod inside tmux or so
16:22:39 <selsta> or keep an unrestricted port open for localhost
16:23:15 <hyc> yeah there's really no reason to restrict localhost
16:29:19 <DeanGuss> Error: Couldn't connect to daemon: 127.0.0.1:18081
16:29:21 <DeanGuss> rpc-bind-ip=127.0.0.1		# Bind only to localhost
16:29:21 <DeanGuss> rpc-bind-port=18081		# Bind on default port
16:29:21 <DeanGuss> restricted-rpc=0		# (Don't) Prevent unsafe RPC calls
16:29:31 <DeanGuss> I have all that on... :(
16:35:05 <DeanGuss> Oh, working now, thanks selsta.  I had to also switch to public-node=0
17:31:13 <chown> how do I point monerod to my blockchain?
17:31:52 <selsta> --data-dir
17:35:53 <chown> ok so my block chain only has su permissions 
17:36:12 <chown> How do I change permissions of the directory and all the files in the diorectory so that my normal user can access them?
17:36:22 <chown> Chown and Chmod ironically confuse the shit out of m3e
17:45:07 <sech1> sudo chown -R user:group path/to/dir and then sudo chmod -R 755 path/to/dir
17:50:25 <chown> sech1: Thanks mayn
20:53:47 <tinybronca[m]> test
22:52:55 <tinybronca[m]> Hi so if I kill monderod it will be okay restarting?
22:53:53 <merope> Depends on how you kill it
23:02:23 <garth> If you kill it, kill it slowly. 
23:09:39 <Torr> See?! And some msm folks still labels us as terrorists when we're just humble psychos going on with everyday life.
23:24:45 <hyc> you can kill monerod arbitrarily, makes no difference. but if you kill the machine ungracefully and you're not using --db-sync-mode=safe you will probably corrupt the DB
23:25:19 <hyc> on windows, an OS or hardware crash seems to pretty reliably kill the DB. On Linux with ext4 it's so far unheard of