- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: mmap failed for dld mmap failed for TSD
Categories
Company
Local Language
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
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
Community
Resources
Forums
Blogs
- 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
10-20-2004 04:39 AM
10-20-2004 04:39 AM
mmap failed for dld mmap failed for TSD
Here is the log from the core.
B.11.11
9000/800
101901557
build9i
l>X{
UUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU?
>B$Revision: 92453-07 linker linker crt0.o B.11.16 000601 $
/usr/lib/dld.sl
ERROR: mmap failed for dld
ERROR: mmap failed for TSD
@@@@@@@@@@@@@@@@@@@@@@@@@@
/tmp/shxxxxxxxxxx.aaaaaaaaaa
LINES
LINES=1
COLUMNS
COLUMNS=1
ksh: no memory
eE;,TtFf
@(#) $ B.11.11_LR Jul 24 2003 00:43:42 $
We have recently upgraded to oracle client 9.2.0 from oracle 8.1.7.
Here is the info for libc
PHCO_25569 1.0 libc cumulative header file patch
PHCO_28481 1.0 cumulative 10.20 libc compatibility support
PHCO_29328 1.0 libc manpage cumulative patch
PHCO_31061 1.0 libc cumulative patch
When I try an ldd on dld.sl in /usr/lib/
This is what I get.
/usr/lib/dld.sl: Call to mmap() failed - TEXT /usr/lib/dld.sl
/usr/lib/dld.sl: Not enough space
The swap mem info is
Mb Mb Mb PCT START/ Mb
TYPE AVAIL USED FREE USED LIMIT RESERVE PRI NAME
dev 2000 59 1941 3% 0 - 1 /dev/vg00/lvol2
dev 2000 59 1941 3% 0 - 1 /dev/vg00/swap2
dev 2000 59 1941 3% 0 - 1 /dev/vg00/swap3
reserve - 2118 -2118
memory 3061 1323 1738 43%
total 9061 3618 5443 40% - 0 -
I'd appreciate it if someone could help out. I have tried searching the web but havent found any answers yet.
Thanks,
Kiran Nadgir
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-20-2004 04:48 AM
10-20-2004 04:48 AM
Re: mmap failed for dld mmap failed for TSD
Also in your script, do ulimit -t unlimited (if you are using posix shell) at the start of the script.
Anil
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-20-2004 05:04 AM
10-20-2004 05:04 AM
Re: mmap failed for dld mmap failed for TSD
maxtsiz 262144 - 0-503859 Pages -
maxtsiz_64bit 262144 - 1024-1073741823 Pages -
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-20-2004 05:07 AM
10-20-2004 05:07 AM
Re: mmap failed for dld mmap failed for TSD
Check and post.
Anil
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-20-2004 05:43 AM
10-20-2004 05:43 AM
Re: mmap failed for dld mmap failed for TSD
There is one thing which I noticed is unusual.
I use one script to set all env vars. When I have this line
export LD_PRELOAD=/usr/lib/libcl.sl:/usr/lib/libpthread.sl
I get the coredump, If I comment out this line it works fine.
We have also upgraded DBD Oracle as well as perl
/opt/perl5.6.1/lib/site_perl/5.6.1/PA-RISC2.0/auto/DBD/Oracle> ldd Oracle.sl
/usr/lib/libm.2 => /usr/lib/libm.2
/usr/lib/libdld.2 => /usr/lib/libdld.2
/usr/lib/libc.2 => /usr/lib/libc.2
/usr/lib/libdld.2 => /usr/lib/libdld.2
/usr/lib/libpthread.1 => /usr/lib/libpthread.1
/usr/lib/librt.2 => /usr/lib/librt.2
/usr/lib/libcl.2 => /usr/lib/libcl.2
/usr/lib/libisamstub.1 => /usr/lib/libisamstub.1
/usr/lib/libdld.2 => /usr/lib/libdld.2
/opt/oracle/product/9.2.0/lib32//libclntsh.sl.9.0 => /opt/oracle/product/9.2.0/lib32//libclntsh.sl.9.0
/usr/lib/libcl.2 => /usr/lib/libcl.2
/usr/lib/libc.2 => /usr/lib/libc.2
/usr/lib/libm.2 => /usr/lib/libm.2
/usr/lib/libdld.2 => /usr/lib/libdld.2
/usr/lib/libnss_dns.1 => /usr/lib/libnss_dns.1
/usr/lib/libdld.2 => /usr/lib/libdld.2
/usr/lib/libpthread.1 => /usr/lib/libpthread.1
/usr/lib/librt.2 => /usr/lib/librt.2
/opt/oracle/product/9.2.0/lib32/libwtc9.sl => /opt/oracle/product/9.2.0/lib32/libwtc9.sl
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-20-2004 06:01 AM
10-20-2004 06:01 AM
Re: mmap failed for dld mmap failed for TSD
Really do not know what LD_PRELOAD does. Most probablly it loads the libraries into the memory. Commenting it out, will load the libraries as and when required. This is what my understanding says.
Not sure though. If ulimit is set to unlimited and maztsiz_64bit is high enought, I do not see a reason it should core dump.
Anil
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-20-2004 06:40 AM
10-20-2004 06:40 AM
Re: mmap failed for dld mmap failed for TSD
2. use LD_PRELOAD_ONCE instead of LD_PRELOAD.
3. do not try to make sense out of the strings in a corefile. use a debugger such as gdb to look at the contents of a core file.
"file core" will usually tell you which application dumped this core. run gdb with the paths to the application and corefile such as "gdb /opt/emacs/bin/emacs /tmp/core". the gdb "bt" command should give you the stack trace - this is the information you can provide when you ask for help.
--
ranga