--- Day changed Sun Mar 25 2018 00:04 -!- simlay [~simlay@gateway/tor-sasl/simlay] has joined #lnd 00:28 -!- simlay [~simlay@gateway/tor-sasl/simlay] has quit [Ping timeout: 268 seconds] 00:30 -!- simlay [~simlay@gateway/tor-sasl/simlay] has joined #lnd 01:02 -!- colatkinson [~colatkins@cpe-67-240-56-42.nycap.res.rr.com] has quit [Quit: colatkinson] 02:07 -!- anome [~anome@unaffiliated/anome] has joined #lnd 02:11 -!- deusexbeer [~deusexbee@095-129-169-253-dynamic-pool-adsl.wbt.ru] has joined #lnd 02:20 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #lnd 02:21 -!- afoutopatisa [5027c0bb@gateway/web/freenode/ip.80.39.192.187] has quit [Quit: Page closed] 02:24 -!- anome [~anome@unaffiliated/anome] has quit [] 02:36 -!- simlay [~simlay@gateway/tor-sasl/simlay] has quit [Ping timeout: 268 seconds] 02:51 -!- anome [~anome@unaffiliated/anome] has joined #lnd 03:00 -!- weedcoder [~weedcoder@pro75-4-82-238-201-154.fbx.proxad.net] has quit [Quit: weedcoder] 03:00 -!- anome [~anome@unaffiliated/anome] has quit [] 03:41 -!- shtirlic [~shtirlic@Shtirlic-2-pt.tunnel.tserv6.fra1.ipv6.he.net] has quit [Quit: ZNC - http://znc.in] 03:42 -!- shtirlic [~shtirlic@Shtirlic-2-pt.tunnel.tserv6.fra1.ipv6.he.net] has joined #lnd 04:16 -!- User__ [~User@133-203.dorm.ncu.edu.tw] has joined #lnd 04:20 -!- ken2812221 [~User@133-203.dorm.ncu.edu.tw] has quit [Ping timeout: 264 seconds] 04:24 -!- Giszmo [~leo@pc-37-38-86-200.cm.vtr.net] has quit [Ping timeout: 246 seconds] 04:28 -!- Giszmo [~leo@pc-37-38-86-200.cm.vtr.net] has joined #lnd 04:37 -!- larafale [~larafale@ax213-1-82-66-157-194.fbx.proxad.net] has joined #lnd 04:38 -!- anome [~anome@unaffiliated/anome] has joined #lnd 04:39 -!- jchia_1 [~jchia@116.192.18.160] has quit [Ping timeout: 264 seconds] 04:40 -!- drexl [~drexl@cpc130676-camd16-2-0-cust445.know.cable.virginm.net] has joined #lnd 04:41 -!- larafale [~larafale@ax213-1-82-66-157-194.fbx.proxad.net] has quit [Read error: Connection reset by peer] 04:57 -!- conundru- is now known as conundrum 04:58 -!- offerm [c7cb6522@gateway/web/freenode/ip.199.203.101.34] has joined #lnd 05:00 < offerm> Hi Guys, What can be the reason for this error? 05:00 < offerm> 2018-03-25 10:41:48.574 [DBG] PEER: Received ChannelAnnouncement(chain_hash=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f, short_chan_id=553951550347608065) from 35.227.81.65:9735 2018-03-25 10:41:48.574 [DBG] PEER: Received NodeAnnouncement(node=03bd3466efd4a7306b539e2314e69efc6b1eaee29734fcedd78cf81b1dde9fedf8, update_time=2018-02-07 12:14:58 +0200 IST) from 35.227.81.65:9735 2018-03-25 10:41:48.574 [ERR] DISC: Igno 05:01 < offerm> Ignoring ChannelAnnouncement from chain=%v, gossiper on chain=%v 000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f 000000000933ea01ad0ee984209779baaec3ced90fa3f408719526f8d77f4943 05:01 < offerm> I'm using lnd with the following : lnd --bitcoin.active --bitcoin.testnet --debuglevel=debug --bitcoin.node=neutrino --neutrino.connect=faucet.lightning.community 05:07 < lndbot> offerm, one is testnet the other is mainnet. there’s been some cross pollination due to mixing of dns records, but some might still be propagating 05:10 < offerm> I'm getting these channels from faucet.lightning.community. Should i announce mainnet channels? 05:11 < offerm> "should it" 05:15 -!- jchia_1 [~jchia@45.32.62.73] has joined #lnd 05:18 -!- Giszmo [~leo@pc-37-38-86-200.cm.vtr.net] has quit [Ping timeout: 240 seconds] 05:19 -!- jchia_1 [~jchia@45.32.62.73] has quit [Remote host closed the connection] 05:19 < offerm> I now see that it is not from faucet.lightning.community but from a random node. 05:20 -!- jchia_1 [~jchia@45.32.62.73] has joined #lnd 05:21 -!- jchia_1 [~jchia@45.32.62.73] has quit [Remote host closed the connection] 05:21 -!- jchia_1 [~jchia@116.192.18.160] has joined #lnd 05:24 -!- anome [~anome@unaffiliated/anome] has quit [] 05:26 -!- Akihabara [Akihabara@static.163.101.201.195.clients.your-server.de] has quit [] 05:29 < offerm> connor, what should I do to get initial nodes from testnet? 05:38 -!- anome [~anome@unaffiliated/anome] has joined #lnd 05:43 -!- anome [~anome@unaffiliated/anome] has quit [] 05:52 -!- anome [~anome@unaffiliated/anome] has joined #lnd 05:53 -!- Akihabara [Akihabara@static.163.101.201.195.clients.your-server.de] has joined #lnd 05:55 -!- belcher [~belcher@unaffiliated/belcher] has joined #lnd 06:03 -!- anome [~anome@unaffiliated/anome] has quit [] 06:19 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-qthllmupynntxgur] has quit [Quit: Connection closed for inactivity] 06:52 -!- anome [~anome@unaffiliated/anome] has joined #lnd 07:13 -!- anome [~anome@unaffiliated/anome] has quit [] 07:38 -!- anome [~anome@unaffiliated/anome] has joined #lnd 07:47 -!- Argonath [bb41ddc5@gateway/web/freenode/ip.187.65.221.197] has joined #lnd 07:50 < Argonath> some of my channels are turning active:false after a few hours.. what is probably the answer for that? 07:57 -!- _Ulmo_ [1804e4d5@gateway/web/freenode/ip.24.4.228.213] has joined #lnd 07:58 -!- _Ulmo_ is now known as Ulmo 07:58 < Ulmo> Hello lnd. What happens if I pay the same invoice twice? 08:00 -!- anome [~anome@unaffiliated/anome] has quit [] 08:02 -!- weedcoder [~weedcoder@pro75-4-82-238-201-154.fbx.proxad.net] has joined #lnd 08:03 -!- Ulmo [1804e4d5@gateway/web/freenode/ip.24.4.228.213] has quit [Ping timeout: 260 seconds] 08:07 <@mlz> nothing? 08:08 -!- anome [~anome@unaffiliated/anome] has joined #lnd 08:08 <@mlz> Argonath, they're probably offline 08:10 < Argonath> well, not so sure.. one of them is the Yalls mainnet node.. I do think I'm having this same issue here https://github.com/lightningnetwork/lnd/issues/901 08:21 -!- offerm [c7cb6522@gateway/web/freenode/ip.199.203.101.34] has quit [Ping timeout: 260 seconds] 08:41 -!- anome [~anome@unaffiliated/anome] has quit [] 08:47 -!- Giszmo [~leo@pc-37-38-86-200.cm.vtr.net] has joined #lnd 09:03 < Veggen> mlz: there's currently no protection against paying same invoice twice, I think. 09:03 <@mlz> yea roasbeef had to change it to do something i forget 09:07 < Veggen> preparations for AM? 09:07 < Veggen> AMP? 09:17 < BB-Martino> Being able to pay the same invoice twice would allow for donation invoices, no? Where you don't need to identify who the payment came from. 09:18 < Veggen> mmm, probably. but you should switch it every 2nd hour or so. 09:18 < Veggen> or, let lifetime be very long. not sure if that gives problems. 09:24 -!- anome [~anome@unaffiliated/anome] has joined #lnd 09:30 -!- anome [~anome@unaffiliated/anome] has quit [] 09:47 -!- jchia_1 [~jchia@116.192.18.160] has quit [Ping timeout: 240 seconds] 09:57 -!- deusexbeer [~deusexbee@095-129-169-253-dynamic-pool-adsl.wbt.ru] has quit [Quit: Konversation terminated!] 10:00 < Argonath> there is a command to check the history of closed channels? 10:05 -!- jchia_1 [~jchia@116.192.18.160] has joined #lnd 10:13 -!- deusexbeer [~deusexbee@095-129-169-253-dynamic-pool-adsl.wbt.ru] has joined #lnd 10:39 < k1234> question: why would my value in lncli channelbalance fluctuate when a) I haven't added any new channels and b) lncli fwdinghistory is empty? 10:59 < BB-Martino> people opening channels to you maybe? 11:00 < BB-Martino> ps. thanks for 'fwdinghistory' - I didn't know that existed. 11:00 < BB-Martino> if I routed a payment, it would show up in there? 11:01 < Veggen> fwdinghistory? yes. 11:01 < BB-Martino> darn. it's empty :( 11:05 < Veggen> it empties each day. 11:06 < Veggen> however, feereport will show fees collected (last month or so, I think) 11:09 < BB-Martino> very useful. thank you, kind sir. 11:10 < BB-Martino> i just wish the fwdinghistory didn't empty daily but i can grab it and put it in a DB 11:11 < BB-Martino> my fwdhistory says: 4 satoshis earned this week. /quits job 11:32 -!- rls [~rls@user-24-214-190-146.knology.net] has joined #lnd 11:33 -!- psyopp [~rls@74.120.222.234] has joined #lnd 11:36 -!- rls [~rls@user-24-214-190-146.knology.net] has quit [Ping timeout: 248 seconds] 11:37 < k1234> bb-martino: someday... 11:38 < k1234> question: can someone eli5 what the ""num_updates": "46"," in lncli listchannels means. What are the channel "updates" and which node initiates these? 11:38 < k1234> clarification: which node in the channel? IE: the one that initiated the channel, or the one to whom the channel connects? 11:41 -!- ChunkyPuffs [~ChunkyPuf@gateway/tor-sasl/chunkypuffs] has quit [Remote host closed the connection] 11:42 -!- dermoth [~dermoth@gateway/tor-sasl/dermoth] has quit [Remote host closed the connection] 11:42 -!- ChunkyPuffs [~ChunkyPuf@gateway/tor-sasl/chunkypuffs] has joined #lnd 11:42 -!- dermoth [~dermoth@gateway/tor-sasl/dermoth] has joined #lnd 11:43 -!- k1234 [62dfe998@gateway/web/freenode/ip.98.223.233.152] has quit [Ping timeout: 260 seconds] 11:51 <@mlz> im still not clear what "num_updates" actually means, i think it's the number how many times your node is connected to another node and the gossip is exchanged between the nodes but im not sure 11:51 <@mlz> connected but doesn't mean they stay connected 12:06 < doodah> I bet the channelbalance fluctuations are from the commit_fee changing due to fee estimation. 12:07 -!- deusexbeer [~deusexbee@095-129-169-253-dynamic-pool-adsl.wbt.ru] has quit [Read error: Connection reset by peer] 12:08 -!- deusexbeer [~deusexbee@093-092-177-126-dynamic-pool-adsl.wbt.ru] has joined #lnd 12:12 -!- ChunkyPuffs [~ChunkyPuf@gateway/tor-sasl/chunkypuffs] has quit [Remote host closed the connection] 12:12 -!- ChunkyPuffs [~ChunkyPuf@gateway/tor-sasl/chunkypuffs] has joined #lnd 12:14 -!- anome [~anome@unaffiliated/anome] has joined #lnd 12:22 -!- anome [~anome@unaffiliated/anome] has quit [] 12:50 -!- anome [~anome@unaffiliated/anome] has joined #lnd 12:54 -!- anome [~anome@unaffiliated/anome] has quit [Client Quit] 12:55 -!- anome [~anome@unaffiliated/anome] has joined #lnd 12:59 -!- anome [~anome@unaffiliated/anome] has quit [Client Quit] 13:09 -!- psyopp [~rls@74.120.222.234] has quit [Remote host closed the connection] 13:11 -!- jambi [~jim@213.152.161.25] has joined #lnd 13:20 -!- fusion44 [~fusion44@p2E59FE2A.dip0.t-ipconnect.de] has quit [Quit: Leaving.] 13:31 -!- skyrus [2fbd49aa@gateway/web/freenode/ip.47.189.73.170] has joined #lnd 13:33 < skyrus> i have a concern regarding the channel.db file, it seems as if there are issues when you try to use an outdated channel.db (only containing outdated channel states) is't this a major issue? it means there is no way to back up the channel.db file, not practically anyway because updates happen so frequently 13:35 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 256 seconds] 13:49 -!- belcher [~belcher@unaffiliated/belcher] has joined #lnd 13:52 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Ping timeout: 264 seconds] 13:58 -!- anome [~anome@unaffiliated/anome] has joined #lnd 13:58 -!- anome [~anome@unaffiliated/anome] has quit [Client Quit] 14:00 -!- anome [~anome@unaffiliated/anome] has joined #lnd 14:01 -!- anome [~anome@unaffiliated/anome] has quit [Client Quit] 14:31 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #lnd 14:43 -!- anome [~anome@unaffiliated/anome] has joined #lnd 14:58 -!- pioklo [~Pioklo@118-40.echostar.pl] has joined #lnd 15:28 < cluelessperson> Since the connection is refused 15:28 < cluelessperson> I think maybe bitcoind has banned it 15:34 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-vqoulstqjkxoeqen] has joined #lnd 15:37 < lndbot> skyrus, there would be a db migration between official releases. those could be applied retroactively 15:37 -!- anome [~anome@unaffiliated/anome] has quit [] 15:38 < skyrus> conner: no I'm talking about state info, even a small state change that is missed puts the entire channel capacity at risk, seems like it would be useful for nodes to offer state information to nodes which may have lost it 15:41 < lndbot> ahh, yeah this is something we will be exploring with watchtowers and static backup schemes 15:41 < lndbot> we already support the ability to detect if you’ve lost data 15:41 < lndbot> next step, recovering 15:42 < lndbot> small steps :slightly_smiling_face: 15:43 < lndbot> ^^ :nerd_face: 15:44 < lndbot> btw @conner did you check what I posted on dev-talk? 15:56 -!- skyrus [2fbd49aa@gateway/web/freenode/ip.47.189.73.170] has quit [Quit: Page closed] 15:58 -!- rls [~rls@67.215.10.250] has joined #lnd 16:15 -github-lnd:#lnd- [lnd] alexbosworth opened pull request #942: htlcswitch: trivial whitespace (master...patch-3) https://git.io/vx0LO 16:28 -!- roasbeef [~root@104.131.26.124] has quit [Ping timeout: 252 seconds] 16:30 -!- roasbeef [~root@104.131.26.124] has joined #lnd 16:45 -!- AndBobsYourUncle [~AndBobsYo@cpe-23-240-21-154.socal.res.rr.com] has joined #lnd 16:48 -!- pioklo [~Pioklo@118-40.echostar.pl] has quit [Ping timeout: 265 seconds] 17:22 -!- drexl [~drexl@cpc130676-camd16-2-0-cust445.know.cable.virginm.net] has quit [Remote host closed the connection] 17:24 -!- melvster [~melvin@ip-86-49-18-198.net.upcbroadband.cz] has quit [Ping timeout: 240 seconds] 17:31 -!- k1234 [62dfe998@gateway/web/freenode/ip.98.223.233.152] has joined #lnd 17:32 < k1234> question: I've had an "unconfirmed balance" for 4+ days when I run lncli walletbalance. What can I do to refresh this (no pending channels, no new channels created). Seems like a failure to adequatel update balances... I have restarted lnd and bitcoind. What to do? 17:33 -!- rls [~rls@67.215.10.250] has quit [Remote host closed the connection] 17:35 <@mlz> k1234, have you tried to withdraw that amount? 17:50 -!- colatkinson [~colatkins@cpe-67-240-56-42.nycap.res.rr.com] has joined #lnd 18:06 -!- colatkinson [~colatkins@cpe-67-240-56-42.nycap.res.rr.com] has quit [Ping timeout: 240 seconds] 18:20 < k1234> @mlz: I haven't yet... Will do so and report back. 18:21 < k1234> I do know that when I have tried to open a channel with > the confirmed amount it has thrown an error... 18:29 -github-onion:#lnd- [lightning-onion] Roasbeef pushed 2 new commits to master: https://git.io/vx0OZ 18:29 -github-onion:#lnd- lightning-onion/master 804f616 Matt Drollette: ensure replays is fully initialized before using it 18:29 -github-onion:#lnd- lightning-onion/master c861375 Olaoluwa Osuntokun: Merge pull request #23 from MDrollette/nil-replayset... 18:31 -!- camulos [~user@103.77.78.248] has joined #lnd 18:40 -github-lnd:#lnd- [lnd] Roasbeef pushed 1 new commit to master: https://git.io/vx0O7 18:40 -github-lnd:#lnd- lnd/master 23b3eaf Olaoluwa Osuntokun: build: update lightning-onion commit hash... 18:54 -!- belcher [~belcher@unaffiliated/belcher] has quit [Quit: Leaving] 19:18 -github-lnd:#lnd- [lnd] Roasbeef opened pull request #943: lnwallet: use btcutil.NewAmount for BTC -> SAT conversions (master...btc-rounding-fix) https://git.io/vx0s5 19:24 < roasbeef> mlz: yeh we can add a min channel size to accept for incoming channels 19:24 < roasbeef> there's an issue for this i think 19:24 -!- Argonath [bb41ddc5@gateway/web/freenode/ip.187.65.221.197] has quit [Quit: Page closed] 19:26 < roasbeef> to add more node policy for accepting incoming channels 19:26 < roasbeef> orium: if/when others add inbound bandwidth towards you, then that can be used to start to rebalance channels 19:27 < roasbeef> BB-Martino: all those maps are really just the data of other people, they aren't authorotative 19:27 < roasbeef> HighVoltage: it may have been that the fee set was too low? iirc litecoin still has priority in their default mining policy, so you can try to rebroadcast the txn, tho lnd will itself on restart 19:29 -github-lnd:#lnd- [lnd] Roasbeef closed pull request #938: Invoice macaroon path fix (master...hotfix/invoice-macaroon-path) https://git.io/vxRt4 19:29 < roasbeef> cluelessperson: soon you'll just run lnd, and that's it 19:29 < roasbeef> cluelessperson: is it unclear? it's in the docs, and also the sample lnd conf 19:30 < roasbeef> cluelessperson: https://github.com/lightningnetwork/lnd/blob/master/docs/INSTALL.md#running-lnd-using-the-bitcoind-or-litecoind-backend 19:31 < roasbeef> cluelessperson: gotta configure zmq on the bitcoind node 19:31 < roasbeef> fwdinghistory only shows the past day 19:31 < roasbeef> you can do custom time range queries if you look at the args for the command 19:31 < roasbeef> tho they're in unix teimstamps, so a bit hard to use on the command line 19:32 < roasbeef> perhaps we should add like a `--last-month` flag and things like that 19:32 < roasbeef> or num days, etc 19:32 < roasbeef> k1234: channels acn be updated when things are routed, or just due to the fee on the commitment transaction being updated 19:33 < k1234> roasbeef: thx. 19:33 < roasbeef> k1234: look at the logs when you restart, do you see a rebroadcast attempt? 19:33 < roasbeef> we'll try to rebroadcast things that don't get confirmed on resrtart 19:33 < roasbeef> you can also try to increase the logging level of LNWL 19:33 < k1234> checking logs... 19:48 -!- DrOlmer [~DrOlmer@unaffiliated/drolmer] has quit [Quit: Leaving] 19:54 < k1234> roasbeef: can't find a rebroadcast attempt in the logs. the tx (onchain) that I think is causing this issue is this one: 2cd28abb8306bd7f9ecdd57564639e46a0630696a919eb59bd4b36c324aad8e9 (although I'm not sure about this...) 19:55 < k1234> you seem to be implying that it's a broadcast issue for onchain txns... is that what you're saying? 19:55 < roasbeef> why do you think that tx is causing an issue? 19:55 < roasbeef> it was spent already 19:55 < roasbeef> if there're unconfirmed outputs, it'll try to retransmit em 19:56 < k1234> I think that transaction is causing the issue because it's the only one near the amount listed as unconfirmed in my lncli walletbalance. 19:56 < k1234> obviously not a large amount... jsut trying to figure out what happened. 19:57 < k1234> all of my lncli listchaintxns are confirmed, but the lncli walletbalance shows an "unconfirmed balance" value. 19:57 < k1234> so I'm not sure what is going on... I don't believe there are any unconfirmed outputs... or, at least, I don't know how to know if there are or what their txid is.... 19:58 < k1234> or how to find them (given that I've already looked in lncli listchaintxns) 19:59 -!- colatkinson [~colatkins@cpe-67-240-56-42.nycap.res.rr.com] has joined #lnd 19:59 < k1234> is there a way to see a list of what transactions are being calculated into the "unconfirmed balance" in lncli walletbalance? 20:01 -!- colatkinson [~colatkins@cpe-67-240-56-42.nycap.res.rr.com] has quit [Client Quit] 20:36 < camulos> how do i convert a payment request to a QR code? (so that wallets like eclair can use it) 20:41 -!- colatkinson [~colatkins@cpe-67-240-56-42.nycap.res.rr.com] has joined #lnd 20:51 -!- weedcoder [~weedcoder@pro75-4-82-238-201-154.fbx.proxad.net] has quit [Quit: weedcoder] 20:54 -!- psyopp [~rls@74.120.222.234] has joined #lnd 21:02 <@mlz> k1234, what's the txid for the unconfirmed tx? 21:02 -!- camulos [~user@103.77.78.248] has left #lnd [] 21:17 -!- colatkinson [~colatkins@cpe-67-240-56-42.nycap.res.rr.com] has quit [Quit: colatkinson] 21:18 -!- naribia [2fbd49aa@gateway/web/freenode/ip.47.189.73.170] has joined #lnd 21:54 < cluelessperson> roasbeef: zmq is configured on bitcoind, but I get connection refused 21:55 < cluelessperson> connection refused means the connection was rejected/closed, rather than nothing being there to listen 21:55 < cluelessperson> suggests bitcoind ban or something 21:55 < cluelessperson> I'm uncertain 21:55 < cluelessperson> also, server=1 appears to be required to enable json rpc usage 21:55 < cluelessperson> will test :) 22:06 -!- colatkinson [~colatkins@cpe-67-240-56-42.nycap.res.rr.com] has joined #lnd 22:11 < Veggen> nono. 22:11 < Veggen> connection refused usually means nothing listened. 22:12 < cluelessperson> Veggen: I might be wrong, it's been awhile. 22:12 < cluelessperson> Veggen: pretty sure I'd just get a timeout if nothing's listening 22:12 < Veggen> timeout would be if there's no ip-address there. Or theres a firewall dropping it. 22:13 < cluelessperson> Veggen: ah, well, I cannot seem to open a telnet to 127.0.0.1 28332 22:13 < cluelessperson> not sure why 22:13 < Veggen> netstat -an | grep LISTEN 22:14 < Veggen> netstat -an | grep LISTEN | grep tcp 22:14 < Veggen> (last one is better) 22:14 < cluelessperson> that port isn't listening 22:14 < Veggen> which means that bitcoind doesn't have zmq on that port :) 22:14 < cluelessperson> https://hastebin.com/raw/odujicafoh 22:14 < cluelessperson> I see, not sure why 22:15 < cluelessperson> ./configure shows zmq enabled, and it's in the conf 22:16 < Veggen> what's your bitcoin.conf ? 22:16 < cluelessperson> Veggen: https://hastebin.com/raw/petamujuge 22:17 * cluelessperson will change the hashes -_-; 22:18 < Veggen> no zmq support in bitcoind? 22:19 < cluelessperson> ...I might be stupid 22:19 < cluelessperson> I'm sorry, I'm stupid. 22:20 < cluelessperson> didn't redo MAKE after reconfiguring 22:20 < cluelessperson> AHHHH 22:20 < Veggen> :) 22:21 * cluelessperson greps his command history for make 22:21 < cluelessperson> nope 22:22 < cluelessperson> For future reference, is there a method to check for ZMQ, say in bitcoind's log, or version info? 22:25 -github-onion:#lnd- [lightning-onion] randolf opened pull request #24: Improvements to spelling, punctuation, and grammar (master...patch-1) https://git.io/vx08W 22:29 < cluelessperson> Veggen: So, what really confused me at the beginning, is that it first showed as a 401 error 22:29 < cluelessperson> from there I just assumed it was there 22:38 < cluelessperson> woot 22:42 < cluelessperson> Sorry for being a pain in the ass everyone 22:43 -!- psyopp [~rls@74.120.222.234] has quit [Read error: Connection reset by peer] 22:45 -!- rls [~rls@74.120.222.234] has joined #lnd 22:47 -!- dermoth [~dermoth@gateway/tor-sasl/dermoth] has quit [Remote host closed the connection] 22:48 -!- dermoth [~dermoth@gateway/tor-sasl/dermoth] has joined #lnd 22:58 < CubicEarths> Anyone know what this is about: 2018-03-25 07:21:46.159 [ERR] CMGR: Can't accept connection: accept tcp [::]:9735: accept4: too many open files 23:01 < cluelessperson> CubicEarths: electrum server has run into that problem a bit, it required raising the open file limit 23:01 * cluelessperson google searches 23:02 < cluelessperson> echo "bitcoin hard nofile 131072" >> /etc/security/limits.conf 23:02 < cluelessperson> echo "bitcoin soft nofile 131072" >> /etc/security/limits.conf 23:02 < cluelessperson> CubicEarths: ^ something like that 23:03 < cluelessperson> CubicEarths: you can also search for, "ulimit for user" 23:04 < cluelessperson> --- 23:09 -!- rls [~rls@74.120.222.234] has quit [Remote host closed the connection] 23:29 < CubicEarths> Interesting. I running stock ubuntu and only LND and Bitcoind. I assume there must be a way to address on LNDs side of things 23:32 < cluelessperson> CubicEarths: there isn't 23:32 < cluelessperson> CubicEarths: this is an OS/environment option that limits the number of connections/open files a user can have on the system 23:32 < cluelessperson> CubicEarths: some services require hundreds of thousands, for example with databases 23:35 < CubicEarths> In this case, are open files and connections counted the same way and added up? They seem like different things to me. 23:36 < cluelessperson> CubicEarths: yes 23:36 < cluelessperson> CubicEarths: run the command, "lsof" 23:36 < cluelessperson> list open files 23:39 < CubicEarths> lots of output!