Booting time may take up to several hours due to starting the Symantec Messaging Gateway DB service.
|Article:TECH181086|||||Created: 2012-02-09|||||Updated: 2012-07-05|||||Article URL http://www.symantec.com/docs/TECH181086|
|NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.|
Boot time may be drastically affected by the number of Policy Groups configured and by the number of Content Filtering Policies assigned to each of the groups.
The boot process doesn't quit unexpectedly but can take an exceedingly long amount of time to start the Symantec Messaging Gateway DB (smg-db) service, temporarily halting the starting of other services.
The length of time will increase with each Policy Group and each Content Filtering Policy that is added. The amount of time increase will vary with less time added for content rules and considerably more time added for policy groups.
- Symantec Messaging Gateway 9.5.3
- Many group policies with many content rules for each.
This problem is related to the size of one of the Messaging Gateway configuration files, which is indirectly related to the number of Policy Groups and Content Filtering Policies.
This issue has been addresssed in the SMG 9.5.4 release.
Article URL http://www.symantec.com/docs/TECH181086