Welcome Serena Central users! CLICK HERE
The migration of the Serena Central community is currently underway. Be sure to read THIS MESSAGE to get your new login set up to access your account.
DavudOeden Super Contributor.
Super Contributor.
488 views

GW 18.1.1 POA Log: Error: Memory error. Memory function failure [8101] User: XXXXXXX

Hello,

we have a lot of "Error: Memory error. Memory function failure [8101] User:" errors in our POA Log.

GroupWise Version 18.1.1 running on SLES 11 SP4.

Any ideas why this error occures so often?

D.O.

Labels (1)
0 Likes
19 Replies
Knowledge Partner
Knowledge Partner

Re: GW 18.1.1 POA Log: Error: Memory error. Memory function failure [8101] User: XXXXXXX

I haven't seen those myself, but doing a little digging it appears they are either related to some low resources on the server or possible database corruption.  Do you have the standard maintenance tasks running on your server?  You want to have structural and content checks running on a regular basis to make sure GroupWise stays in good shape.  Here is a link that might help: https://www.konecnyad.ca/andyk/gwmnt5x.htm

--
Ken
Knowledge Partner

Create and vote for enhancements!
Idea Exchange sites within this community are now coming online for some of the Collaboration Products!
GroupWise Idea Exchange - https://community.microfocus.com/t5/GroupWise-Idea-Exchange/idb-p/GWideas
SMG Idea Exchange - https://community.microfocus.com/t5/Secure-Messaging-Gateway-Idea/idb-p/SMG_Ideas
Old method is still available for some products here: https://www.microfocus.com/products/enhancement-request.html
0 Likes
DavudOeden Super Contributor.
Super Contributor.

Re: GW 18.1.1 POA Log: Error: Memory error. Memory function failure [8101] User: XXXXXXX

Hello,

I have 3 standard maintenance tasks. One of them with DB Check and fix.

D.O.

0 Likes
Knowledge Partner
Knowledge Partner

Re: GW 18.1.1 POA Log: Error: Memory error. Memory function failure [8101] User: XXXXXXX

Not sure what your maintenance tasks are, but you should have a structure check and a content check.  They should be handled separately.  I would recommend using the settings I list below.  The structure check should happen daily and the content check once a week.

Structure Check

analyze fix databases
* structure
   * index check
* fix problems
databases
* user/resources
* message

Content Check

analyze fix databases
* content
  * collect statistics
  * attachment file check
* fix problems
  * update user disk space totals
databases
* user/resources
* message

--
Ken
Knowledge Partner

Create and vote for enhancements!
Idea Exchange sites within this community are now coming online for some of the Collaboration Products!
GroupWise Idea Exchange - https://community.microfocus.com/t5/GroupWise-Idea-Exchange/idb-p/GWideas
SMG Idea Exchange - https://community.microfocus.com/t5/Secure-Messaging-Gateway-Idea/idb-p/SMG_Ideas
Old method is still available for some products here: https://www.microfocus.com/products/enhancement-request.html
DavudOeden Super Contributor.
Super Contributor.

Re: GW 18.1.1 POA Log: Error: Memory error. Memory function failure [8101] User: XXXXXXX

Hello,

thanks for this informations.

Have had a job which does all in one but only once a week.

Deactivated it and created two new jobs as you described. Structure daily and content checkt once a week.

So will see next report tomorrow. But the old weekly job which does all in one, should have reported problems too. But I dont find the reports at the moment. Otherwise will see tomorrow what the log tells me.

Will post the results tomorrow. 

0 Likes
Knowledge Partner
Knowledge Partner

Re: GW 18.1.1 POA Log: Error: Memory error. Memory function failure [8101] User: XXXXXXX

I forget the reason, but the preferred method is to always run contents and structure checks as two separate tasks.  Let us know if you see any changes.

--
Ken
Knowledge Partner

Create and vote for enhancements!
Idea Exchange sites within this community are now coming online for some of the Collaboration Products!
GroupWise Idea Exchange - https://community.microfocus.com/t5/GroupWise-Idea-Exchange/idb-p/GWideas
SMG Idea Exchange - https://community.microfocus.com/t5/Secure-Messaging-Gateway-Idea/idb-p/SMG_Ideas
Old method is still available for some products here: https://www.microfocus.com/products/enhancement-request.html
0 Likes
Micro Focus Expert
Micro Focus Expert

Re: GW 18.1.1 POA Log: Error: Memory error. Memory function failure [8101] User: XXXXXXX

Hi D.O.

As far as I am aware there is no single cause for a Memory Function failure 8101 error in the POA logs.  For example, I've seen this error being caused by a corrupt signature in conjunction with Vacation rules.  Sorry, not a solution, just information.

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
DavudOeden Super Contributor.
Super Contributor.

