HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- unable to obtain mapped memory error
Operating System - HP-UX
1834150
Members
3534
Online
110064
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
11-03-2008 01:01 PM
11-03-2008 01:01 PM
unable to obtain mapped memory error
Hi
Is anybody familiar with:
Catastrophic error: unable to obtain mapped memory
error message?
I am getting this message during build process on build server (HPUX 11.23) that is located in HPVM environment, not problem when build server is located on Physical server (rx6600).
I am not even sure whether this is HP-UX error message (say from mmap) or it is reported by other applications.
But coincidentally, the pattern (in build process log files) is that this error is following instance just after build server contacts Mainwin license server.
Build process is based on perl script (/opt/ActivePerl-5.8/bin/perl5.8.8)
Note:
B9007AA C.11.23.14 HP C/aC++ Developer's Bundle
Is anybody familiar with:
Catastrophic error: unable to obtain mapped memory
error message?
I am getting this message during build process on build server (HPUX 11.23) that is located in HPVM environment, not problem when build server is located on Physical server (rx6600).
I am not even sure whether this is HP-UX error message (say from mmap) or it is reported by other applications.
But coincidentally, the pattern (in build process log files) is that this error is following instance just after build server contacts Mainwin license server.
Build process is based on perl script (/opt/ActivePerl-5.8/bin/perl5.8.8)
Note:
B9007AA C.11.23.14 HP C/aC++ Developer's Bundle
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-03-2008 04:32 PM
11-03-2008 04:32 PM
Re: unable to obtain mapped memory error
Running build script with tusc is reporting number of
tusc: ttrace(TT_PROC_RDDATA, 9862, 0, 1, 4, 87ffffffffffef80): Bad address
tusc: ttrace(TT_PROC_RDDATA, 21380, 0, 1, 4, 87ffffffffffef80): Bad address
tusc: ttrace(TT_PROC_RDDATA, 22202, 0, 1, 4, 87ffffffffffef80): Bad address
tusc: ttrace(TT_PROC_RDDATA, 22202, 0, 1, 4, 87ffffffffffef80): Bad address
tusc: ttrace(TT_PROC_RDDATA, 22202, 0, 1, 4, 87ffffffffffef80): Bad address
tusc: ttrace(TT_PROC_RDDATA, 22202, 0, 1, 4, 87ffffffffffef80): Bad address
in the terminal where the build was started?
tusc: ttrace(TT_PROC_RDDATA, 9862, 0, 1, 4, 87ffffffffffef80): Bad address
tusc: ttrace(TT_PROC_RDDATA, 21380, 0, 1, 4, 87ffffffffffef80): Bad address
tusc: ttrace(TT_PROC_RDDATA, 22202, 0, 1, 4, 87ffffffffffef80): Bad address
tusc: ttrace(TT_PROC_RDDATA, 22202, 0, 1, 4, 87ffffffffffef80): Bad address
tusc: ttrace(TT_PROC_RDDATA, 22202, 0, 1, 4, 87ffffffffffef80): Bad address
tusc: ttrace(TT_PROC_RDDATA, 22202, 0, 1, 4, 87ffffffffffef80): Bad address
in the terminal where the build was started?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-03-2008 09:55 PM
11-03-2008 09:55 PM
Re: unable to obtain mapped memory error
Are you running out of swapspace? swapinfo -tam
>B9007AA C.11.23.14
The secret decoder ring says this is A.06.15. A.06.20 is available.
>B9007AA C.11.23.14
The secret decoder ring says this is A.06.15. A.06.20 is available.
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
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP