• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1549
  • Last Modified:

Frequent core dump file generated in IBM-AIX

From one of my application i am getting Frequent core dump file generated in IBM-AIX, is there any kernel / tcp parameter i have to set to get rid of this, if so how?
0
umesh4exp
Asked:
umesh4exp
  • 3
  • 3
  • 2
5 Solutions
 
woolmilkporcCommented:
What do you try to achieve?

There is surely no AIX parameter which can inhibit your application from aborting/core dumping.

You can have AIX move all coredumps to a central location, this is done by

syscorepath -p [directoryname]

There are two more parameters, '-c' for unset (dump to work dir of process) and '-g' for displaying the current setting.

Note that all core dumps will go to the directory set above, in the format 'core.pid.ddhhmmss'. There is no selection based on applications/processes etc.

Setting the core path to /dev/null is not possible (and I wouldn't recommend that, if it was).
You should cleanup the core path directory regularly, e.g. with find based on mtime of 10 days or more:

find $(syscorepath -g) -mtime +10 -exec rm {} \;

I hope I understood your Q right, if not, please come back and explain!

Cheers

wmp

0
 
umesh4expAuthor Commented:
In application document , they specified for frequent core dump generation, inform them(company) for other UNIX systems. For IBM AIX platform limit the core size to a maximum of 10KB.  I don't know what to do. Any Suggestions?
0
 
woolmilkporcCommented:
OK,
that's a setting for the individual user under whose ID the application is running.
Simplest way is: Enter 'smitty chuser', select the appropriate user, on the following screen scroll down to 'core file size ...' and change the hard and soft limits to the value you desire.
Alternatively you can edit /etc/security/limits and change the user's entry there. Remember that you have to logoff and logon for this to take effect, and to recycle the concerned background processes.

Wmp
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
woolmilkporcCommented:
P.S. The size limit has to be entered in units of 512-byte blocks, so for 10K use '20'
Please keep in mind that such a small core dump will be uselessfor debugging purposes in almost any case!
0
 
gheistCommented:
Usually crashing programs are built for 256MB memory model and run with legacy malloc. They also crash when process size reaches 256MB. This is definetly memory leak in program, has to be reported to vendor.
MALLOC_TYPE=3.1 ./program

You can also use dbx to extract crash conditions from core file - do you want crash course in process debuging?
0
 
umesh4expAuthor Commented:
Yes gheist i need some crash course in process debuging,
in IBM server dbx is not installed any tools similar to dbx.
0
 
gheistCommented:
dbx debugger is available in bos.adt.debug
check oslevel -r
Download patch set you have: http://support.bull.com/ols/product/system/aix
Do full mksysb backup and full backup of other volume groups and full backup of databases you have.
insert AIX install media
install bos.adt.debug
apply patchset
reboot if indicated
Do another full backup.

Backups easier with NIM if you have one server for that.

After your system software is in stable state:
Chap. 7 from http://www.redbooks.ibm.com/abstracts/sg245674.html?Open

0
 
gheistCommented:
B means incomplete answer - can you describe what you did better than suggested?
0

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 3
  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now