Re: GW 18.1.1 POA Log: Error: Memory error. Memory function failure [8101] User: XXXXXXX

GWCheck finished, but the Erros in the POA Log are still there...

GWCheck summary :

STRUCTURAL VERIFICATION of system databases
STRUCTURAL VERIFICATION of database ngwguard.db
- Database is structurally consistent

***** OVERALL STATS FOR THIS RUN *****
*********************************************************************
Uncorrectable conditions encountered:
CODE DESCRIPTION COUNT
---- -------------------------------------------------- -----
50 Orphaned Blob files (deleted)...................... 12
83 Items that have failed to archive.................. 170
Correctable conditions encountered:
CODE DESCRIPTION COUNT
---- -------------------------------------------------- -----
3 LIN_ATTACHMENT_RECORDs found but not used.......... 73
7 User Attachments found but not referenced.......... 5
19 MSG host recs, LIN_DRN pointing to missing record.. 1228
22 MSG user recs, LIN_DRN pointing to missing record.. 4320
30 Folder records found with improper parents......... 25
32 Records found with improper folders................ 2
37 Item records with missing message database recs.... 1212
52 Outdated search records found...................... 2440
66 GWCheck log files in log directory................. 2
67 Outdated execution records.(notify/alarm).......... 12609
76 Folders/books with distribution list problems...... 6
78 Item records with invalid fields................... 1949
79 Duplicate folder names at same level............... 6
82 Inaccessible attachment files...................... 14
89 Users exceeding defined size limits................ 11
90 Users exceeding threshold limits................... 85
93 Unused blob files (deleted)........................ 356
96 Records found with duplicate invalid fields........ 8
98 Category records missing fields.................... 18
99 Duplicate category names........................... 1
100 Users missing system categories.................... 4
102 Contact folders out of sync........................ 66
105 Access records in need of repair................... 41
*********************************************************************

 

0 Likes
Knowledge Partner
Knowledge Partner

Re: GW 18.1.1 POA Log: Error: Memory error. Memory function failure [8101] User: XXXXXXX


@DavudOeden wrote:

GWCheck finished, but the Erros in the POA Log are still there...

GWCheck summary :

STRUCTURAL VERIFICATION of system databases
STRUCTURAL VERIFICATION of database ngwguard.db
- Database is structurally consistent

***** OVERALL STATS FOR THIS RUN *****
*********************************************************************
Uncorrectable conditions encountered:
CODE DESCRIPTION COUNT
---- -------------------------------------------------- -----
50 Orphaned Blob files (deleted)...................... 12
83 Items that have failed to archive.................. 170
Correctable conditions encountered:
CODE DESCRIPTION COUNT
---- -------------------------------------------------- -----
3 LIN_ATTACHMENT_RECORDs found but not used.......... 73
7 User Attachments found but not referenced.......... 5
19 MSG host recs, LIN_DRN pointing to missing record.. 1228
22 MSG user recs, LIN_DRN pointing to missing record.. 4320
30 Folder records found with improper parents......... 25
32 Records found with improper folders................ 2
37 Item records with missing message database recs.... 1212
52 Outdated search records found...................... 2440
66 GWCheck log files in log directory................. 2
67 Outdated execution records.(notify/alarm).......... 12609
76 Folders/books with distribution list problems...... 6
78 Item records with invalid fields................... 1949
79 Duplicate folder names at same level............... 6
82 Inaccessible attachment files...................... 14
89 Users exceeding defined size limits................ 11
90 Users exceeding threshold limits................... 85
93 Unused blob files (deleted)........................ 356
96 Records found with duplicate invalid fields........ 8
98 Category records missing fields.................... 18
99 Duplicate category names........................... 1
100 Users missing system categories.................... 4
102 Contact folders out of sync........................ 66
105 Access records in need of repair................... 41
*********************************************************************

 


This log doesn't really look like a *fix problems* has been run on this PO recently. Most of these errors should no longer show on subsequent gwcheck runs.

CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de
0 Likes
Knowledge Partner
Knowledge Partner

Re: GW 18.1.1 POA Log: Error: Memory error. Memory function failure [8101] User: XXXXXXX

GWCheck finished, but the Errors in the POA Log are still there...

- How tight are you for RAM?  is the swap being mostly used up or hardly touched?
   free -m is the linux level command to see it easily, or it is in the top section of top. 
   for more on understanding the results I wrote up https://www.konecnyad.ca/andyk/freemem.htm

- are the structural GWChecks coming clean or are there errors there as well?   fix any at that level first

- as per Masimo,  confirm that the Fix part is turned on for GWChecks.   the output should have a line in the top section
    Action = Analyze/Fix

