Unable to `chef-server-ctl reconfigure` a new 15.3.2 install on Ubuntu 22.04 about chef-server

[uskf]

I have confirmed same "CorruptIndexException" log with chef-server 15.3.2 on Ubuntu 20.04.
Perhaps this problem is caused by zlib v1.2.12 and resolved by zlib v1.2.13.
madler/zlib#613

Replacing libz.so.1.2.12 to libz.so.1.2.13 resolved this problem.

$ tar zxf zlib-1.2.13.tar.gz
$ cd zlib-1.2.13
$ ./configure
$ make
$ sudo cp libz.so.1.2.13 /opt/opscode/embedded/lib/
$ cd /opt/opscode/embedded/lib/
$ sudo ln -sf libz.so.1.2.13 libz.so
$ sudo ln -sf libz.so.1.2.13 libz.so.1

[uskf]

@dkowis Yes!

AFAIK, this problem occurs on cpu that does not support SSE 4.2.
If the physical cpu supports SSE 4.2, enabling SSE 4.2 on the virtual cpu resolves this problem.

[dkowis]

I have tested this on a KVM based VM on my desktop, which has NVMe Backed storage, and it worked fine.

Perhaps there's some race condition during the setup that is causing the opensearch/elasticsearch to become corrupt after 14.14.x ?

I have confirmed I have no other data corruption problems on my server hardware, and the iSCSI disks.

[dkowis]

Replacing libz.so.1.2.12 to libz.so.1.2.13 resolved this problem.

To get the order of operations correct:

1. Install from package
2. update zlib as you described, installing it into the opscode embedded
3. chef-server-ctl reconfigure so that it installs

Yes?

[dkowis]

Ah yeah that'd do it, these CPUs are slightly too old for that: https://ark.intel.com/content/www/us/en/ark/products/75277/intel-xeon-processor-e52680-v2-25m-cache-2-80-ghz.html

Thanks for finding this! I hope the chef team updates it!

[dkowis]

Ah yeah that'd do it, these CPUs are slightly too old for that: https://ark.intel.com/content/www/us/en/ark/products/75277/intel-xeon-processor-e52680-v2-25m-cache-2-80-ghz.html

Actually, I think this CPU should support SSE4.2 It's supposedly Sandy Bridge era, which, in theory, supports SSE 4.2 HRMMM

[dkowis]

Yeah, I don't see it passed through in proxmox, so I've gotta figure that part out!

[uskf]

probably same problem #3451