Hi Kim Minh,
thanks for your report. The solution from ygrek is what I have in
debian/patches/bdb-dbt-readonly.patch . And this is only partially
helping, as you can see on your server.
I have the same problem and the workaround for now is to detect if the
process goes into 100% CPU and restart it.
But I will have a try with your solution.
Regards
Christoph
Am 05.02.21 um 10:36 schrieb Kim Minh Kaplan:
> Package: sks
> Version: 1.1.6+git20200620.9e9d504-1+b1
> Severity: important
> Tags: upstream
> X-Debbugs-Cc: kaplan+debian....@kim-minh.com
>
> Dear Maintainer,
>
> The sks 1.1.6+git20200620.9e9d504-1 currently packaged in testing has
> important defect that prevents it from synchronizing properly with other
> servers. Here is an log:
>
> Feb 04 18:29:32 ns383488 sks[19622]: 2021-02-04 18:29:32 Disabling gossip
> Feb 04 18:29:37 ns383488 sks[19622]: 2021-02-04 18:29:37 Requesting 20
> missing keys from <ADDR_INET [x.x.x.x]:11371>, starting with
> 00FA33B4F729DFD5C8E7402D0C93CCC8
> Feb 04 18:29:37 ns383488 sks[19622]: 2021-02-04 18:29:37 20 keys received
> [...]
> Feb 04 18:29:37 ns383488 sks[19621]: 2021-02-04 18:29:37 Fatal database
> error: Bdb.DBError("BDB0620 DB_DBT_READONLY should not be set on data DBT.")
> Feb 04 18:29:37 ns383488 sks[19621]: 2021-02-04 18:29:37 Key addition failed:
> Stdlib.Sys.Break
> [...]
> Feb 04 18:29:38 ns383488 sks[19621]: 2021-02-04 18:29:38 Fatal database
> error: Bdb.DBError("BDB0110 Log sequence error: page LSN 42312 2571343;
> previous LSN 42312 1593741")
> Feb 04 18:29:38 ns383488 sks[19621]: 2021-02-04 18:29:38 Key addition failed:
> Stdlib.Sys.Break
> Feb 04 18:29:38 ns383488 sks[19622]: 2021-02-04 18:29:38 Requesting 20
> missing keys from <ADDR_INET [x.x.x.x]:11371>, starting with
> 1E8607A792DA0C5653E34619386F25CF
> Feb 04 18:29:38 ns383488 sks[19622]: 2021-02-04 18:29:38 20 keys received
> Feb 04 18:32:38 ns383488 sks[19622]: 2021-02-04 18:32:38 get_missing_keys
> terminated by timeout
>
> At this point the sks server is deadlocked and can only be terminated.
>
> The issue (https://github.com/SKS-Keyserver/sks-keyserver/issues/82) is
> fixed in upstream.
>
