Hello, 

Thank you for reporting this issue. I'm going to open a ticket for the High memory usage but I want to ask you a couple of questions before opening one for the system clock issue. 

Looking forward to hearing from you. 

Thanks, 

Zach,

We are PDT (UTC -8 Pacific Time)

SmarterMail Self-Diagnostic shows the following:

After a resync of the w32tm service we show the following on the DC and the SmarterMail AD member:

Domain Controller:
w32tm /query /status
Leap Indicator: 0(no warning)
Stratum: 3 (secondary reference - syncd by (S)NTP)
Precision: -6 (15.625ms per tick)
Root Delay: 0.0621185s
Root Dispersion: 7.7767087s
ReferenceId: 0x9BF8C41C (source IP:  155.248.196.28)
Last Successful Sync Time: 4/12/2023 10:44:46 AM
Source: 2.us.pool.ntp.org
Poll Interval: 6 (64s)

SmarterMail Server:
w32tm /query /status
Leap Indicator: 0(no warning)
Stratum: 4 (secondary reference - syncd by (S)NTP)
Precision: -23 (119.209ns per tick)
Root Delay: 0.0636210s
Root Dispersion: 7.8205975s
ReferenceId: 0xC0A80103 (source IP:  192.168.1.3)
Last Successful Sync Time: 4/12/2023 10:55:33 AM
Source: dc.scarabmedia.com
Poll Interval: 6 (64s)

We were able to resolve the problem by enabling High Accuracy on the DC & all AD members running SmarterMail, although in the case of one of our Incoming Gateways we had to migrate the Windows 2016 Server from a VMWare Host to a Hyper-V Host that had High Accuracy enabled in the Windows registry.

The site https://time.is shows the following (but this is after enabling High Accuracy and moving from VMWare Host to Hyper-V with High Accuracy enabled):

Domain Controller
Your time is exact! The difference from Time.is was -0.002 seconds (±0.040 seconds)

SmarterMail Server
Your time is exact! The difference from Time.is was +0.014 seconds (±0.026 seconds)

Zach,

We just noticed that the Incoming Gateway we migrated from VMWare to Hyper-V to resolve the Time issue has SmarterMail showing a max of 1.2GB Memory usage (it routinely recycles upon trash collection and drops down to @ 700MB and works it way back up to @ 1.2, rinse and repeat). Since this looks good we restarted the other Incoming Gateways. Although ClamAV - clamd is using a larger amount of RAM on one of them (@2GB) the SmarterMail service itself is showing consistently at @ 1.2GB across all three Incoming Gateways after a system reboot. So, it may have been a sub-process running post-installation/conversion that was causing a memory leak.

After decades with SmarterMail I should know by now that if there is a problem post-upgrade I should reboot the SmarterMail server first and foremost to troubleshoot.

Hello,

Thanks for the updates. 

So, the memory issue was resolved by restarting the system. The time issue has been fixed by enabling high accuracy. I'm happy to hear that worked for you!

I suggest that you keep an eye on ClamAV and check if it continues to use a lot of memory. In some cases, ClamAV has been known to consume up to 2.5GB of memory, but it should go down after some time.

Next week, I'll follow up with you on the ticket to check if everything is going well and if you're experiencing any more problems. If everything is working fine, we can close the ticket.

Thank you,

Ours doubled from 4GB to 8GB and slowly rising.... nothing critical though.

I'm using SM build 8454 (but I've noticed this earlier) as only Incoming Gateways and all of them (3) use: 11GB, 10GB and 20GB or RAM.

Spool levels are at level about 1400, 1400 and 400 messages in Waiting to deliver sections so this are not a big numbers I think. I use incoming gateways only for SPAM filtering (rspamd and other built in functions) and I don't use ClamAV on them. Also I can't update to later builds since SPAM headers being added by latest build are encoded which is being decoded on destination server but I don't want to update main server yet.

RAM usage which I provided at the beggining is from task manager and here you have stats from SM dashboards of Incoming Gateways

EDIT: I don't use AD and systems are virtualised on VMWare and higher memory usage I've noticed when I started using preview versions of latest SM release since I wanted to integrated rspamd solution for spam checking.

EDIT2: Memory usage is something which returns after some time of service uptime. It returns after system restart or service restart after some period of time so this is not something which occured one time.

Just had to restart server because RAM was maxxed at 99%. I upgraded weeks ago so I know nothing is being parsed still because of an upgrade. I've never had memory issues with SmarterMail until recently. I'm currently on v8524 because there's too many problems with the latest version.

I also am getting an occasional warning about time not being synced.

Hi Seph. Can you check if the clock is synchronizing with the host via vmtools??
If it does, turn it off.

My server is not a VM. It's a single, dedicated, hardware host. My RAM is already at 89% and I restarted service this morning.

Using SM custom build 8536 for several days adn it seems that work better.
Today I have upgraded to official 8538 and I had no RAM nor CPU spikes till now