I//O-hannes

The `nats server report jetstream` command needs a system account so I also have that in place. ;)

I guess it doesn't have anything to do with the cli client version, since the problem is showing during either nats-server shutdown or startup.

Here's some -DVV logs from nats-server. One where nats-server exits with "panic: corrupt state file" and one where it exits with "panic: JetStream Cluster Unknown group entry op type!" [unknown-group-entry-op-type.log](https://github.com/nats-io/nats-server/files/10443065/unknown-group-entry-op-type.log)...

Retrying to start the server on the same cluster multiple times it finally succeeded. Here's the -DVV log from the successful startup including a normal shutdown. [succesful-startup.log](https://github.com/nats-io/nats-server/files/10443176/succesful-startup.log)

Note all of these logs were generated without changing anything in the cluster or locally. Sometimes nats-server fails to startup with various error messages, sometimes it succeeds.

I'll try to repro this on my local machine, so it will be easier to debug. I'm suspecting it has something to do with multi tenancy as it is not...

Yes, it doesn't work. Only thing that works is retrying starting the nats-server process. Sometimes it works. Another thing I noticed is when running `nats server report jetstream` after I...

@derekcollison thanks for your help! Just to lighten the mood a bit, I think it's really great that you take the time to try and understand what is most likely...

Yeah, ended up doing the same.