gromox 3.0

segro · 2025-10-01T12:40:47+00:00

hallo zusammen, im Community Repo ist seit heute früh gromox 3.0 drin Lange Release liste... https://github.com/grommunio/gromox/releases War schon jeman...

SecureVibe

DVCon how did you update your appliances? Via the web-ui, the cli-ui or with the terminal? Could it be that using the web-ui for the update can cause problems?

DVCon

@SecureVibe
I usually update via web-ui.

WalterH

DVCon I usually update via web-ui.

Ich update immer über die Command Line mit grommunio-update update --noreboot.

WalterH

SecureVibe /var/lib/gromox/user/domain/user/exmdb/exchange.sqlite3

Was sagt ein lsof /var/lib/gromox/user/domain/user/exmdb/exchange.sqlite3 ? Den Pfad natürlich richtig ausfüllen.
Dann versuchen alle Prozesse die das File offen haben zu beenden und dann den http restarten und nochmals testen.
Wenn das nicht hilft, Server rebooten und testen.

SecureVibe

WalterH es sieht so aus, als hätte nur gromox http die Datei offen
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME http 11169 gromox 154ur REG 254,0 2842386432 1469317531 /var/lib/gromox/user/domain/user/exmdb/exchange.sqlite3 http 11169 gromox 189ur REG 254,0 2842386432 1469317531 /var/lib/gromox/user/domain/user/exmdb/exchange.sqlite3 http 11169 gromox 266ur REG 254,0 2842386432 1469317531 /var/lib/gromox/user/sdomain/user/exmdb/exchange.sqlite3 http 11169 gromox 277ur REG 254,0 2842386432 1469317531 /var/lib/gromox/user/domain/user/exmdb/exchange.sqlite3 http 11169 gromox 332ur REG 254,0 2842386432 1469317531 /var/lib/gromox/user/domain/user/exmdb/exchange.sqlite3

WalterH

DVCon OK, so on proxmox, too...

The customer where we encountered this issue is also using Proxmox. However, we have almost all of our virtualizations on Proxmox and have only encountered this problem once, so I don't believe it is a Proxmox-specific issue.

DVCon

WalterH we have almost all of our virtualizations on Proxmox and have only encountered this problem once, so I don't believe it is a Proxmox-specific issue.

That's not how I meant it. If SecureVibe would have used HyperV then it may have been a HyperV issue.

SecureVibe

ckd

so we tried the gromox-export on your test appliance with gromox v3.3 with a backup of our problematic mailbox.
The export file is only half the size of the actual mailbox size (without compression). And the import to another mailbox throws this error: exm: write_message RPC failed

The import works with the -D (delivery) flag. But then the folder structure is lost and only about half the emails are imported, because the export file is incomplete.

Have you experienced these issues as well?

WalterH

did you upgrade to gromox 3.3.12 supported, if not, update now.
Do you have this parameter: /etc/gromox/gromox.cfg:exmdb_force_write_txn=1 if yes, remove this parameter and restart gromox-http.
But most important, update to gromox 3.3.12.

DVCon

I don't see a change with 3.3.12 and a fresh converted vhdx from dynamic to fixed on a NVMe volume.

`[2026-01-27 09:26:30.117432]: sqlite3_step(/var/lib/gromox/user/domain.tld/username/exmdb/exchange.sqlite3) "SELECT folder_id, permission FROM permissions WHERE username='someuser@domain.tld'": file is not a database (26)

[2026-01-27 09:26:30.117747]: sqlite3_step(/var/lib/gromox/user/domain.tld/username/exmdb/exchange.sqlite3) "SELECT folder_id, permission FROM permissions WHERE username='default'": file is not a database (26)

[2026-01-27 09:26:30.118831]: sqlite3_step(/var/lib/gromox/user/domain.tld/username/exmdb/exchange.sqlite3) "SELECT config_value FROM configurations WHERE config_id=1": file is not a database (26)`

localhost:~ # lsof /var/lib/gromox/user/domain.tld/username/exmdb/exchange.sqlite3 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME http 1548 gromox 68ur REG 254,0 618811392 1883242629 /var/lib/gromox/user/domain.tld/username/exmdb/exchange.sqlite3 http 1548 gromox 74ur REG 254,0 618811392 1883242629 /var/lib/gromox/user/domain.tld/username/exmdb/exchange.sqlite3

WalterH

Do you have virus scanners or other software on your system that does not come from grommunio? If so, please disable them.
If you restart the http: systemctl restart gromox-http, does this mailbox then work, even if only for a short time?

DVCon

There is no third party virus scanner on the system. There is also no backup running when it occurs.
After restarting gromox-http the affected mailbox usually works for a few days. But there have also been days, when a restart only helped for a few hours.

WalterH

Did you open a ticket with support?

DVCon

Yes, it's open since 09/09/25.

sinux

Da Proxmox und HyperV betroffen sind, wie sieht es denn mit den VM HDD's aus, also dessen Treiber in der VM, virtio oder vielleicht ältere SCSI oder dergleichen und write back / write through ? Ist nur ein Verdacht das ggf. doch etwas von "außen" Einfluss hat.

DVCon

Die Appliance, bei der es häufiger vorkommt, läuft auf einem NVMe-Spiegelsatz (derzeit exklusiv). Die VROC-Treiber hatte ich kürzlich noch einmal aktualisiert. Cache ist deaktiviert. Die VM hatte ich auch testweise schon mal auf einen SAS-SSD-Spiegelsatz verschoben, ohne dass es etwas am Problem geändert hat.
Die Appliance, bei der es nicht ganz so oft vorkommt, läuft auf einer Einzel-NVMe (Cache deaktiviert). Treiber-mäßig ist da nicht viel machbar.

In sehr ähnlichen Setups läuft das bei anderen Kunden problemlos.

« Previous Page