1748128 Members
3651 Online
108758 Solutions
New Discussion юеВ

Re: core files

 
Kapil Jha
Honored Contributor

Re: core files

these tar files are created by HP Replication Solutions Manager(RSM)

http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&taskId=110&prodSeriesId=3807693&prodTypeId=18964&objectID=c01677859

You may have to check why its generating so much logs and may be restart the rsm agent.

BR,
Kapil+
I am in this small bowl, I wane see the real world......
S.S.
Super Advisor

Re: core files

Hi,

Today, i have found that the core files are generated in /home filesystem also.
These files are generated every day since 8th March.

-rw------- 1 dba 136197628 Mar 8 19:10 core.24320
-rw------- 1 dba 136197628 Mar 8 19:10 core.10115
-rw------- 1 dba 136197628 Mar 9 19:10 core.6579
-rw------- 1 dba 136197628 Mar 9 19:10 core.22142
-rw------- 1 dba 136197628 Mar 10 19:10 core.22891
-rw------- 1 dba 136197628 Mar 10 19:10 core.8357
-rw------- 1 dba 136197628 Mar 11 19:10 core.10714
-rw------- 1 dba 136197628 Mar 11 19:10 core.26272

Btw, We did the patching on March 7th and installed only the security patches on this server.

I have checked with DBA team, they said that one of the script actually starts at 19:10 and will create a log file in some other location in which that directory path is not existed.
May i know due to that the core dumps are happening?

Thank you.

Kapil Jha
Honored Contributor

Re: core files

All this is amazing, initially I did not see any core file (at least for me) now I have at.

Oracle says
>>>they said that one of the script actually starts at 19:10 and will create a log file in some other location in which that directory path is not existed.

what does it means exactly.

anyways these are real core files and not log files.
core.10115 ----created for process id 10115

what core.10115

would tell you why it created what signal caoused this core file.

BR,
Kapil+
I am in this small bowl, I wane see the real world......
Kapil Jha
Honored Contributor

Re: core files

We do not know what that script do,
you have to check that acript which runs at 19:10

BR,
Kapil+
I am in this small bowl, I wane see the real world......
S.S.
Super Advisor

Re: core files

Hi,

This was terminated with signal 11.

Checked by using gdb.
(gdb) core core.10115
warning: Unknown symbols for 'core.10115'; use the 'symbol-file' command.
Core was generated by `sh'.
Program terminated with signal 11, Segmentation fault.

#0 0xc00264a4 in ()
Cannot access memory at address 0xc00264a4

and the 'what' output:

# what core.10115
core.10115:
Version M-11/16/88f
$ B.11.11_LR Mar 11 2008 04:52:07 $
$ PATCH_11.11/PHCO_38279 Jul 3 2009 04:56:42 $
SMART_BIND
92453-07 dld dld dld.sl B.11.68 090608
Laurent Menase
Honored Contributor

Re: core files

Check your sh version is the last one.
PHCO_40121

Since you already have the last libc according to the what string, if you have the last sh, then it would make sens to ask to HP support.
Dennis Handly
Acclaimed Contributor

Re: core files

>(gdb) core core.10115
>warning: Unknown symbols for 'core.10115'; use the 'symbol-file' command.
Core was generated by `sh'.

If you use: gdb /usr/bin/sh core.10115
then you can use "bt" to get a stack trace.

>Kapil: what core.10115
would tell you why it created what signal caused this core file.

A better command is "file core.10115".