We prepared a clone of our current production rig (5000 domains - 20k accounts - ~12TB of data) in order to attempt an upgrade to the BETA.
Before bringing the clone online we changed IP addresses config, hostname, etc. and also disabled the POP/IMAP fetch services (we wouldn't like our testing clone to collect external user data from their external accounts).
Everything was running good with the current stable version on the clone.
We ran the beta installation and after the install was finished the service is (re)started.
For about 20-25 minutes I spied the smartermail.exe process disk activity (through resmon) and it seemd to read/write a lot of json files (domains/users settings), I suppose these files need to be updated.
But we have no view on what is going on (I tried to find some logs about an update process but the only log I found was the 2022.12.15-StartAndStop.log which contains not that much infos:
[16:32:30.316]  MailService process id(s): 7596
[16:32:30.316]  OnStart: Called
[16:32:30.316]  OnStart: Failover not enabled.
[16:32:30.316]  OnStart: Starting ServiceLifetimeFunction thread...
[16:32:30.316]  OnStart: ServiceLifetimeFunction thread started successfully.
[16:32:30.316]  OnStart: Completed
[16:32:30.316]  ServiceLifetimeFunction: Called
[16:32:30.316]  ServiceLifetimeStart: Called
[16:32:30.378]  ServiceLifetimeStart: Completed
[16:32:30.378]  ServiceLifetimeFunction: Entering service wait loop
After these 25 minutes of disk activity, the SmarterMail.exe process crashes.
I started again the service and the result was the same (but a bit faster, thanks to disk cache I guess...)
Any idea what could be wrong ?
PS: Os is Windows 2019 with latest updates