New GW install. GWIA keeps stopping.

[Cougie]

Build Number:132269
Revision:18.1.0

Hi this is a brand new GW server install. Everything is working fine.
But GWIA service has stopped itself everyday for the past 3 days now. Everything is OK after I manually start it back up.

How can I find out what's causing this?

Thanks.

[ketter]

On Wed, 16 Jan 2019 06:56:02 GMT, Cougie
<Cougie@no-mx.forums.microfocus.com> wrote:

>
>Build Number:132269
>Revision:18.1.0
>
>Hi this is a brand new GW server install. Everything is working fine.
>But GWIA service has stopped itself everyday for the past 3 days now.
>Everything is OK after I manually start it back up.
>
>How can I find out what's causing this?
>
>Thanks.

Make sure GWIA logging is set to verbose and review the logs.

You can also setup GWHA to automatically restart GroupWise components
(assuming this is running on Linux or OES).

--
Ken
Knowledge Partner

Create and vote for enhancements!
https://www.microfocus.com/products/enhancement-request.html

[laurabuckley]

Hi,

What operating system is this GWIA server running?

If it is SLES 12 SPx or OES 2018 please implement TID 7019037. After doing so run this command:

ldd /opt/novell/groupwise/agents/bin/gwia

The only thing you are looking for in the output is this:

the libpthread.so.0 should reference /lib64/noelision/libpthread.so.0


Cheers,

[Cougie]

It's OES 2018 SLES 12 SP2

I've enabled GWIA verbose logging.

I've applied the change in TID 7019037. (Ie added /lib64/noelision to beginning of /etc/ld.so.conf and restarted GW agents.)

Output has this line: libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f9c0061a000)
I don't see "noelision" anywhere in the output.

I'll check out the GWIA log when it happens again.

Thanks.

[laurabuckley]

Hi,

Post the output of your ld.so.conf just so we can have more eyes on it for typos.

Cheers,

[bkesting]

Resurrecting this thread a bit......I am running GW 18.1 on SLES 12 SP3 and I too am experiencing random crashes of my GWIA. I can't seem to find anything in my logs that point to what might be happening. It might go weeks without a crash, or it might do it several times a day. Really seems random. I can manually start it back up and it comes back to life.

Is the above TID the recommended fix?

[laurabuckley]

Hi,

That TID regarding the "noelision" is a good place to start.

Cheers,

[bkesting]

laurabuckley;2497195 wrote:
Hi,

That TID regarding the "noelision" is a good place to start.

Cheers,

Seems to be working fine now post TID implementation. Thanks