Missing jcryption_keypair file, error during upgrade to 1.9.4-3+jammy

[bayardo.rivas]

I got this error again after upgrading from version 1.9.4-1 to 1.9.4-3. The messages is:

.....reduced the number of log lines to read only the important lines

1 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.
Need to get 13.1 MB of archives.
After this operation, 139 kB of additional disk space will be used.
Do you want to continue? [Y/n] Y
Get:1 http://rpms.litespeedtech.com/debian jammy/main amd64 openlitespeed amd64 1.9.4-3+jammy [13.1 MB]
Fetched 13.1 MB in 0s (74.4 MB/s)
(Reading database ... 103283 files and directories currently installed.)
Preparing to unpack .../openlitespeed_1.9.4-3+jammy_amd64.deb ...
Unpacking openlitespeed (1.9.4-3+jammy) over (1.9.4-1+jammy) ...
Setting up openlitespeed (1.9.4-3+jammy) ...
dpkg: error processing package openlitespeed (--configure):
installed openlitespeed package post-installation script subprocess was killed by signal (Killed)
Errors were encountered while processing:
openlitespeed
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)

If I check installation, the package is installed but it is not configured:

dpkg -l | grep openlitespeed
iF openlitespeed 1.9.4-3+jammy amd64 High Performance, lightweight, open source HTTP server

Logs:

sudo grep -i openlitespeed /var/log/dpkg.log | tail -n 30
2026-11-05 15:09:18 upgrade openlitespeed:amd64 1.9.4-1+jammy 1.9.4-3+jammy
2026-11-05 15:09:18 status half-configured openlitespeed:amd64 1.9.4-1+jammy
2026-11-05 15:09:20 status unpacked openlitespeed:amd64 1.9.4-1+jammy
2026-11-05 15:09:20 status half-installed openlitespeed:amd64 1.9.4-1+jammy
2026-11-05 15:09:22 status unpacked openlitespeed:amd64 1.9.4-3+jammy
2026-11-05 15:09:22 configure openlitespeed:amd64 1.9.4-3+jammy <none>
2026-11-05 15:09:22 status unpacked openlitespeed:amd64 1.9.4-3+jammy
2026-11-05 15:09:22 status half-configured openlitespeed:amd64 1.9.4-3+jammy

When I try to configure the package:

sudo dpkg --configure openlitespeed
Setting up openlitespeed (1.9.4-3+jammy) ...
/usr/bin/md5sum: /usr/local/lsws/admin/conf/jcryption_keypair: No such file or directory

Checked with ChatGPT and looks like this is something inherited that is not used in new versions. I created an empty file and it complete the --configuration of the package, but it doesn't make sense to me.

sudo touch /usr/local/lsws/admin/conf/jcryption_keypair
sudo chown lsadm:lsadm /usr/local/lsws/admin/conf/jcryption_keypair
sudo chmod 600 /usr/local/lsws/admin/conf/jcryption_keypair

sudo dpkg --configure openlitespeed
dpkg: error processing package openlitespeed (--configure):
package openlitespeed is already installed and configured
Errors were encountered while processing:
openlitespeed

And then looks like installed and configured:

dpkg -l | grep openlitespeed
ii openlitespeed 1.9.4-3+jammy amd64 High Performance, lightweight, open source HTTP server

Thanks for any comment.

 

[Cold-Egg]

I think I found the possible reason is that you have jcryption_keypair.dpkg, but jcryption_keypair and cuasing the issue.
Could you share the output with the following command?

ls -la /usr/local/lsws/admin/conf/jcryption_keypair*
dpkg-divert --list | grep jcryption

We'll enhance the package logic to prevent similar issues in the future.

 

[bayardo.rivas]

Hey, @Cold-Egg thanks for reply.

ls -la /usr/local/lsws/admin/conf/jcryption_keypair*
-rw------- 1 lsadm lsadm 0 Nov 5 15:17 /usr/local/lsws/admin/conf/jcryption_keypair
-rw-r--r-- 1 lsadm lsadm 529 Sep 23 2025 /usr/local/lsws/admin/conf/jcryption_keypair.dpkg
-rw-r--r-- 1 lsadm lsadm 529 Aug 21 2025 /usr/local/lsws/admin/conf/jcryption_keypair.dpkg.dpkg-tmp

dpkg-divert --list | grep jcryption --> No results.

@Cold-Egg , what is the use of this file? I found that it was supposed to help with encription in WedAdmin console but it's not used anymore. Could you say something about it?

 

[Cold-Egg]

The issue is caused by the presence of jcryption_keypair.dpkg without the corresponding jcryption_keypair file.
Since Jcryption is not being used, you have two options to resolve this:

1. Remove the existing files:
   rm -f /usr/local/lsws/admin/conf/jcryption_keypair*
2. Alternatively, manually create the missing jcryption_keypair file to allow the upgrade to proceed.

In the next release, we'll improve the package installation logic to check for both files and handle this situation properly.

That's correct, the file will be generated automatically when downgrading to v1.8.x or upgrading from v1.8.x.