Back to Community Threads
2
[BETA 7452] Some domains cannot load after update from previous build
Problem reported by Sébastien Riccio - 5/27/2020 at 7:27 PM
Resolved
Hello,

I've updated our test server to the latest beta build tonight and after login in as admin around 10 domains (on 5k) where not able to load.

Error loading domain, displayed in the domain list, instead of the domains infos.

Unfortunately I did not take a screenshot of this and attempted a restart of the server.

After the restart of the server, no more errored domains. It looked good to me but in fact all the previously failed domains are completly _gone_ and not listed anymore.

I remember only one of the domain name, and it can't be found anymore. The domain data files though, are still on the disk.

Is there a way to know what happened and which other domains where affected ? I've searched one of the domain name in the log files but found nothing about it.

Note: this is hopefully a beta test server with only activity on a domain for testing purposes, but still I would like to know why this happened and how to fix it as we were planning to update our production server (not sure anymore ...)

Thank you for your help.
Sébastien Riccio
System & Network Admin

5 Replies

Reply to Thread
0
Sébastien Riccio Replied
5/27/2020 at 7:39 PM
Actually I found something in conversion log by manually "grep'ing" the file. Seems they are not available in the troubleshooter page log files.

03:14:57.431 [domain1.com][Error] Message: Critical error loading domain (domain1.com) after conversion
Exception: Utf8Json.JsonParsingException: expected:'{', actual:' ', at offset:0
   at Utf8Json.JsonReader.ReadIsBeginObjectWithVerify()
   at Utf8Json.Formatters.SmarterMail_Common_Files_DomainFiles_DomainAccountsFileFormatter32.Deserialize(JsonReader& , IJsonFormatterResolver )
   at Utf8Json.JsonSerializer.Deserialize[T](Byte[] bytes, Int32 offset, IJsonFormatterResolver resolver)
   at SmarterMail.Common.Files.FileFunctions.ParseJsonFile[T](Byte[] data)
   at SmarterMail.Common.Files.FileFunctions.ReadJsonFile[T](String path, String cacheBusterKey, Action onLoadFromDisk)
   at SmarterMail.Common.Files.DomainFiles.DomainAccountsFile.Read(BlockIdGenFile genFile, String path, String cacheBusterKey)
   at MailService.Repositories.DomainRepository.ReloadUserRepositories()
   at MailService.Repositories.DomainRepository.LoadRequiredItemsFromRepository()
03:14:58.294 [domain2.com][Error] Message: Critical error loading domain (domain2.com) after conversion
Exception: Utf8Json.JsonParsingException: expected:'{', actual:' ', at offset:0
   at Utf8Json.JsonReader.ReadIsBeginObjectWithVerify()
   at Utf8Json.Formatters.SmarterMail_Common_Files_DomainFiles_DomainAccountsFileFormatter32.Deserialize(JsonReader& , IJsonFormatterResolver )
   at Utf8Json.JsonSerializer.Deserialize[T](Byte[] bytes, Int32 offset, IJsonFormatterResolver resolver)
   at SmarterMail.Common.Files.FileFunctions.ParseJsonFile[T](Byte[] data)
   at SmarterMail.Common.Files.FileFunctions.ReadJsonFile[T](String path, String cacheBusterKey, Action onLoadFromDisk)
   at SmarterMail.Common.Files.DomainFiles.DomainAccountsFile.Read(BlockIdGenFile genFile, String path, String cacheBusterKey)
   at MailService.Repositories.DomainRepository.ReloadUserRepositories()
   at MailService.Repositories.DomainRepository.LoadRequiredItemsFromRepository()
03:15:08.747 [domain3.com][Error] Message: Critical error loading domain (domain3.com) after conversion
Exception: Utf8Json.JsonParsingException: expected:'{', actual:' ', at offset:0
   at Utf8Json.JsonReader.ReadIsBeginObjectWithVerify()
   at Utf8Json.Formatters.SmarterMail_Common_Files_DomainFiles_DomainAccountsFileFormatter32.Deserialize(JsonReader& , IJsonFormatterResolver )
   at Utf8Json.JsonSerializer.Deserialize[T](Byte[] bytes, Int32 offset, IJsonFormatterResolver resolver)
   at SmarterMail.Common.Files.FileFunctions.ParseJsonFile[T](Byte[] data)
   at SmarterMail.Common.Files.FileFunctions.ReadJsonFile[T](String path, String cacheBusterKey, Action onLoadFromDisk)
   at SmarterMail.Common.Files.DomainFiles.DomainAccountsFile.Read(BlockIdGenFile genFile, String path, String cacheBusterKey)
   at MailService.Repositories.DomainRepository.ReloadUserRepositories()
   at MailService.Repositories.DomainRepository.LoadRequiredItemsFromRepository()
03:15:10.919 [domain4.com][Error] Message: Critical error loading domain (domain4.com) after conversion
Exception: Utf8Json.JsonParsingException: expected:'{', actual:' ', at offset:0
   at Utf8Json.JsonReader.ReadIsBeginObjectWithVerify()
   at Utf8Json.Formatters.SmarterMail_Common_Files_DomainFiles_DomainAccountsFileFormatter32.Deserialize(JsonReader& , IJsonFormatterResolver )
   at Utf8Json.JsonSerializer.Deserialize[T](Byte[] bytes, Int32 offset, IJsonFormatterResolver resolver)
   at SmarterMail.Common.Files.FileFunctions.ParseJsonFile[T](Byte[] data)
   at SmarterMail.Common.Files.FileFunctions.ReadJsonFile[T](String path, String cacheBusterKey, Action onLoadFromDisk)
   at SmarterMail.Common.Files.DomainFiles.DomainAccountsFile.Read(BlockIdGenFile genFile, String path, String cacheBusterKey)
   at MailService.Repositories.DomainRepository.ReloadUserRepositories()
   at MailService.Repositories.DomainRepository.LoadRequiredItemsFromRepository()

Real domain names redacted for privacy...
Sébastien Riccio System & Network Admin https://swisscenter.com
0
Derek Curtis Replied
5/28/2020 at 5:36 AM
Employee Post
Hi, Sebastien

I started a ticket for this and your other issue last night and asked for a few files. Please double check and let me know if you got the emails or not. Thanks!
Derek Curtis COO SmarterTools Inc. www.smartertools.com
0
Grady Werner Replied
5/28/2020 at 9:20 AM
Employee Post Marked As Resolution
Update to this for people following.  The five domains had some corrupted files, and the reported issue is not related to last night's build.
Grady Werner SmarterTools Inc. www.smartertools.com
0
Sébastien Riccio Replied
5/28/2020 at 9:52 AM
Yes, it's not related to this particular build. It was on a test server for the beta and the files were probably already corrupted long before the update attempt.

Thank you for looking in to it.
Sébastien Riccio System & Network Admin https://swisscenter.com
0
Tim Uzzanti Replied
5/28/2020 at 9:56 AM
Employee Post
We appreciate the feedback.  I'm glad Grady is continuing to work with you as you move to production.
Tim Uzzanti CEO SmarterTools Inc. www.smartertools.com
Back to Community Threads

Reply to Thread

Related Knowledge Base Articles

SmarterTools Licensing InformationGeneral Topics
Attaching SmarterMail 16.x and Older Domains to New BuildsSmarterMail > Domain/User Configuration and Management
Upgrading SmarterMail (Domain Conversion)SmarterMail > Installation and Configuration
Migrate SmarterMail to a Different ServerSmarterMail > Installation and Configuration
New SmarterMail and WHMCS IntegrationUtilities and Conversion Tools