Cool Solutions

Upgrade Tips for GroupWise on Linux



By:

June 12, 2007 8:23 am

Reads:4,666

Comments:1

Score:Unrated

Problem

A Forum reader recently asked:

“I tried to perform the upgrade of my GroupWise 7.0.1 system on OES Linux. Currently, the MTA, POA and GWIA are functioning perfectly on the system. I tried to perform the upgrade, but it crashed.

I downloaded the upgrade tarball and expanded it on my system. I started the install and got through the file copy just fine. It prompted for the domain location; I browsed to the directory and hit Enter. At that point, the upgrade stopped and the program exited. There was no error message and I can’t find anything in the logs.”

And here’s the response from Alan Evans …

Solution

For service packs, all you should need to do is upgrade the RPMs. This has worked for me for the following upgrades:

6.5.6 –> 6.5.7
6.5.7 –> 7.0.1
7.0.1 –> 7.0.2

Here’s what you need to do:

1. cd to the directory where you extracted the tar file to and issue these commands:

rpm -Uvh ./agents/linux/novell-groupwise-agents-7.0.2-20070406.i386.rpm
rpm -Uvh ./internet/gwia/linux/novell-groupwise-gwia-7.0.2-20070406.i386.rpm
rpm -Uvh ./internet/webaccess/linux/novell-groupwise-gwinter-7.0.2-20070406.i386.rpm
rpm -Uvh ./internet/webaccess/linux/novell-groupwise-webaccess-7.0.2-20070406.i386.rpm

2. Then issue the following command to restart the various agents and apache/tomcat:

/etc/init.d/grpwise restart
/etc/init.d/tomcat4 restart

– or for SLES 10 -

/etc/init.d/tomcat5 restart
/etc/init.d/apache2 restart

3. Rather than hunting for the RPMs, you can just cd to the directory where you extracted the tar file to and issue this command:

find . -name "*.rpm"

This takes only a few minutes. The only glitch I have is that I am running on SLES 10, which does not use jod_jk apache. So, I have to change my /etc/apache2/conf/gw.conf file.

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this post.
Loading ... Loading ...

Tags:
Categories: Uncategorized

Disclaimer: This content is not supported by Novell. It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test it thoroughly before using it in a production environment.

1 Comment

  1. By:AnthonyHilton

    I used this tip to upgrade the MTA and WebAccess on a SLES10 box to 7.0.3 HP3 – thanks for the help.

    I had to add the –force switch to the command rpm to upgrade the Agents because the command in the tip reported many files like this:

    file /opt/novell/groupwise/agents/lib/libvs_swf.so from install of novell-groupwise-agents-7.0.3-20090508 conflicts with file from package novell-groupwise-gwinter-7.0.1-20060627

    so the command I used was:

    rpm -Uvh --force ./agents/linux/novell-groupwise-agents-7.0.3-20090508.i386.rpm

    then the others ran as written by Alan Evans.

    The change to /etc/apache2/conf.d/gw.conf (which is a symlink to /etc/opt/novell/gw/gw.conf is to comment out the line:

    JkMount /gw/* ajp13

    and add a new line:

    ProxyPass /gw/ ajp://localhost:8009/gw/

    (I think the port should be 9009 on OES2 Linux because 8009 is used by Remote Manager).

    Anthony

Comment

RSS