Upgrade the 9 patch 34

[181874]

What solved was to remove the whole docserver XML block from the jetty config xmls (jetty/etc/jetty.xml & jetty/etc/jetty.xml.in).

Another interesting fact: imapd "won't" start with error message

Code: Select all

[Fatal Error] :1:1: Content is not allowed in prolog.
ERROR StatusLogger Error parsing null
 org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 1; Content is not allowed in prolog.
        at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
        at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
        at org.apache.logging.log4j.core.config.xml.XmlConfiguration.<init>(XmlConfiguration.java:92)
        at org.apache.logging.log4j.core.config.xml.XmlConfigurationFactory.getConfiguration(XmlConfigurationFactory.java:46)
        at org.apache.logging.log4j.core.config.ConfigurationFactory$Factory.getConfiguration(ConfigurationFactory.java:578)
        at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:179)
        at org.apache.logging.log4j.core.config.Configurator.initialize(Configurator.java:86)
        at org.apache.logging.log4j.core.config.Configurator.initialize(Configurator.java:67)
        at com.zimbra.cs.imap.ImapDaemon.main(ImapDaemon.java:100)
ERROR StatusLogger No logging configuration
12:12:02.912 [main] ERROR zimbra.store - Failed to initialize VolumeManager
com.zimbra.common.service.ServiceException: system failure: Database connection pool not initialized.
        at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:293) ~[zimbracommon.jar:9.0.0_GA_3954]
        at com.zimbra.cs.db.DbPool.getConnection(DbPool.java:327) ~[zimbrastore.jar:9.0.0_GA_3954]
        at com.zimbra.cs.db.DbPool.getConnection(DbPool.java:322) ~[zimbrastore.jar:9.0.0_GA_3954]
        at com.zimbra.cs.volume.VolumeManager.load(VolumeManager.java:61) ~[zimbrastore.jar:9.0.0_GA_3954]
        at com.zimbra.cs.volume.VolumeManager.<init>(VolumeManager.java:50) [zimbrastore.jar:9.0.0_GA_3954]
        at com.zimbra.cs.volume.VolumeManager.<clinit>(VolumeManager.java:41) [zimbrastore.jar:9.0.0_GA_3954]
        at com.zimbra.cs.store.StoreManager.getInstance(StoreManager.java:79) [zimbrastore.jar:9.0.0_GA_3954]
        at com.zimbra.cs.imap.ImapDaemon.main(ImapDaemon.java:106) [zimbrastore.jar:9.0.0_GA_3954]
12:12:02.930 [main] FATAL zimbra.system - unable to initialize blob store
java.lang.NullPointerException: Cannot invoke "com.zimbra.cs.volume.Volume.getId()" because the return value of "com.zimbra.cs.volume.VolumeManager.getCurrentMessageVolume()" is null
        at com.zimbra.cs.store.StoreManager.getInstance(StoreManager.java:79) [zimbrastore.jar:9.0.0_GA_3954]
        at com.zimbra.cs.imap.ImapDaemon.main(ImapDaemon.java:106) [zimbrastore.jar:9.0.0_GA_3954]

BUT in the background imapd is working and I am able to connect with clients to it.

[L. Mark Stone]

FWIW imapd is long since deprecated and indeed never exited beta status.

It does work in my experience with Network Edition customers who installed it when it was being actively developed and have done in-place upgrades since.

But I’m not sure that it’s correct to expect imapd to work 100% correctly on any new installs these days, NE or OSE.

[181874]

So IMAP is no longer needed?
Is this being handled somehow else?

[181874]

Hi Mark,

I can confirm that uninstalling the imapd service did not break my Zimbra OSE - so it's fine and the annoying error is gone.

The only thing that Zimbra developers should mention somewhere is the Onlyoffice dependency as this is not part of to FOSS repositories.
If you build your own Zimbra version of it, it is in general not ready to use and you need to remove some lines from jetty.xml

[yogesh.dasi]

Onlyoffice repository has been updated to new location and the instructions for the same can be seen here https://wiki.zimbra.com/index.php/Zimbr ... ses/10.0.2

[181874]

Is this also valid for Zimbra 9?

[yogesh.dasi]

No, Onlyoffice is only for Zimbra 10.

[181874]

But why is Onlyoffice then part of the building process for Zimbra 9?

[umashankar.avagadda]

But why is Onlyoffice then part of the building process for Zimbra 9?

can you please share the steps that you are following for building the Zimbra 9?

[181874]

I have cloned this Git repository https://github.com/ianw1974/zimbra-build-scripts
Then I have followed the instructions and installed all necessary packages for the build process.
After that I copied the build config file config.build.9 to config.build so it should compile Zimbra 9.

After compiling it I installed it and upgraded my existing Zimbra version.
Not sure if this helps but it mentions that it upgrades the database to version 118.