Hi,

I am running a iplanet webserver in a HP-UX box and the iplanet webserver is crashing oftenly. I want to take a core dump. Could you please let me know how can i check whether server core is enabled?

if not how can i enable the same?

Also let me know to which path it saves the core.

Thanks.

Any executing image can core dump. It may be one of the ulimit settings for the iplanet webserver user(s). -- I do not know iplanet.

logon or su to the user.

jmcnama  > ulimit -a
time(seconds)        unlimited
file(blocks)         unlimited
data(kbytes)         2015464
stack(kbytes)        256000
memory(kbytes)       unlimited
coredump(blocks)     4194303

Thanks for your reply.

It says.

stripes $ ulimit -a
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) 524288
stack(kbytes) 15360
memory(kbytes) unlimited
coredump(blocks) 4194303

Any idea where the cores will be created?

And also can you help me with the command to generate core on a running process.

the file named core will be in the current working directory of the iplanet process - or iplanetd process or whatever it is called. It may be several processes.
Assuming there is an iplanet user account

awk -F: '/iplanet/{print $6}' /etc/passwd | read homedir
find $homedir -name core -user iplanet

ps -ef | grep iplanet

kill -SEGV <pid>

Hi,

Thanks for the replies.Even kill -3 <pid> generates the core..

Kris

Hi,

My Requirement is pretty different actually. I am looking for the core generation for setuid processes. where my webserver parent process is running as root and child process running in different id.

I use HP-UX 11.11.

Here is the work around for generating core.

A process with an effective user ID different from its real user ID does not produce a core image.
setuid of course changes the effective uid, which prevents a core file

HP-UX 11.11 has an enhanced core product that adds support for core to be dumped of pink processes.
This kernel functionality is built into HP-UX 11.23.

Enhanced Core:
Hewlett-Packard Co. states:

Overview
This product contains kernel support to dump core of a setuid/setgid process (whose effective user/group ID is
different from it's real user/group ID). To do so, first another root process should become the debugger of this
process using the ttrace(2) system call. Then the debugger process can request core of this process using the
TT_PROC_CORE request of the ttrace(2) system call. The core file produced will have root credentials and
permission for root to read and write.

A process with any kind of setuid operation gets flagged not to dump core.

I do not know anything about pink. Sorry.