kargh

Just to be clear, since that but report is quite long: 1. Upgraded from 22.2.7 to 22.3.2 2. Started redpanda -- would not start 3. Downgraded from 22.3.2 to 22.3.1...

It is a 10 node cluster. I didn't have much of a choice as far as downgrading, I wanted to get the node back online. On Wed, Nov 16, 2022,...

@travisdowns Yeah, looking at the timestamps, some of those are from prior to the upgrade. That would have been on v22.2.7. The opcode errors would have been from v22.3.2.

@andrwng That error message happened right after I upgraded the node and tried to start it -- within 5 minutes of running the yum update command. The original issue Alex...

Upgraded to 22.3.3 and here is the full log from when I started the service until it failed: ``` -- Logs begin at Thu 2022-11-17 08:45:50 EST. -- Nov 17...

Also, here are the logs from 22.2.7 from when I issued the `rpk cluster maintenance enable 0 --wait` command and then stopped redpanda. Not sure if there will be anything...

Is it safe to do a yum uninstall then reinstall? I assume the config files and such will remain in place.

Now the entire cluster is unstable (I've not changed anything). This is in dmesg: ``` [Thu Nov 17 14:03:07 2022] reactor-27[63448]: segfault at 18 ip 0000564710ce56da sp 00007f7867df1b80 error 4...

``` Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 64 On-line CPU(s) list: 0-63 Thread(s) per core: 1 Core(s) per socket: 64 Socket(s): 1 NUMA node(s): 1...

@emaxerrno Can you provide me quick and dirty instructions on that? It has been a long time since I played around with that.