tommylp

Same problem? Cluster Size: 3 Nats: 2.7.4 Using Nats Security with distributed JWT's Updated to a new Version (2.7.4) from 2.6.6. Before upgrading a nats backup of the streams where...

``` 12:20:23 >>> $JS.API.STREAM.CREATE. {"name":"","subjects":[".\u003e\u003e"],"retention":"limits","max_consumers":-1,"max_msgs":-1,"max_bytes":-1,"max_age":7776000000000000,"max_msg_size":-1,"storage":"file","discard":"old","num_replicas":2,"duplicate_window":300000000000} 12:20:23

Rerun with 1 `>` ``` nats -s --creds stream create --config stream.config --trace 12:25:47 >>> $JS.API.STREAM.CREATE. {"name":"","subjects":[".\u003e"],"retention":"limits","max_consumers":-1,"max_msgs":-1,"max_bytes":-1,"max_age":7776000000000000,"max_msg_size":-1,"storage":"file","discard":"old","num_replicas":2,"duplicate_window":300000000000} 12:25:47

Content of config ``` { "name": "", "subjects": [ ".\u003e" ], "retention": "limits", "max_consumers": -1, "max_msgs": -1, "max_bytes": -1, "max_age": 7776000000000000, "max_msg_size": -1, "storage": "file", "discard": "old", "num_replicas": 2, "duplicate_window":...

server list ``` +-----------------------------------------------------------------------------------------------------------------------------------+ | Server Overview | +-------------+------------+-----------+---------+-----+-------+------+--------+-----+--------+-----+------+----------+-------------+ | Name | Cluster | IP | Version | JS | Conns | Subs | Routes | GWs | Mem |...

server report jsz: ``` +-------------------------------------------------------------------------------------------------------+ | JetStream Summary | +--------------+-----------+---------+-----------+----------+-------+--------+------+---------+---------+ | Server | Cluster | Streams | Consumers | Messages | Bytes | Memory | File | API Req |...

Yes, no problem. ``` nats -s --creds stream create --config stream.config --trace 12:32:41 >>> $JS.API.STREAM.CREATE. {"name":"","subjects":[".\u003e"],"retention":"limits","max_consumers":-1,"max_msgs":-1,"max_bytes":-1,"max_age":7776000000000000,"max_msg_size":-1,"storage":"file","discard":"old","num_replicas":1,"duplicate_window":300000000000} 12:32:41 Acknowledgements: true Retention: File - Limits Replicas: 1 Discard Policy: Old Duplicate Window:...

Unfortunately setting the `num_replicas` to 1 in the backup.json file did not solve the problem. ``` nats: error: restore failed: malformed or corrupt message ```

Do I need to update the value inside the base64 `configuration` also? But that will probably not work, because of a change of the checksum value.

How is the checksum created? ``` { "type": "stream", "time": "2022-03-28T08:27:07Z", "configuration": "", "checksum": "31423daa92ee............" } ```