EWS hangs while gromox-http stays active

souverain · 2026-05-22T08:31:39+00:00

Hello, We encountered a temporary issue with EWS access on a grommunio/gromox server. The webmail was working, but Apple Mail on macOS could no longer conn...

FvA

Any update on this? I wrote a short script to restart gromox-http when a curl to 'http://127.0.0.1:10080/EWS/Exchange.asmx' doesn't give a 405 in return. Not ideal, but it keeps Outlook alive for now.

Update, as per souverain's post, upgraded to:
grommunio-admin-api 1.19.11.mc7e4cbd lp156.5.1
grommunio-admin-common 50.10f1afb lp156.51.1
grommunio-admin-web 5.0.0.32.a076725 lp156.172.1
grommunio-antispam 4.0.1 lp156.5.1
grommunio-common 29.9 lp156.19.1
grommunio-cui 1.1.3.b0091e0 lp156.7.1
grommunio-dav 1.6.24.84942ef lp156.1.1
grommunio-dbconf 1.1.2.4bbae9a lp156.15.1
grommunio-error-pages 1.0.10.bb2df37 lp156.26.1
grommunio-imapsync 2.314 lp156.1.1
grommunio-index 1.5.0.gb0a01b9 lp156.2.1
grommunio-release 2025.1.2 lp156.8.1
grommunio-setup 1.1.16.46f2af3 lp156.73.1
grommunio-sync 2.4.8.483c521 lp156.23.1
grommunio-web 3.18.7.gec5085ffd lp156.481.3
gromox 3.7.256.me40a504 lp156.48.1
gromox-debuginfo 3.7.256.me40a504 lp156.48.1
gromox-debugsource 3.7.256.me40a504 lp156.48.1

Will see if the issue is resolved now.

mark1

FvA
I am interested in the workaround script. Would you be willing to share the script with us?

FvA

Sure, fairly straightforward test and restart.

I run this every 2 minutes in a cron job:
grommunio:~ # cat /etc/cron.d/gromox-http-watchdog
*/2 * * * * root /usr/local/sbin/gromox-http-watchdog.sh >/dev/null 2>&1

The script:

#!/bin/bash
set -euo pipefail

URL='http://127.0.0.1:10080/EWS/Exchange.asmx'
LOCK='/run/gromox-http-watch.lock'
LOGFILE='/var/log/gromox-http-watchdog.log'

mkdir -p /var/log
touch "$LOGFILE"
chmod 0644 "$LOGFILE"

exec >>"$LOGFILE" 2>&1

log() {
  printf '[%s] %s\n' "$(date -Is)" "$*"
}

probe() {
  curl -sS -o /dev/null -w "HTTP=%{http_code} TIME=%{time_total}\n" --max-time 10 "$URL" 2>/dev/null || true
}

exec 9>"$LOCK"
flock -n 9 || exit 0

result="$(probe)"

if [[ "$result" == HTTP=405* ]]; then
  exit 0
fi

log "probe failed: $result; restarting gromox-http"
systemctl restart gromox-http.service

for _ in $(seq 1 30); do
  sleep 5
  result="$(probe)"
  if [[ "$result" == HTTP=405* ]]; then
    log "service recovered: $result"
    exit 0
  fi
done

log "service did not recover after restart"
exit 1

mark1

Thank you very much for the quick reply.
I will test it on my server.

souverain

mark1 please can you give us your feedback after ?

mark1

souverain
After the upgrade to OS 16.0:
gromox 3.7.256.me40a504-lp160.48.1 (all current versions)
grommunio-web 3.18.7.gec5085ffd-lp160.481.3
mapi-header-php 2.1.22.762be6f-lp160.10.1,
no further errors have occurred so far.
After one day of operation, the gromox-http-watchdog.log is still empty.

mark1

Yes, gladly.
The script is already running. I'll report back as soon as there's anything in the log.

FvA

