question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Hello! I’m having trouble using ZAP for the first time. Trying on a MBP running latest macOS.

I’ve attempted getting rid of the data folder, removing Lnd folder entirely, and on different networks.

Below is the content of my logs. This has been the output for a few days:

2018-07-14 20:50:13.746 [INF] LTND: Version 0.3.0-alpha
2018-07-14 20:50:13.748 [INF] CHDB: Checking for schema update: latest_version=0, db_version=0
2018-07-14 20:50:13.751 [INF] RPCS: Generating TLS certificates...
2018-07-14 20:50:15.479 [INF] RPCS: Done generating TLS certificates
2018-07-14 20:50:15.480 [INF] LTND: Primary chain is set to: bitcoin
2018-07-14 20:50:15.530 [INF] BTCN: Loaded 0 addresses from file '/Users/parthmehrotra/Library/Application Support/Lnd/data/testnet3/bitcoin/peers.json'
2018-07-14 20:50:15.531 [DBG] CMGR: Attempting to connect to 127.0.0.1:18333 (reqid 2)
2018-07-14 20:50:15.531 [DBG] CMGR: Attempting to connect to 188.166.148.62:18333 (reqid 1)
2018-07-14 20:50:15.532 [DBG] CMGR: Failed to connect to 127.0.0.1:18333 (reqid 2): dial tcp 127.0.0.1:18333: getsockopt: connection refused
2018-07-14 20:50:15.532 [DBG] CMGR: Retrying connection to 127.0.0.1:18333 (reqid 2) in 5s
2018-07-14 20:50:15.535 [INF] CMGR: DNS discovery failed on seed x49.testnet-seed.bitcoin.jonasschnelli.ch: lookup x49.testnet-seed.bitcoin.jonasschnelli.ch: no such host
2018-07-14 20:50:15.569 [INF] CMGR: 3 addresses found from DNS seed testnet-seed.bluematt.me
2018-07-14 20:50:15.630 [DBG] CMGR: Connected to 188.166.148.62:18333 (reqid 1)
2018-07-14 20:50:15.630 [DBG] BTCN: Sending version (agent /btcwire:0.5.0/neutrino:0.0.1-alpha/, pver 70013, block 0) to 188.166.148.62:18333 (outbound)
2018-07-14 20:50:15.727 [DBG] BTCN: Received version (agent /btcwire:0.5.0/btcd:0.12.0/, pver 70013, block 1353593) from 188.166.148.62:18333 (outbound)
2018-07-14 20:50:15.727 [DBG] BTCN: Negotiated protocol version 70013 for peer 188.166.148.62:18333 (outbound)
2018-07-14 20:50:15.727 [DBG] BTCN: Added time sample of 0s (total: 1)
2018-07-14 20:50:15.727 [INF] BTCN: New valid peer 188.166.148.62:18333 (outbound) (/btcwire:0.5.0/btcd:0.12.0/)
2018-07-14 20:50:15.727 [DBG] BTCN: Connected to 188.166.148.62:18333
2018-07-14 20:50:15.727 [DBG] BTCN: New peer 188.166.148.62:18333 (outbound)
2018-07-14 20:50:15.727 [INF] BTCN: Syncing to block height 1353593 from peer 188.166.148.62:18333
2018-07-14 20:50:15.727 [DBG] BTCN: Received verack from 188.166.148.62:18333 (outbound)
2018-07-14 20:50:15.727 [DBG] BTCN: Sending getaddr to 188.166.148.62:18333 (outbound)
2018-07-14 20:50:15.728 [INF] BTCN: Downloading headers for blocks 1 to 546 from peer 188.166.148.62:18333
2018-07-14 20:50:15.728 [DBG] BTCN: Sending verack to 188.166.148.62:18333 (outbound)
2018-07-14 20:50:15.728 [DBG] BTCN: Sending getheaders (locator 000000000933ea01ad0ee984209779baaec3ced90fa3f408719526f8d77f4943, stop 000000002a936ca763904c3c35fce2f3556c559c0214345d31b1bcebf76acb70) to 188.166.148.62:18333 (outbound)
2018-07-14 20:50:15.904 [DBG] BTCN: Received addr (1000 addr) from 188.166.148.62:18333 (outbound)
2018-07-14 20:50:15.989 [DBG] BTCN: Received headers (num 546) from 188.166.148.62:18333 (outbound)
2018-07-14 20:50:15.995 [INF] BTCN: Verified downloaded block header against checkpoint at height 546/hash 000000002a936ca763904c3c35fce2f3556c559c0214345d31b1bcebf76acb70
2018-07-14 20:50:16.003 [DBG] BTCN: Sending getcfheaders to 188.166.148.62:18333 (outbound)
2018-07-14 20:50:16.003 [DBG] BTCN: Sending getcfheaders to 188.166.148.62:18333 (outbound)
2018-07-14 20:50:16.003 [DBG] BTCN: Sending getheaders (locator 000000002a936ca763904c3c35fce2f3556c559c0214345d31b1bcebf76acb70, stop 00000000009e2958c15ff9290d571bf9459e93b19765c6801ddeccadbb160a1e) to 188.166.148.62:18333 (outbound)
2018-07-14 20:50:16.088 [DBG] BTCN: Received reject (cmd malformed, code REJECT_MALFORMED, reason Cant read message from 96.65.16.158:51700 inbound: ReadMessage: payload exceeds max length  header indicates 66 bytes, but max payload size for messages of type getcfheaders is 37.) from 188.166.148.62:18333 (outbound)
2018-07-14 20:50:16.089 [ERR] BTCN: Can't read message from 188.166.148.62:18333 (outbound): read tcp 10.64.221.117:51700->188.166.148.62:18333: read: connection reset by peer
2018-07-14 20:50:16.089 [DBG] BTCN: Sending reject (cmd malformed, code REJECT_MALFORMED, reason Cant read message from 188.166.148.62:18333 outbound: read tcp 10.64.221.117:51700188.166.148.62:18333: read: connection reset by peer) to 188.166.148.62:18333 (outbound)
2018-07-14 20:50:16.089 [INF] BTCN: Lost peer 188.166.148.62:18333 (outbound)
2018-07-14 20:50:16.089 [DBG] BTCN: Removed peer 188.166.148.62:18333 (outbound)
2018-07-14 20:50:16.089 [DBG] CMGR: Disconnected from 188.166.148.62:18333 (reqid 1)
2018-07-14 20:50:16.090 [DBG] CMGR: Reconnecting to 188.166.148.62:18333 (reqid 1)
2018-07-14 20:50:16.090 [DBG] CMGR: Retrying connection to 188.166.148.62:18333 (reqid 1) in 5s
2018-07-14 20:50:16.094 [INF] BTCN: Catching up regular filter headers from 0 to 546
2018-07-14 20:50:16.094 [INF] BTCN: Catching up extended filter headers from 0 to 546
2018-07-14 20:50:16.094 [WRN] BTCN: No sync peer candidates available

The last couple log messages just repeat indefinitely beyond that point.

The ZAP client’s progress is stuck at 73%.

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:7 (4 by maintainers)

github_iconTop GitHub Comments

2reactions
mrfeltoncommented, Jul 15, 2018

Correct. (new release is coming shortly…)

0reactions
mrfeltoncommented, Jul 27, 2018

I’m closing this issue as it relates to an older version of Zap. The sync process has had an overhaul in v0.2.0.

Read more comments on GitHub >

github_iconTop Results From Across the Web

How To Fix the Steam Unable to Sync Files Error - Alphr
1. Launch the Steam app. 2. Navigate to “LIBRARY.” 3. Select the “Games” tab.
Read more >
How to fix Steam was unable to sync your files error
Steam was unable to sync your files · Check if the Steam servers are down. · Delete the userdata folder. · Verify the...
Read more >
7 Ways to Fix Steam when It's Unable to Sync Your Files
The Steam unable to sync files error arises because of corrupted cloud data, corrupted game files, and conflicting security utilities.
Read more >
Fix account sync issues - Android Help - Google Support
If your phone is having problems syncing with your Google Account, you could see a message, "Sync is currently experiencing problems.
Read more >
How To Fix Steam Was Unable To Sync Your Files Error [2022]
How to fix Steam was unable to sync your files error · Fix #1: Check the Steam servers status. · Fix #2: Adjust...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found