Skip to main content link. Accesskey S
  • Help
  • IBM Logo
  • IBM Notes and Domino wiki
  • All Wikis
  • All Forums
  • ANNOUNCEMENT: THIS WIKI IS READ-ONLY. Learn more...
  • Home
  • Product Documentation
  • Community Articles
  • Learning Center
  • IBM Redbooks
  • API Documentation
Search
Community Articles > Lotus Domino > Domino memory > AccessAllProtected Crashes Involving Shared Memory
  • Share Show Menu▼
  • Subscribe Show Menu▼

About the Original Author

Click to view profileIBM contributorShermeker D Sanders
Contribution Summary:
  • Articles authored: 2
  • Articles edited: 0
  • Comments Posted: 0

Recent articles by this author

AccessAllProtected Crashes Involving Shared Memory

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.

"POOL IS FULL" Memory Errors on Various Blocks

When the server is reporting pool full errors, it is experiencing a possible memory leak in the block for the listed pool. The top 5 commonly reported memory blocks with this condition are discussed in this article
Community articleAccessAllProtected Crashes Involving Shared Memory
Added by IBM contributorShermeker D Sanders | Edited by IBM contributorShermeker D Sanders on October 24, 2012 | Version 14
expanded Abstract
collapsed 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:
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.

        
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

107= Insufficient Memory
1B1= Cannot attach to shared memory region
1F5= Cannot attach to shared memory region, typically occurs on server startup

Related Documents

Domino 8.5.2 crashes with Error Message: PANIC: AccessAllProtected() error *** from MapSharedRegion on pool *** of *** pools (Technote #1469956)

High usage of BLK_LOCAL_BLOCK caused iNotes server crash after upgrade to 8.5.2 (Technote #1451604)

Domino JVMs create extra AIX shared memory segments causing Domino server crash (Technote #1572118)

Lotus Domino HTTP Server crashing daily - PANIC: Cannot attach to shared memory region (Technote # 1252299)

Server crashes due to low memory condition after backup application runs (Technote #1211241)

NSF_BACKUP_MEMORY_CONSTRAINED and NSF_BACKUP_MEMORY_LIMIT (Notes/Domino wiki article)

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 a 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.
expanded Attachments (0)
collapsed Attachments (0)
expanded Versions (16)
collapsed Versions (16)
Version Comparison     
VersionDateChanged by              Summary of changes
16Jan 22, 2013, 4:12:46 PMJody Colman  IBM contributor
15Oct 24, 2012, 6:03:41 PMShermeker D Sanders  IBM contributor
This version (14)Oct 24, 2012, 6:02:40 PMShermeker D Sanders  IBM contributor
13Jul 31, 2012, 7:10:18 PMShermeker D Sanders  IBM contributor
12Jul 13, 2012, 12:32:39 PMTerri Puckett  IBM contributorAdded DDM technote
11Jul 6, 2012, 5:02:32 PMTerri Puckett  IBM contributorMinor Change
10Jul 6, 2012, 4:39:57 PMTerri Puckett  IBM contributorMinor Change
9Jul 5, 2012, 12:34:15 PMTerri Puckett  IBM contributorFormatting changes
8Jul 5, 2012, 12:20:23 PMTerri Puckett  IBM contributor
7Jun 26, 2012, 2:46:45 PMShermeker D Sanders  IBM contributor
5Jun 26, 2012, 2:46:04 PMShermeker D Sanders  IBM contributor
4Jun 26, 2012, 2:44:36 PMShermeker D Sanders  IBM contributor
3Jun 26, 2012, 2:43:38 PMShermeker D Sanders  IBM contributor
2Jun 26, 2012, 2:40:55 PMShermeker D Sanders  IBM contributor
1Jun 25, 2012, 12:17:28 PMShermeker D Sanders  IBM contributor
1Jun 26, 2012, 1:57:32 PMShermeker D Sanders  IBM contributor
Copy and paste this wiki markup to link to this article from another article in this wiki.
Go ElsewhereStay ConnectedHelpAbout
  • IBM Collaboration Solutions wikis
  • IBM developerWorks
  • IBM Software support
  • Twitter LinkIBMSocialBizUX on Twitter
  • FacebookIBMSocialBizUX on Facebook
  • ForumsLotus product forums
  • BlogsIBM Social Business UX blog
  • Community LinkThe Social Lounge
  • Wiki Help
  • Forgot user name/password
  • About the wiki
  • About IBM
  • Privacy
  • Accessibility
  • IBM Terms of use
  • Wiki terms of use