The issue hasn’t been resolved yet; I’m seeing a fair few log entries from my script.
Also, and this is relatively new, thousands upon thousands of log entries like these:
exmdb-audit: truncated message /var/lib/gromox/user/<domain>/<user>

ozy

@FvA See https://community.grommunio.com/d/2594-speed-up-grommunio-and-g-web/2 to resolve the truncated message flood.

FvA

ozy Appreciate that, that calmed down the logs indeed. Now back to keeping an eye on gromox-http!

souverain

mark1

Thank you for your feedback.

Here is my current configuration as of today:

gromox 3.7.256.me40a504-lp156.48.1
mapi-header-php 2.1.22.762be6f-lp156.10.1
grommunio-admin-api 1.19.14.mc1556b8-lp156.6.1
grommunio-admin-web 5.0.0.32.bd860f9-lp156.171.1
grommunio-antispam 4.0.1-lp156.5.1
grommunio-common 29.11-lp156.20.1
grommunio-cui 1.1.50.23b8a9d-lp156.9.1
grommunio-dav 1.6.24.84942ef-lp156.3.1
grommunio-sync 2.4.10.5ab819e-lp156.26.1
grommunio-web 3.18.7.gec5085ffd-lp156.482.1
postfix 3.8.4-150600.3.3.1

I keep applying the latest updates, but so far I still do not see the issue being resolved.

I will give it a few more weeks, but if I do not see the problem being seriously acknowledged and addressed, I will probably have to move away from this solution and look for another one.

My goal is quite simple: if it works reliably for me, then I can confidently recommend it to others. I want to be able to share a good experience with my users, but at this stage I still cannot honestly say that this deployment is a success.

Duese6

Is anyone else still seeing OOM issues
(similar to https://community.grommunio.com/d/2713-out-of-memory-error-after-installing-todays-updates/6 and https://community.grommunio.com/d/2721-huge-ews-traffic-with-apple-mail-after-recent-updates/16), even on 3.7.256?

WalterH

I see OOM killer issues also with 3.7.328.

ozy

I tend to get OOM since I updated to 3.7.256, with memory spikes I can't explain. Usually kills nginx.
Perhaps I shouldn't have increase nginx workers from 1 to 10 ?
That increase would also mean that my server should handle 10x1024 requests instead of 1024 (shouldn't happen anyway, I only host very small servers).
@WalterH Isn't v3.7.256 the latest currently ?

WalterH

https://community.grommunio.com/d/2713-out-of-memory-error-after-installing-todays-updates/8

mwilliams

We have just released a development build at https://download.grommunio.com/devel -> could you please check and validate if that works for you now?

Please only update gromox -> only that package is up-to-date

To be sure: restart nginx as well to free the memory of nginx once as well.

The version you should look out for is gromox-3.7.343.x7f4ba66

mwilliams

Also, especially for nginx: please check your worker configuration under /etc/nginx/nginx.conf to:

worker_processes auto;

to make sure the nginx is using the maximum threads possible but also recycle appropriately (freeing up memory over-candid memory usage).

also noteworthy: the common nginx configuration package has been updated as well (surfacing in the next 15 mins) from both community and supported -> please update.

Both actions aggregated have sustained a 10k user blast very well. But still: It is a development build for which all testing has not been completed, so please share your experiences with us.

Duese6

@mwilliams
I commented on the other thread
https://community.grommunio.com/d/2713-out-of-memory-error-after-installing-todays-updates/16

mwilliams

souverain

gromox 3.7.256.me40a504 you are running doesn't have any of the mentioned fixes, which is why the development builds were provided for validation. if you want to wait until it shows up in community/supported: sure, but then just simply wait until announced here.

souverain

mwilliams Okay, I’ll wait then, but I won’t hide the fact that I had a good feeling about this solution, and now things are starting to go seriously wrong. It’s a shame because I really believe in this solution. But if it’s not working for me in practice, I’ll have to find an alternative solution.

mwilliams

souverain

I don't know what you expect more than a development build is provided within very few days for verification. expect updates in community/supported very soon.

« Previous Page Next Page »