This is an experimental solution to providing near-live synchronisation between two Zimbra servers so that one of them is live and the other is kept in a warm or very warm standby state.
The system is symmetrical. The sync can work in reverse when the mirror server becomes the active server. This allows easy fall-back to the original server once the failover condition is resolved.
I am using a single server installation and was using the RHEL7_64 FOSS edition, Patch 8.8.9_P7 and Live sysnc script was working fine all this days.
Yesterday I upgraded my email server with RHEL7_64 FOSS edition, Patch 8.8.11_P2 and now while doing live sync, we are getting the below error in the live sync log:
Sun Feb 10 03:47:04 PST 2019 :Syncing /opt/zimbra/redolog/redo.log
Sun Feb 10 03:47:04 PST 2019 :Syncing /opt/zimbra/redolog/redo.log done
Sun Feb 10 03:47:04 PST 2019 :Syncing redologs done
Sun Feb 10 03:47:04 PST 2019 :Purging redolog directory and archives
Sun Feb 10 03:47:04 PST 2019 :Purge redolog directory and archives done
Sun Feb 10 03:47:06 PST 2019 :Replaying redologs...
Exception in thread "main" java.lang.NoClassDefFoundError: graphql/GraphQLError
at com.zimbra.graphql.resources.GQLExtension.init(GQLExtension.java:49)
at com.zimbra.cs.extension.ExtensionUtil.initAllMatching(ExtensionUtil.java:128)
at com.zimbra.cs.extension.ExtensionUtil.initAll(ExtensionUtil.java:154)
at com.zimbra.cs.util.Zimbra.startup(Zimbra.java:267)
at com.zimbra.cs.util.Zimbra.startupCLI(Zimbra.java:185)
at com.zimbra.cs.redolog.util.PlaybackUtil.setup(PlaybackUtil.java:394)
at com.zimbra.cs.redolog.util.PlaybackUtil.main(PlaybackUtil.java:369)
Caused by: java.lang.ClassNotFoundException: graphql.GraphQLError
at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
... 7 more
Sun Feb 10 03:47:10 PST 2019 :Replay of redolog failed
Sun Feb 10 03:47:10 PST 2019 :Replaying redologs done
Sun Feb 10 03:47:10 PST 2019 :Re-starting Zimbra mailbox service
Sun Feb 10 03:47:37 PST 2019 :Purging remote redolog directory
Sun Feb 10 03:47:37 PST 2019 :Purging remote redolog directory done
Sun Feb 10 03:47:37 PST 2019 :Live streaming redolog
Sun Feb 10 03:47:42 PST 2019 :Live streaming redolog established
anyone has any clue about this error and any resolution for this.
alogicking wrote:Yesterday I upgraded my email server with RHEL7_64 FOSS edition, Patch 8.8.11_P2 and now while doing live sync, we are getting the below error in the live sync log:
Something similar has been reported on gitlab. It appears to be the output of zmplayredo command, but I cannot say what's causing it. You should search more about that command
alogicking wrote:Yesterday I upgraded my email server with RHEL7_64 FOSS edition, Patch 8.8.11_P2 and now while doing live sync, we are getting the below error in the live sync log:
Something similar has been reported on gitlab. It appears to be the output of zmplayredo command, but I cannot say what's causing it. You should search more about that command
Thanks Maxxer, for your prompt response. I was going through the code of zmplayredo command could find that there were some jar file reference missing like: graphql-java-9.0.jar and others.
Zimbra support has given us a fix to avoid the exception (java.lang.NoClassDefFoundError: graphql/GraphQLError) - you need simply to remove the contents of a folder :
It fixes the zmplayredo problem. According to Zimbra, GraphQL library is an experimental feature they have added in some tools but it is not yet production-ready.
again after upgrading to Release 8.8.12_GA_3794.RHEL7_64_20190329045002 RHEL7_64 FOSS edition, Patch 8.8.12_P1 proxy. edition, I am getting the below error while using live_sync
which: no zmhsm in (/opt/zimbra/bin:/opt/zimbra/common/lib/jvm/java/bin:/opt/zimbra/common/bin:/opt/zimbra/common/sbin:/usr/sbin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin)
Mon Jun 24 08:28:34 PDT 2019 :Syncing /opt/zimbra/redolog/redo.log
Mon Jun 24 08:28:34 PDT 2019 :Syncing /opt/zimbra/redolog/redo.log done
Mon Jun 24 08:28:34 PDT 2019 :Syncing redologs done
Mon Jun 24 08:28:34 PDT 2019 :Purging redolog directory and archives
Mon Jun 24 08:28:34 PDT 2019 :Purge redolog directory and archives done
Mon Jun 24 08:28:37 PDT 2019 :Replaying redologs...
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.openzal.zal.extension.StoreManagerImpl (file:/opt/zimbra/lib/ext/zimbradrive/zal.jar) to field java.lang.reflect.Method.modifiers
WARNING: Please consider reporting this to the maintainers of org.openzal.zal.extension.StoreManagerImpl
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/opt/zimbra/lib/jars/slf4j-log4j12-1.6.4.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/opt/zimbra/jetty_base/webapps/service/WEB-INF/lib/slf4j-log4j12-1.6.4.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
Mon Jun 24 08:28:44 PDT 2019 :Replay of redolog failed
Mon Jun 24 08:28:44 PDT 2019 :Replaying redologs done
Mon Jun 24 08:28:44 PDT 2019 :Re-starting Zimbra mailbox service
Mon Jun 24 08:29:11 PDT 2019 :Purging remote redolog directory
Mon Jun 24 08:29:11 PDT 2019 :Purging remote redolog directory done
Mon Jun 24 08:29:11 PDT 2019 :Live streaming redolog
Mon Jun 24 08:29:16 PDT 2019 :Live streaming redolog established
Setting up watches. Beware: since -r was given, this may take a while!
Watches established.