Notifications
Clear all
Topic starter
05/10/2021 13:19
Dear all,
We are using multi servers (2 ldaps, 1 mta/proxy, 2 mailstores, 1 archive server) with zimbra 9 on centos 7. Recently HSM seems to not run on archive server and /opt is almost full.
We set policy to 1 days (or 8 hours) and apply the HSM Policy with the following result:
[zimbra@archive ~]$ zxsuite hsm monitor cc90ed70-8d1f-43d4-a411-83ea8e27c151 Operation not found Unable to monitor operation cc90ed70-8d1f-43d4-a411-83ea8e27c151
We tried to restart zimbra on archive server, run hsm from the command line but the same result:
[zimbra@archive ~]$ zxsuite hsm doMoveBlobs start operationId 50c766ed-962d-4585-a2f1-920296d7f8a6 server archive.paiho.vn monitorCommand zxsuite hsm monitor 50c766ed-962d-4585-a2f1-920296d7f8a6 [zimbra@archive ~]$ zxsuite hsm monitor 50c766ed-962d-4585-a2f1-920296d7f8a6 Operation not found Unable to monitor operation 50c766ed-962d-4585-a2f1-920296d7f8a6
Here are some output from our system:
[zimbra@archive ~]$ zmprov gs `zmhostname` |grep NG zimbraNetworkAdminNGEnabled: TRUE zimbraNetworkMobileNGEnabled: FALSE zimbraNetworkModulesNGEnabled: TRUE [zimbra@archive ~]$ zxsuite hsm getproperty Warning: this command is deprecated use instead: zxsuite config server {set|get|empty} {serverName} [attr1 value1 [attr2 value2...]] ZxPowerstore_ModuleEnabledAtStartup true (true) ZxPowerstore_MoveSchedulingEnabled true (false) ZxPowerstore_MoveStartTime 2 (2) ZxPowerstore_SpaceThreshold 1024 (1024) ZxPowerstore_EnableHsmOnNe false (false) [zimbra@archive ~]$ zxsuite hsm getServices services module could_start false could_stop true running true powerstore-log could_start false could_stop true running true store-manager-service could_start false could_stop true running true schedule-move-operation could_start false could_stop true running true powerstore-attribute-listeners could_start false could_stop true running true [zimbra@archive ~]$ zxsuite hsm getHsmPolicy policies message,document:before:-1days [zimbra@archive ~]$ zxsuite hsm getAllVolumes primaries id 1 name message1 path /opt/zimbra/store compressed true threshold 4096 storeType LOCAL isDrivePrimary true isCurrent true volumeType primary secondaries id 3 name hsm1 path /hsm1 compressed true threshold 4096 storeType LOCAL isCurrent true volumeType secondary indexes id 2 name index1 path /opt/zimbra/index compressed false threshold 4096 storeType LOCAL isCurrent true volumeType index [zimbra@archive ~]$ zxsuite core getVersion CLI versions: network_modules_version 3.1.8 network_modules_commit 2806c76553d156cb8e2f1037f61b209f4c1a7314 zal_version 2.21.0 zal_commit 7d8a9064e748469d0cf300c2c673fa55ece599bf Server versions: version 3.1.8 commit 2806c76553d156cb8e2f1037f61b209f4c1a7314 system_type network_modules product Network Modules NG zimbraNetworkModulesNGEnabled TRUE network true zal_version 2.21.0 zal_commit 7d8a9064e748469d0cf300c2c673fa55ece599bf
Hope someone can help (we opened a case with zimbra support but the response is quite slowly and our /opt is nearly full now).
Best regards,
Minh.