--- Log opened Wed Nov 18 00:00:20 2020
01:31 -!- kristapsk_ [~KK@gateway/tor-sasl/kristapsk] has joined #c-lightning
01:34 -!- az0re [~az0re@gateway/tor-sasl/az0re] has quit [Ping timeout: 240 seconds]
01:34 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Ping timeout: 240 seconds]
01:38 -!- mryandao [~mryandao@gateway/tor-sasl/mryandao] has quit [Remote host closed the connection]
01:39 -!- mryandao [~mryandao@gateway/tor-sasl/mryandao] has joined #c-lightning
02:05 -!- kexkey [~kexkey@static-198-54-132-91.cust.tzulo.com] has quit [Ping timeout: 265 seconds]
02:08 -!- vasild_ [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
02:11 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
02:11 -!- vasild_ is now known as vasild
02:25 -!- zmnscpxj__ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has joined #c-lightning
02:42 -!- midnight [~midnight@unaffiliated/midnightmagic] has quit [Ping timeout: 244 seconds]
02:46 -!- midnight [~midnight@unaffiliated/midnightmagic] has joined #c-lightning
03:32 -!- jasan [~j@n.bublina.eu.org] has joined #c-lightning
03:48 -!- belcher_ is now known as belcher
03:52 -!- sr_gi [~sr_gi@80.174.218.168.dyn.user.ono.com] has quit [Read error: Connection reset by peer]
03:53 -!- sr_gi [~sr_gi@80.174.218.168.dyn.user.ono.com] has joined #c-lightning
04:04 -!- mrostecki_ [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Quit: Leaving]
04:47 -!- zmnscpxj_ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has joined #c-lightning
04:47 -!- zmnscpxj__ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has quit [Remote host closed the connection]
05:37 -!- shesek [~shesek@unaffiliated/shesek] has joined #c-lightning
06:06 -!- liberliver [~Thunderbi@144.49.211.130.bc.googleusercontent.com] has joined #c-lightning
06:08 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Remote host closed the connection]
06:08 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #c-lightning
06:14 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-lsntjcdlexygkbwj] has left #c-lightning []
06:14 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-lsntjcdlexygkbwj] has joined #c-lightning
06:34 -!- shesek [~shesek@unaffiliated/shesek] has quit [Remote host closed the connection]
06:35 -!- shesek [~shesek@unaffiliated/shesek] has joined #c-lightning
06:38 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has joined #c-lightning
06:39 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning
06:52 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Ping timeout: 240 seconds]
06:58 < ark> Hello
06:58 < ark> muy node LN is crash
06:58 < zmnscpxj_> no backups?
07:03 < ark> It currently has no channels as I had to shut down the node due to a previous problem
07:03 < ark> For the rest it does not seem that anything has been corrupted
07:03 < ark> But I say it because the server should not crash
07:03 < zmnscpxj_> any logs?
07:04 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning
07:04 < ark> yes
07:06 < ark> https://0bin.net/paste/efjL-F3v#MEVGrjsf9OBU651eFHe7MI0vwh2pieCZ3PNSFv-zrIv
07:07 -!- alko89 [~alko89@unaffiliated/alko89] has quit [Quit: ZNC 1.7.5 - https://znc.in]
07:07 < ark> Where can I upload the complete log file?
07:08 -!- alko89 [~alko89@unaffiliated/alko89] has joined #c-lightning
07:08 < zmnscpxj_> You checked that `bitcoind` is running?
07:09 < zmnscpxj_> And you have set the RPC username + password?
07:09 < ark> yes, bitcoind is running
07:10 < zmnscpxj_> do you have `bitcoin-rpcuser` and `bitcoin-rpcpassword` settings for your `lightningd` configuration?
07:11 < zmnscpxj_> can the user that is running `lightningd` also run `bitcoin-cli getblockcount`?
07:11 < ark> yes
07:11 < zmnscpxj_> which question are you answering "yes" to?
07:14 < jasan> ark: How big is the full log file?
07:15 < jasan> s/full/complete/
07:15 < zmnscpxj_> sorry, have to go AFK soon....... 
07:16  * jasan will be here
07:16 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Remote host closed the connection]
07:16 < ark> log file size is 109MB
07:17 < ark> sorry, I'm checking everything
07:17 < jasan> ark: everything fine
07:18 < jasan> ark: do you have any github access to gist it? Or may I offer you a tor endpoint where you can netcat it?
07:22  * jasan sent ark the details how to send the log to an onion endpoint
07:25 < ark> I have done all the checks you say with bitcoin-cli and it works
07:25 < ark> The credentials were set with the --bitcoin-rpcpassword and --bitcoin-rpcuser options
07:25 < zmnscpxj_> bitcoind is on the same machine?
07:30 < ark> no, it's in different docker containers
07:31 < zmnscpxj_> possibly something interrupted their interconnection?
07:31  * zmnscpxj_ is ignorant of docker
07:32 < ark> It is possible that the connection could have been lost at some point, but if for some reason a container falls, it will restart itself
07:33 < zmnscpxj_> could be the root cause? `lightningd` mostly assumes it is running on the same machine as the `bitcoind`
07:33 < zmnscpxj_> but not sure about docker...
07:35 -!- az0re [~az0re@gateway/tor-sasl/az0re] has joined #c-lightning
07:37 < ark> From what I have seen, it assumes that you have access to bitcoin-cli and it allows the connection through the network, so it has some parameters of ip: port
07:38 < zmnscpxj_> yes, but it is not as well tested as the case where everything is in the same machine
07:38 < zmnscpxj_> you could try increasing the timeout though
07:38 < jasan> --bitcoin-retry-timeout
07:38 < zmnscpxj_> yes
07:58 -!- kexkey [~kexkey@static-198-54-132-91.cust.tzulo.com] has joined #c-lightning
08:04 < ark> I seem to have found the cause
08:04 < ark> bitcoind is using cookie mode
08:04 < ark> And since I did not see an option in lightning to use the bitcoin cookie, I put the content of that file in the LN parameters as username and password.
08:04 < ark> But it seems the cookie has changed
08:04 < zmnscpxj_> ah, possibly.
08:05 < zmnscpxj_> and if the bitcoind is on another (virtual) computer then the lightningd-runner cannot read the cookie file...?
08:07 < jasan> yes
08:09 < jasan> ark: use rather share/rpcauth.py to generate rpcauth for bitcoind, it will also write you the password; username you choose (./rpcauth.py <username>)
08:09 < jasan> that's bitcoin/share/rpcauth/rpcauth.py
08:13 < ark> thanks
08:14 < ark> It should also not crash
08:15 < zmnscpxj_> crashing is how it gets your attention
08:17 < jasan> we (humans) learn by crashes
08:17 < jasan> OK, leaving now
08:18 -!- jasan [~j@n.bublina.eu.org] has quit [Quit: Bye!]
09:20 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has joined #c-lightning
09:53 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Remote host closed the connection]
09:53 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #c-lightning
10:30 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Remote host closed the connection]
10:34 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has joined #c-lightning
10:36 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Remote host closed the connection]
10:40 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has joined #c-lightning
10:41 -!- DeanWeen [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning
10:42 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection]
10:50 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Ping timeout: 240 seconds]
11:20 -!- DeanWeen [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection]
11:20 -!- DeanWeen [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning
11:27 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
11:31 -!- liberliver [~Thunderbi@144.49.211.130.bc.googleusercontent.com] has quit [Ping timeout: 240 seconds]
12:22 -!- nothingmuch_ is now known as nothingmuch
12:52 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 256 seconds]
13:00 -!- zmnscpxj_ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has quit [Ping timeout: 240 seconds]
13:31 -!- DeanWeen [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection]
13:32 -!- DeanWeen [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning
13:49 -!- DeanWeen [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection]
13:49 -!- DeanWeen [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning
14:08 -!- vasild_ [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
14:09 -!- kristapsk_ [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection]
14:10 -!- kristapsk_ [~KK@gateway/tor-sasl/kristapsk] has joined #c-lightning
14:12 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
14:12 -!- vasild_ is now known as vasild
14:18 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
14:26 -!- Jackielove4u [uid43977@gateway/web/irccloud.com/x-mxowwcwnuzktweyq] has quit [Ping timeout: 260 seconds]
14:26 -!- Jackielove4u [uid43977@gateway/web/irccloud.com/x-lecmkndyxyxbgylp] has joined #c-lightning
14:28 -!- fiatjaf [~fiatjaf@2804:7f2:2986:ebf7:ea40:f2ff:fe85:d2dc] has quit [Ping timeout: 260 seconds]
14:29 -!- user998_ [~user@2a03:b0c0:1:e0::6f8:6001] has joined #c-lightning
14:29 -!- fiatjaf [~fiatjaf@2804:7f2:2986:ebf7:ea40:f2ff:fe85:d2dc] has joined #c-lightning
14:31 < user998_> if I want to run MANY wallets on the same machine, what are my options?
14:31 < user998_> Do I need to containerize each instance of c-lightning?
14:41 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-lsntjcdlexygkbwj] has left #c-lightning []
14:41 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-lsntjcdlexygkbwj] has joined #c-lightning
15:12 -!- Ed0 [~edouard@2001:41d0:401:3100::4897] has quit [Ping timeout: 244 seconds]
15:13 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Ping timeout: 240 seconds]
15:13 -!- t0mix [~t0mix@78-141-123-99.dynamic.orange.sk] has quit [Ping timeout: 240 seconds]
15:15 -!- Ed0 [~edouard@137.ip-193-70-113.eu] has joined #c-lightning
15:26 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #c-lightning
15:35 -!- kristapsk_ [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection]
15:53 < rusty> user998_: no, you can just run them with different ports and different --lightning-dir.
15:54 < rusty> (Assuming you want them to receive incoming connections...)
15:59 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has joined #c-lightning
16:20 -!- DeanWeen [~dean@gateway/tor-sasl/deanguss] has quit [Ping timeout: 240 seconds]
16:36 < user998_> @rusty that is awesome!
16:36 < rusty> Yeah, they can all share a bitcoind too
16:37 < user998_> just set rpcmax to 4*(number of c-l instances), right?
16:41 < rusty> user998_: oh yeah, it will get upset about that :)
16:43 < user998_> do you think I could host 100 or 1000 c-l's on a decent server?
16:43 < user998_> rusty: do you think I could host 100 or 1000 c-l's on a decent server?
16:48 < rusty> user998_: hmm, I don't know! Looking on my node now.
16:52 < rusty> CPU won't be a problem, but memory might be.  We haven't optimized that mich
16:53 < user998_> how much RAM per instance?
17:12 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 240 seconds]
18:19 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
19:06 -!- DeanWeen [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning
19:54 -!- belcher_ [~belcher@unaffiliated/belcher] has joined #c-lightning
19:57 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 240 seconds]
20:08 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning
20:55 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Ping timeout: 240 seconds]
21:04 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #c-lightning
21:21 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Remote host closed the connection]
21:22 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #c-lightning
21:29 -!- cltrbreak_MAD2 [~ctrlbreak@159.2.182.106] has joined #c-lightning
21:33 -!- ctrlbreak_MAD [~ctrlbreak@159.2.182.106] has quit [Ping timeout: 272 seconds]
22:58 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-lsntjcdlexygkbwj] has left #c-lightning []
22:59 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-lsntjcdlexygkbwj] has joined #c-lightning
--- Log closed Thu Nov 19 00:00:21 2020