HCL Notes and Domino wiki: Domino memory: AccessAllProtected Crashes Involving Shared Memory

AccessAllProtected Crashes Involving Shared Memory

Added by ~Kirk Nonhipi | Edited by IBM contributor

~Carol Frojumilitader on January 22, 2013 | Version 16

Actions ▼

Abstract

Abstract

Avoid PANIC: Insufficient memory, PANIC: Cannot attach to shared memory region, due to insufficient access (probably owned by another user or group), PANIC: AccessAllProtected() error (107 or 1B1 or 1F5) from MapSharedRegion on pool ### of ### pools.

Tags: memory, insufficient, shared, MapSharedRegion, accessallprotected

This article is part of a larger series: Preventative Actions and Troubleshooting Common Domino Memory Issues

AccessAllProtected crashes occur when a Domino process tries to map a segment of shared memory into the address space and there is no room in the virtual address space to map it. Once this occurs, Domino will panic with one of the below messages:

of

Prior to this type of crash condition occurring, the following errors are typically reported in the console log:

Insufficient memory
~~Maximum number of memory segments that Notes can support has been exceeded~~
Error attaching to shared memory [loc=MapSharedRegion,error code=##,ptr=ffffffff] -- check Notes configuration variables

Once the errors are reported on the server console then the administrator should take the below actions to reduce the likelihood of the crash occurring:

1. Capture two manual NSDs:

How to run NSD manually on a Domino server for UNIX platforms (Technote #1214298)
How to run a manual NSD for Notes/Domino on Windows (Technote # 1204263)

2. Bring down the Domino server

3. Enable the following debug in the server's notes.ini:

CONSOLE_LOG_ENABLED=1
DEBUG_THREADID=1

4. Restart the Domino server

5. Setup memory dumps for collection every 4 hours to capture memory allocations

How to automate the collection of memory dumps (Technote #1104943)

6. Submit the manually executed NSD(s) and console log file from the incident to Lotus Support

7. If the issue reoccurs then submit the NSD(s), console log and memory dumps from the incident to Lotus Support.

Proactive Actions

The Domino administrator can monitor for any of the above error messages reported to the Domino console by using Domino Domain Monitoring (DDM) probes to alert them once they occur so that the listed actions can be performed.

Notes/Domino Best Practices: Domino Domain Monitoring (DDM) (Technote #7009312)

Monitor Domino stats (Windows only)
- Set up a Program Document to dump out the *MemFreeKBytes stat for each Domino process every 30 minutes" using the command: Show Stat Platform.Process.*.1.MemFreeKBytes

- When the stat reaches around 150-200 MB (150000 -200000), perform steps 1 -6.

Additional Information regarding the AccessAllProtected errors

Go back to: Preventative Actions and Troubleshooting Common Domino Memory Issues

About the Author
Shermeker Sanders is an IBM Certified IT Specialist currently working as an Advisory Software Engineer Lead in the IBM Collaborative Solutions (ICS) division on the Domino UNIX Crash & Performance team in Atlanta, GA. Previously she worked on the AIX pSeries Kernel and Crash teams in Dallas, TX.