core.dmp files hogging space on C:\
The C:/ on my CLM server has been filling up lately. I realized a handful of files within the WebSphere directory were responsible for about 63 GB of data.
The files are labeled "core.********.******.****.****.dmp" The ****** portion seems to be a date/time stamp for when the file was created. The files are stored in the following directory... C:\IBM\Websphere\AppServer\profiles\AppSrv01. Can anyone tell me about these files? They average about 12-14 GB in size. Thanks! |
3 answers
these are system dmp files which are triggered on an event of running Native or Heap out of memory , depending on what you have set as -Xdump JVM argument
These files in huge in size , depending on how much heap is configured and how much was used when the process Ran out of memory, I would expect your server not to work if that happens. Otherwise check Xdump argument to see if has argument to write system dump when ever you take a JAVA core. Comments These are the Generic JVM arugments I have set in Websphere Admin Console....
If you're using WAS 8.5.5, it by default creates a system dump when the first OOM occurs.
|
you can delete them, its safe to do it
|
Depending on their age (as you say, the file names contain timestamps), if they're very old then you can probably just delete them as too much time has likely passed for them to be of any value. If however they're recent, it's an indication that your WebSphere server is running into problems and is crashing so you would do well to move them somewhere safe and begin an investigation into the issue that's causing the crashes.
They are often accompanied by javacores, heapdumps, snapdumps etc. All these files can be used to diagnose problems within the WebSphere server so if you do move them you should keep them together. Comments Some of them are older (from 2015). Some of them are recent, including today, 2 days ago, and 5 days ago. There are also javacores and heapdump files that have similar timestamps so I will try to keep those files together (the recent ones anyway).
I think the -Xdump option can do that but it's probably not a good idea to prevent these files from being created; without them you won't be able to determine the cause of the crashes and if you ever decide to open a PMR the WebSphere support team will need them to begin diagnosing the issue. As mentioned in another answer; the likelihood is your server is running out of RAM so you'd be better served in determining why the dumps are being taken.
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.