HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- shared memory problem. SOS.
Operating System - HP-UX
1827880
Members
1398
Online
109969
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-11-2001 02:58 PM
06-11-2001 02:58 PM
shared memory problem. SOS.
Hi.
We have two identical L class servers, serving production and development roles,running sybase. On one server, if the sybase is up, it will not let me run ignite or sam in the X-windows mode. (It lets me run gpm, though.) It gives the following error:
sam: FATAL ERROR: Unable to load library "/usr/lib/Motif1.2_R6/./libXm.3": Not enough space
On the other hand, if they try to start sybase when I am running either sam or ignite (in the X-windows), it fails giving the following error:
00: 00000:00000:2001/06/11 16:11:11.07 kernel os_create_region: can't allocate 742694912 bytes
00: 00000:00000:2001/06/11 16:11:11.07 kernel kbcreate: couldn't create server region 1.
00: 00000:00000:2001/06/11 16:11:11.07 kernel kistartup: could not create shared memory
Interestingly, the prod. box which is at the same patch level and kernel parameters, is giving no such errors/problems. It works perfectly alright. I have cross checked the kernel parameters from both the servers, could not find any difference. I have 4 GB ram, 8 GB swap and two processors.
If any one can shed some light, it will be greatly appreciated.
Thanks in advance for your reply and valuable time,
Regards
Anu Mathew
We have two identical L class servers, serving production and development roles,running sybase. On one server, if the sybase is up, it will not let me run ignite or sam in the X-windows mode. (It lets me run gpm, though.) It gives the following error:
sam: FATAL ERROR: Unable to load library "/usr/lib/Motif1.2_R6/./libXm.3": Not enough space
On the other hand, if they try to start sybase when I am running either sam or ignite (in the X-windows), it fails giving the following error:
00: 00000:00000:2001/06/11 16:11:11.07 kernel os_create_region: can't allocate 742694912 bytes
00: 00000:00000:2001/06/11 16:11:11.07 kernel kbcreate: couldn't create server region 1.
00: 00000:00000:2001/06/11 16:11:11.07 kernel kistartup: could not create shared memory
Interestingly, the prod. box which is at the same patch level and kernel parameters, is giving no such errors/problems. It works perfectly alright. I have cross checked the kernel parameters from both the servers, could not find any difference. I have 4 GB ram, 8 GB swap and two processors.
If any one can shed some light, it will be greatly appreciated.
Thanks in advance for your reply and valuable time,
Regards
Anu Mathew
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-11-2001 04:11 PM
06-11-2001 04:11 PM
Re: shared memory problem. SOS.
Looks like you are hitting a kernel fence such as maxdsiz. Make sure maxdsiz is plenty large (ie, 900 megs) so you won't hit this runaway program limit. Additionally, the amount of virtual memory should be checked. If swapmem_on is 1, then virtual memory is about 75% RAM plus all swap space. If swapmem_on is 0, then swap space is all tou have to run programs. Use swapinfo -tm to check.
sam and swinstall (and other dual interface programs) use a lot more RAM in the GUI mode. For shared memory programs, the problem, especially for 32-bit programs, is orphan segments and fragmentation. Use ipcs -mop to look for zero NATTCH and seg addr = 0 as these segments can be released with ipcs.
Bill Hassell, sysadmin
sam and swinstall (and other dual interface programs) use a lot more RAM in the GUI mode. For shared memory programs, the problem, especially for 32-bit programs, is orphan segments and fragmentation. Use ipcs -mop to look for zero NATTCH and seg addr = 0 as these segments can be released with ipcs.
Bill Hassell, sysadmin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-18-2001 12:57 PM
06-18-2001 12:57 PM
Re: shared memory problem. SOS.
Hi,
Thanks for the reply. It was not the Kernel parameters, but two run-away processes midaemon and mib2agt creating the pain. Thanks for your input, since it helped me in a certain way to address the issue.
Regards
Anu Mathew
Thanks for the reply. It was not the Kernel parameters, but two run-away processes midaemon and mib2agt creating the pain. Thanks for your input, since it helped me in a certain way to address the issue.
Regards
Anu Mathew
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP