Zcash testnet sync stuck at block 299186

[garethtdavies]

My testnet sync got stuck at block 299186 and it is unclear how to resolve the issue to continue the sync. As the below it is having issues with this block https://explorer.testnet.z.cash/block/000001198d61f47868170a4aca6a10e7a1bfc80e316b9caa2cbaa12e3a8bf14f

2019-06-27 16:47:59  INFO sync Processed 1000 blocks in 3.06 seconds (326.49 blk/s).    Peers: 10 (act: 10, idl: 0, bad: 0).    Chain: [sch:16 > req:176 > vfy:288 > db:297770]
2019-06-27 16:48:00  INFO sync Switched to saturated state.     Chain: [sch:0 > req:0 > vfy:352 > db:298058]
2019-06-27 16:48:03  INFO sync Processed 1000 blocks in 2.87 seconds (348.25 blk/s).    Peers: 10 (act: 3, idl: 7, bad: 0).     Chain: [sch:0 > req:71 > vfy:306 > db:299153]
2019-06-27 16:48:03  WARN sync Block "000001198d61f47868170a4aca6a10e7a1bfc80e316b9caa2cbaa12e3a8bf14f" verification failed with error "Difficulty { expected: Compact(537395199), actual: Compact(503493845) }"
2019-06-27 16:48:03  WARN sync Disconnecting from peer#10 due to DoS: Provided wrong block 000001198d61f47868170a4aca6a10e7a1bfc80e316b9caa2cbaa12e3a8bf14f
2019-06-27 16:48:03  WARN sync Block "00ed878caf43a083e012e2f663ee6fac5365634daa77103f9c91a3ae3aba38c3" verification failed with error "Database(UnknownParent)"

Then there are a whole load of

2019-06-27 16:48:03 WARN sync Block "016e981dd1dc689e823804c25375dbd15299e185d40b36db67b3c7f99f8783b8" verification failed with error "Database(UnknownParent)"

and then has not moved from this state for the last 12+ hours:

2019-06-27 16:48:03  WARN sync Block "003d8d9d22b96ffeea1eae5f676b31a06c154e07a6b4a243f7b3c23161522610" verification failed with error "Database(UnknownParent)"
2019-06-27 16:48:04  WARN sync Previous header of the first header from peer#3 `headers` message is unknown. First: 00392e7db96749b147fc15ae9be27ee87075f3e54e88a1285edc0ecf3e226534. Previous: 005c460520287b86582fb344823641973891611d8e4e2ed7416150414475819d
2019-06-27 16:48:04  WARN sync Disconnecting from peer#3 due to misbehavior: Provided dead-end block 005b2f07849c27d7639350ca891aa94a94802cce056c3355736c2c6be5a6358b
2019-06-27 16:48:04  INFO sync Switched to saturated state.     Chain: [sch:0 > req:0 > vfy:0 > db:299187]
2019-06-27 16:48:04  WARN sync Last peer was marked as non-useful. Moving to saturated state.

[garethtdavies]

Writing that reminded me of the underlying issue see zcash/zcash#3552 and zcash/zcash#3568 and this commit zcash/zcash@aede10d

[hdevalence]

Hey, thanks for reporting this and giving detailed logs. Just as a heads' up, we probably won't try to fix it right now, but we will circle back and try to fix it after we've done more of the refactoring we're planning to get done.

[garethtdavies]

Understood. This does make it impossible to run on testnet at present (unless I am missing something) and the recommendation from the launch post of Zebra is to run only on testnet so this may become a popular issue for users.

[daira]

This issue seems to be obsolete.