- I try to run a pair of the Contents Analyze/Fix during the weekend as that second one gives you a better idea of which errors are sticky and need some direct attention.   refer to https://konecnyconsulting.ca/gw/gwlogs.html  for running through those errors and problems.   That list of yours looks like a fix run hasn't been done for a long time, such that this is the 2nd longest list of errors I've seen. I might just have to add a link to this thread to add you to my list at the bottom of the page listed above if you don't have an objection.

 

 

___
Andy of Konecny Consulting in Toronto
Knowledge Partner Profile
If you find a post helpful, click the Like button below. Thanks!
0 Likes
DavudOeden Super Contributor.
Super Contributor.

Re: GW 18.1.1 POA Log: Error: Memory error. Memory function failure [8101] User: XXXXXXX

After Reboot:

Mem: 15953M total, 2446M used, 13506M free, 49M buffers
Swap: 2047M total, 0M used, 2047M free, 1353M cached

But the Error is still there after reboot.

Wanted to start a Analyze/Fix Job now, but job does not start. I'll get a few seconds later a duplicate job information and it says there is still a job running. I started yesterday morning a job, but normaly the job does not take up to 24 hours. Where can I see the running job ? Is it possible to cancel the running anlyze/fix job ?

Regards,

D.O.

0 Likes
Knowledge Partner
Knowledge Partner

Re: GW 18.1.1 POA Log: Error: Memory error. Memory function failure [8101] User: XXXXXXX

those memory use numbers are typical of a freshly rebooted system,  what really matters is how much of swap gets used under normal usage.  I typically aim to add RAM if it quickly (less than a day) uses more than half of the swap.   If you have ganglia on this system, you can see more of how it has been over time. Is this a pure SLES box or is it OES (11 or 2015)?

 

to see if a GWCheck is running,  go to the web console of the POA in question at   http://POA_IP:7181

In the "Thread Status" section, look at "GWCheck Worker Threads"

example of a customer's system I am looking at right now shows as 3, 0, 3
where the first is how many allocated with 4 as the default, the second is now many are in use right now, and the last is what is the max used so far, so just after a system start will be at 0 until the next GWCheck runs.

at the bottom of the first section is:
GWCheck Auto Queues
GWCheck Scheduled Queues

The Auto Queues will be zero until the POA decides there is a problem and launches them on their own.  shows you both active now and what has run

Schedules Queues shows the ones you have launched manually,  when scheduled ones time has launched them, and any sub jobs spawned by either of them.  (example, a single contents check spawns one per db so they add up quick)   The peak is a high water mark for number in the queue at a time rather than a total run to date.

Those queues do represent folders on the PO, with the GWChecks each a file.  So we have a way to remove them (to pause or cancel), but not something we want to jump at until we have a better idea of what is going on.   I've found it is very easy to double submit something so that is my usual first suspect for such things as the 'dreaded' DF2A 'error'

 

 

___
Andy of Konecny Consulting in Toronto
Knowledge Partner Profile
If you find a post helpful, click the Like button below. Thanks!
0 Likes
Micro Focus Expert
Micro Focus Expert

Re: GW 18.1.1 POA Log: Error: Memory error. Memory function failure [8101] User: XXXXXXX

Hi,

Further to what Andy has said... on the POA Web Console Status page... scroll right to the bottom and it will show you the status of GWCheck if it's currently running or idle.

If Idle, stop the POA rename the ngwcheck file and then restart the POA and that *should* clear the maintenance in progress flag.

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
DavudOeden Super Contributor.
Super Contributor.

Re: GW 18.1.1 POA Log: Error: Memory error. Memory function failure [8101] User: XXXXXXX

Hello, now, after 24h RAM looks like this:

Mem: 15953M total, 15698M used, 255M free, 704M buffers
Swap: 2047M total, 8M used, 2039M free, 13235M cached

I found the ngwcheck.db file. Stopped the POA and renamed the DB File to bak. After restarting the POA the job was gone. 

I figured out that the "Memoy Error. Memory function failure [8101]" does not occure on all users. Only 50-100 Users "makes" this problem. The users didnt see any problems in their Clients. But I figured out, sending & reading mails in the client of this users lets this Error occure.

I will do now a lot of GWChecks with Fix until the problems in the error log gets fewer and will see if this error gets solved with the gwchecks.

D.O.

0 Likes
MarkDissington Outstanding Contributor.
Outstanding Contributor.

Re: GW 18.1.1 POA Log: Error: Memory error. Memory function failure [8101] User: XXXXXXX

If they are running OES it should be OES2015 as GW18.1.x doesn't support installs on OES11 - https://www.novell.com/documentation/groupwise18/gw18_guide_install/data/inst_req_admin_hardware_os.html

Might be the cause of the issue if they are.

Mark.

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.