After upgrading to OES 2018, iManager and GroupWise Webaccess or Monitor will not start

  • 7023130
  • 27-Jun-2018
  • 04-Oct-2019

Environment

GroupWise 2014 R2
GroupWise 18
Open Enterprise Server 2018 (OES 2018) Linux

Situation

Upgraded OES 2015 SP1 server to OES 2018.
iManager login screen will not load (error: unable to connect).
GroupWise Webaccess will not start.
Checking status of apache2 service shows it as dead.

Resolution

  1. Upgrade GroupWise 2014 R2 to GroupWise 2018 Service Pack 2. Please refer to the official documentation.   GroupWise Webaccess 2014 R2 or earlier is not supported on the OES 2018 platform.
  1. Unlink the symbolic link for the following files if they exist:
    • unlink /etc/apache2/conf.d/gwmon.conf
    • unlink /etc/apache2/conf.d/gw.conf
    • unlink /etc/apache2/conf.d/gwcal.conf
3.  Create new symbolic links to conf files that support the new apache version 2.4
  • link -s /opt/novell/grpwise-tomcat/apache/gw-2.4.conf /etc/apache2/conf.d/gw.conf
  • link -s /opt/novell/grpwise-tomcat/apache/gwcal-2.4.conf /etc/apache2/conf.d/gwcal.conf
  • link -s /opt/novell/grpwise-tomcat/apache/gwmon-2.4.conf /etc/apache2/conf.d/gwmon.conf
4.  Run the following commands to start apache2, GroupWise Post Office, and restart tomcat:
  • systemctl start apache2
  • systemctl start grpwise
  • systemctl restart novell-tomcat

OR
  • rcapache2 start
  • rcgrpwise start
  • rcnovell-tomcat restart

Cause

When upgrading from OES 2015 SP1 to OES 2018, apache is upgrade from version 2.2 to 2.4. The gw.conf, gwmon.conf and gwcal.conf files for GroupWise 2014 R2 and early versions of GroupWise 18 are only compatible with the older version of apache, 2.2. The presence of these files in the apache conf.d directories prevents apache from starting on OES 2018. Since apache will not start, iManager will not be able to start. GroupWise 18 Webaccess Service Pack 2 adds support for the newer version of Apache included with OES 2018.