Assertion 'c->channel_state == CS_UP' failed at nest/rt-table.c:1543

[Ondrej Zajicek]

On Mon, Sep 23, 2019 at 04:18:00PM +0000, Christoph wrote:
> > If you can add 'debug { events, states };' option to the RPKI option,
> > could you send me the logs during protocol initialization? There should
> > be some part with 'Connected' and 'Changing ... state'.
> > 
> 
> I disabled and enabled it to trigger a sync:
> 
> disable r3k
> enable r3k
> 
> log (not sure if this helps):
> 
> 
> 2019-09-23 19:09:37.098 <INFO> Enabling protocol r3k
> 2019-09-23 19:09:37.098 <TRACE> r3k: Starting
> 2019-09-23 19:09:37.098 <TRACE> r3k: Changing from Down to Connecting state
> 2019-09-23 19:09:37.098 <TRACE> r3k: Opening a connection
> 2019-09-23 19:09:37.098 <TRACE> r3k: Connected
> 2019-09-23 19:09:37.098 <TRACE> r3k: State changed to up
> 2019-09-23 19:09:37.098 <TRACE> r3k: Changing from Connecting to
> Sync-Start state
> 2019-09-23 19:09:37.098 <TRACE> r3k: State changed to start

Thanks. This is strange, the protocol goes correctly to up state, but
then immediately fell back to start state for no obvious reason.

-- 
Elen sila lumenn' omentielvo

Ondrej 'Santiago' Zajicek (email: santiago at crfreenet.org)
OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net)
"To err is human -- to blame it on a computer is even more so."