> 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
2019-09-23 19:09:37.120 <TRACE> r3k: Changing from Sync-Start to
Sync-Running state
2019-09-23 19:09:37.121 <DBG> Assertion 'c->channel_state == CS_UP'
failed at nest/rt-table.c:1543
2019-09-23 19:09:37.121 <DBG> Assertion 'c->channel_state == CS_UP'
failed at nest/rt-table.c:1543
2019-09-23 19:09:37.121 <DBG> Assertion 'c->channel_state == CS_UP'
failed at nest/rt-table.c:1543
2019-09-23 19:09:37.121 <DBG> Assertion 'c->channel_state == CS_UP'
failed at nest/rt-table.c:1543
[...]
2019-09-23 19:09:51.531 <DBG> Assertion 'c->channel_state == CS_UP'
failed at nest/rt-table.c:1543
2019-09-23 19:09:51.531 <DBG> Assertion 'c->channel_state == CS_UP'
failed at nest/rt-table.c:1543
2019-09-23 19:09:51.531 <DBG> Assertion 'c->channel_state == CS_UP'
failed at nest/rt-table.c:1543
2019-09-23 19:09:51.531 <TRACE> r3k: New interval values: refresh: keeps
900s, retry: keeps 15s, expire: 7200s
2019-09-23 19:09:51.531 <TRACE> r3k: Changing from Sync-Running to
Established state
config:
-----------
roa4 table r4;
roa6 table r6;
protocol rpki r3k {
debug { events, states };
roa4 { table r4; };
roa6 { table r6; };
remote 127.0.0.1 port 1323;
retry keep 15;
refresh keep 900;
expire 14400;
}
-----------
