|
Problem(Abstract) |
The following instructs you on generating a coredump for
httpd processes running on AIX®. |
|
|
|
Resolving the
problem |
- Add the following directive in the global scope of the
httpd.conf file:
CoreDumpDirectory /tmp |
|
For more details, see the CoreDumpDirectory
directive on the Apache HTTP Server Version 1.3 Web site.
Note: If you choose to have IBM® HTTP Server generate the core
file in a different directly other than /tmp, you must make sure
your user that the IBM HTTP Server children processes run under, has
permission to write to the directory. The default user for IBM HTTP Server
is nobody. |
|
- Make sure the Full Core option is set on the AIX system. To
enable the Full Core option, as root, run smitty chgsys
and set the value of Enable full CORE dump to true.
- Verify the user account for IBM HTTP Server (for example:
nobody) has unlimited access to generate corefiles on the AIX
system.
Note: For bash or ksh, the following command will display the
current limit:
ulimit -a |
|
Example:
core file size (blocks) |
unlimited |
data seg size (kbytes) |
unlimited |
file size (blocks) |
unlimited |
max memory size (kbytes) |
unlimited |
open files |
unlimited |
pipe size (512 bytes) |
64 |
stack size (kbytes) |
unlimited |
cpu time (seconds) |
unlimited |
max user processes |
128 |
virtual memory (kbytes) |
unlimited |
To set the ulimit for the user account to unlimited, run
the following command:
Root can easily set all limits to unlimited for a user by editing
/etc/security/limits and then setting everything to -1.
Example:
fsize = -1
core = -1
cpu = -1
data = -1
rss = -1
stack = -1
nofiles = -1 |
If you continue to have problems generating coredumps when running the
IBM HTTP Server on AIX, refer to the following document for more
information on available debugging options: MustGather:
Debugging IBM HTTP Server crashes or hangs on UNIX and Linux |
|
|
|
|
|
|