worm5406 Absent Member.
Absent Member.
1587 views

Exit Key Received: Exiting

Over the past 7 days I have got this at least 10 times on our primary mail server.

14:20:07 2481 Exit Key Received: Exiting
14:20:07 2481 Exit Key Received: Exiting


No crashes
No errors
No entries

Server DanitasKingdom
Processor Model Intel(R) Xeon(R) CPU X5650 @ 2.67GHz
Number of Processors 2
Number of Cores Per Processor 6
OS Version SUSE Linux Enterprise Server 11 (x86_64) SP3
Total Server Physical Memory 23 GB
Free Server Physical Memory 2 GB
% of Memory In Use -82
Total Available Disk Space 704.1 GB
Available Free Disk Space 330.0 GB
Main Thread Process ID 9189

Build Dates
GroupWise Agent Build Version 14.2.0 -122092
GroupWise Agent Build Date 12-03-15
GroupWise Resource Build Date 10-08-15
Labels (1)
0 Likes
10 Replies
Micro Focus Expert
Micro Focus Expert

Re: Exit Key Received: Exiting

Hi,

The first thing I recommend you do is update to GroupWise 2014 R2 HP1. There are a ton of stability fixes in the HP1 version.

Please let us know how it goes.

Cheers,
Laura Buckley

Views/comments expressed here are entirely my own.
If you find this post helpful, please show your appreciation and click on "Like" below...
0 Likes
worm5406 Absent Member.
Absent Member.

Re: Exit Key Received: Exiting

Yes that is what I had planned.

Thank you.
0 Likes
Micro Focus Expert
Micro Focus Expert

Re: Exit Key Received: Exiting

Hi,

Please do keep us updated with how things go - thanks 🙂

Cheers,
Laura Buckley

Views/comments expressed here are entirely my own.
If you find this post helpful, please show your appreciation and click on "Like" below...
0 Likes
worm5406 Absent Member.
Absent Member.

Re: Exit Key Received: Exiting

OK I upgraded last night about midnight.

It died about 930am.

In looking through the POA log I had quite a few messaegs about 1 user data base:

09:31:04 CAA4 Possibly damaged blob in database = user123.db
09:31:05 CAA4 Possibly damaged blob in database = user123.db

The last one was 3 seconds before exit key received message popped up.

I took that account and did a contents (with attachments) check and let it run. I did a search for any others and did the same for 2 more users.

As of now 1530 eastern I have had no issues.
0 Likes
worm5406 Absent Member.
Absent Member.

Re: Exit Key Received: Exiting

So much for JINX

Just died at 1630.
0 Likes
Micro Focus Expert
Micro Focus Expert

Re: Exit Key Received: Exiting

Hi,

Please confirm what platform/OS your GroupWise system is running on - thanks.

Cheers,
Laura Buckley

Views/comments expressed here are entirely my own.
If you find this post helpful, please show your appreciation and click on "Like" below...
0 Likes
worm5406 Absent Member.
Absent Member.

Re: Exit Key Received: Exiting

Processor Model Intel(R) Xeon(R) CPU X5650 @ 2.67GHz
Number of Processors 2
Number of Cores Per Processor 6
OS Version SUSE Linux Enterprise Server 11 (x86_64) SP3
Total Server Physical Memory 23 GB
Free Server Physical Memory 4 GB
% of Memory In Use 82
Total Available Disk Space 699.9 GB
Available Free Disk Space 314.0 GB
Main Thread Process ID 3395
Build Dates
GroupWise Agent Build Version 14.2.0 -123047
GroupWise Agent Build Date 03-17-16
GroupWise Resource Build Date 10-08-15
0 Likes
Micro Focus Expert
Micro Focus Expert

Re: Exit Key Received: Exiting

Hi,

All looks good there. I think that it's time to open a Service Request I'm afraid.

Cheers,
Laura Buckley

Views/comments expressed here are entirely my own.
If you find this post helpful, please show your appreciation and click on "Like" below...
0 Likes
worm5406 Absent Member.
Absent Member.

Re: Exit Key Received: Exiting

I think I narrowed it down to this right before it happens:

14:59:53 CF87 Possibly damaged blob in database = user93w.db
14:59:53 CF97 Possibly damaged blob in database = user93w.db
14:59:53 DE74 Possibly damaged blob in database = user93w.db
0 Likes
Micro Focus Expert
Micro Focus Expert

Re: Exit Key Received: Exiting

Hi,

I recommend that you run a GWCheck against that user database. Untick Structure, tick contents and all options beneath contents, most particularly the Attachment option. Take a careful look at the resultant log file and report back.

Looking forward to hearing back from you.

Cheers,
Laura Buckley

Views/comments expressed here are entirely my own.
If you find this post helpful, please show your appreciation and click on "Like" below...
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.