[RPKI] Publication Error after upgrade to Krill 0.10.1

[Christopher Munz-Michielin]

Hello Tim,

Thanks for your reply.  I have managed to isolate this issue down to the 
upgrade from 0.9.6 to 0.10.0, I was able to bring myself up to 0.9.6 
successfully, but as soon as I applied the upgrade to 0.10.0 I received 
the publication error.

I can roll back by restoring the data directory, so that is not a 
concern.  I will email you off list about how to troubleshoot this.


On 2022-09-09 13:02, Tim Bruijnzeels wrote:
> Hi Christopher,
>
> This is unfortunate and unexpected as the same upgrade worked in our test environments.
>
> Perhaps the best cause of action is to try to downgrade again as follows:
>
> 1- stop krill
> 2- restore the data from before the migration
>
> You should find the following directories under your krill data dir (/var/lib/krill/data):
>
> Archive dirs from your old version:
> arch-cas-0.9.3
> arch-ca_objects-0.9.3
> arch-pubd-0.9.3
>
> and migrated dirs for your new version:
> cas
> ca_objects
> pubd
>
> Rename the new migrated dirs, eg. cas-0.10.1, etc
> Then rename the archived dirs to the 'current' dir names: arch-cas-0.9.3 -> cas, etc.
>
> 3- install the old krill version
>
> I think ubuntu 20.04 is Focal Fossa, so:
> apt install krill=0.9.3-1focal
>
> 4- start krill again
>
> It should now continue to work from the data it backed up during the upgrade.
>
>
> And then, if we could email in private I would very much like to have a look at a copy of your data directory, excluding the ssl and keys directories which contain your private keys. If I have access to that data then I should be able to work out what went wrong.
>
> Kind regards,
>
> Tim
>
>
>
>
>
>
>
>
>
>
>> On 9 Sep 2022, at 18:09, Christopher Munz-Michielin via RPKI <rpki at lists.nlnetlabs.nl> wrote:
>>
>> Hey all,
>>
>> Hoping someone can provide a bit of assistance here.  I upgraded from Krill 0.9.3 to 0.10.1 (using the install via apt on Ubuntu 20.04) and since the upgrade I am unable to publish data.  I am using the embedded publisher.
>>
>> In the log files I am seeing
>>
>> 2022-09-09 09:03:53 [WARN] HTTP 400: Publication Server not initialized, see 'krillc pubserver server init --help'
>> 2022-09-09 09:03:53 [ERROR] Failed to publish for 'WestConnect-CA'. Will reschedule to: '2022-09-09T16:08:53+00:00'. Error: HTTP client error: Error response from URI: https://localhost:3000/rfc8181/WestConnect-Pub/, Status: 400 Bad Request, ErrorResponse: {"label":"pub-repo-not-initialized","msg":"Publication Server not initialized, see 'krillc pubserver server init --help'","args":{}}
>>
>> and when I attempt to initialize the publication server with krillc pubserver server init --rrdp https://rpki.tools.westconnect.ca/rrdp/ --rsync rsync://rpki.tools.westconnect.ca/repo/ --token<token> I receive an error saying it's already been initialized.
>>
>> Wandering what recourse I have here to recover?
>>
>> Thanks!
>>
>> -- 
>> RPKI mailing list
>> RPKI at lists.nlnetlabs.nl
>> https://lists.nlnetlabs.nl/mailman/listinfo/rpki