On 6/15/2018 6:21 PM, Viktor Dukhovni wrote:
On Jun 15, 2018, at 6:29 PM, Adam Lewenberg <ada...@stanford.edu> wrote:
This (or something much like it) appears in the initial replication on three
separate 1.5.2 slaves:
You *really* should upgrade the slaves as soon as possible,
however:
2018-06-15T17:45:12 ipropd-slave started at version: 0
2018-06-15T17:45:12 receive complete database
2018-06-15T17:45:47 receive complete database, version 114134
The master has a complete database snapshot whose version is
contiguous with the log. Therefore, instead of sending you
the full database, you're getting the snapshot + incremental
logs after that:
2018-06-15T17:46:44 replaying entry 114135
2018-06-15T17:46:44 replaying entry 114136
2018-06-15T17:46:44 replaying entry 114137
2018-06-15T17:46:44 replaying entry 114138
...
However, there's something amiss with the snapshot
or logs. Better to delete the snapshot on the
master and let it generate a new one, then resync
the slaves. Or there's something wrong with the
iprop code on the slaves, in any case a truly
complete snapshot stands a better chance.
Thanks for your quick reply.
When you say "delete the snapshot on the master and let it generate a
new one" I assume you meant "iprop-log truncate --reset", yes?
Anyway, I did that. All the slaves re-synced and now the "bad"
principals are showing up on the slaves.
Thanks!
Adam Lewenberg
