clausw1
New Member.
1765 views

gwia imap crash (on sled)

Hi,
our gwia crashes every 1-2 hours at business hours, on weekend or at night I had no crash till now.
The problem is IMAP4, we have two GWIAs on two physical servers running, but we have only one imap nameserver entry pointing to a gwia at the same time.
(imap.domain) the Server to which the imap entry points crashes 7-8 times/day, the other gwia is running rock solid, if we change the imap nameserver entry to
the other gwia box the the other box starts crashing. So the problem moves with the imap access.
One Server has OES2SP1 and the other SLED10.2 installed.
Groupwise Version is 8HP2, but the problem exits also in GW8HP1.
IMAP access is only through ssl allowed and we have increased the secure imap threads from 10 to 30, same problem.
any ideas?
Here a typical log:
Restarted gwia1dom gwia1 Wed Jul 8 09:36:01 CEST 2009
Restarted gwia1dom gwia1 Wed Jul 8 10:20:01 CEST 2009
Restarted gwia1dom gwia1 Wed Jul 8 11:28:01 CEST 2009
Restarted gwia1dom gwia1 Wed Jul 8 12:27:01 CEST 2009
Restarted gwia1dom gwia1 Wed Jul 8 12:53:01 CEST 2009
Restarted gwia1dom gwia1 Wed Jul 8 13:15:01 CEST 2009
Restarted gwia1dom gwia1 Wed Jul 8 13:33:01 CEST 2009
Restarted gwia1dom gwia1 Wed Jul 8 13:42:02 CEST 2009
Restarted gwia1dom gwia1 Wed Jul 8 13:55:01 CEST 2009
Restarted gwia1dom gwia1 Wed Jul 8 14:20:01 CEST 2009
Restarted gwia1dom gwia1 Wed Jul 8 14:50:01 CEST 2009
regards
claus
Labels (2)
0 Likes
2 Replies
clausw1
New Member.

Antw: gwia imap crash on sles not sled



>>> Claus Wohlschlager<Claus.Wohlschlager@jku.at> schrieb am Donnerstag, 09. Juli 2009 um 21:42:


Hi,
our gwia crashes every 1-2 hours at business hours, on weekend or at night I had no crash till now.
The problem is IMAP4, we have two GWIAs on two physical servers running, but we have only one imap nameserver entry pointing to a gwia at the same time.
(imap.domain) the Server to which the imap entry points crashes 7-8 times/day, the other gwia is running rock solid, if we change the imap nameserver entry to
the other gwia box the the other box starts crashing. So the problem moves with the imap access.
One Server has OES2SP1 and the other SLED10.2 installed.
Groupwise Version is 8HP2, but the problem exits also in GW8HP1.
IMAP access is only through ssl allowed and we have increased the secure imap threads from 10 to 30, same problem.
any ideas?
Here a typical log:
Restarted gwia1dom gwia1 Wed Jul 8 09:36:01 CEST 2009
Restarted gwia1dom gwia1 Wed Jul 8 10:20:01 CEST 2009
Restarted gwia1dom gwia1 Wed Jul 8 11:28:01 CEST 2009
Restarted gwia1dom gwia1 Wed Jul 8 12:27:01 CEST 2009
Restarted gwia1dom gwia1 Wed Jul 8 12:53:01 CEST 2009
Restarted gwia1dom gwia1 Wed Jul 8 13:15:01 CEST 2009
Restarted gwia1dom gwia1 Wed Jul 8 13:33:01 CEST 2009
Restarted gwia1dom gwia1 Wed Jul 8 13:42:02 CEST 2009
Restarted gwia1dom gwia1 Wed Jul 8 13:55:01 CEST 2009
Restarted gwia1dom gwia1 Wed Jul 8 14:20:01 CEST 2009
Restarted gwia1dom gwia1 Wed Jul 8 14:50:01 CEST 2009
regards
claus
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Antw: gwia imap crash on sles not sled

Claus Wohlschlager wrote:
>
> >>> Claus Wohlschlager<Claus.Wohlschlager@jku.at> schrieb am

> Donnerstag, 09. Juli 2009 um 21:42:
> Hi,
> our gwia crashes every 1-2 hours at business hours, on weekend or at
> night I had no crash till now.
> The problem is IMAP4, we have two GWIAs on two physical servers running,
> but we have only one imap nameserver entry pointing to a gwia at the
> same time.
> (imap.domain) the Server to which the imap entry points crashes 7-8
> times/day, the other gwia is running rock solid, if we change the imap
> nameserver entry to
> the other gwia box the the other box starts crashing. So the problem
> moves with the imap access.
> One Server has OES2SP1 and the other SLED10.2 installed.
> Groupwise Version is 8HP2, but the problem exits also in GW8HP1.
> IMAP access is only through ssl allowed and we have increased the secure
> imap threads from 10 to 30, same problem.
> any ideas?
> Here a typical log:
> Restarted gwia1dom gwia1 Wed Jul 8 09:36:01 CEST 2009
> Restarted gwia1dom gwia1 Wed Jul 8 10:20:01 CEST 2009
> Restarted gwia1dom gwia1 Wed Jul 8 11:28:01 CEST 2009
> Restarted gwia1dom gwia1 Wed Jul 8 12:27:01 CEST 2009
> Restarted gwia1dom gwia1 Wed Jul 8 12:53:01 CEST 2009
> Restarted gwia1dom gwia1 Wed Jul 8 13:15:01 CEST 2009
> Restarted gwia1dom gwia1 Wed Jul 8 13:33:01 CEST 2009
> Restarted gwia1dom gwia1 Wed Jul 8 13:42:02 CEST 2009
> Restarted gwia1dom gwia1 Wed Jul 8 13:55:01 CEST 2009
> Restarted gwia1dom gwia1 Wed Jul 8 14:20:01 CEST 2009
> Restarted gwia1dom gwia1 Wed Jul 8 14:50:01 CEST 2009
> regards
> claus
>
>
>

The obvious is opening a support incident. Unless you can specifically
isolate what messgae is crashing there's not much more to be done than
sending in a coredump.

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.