[ngw] GWHA Problem After Upgrade

Morris Blackham mblackham at microfocus.com
Wed Jan 20 16:15:01 UTC 2016

Matt,  bug number is 961782 and fix is available as FTF in revision
122390.    I twisted Pam's arm to get a TID written

>>> Matt Weisberg <matt at weisberg.net> 1/13/2016 12:03 PM >>>

What is the bug number?  Also, is there a TID about this?  I didn’t see

Thanks Morris.


  Matt Weisberg
  Weisberg Consulting, Inc.
  matt at weisberg.net
  ofc. 248.685.1970
  cell 248.705.1950
  fax 248.769.5963

On 1/13/16, 1:51 PM, "ngw-bounces+matt=weisberg.net at ngwlist.com on
behalf of Morris Blackham" <ngw-bounces+matt=weisberg.net at ngwlist.com on
behalf of mblackham at microfocus.com> wrote:

>Hey Matt, good catch.  While the upgrade from 2014 to R2 added the
> the upgrade from 2012 did not.  Found that 2012 file used spaces as
>whitespace for the parameters and the 2014 file used tabs.   The code
>look for the line to add it after used sed and only looked for  a
>char of whitespace..   Have a bug written up..
>>>> Matt Weisberg <matt at weisberg.net> 1/12/2016 7:16 PM >>>
>I had a site I recently upgraded from GroupWise 2012 to 2014 R2. 
>of the servers were SLES 11 SP4.  The upgrade went fine, but I could
>get the GWHA service to restart a failed PO.  Everything looked
>configured correctly, so I tried telnetting to port 8400 on one of
>upgraded servers:
>Connected to dvcpo.
>Escape character is '^]'.
>gwha: error while loading shared libraries: libssl.so.1.0.0: cannot
>open shared object file: No such file or directory
>Connection closed by foreign host.
>I tested the one server that was a fresh SLES 12 SP1 install and it
>not have this issue.
>I discovered that after the upgrade, the gwha configuration in
>/etc/xinet.d was not updated properly, it looked like this:
>service gwha
>{	    socket_type     = stream
>	    protocol  	  = tcp
>	    wait  		  = no
>	    user  		  = root
>	    server  	    =
>    instances = 1
>    type = UNLISTED
>    port = 8400
>It was missing the environment setting for the library path, so gwha
>couldn’t find the libraries it needed, so I changed it to this:
>service gwha
>{	    socket_type     = stream
>	    protocol  	  = tcp
>	    wait  		  = no
>	    user  		  = root
>	    server  	    =
>	    instances  	 = 1
>	    type  		  = UNLISTED
>	    port  		  = 8400
>	    env  		   =
>And restarted xinetd (rcxinetd restart) and everything started
>I think this is a bug in the upgrade process.  I checked some other
>sites that I had upgraded and they were all missing the library path
>the gwha xinetd config.
>Hope that saves someone some grief!
>>Matt Weisberg
>Weisberg Consulting, Inc.
>matt at weisberg.net
>ofc. 248.685.1970
>cell 248.705.1950
>fax 248.769.5963
>ngw mailing list
>ngw at ngwlist.com

ngw mailing list
ngw at ngwlist.com

More information about the ngw mailing list