04-24-2009
Its the same application crashing again and again.
try to set the ulimit for stack and data to: unlimited. May be this will help.
If not, then generate the snapcore from the directory where system dumped the core, which is /usr/lpp/tsd/tsdserv/core in your case.
This will produce .pax.Z file in /tmp/snapcore directory.
Send this file to IBM for analysis.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
hi, i have an entry in errpt on aix... any help?
---------------------------------------------------------------------------
LABEL: AMQFFST3
IDENTIFIER: 8FED25B9
Date/Time: Fri Nov 15 07:20:05
Sequence Number: 2715
Machine Id: 000694DF4C00
Node Id: ... (1 Reply)
Discussion started by: yls177
1 Replies
2. SuSE
Errpt- Generates an error report from entries in the log.
Errpt is a AIX command.
we want equivallent suse linux command.
If there is no exact replace ment pls give us alternative way.
we want to log each n evry system error and generate an error report (2 Replies)
Discussion started by: vrguha
2 Replies
3. AIX
Hi All,
Can anyone explain me the meanning of the following errors:
LABEL: SC_DISK_ERR2
IDENTIFIER: B6267342
Description
DISK OPERATION ERROR
Probable Causes
DASD DEVICE
Failure Causes
DISK DRIVE
DISK DRIVE ELECTRONICS
Recommended Actions
PERFORM PROBLEM DETERMINATION... (1 Reply)
Discussion started by: gianlu
1 Replies
4. AIX
Hi,
redbook documentation is telling that IY17981 fix is required for aix 4.3.3 to aix 5L migration. But there is no mention about that fix in any ML installation packages.
- My system is ML11 :
oslevel –r
4330-11
- But xlC.rte is on wrong version :
lslpp -L xlC.rte
xlC.rte ... (3 Replies)
Discussion started by: astjen
3 Replies
5. Emergency UNIX and Linux Support
The below is my code
in general according to AIX books
To display a detailed report of all errors logged in the past 24 hours, enter:
errpt -a -s mmddhhmmyy
where the mmddhhmmyy string equals the current month, day, hour, minute, and year, minus 24 hours.
I have tried the... (2 Replies)
Discussion started by: Sounddappan
2 Replies
6. Shell Programming and Scripting
Hi All,
Output of the following command is ok so far ...
netstat -an | grep 192.168.156.1.16507 | awk '{print $5}' | awk '{FS="."} {print $5}'
1297
1350
1394
1211
1255
1259
4606
2184
2009
4890
1398
3941
1671
1780 (1 Reply)
Discussion started by: sraj142
1 Replies
7. AIX
Hi Guys,
I need some help analyzing the attached metrics. System context is 2 LPAR's in a P795 running WebSphere App Server across 4 nodes (2 on each LPAR).
Over the weekend both LPAR's lost power and upon re-start the application server response times have degraded by 25-30% for no obvious... (1 Reply)
Discussion started by: mgburns
1 Replies
8. AIX
1)We have 2 node cluster RAC on AIX:
->test1
->test3
2) After rebooting server both the node sequentailly, we are getting below error from errpt command :
# errpt |more
IDENTIFIER TIMESTAMP T C RESOURCE_NAME DESCRIPTION
FE2DEE00 0901223914 P S SYSXAIXIF DUPLICATE IP ADDRESS... (2 Replies)
Discussion started by: manjusharma128
2 Replies
9. AIX
Hi,
just a short question:
Is a error label always equal to a error identifier?
So it does not matter if i search for an specific identifier (errpt -j) or a specific label (errpt -J)?
Regards
Ron (5 Replies)
Discussion started by: -=XrAy=-
5 Replies
10. UNIX for Beginners Questions & Answers
Medel : 9117-MMC
OS: AIX 6.1
Patch level : 6100-07-04-1216
Hacmp version : HACMP v 6.1.0.8
Oracle : 11.2.0.3 RAC
Node : 2 node
Dear, my one node server has been restarted early this morning, So, i tried to start HA and Oracle database.
after that, the follow error appears at the node... (1 Reply)
Discussion started by: tomato00
1 Replies
gcore(1) BSD General Commands Manual gcore(1)
NAME
gcore -- get core images of running processes
SYNOPSIS
gcore [-s] [-v] [-b size] [-o path | -c pathformat] pid
DESCRIPTION
The gcore program creates a core file image of the process specified by pid. The resulting core file can be used with a debugger, e.g.
lldb(1), to examine the state of the process.
The following options are available:
-s Suspend the process while the core file is captured.
-v Report progress on the dump as it proceeds.
-b size Limit the size of the core file to size MiBytes.
The following options control the name of the core file:
-o path
Write the core file to path.
-c pathformat
Write the core file to pathformat. The pathformat string is treated as a pathname that may contain various special characters which
cause the interpolation of strings representing specific attributes of the process into the name.
Each special character is introduced by the % character. The format characters and their meanings are:
N The name of the program being dumped, as reported by ps(1).
U The uid of the process being dumped, converted to a string.
P The pid of the process being dumped, converted to a string.
T The time when the core file was taken, converted to ISO 8601 format.
% Output a percent character.
The default file name used by gcore is %N-%P-%T. By default, the core file will be written to a directory whose name is determined from the
kern.corefile MIB. This can be printed or modified using sysctl(8).
The directory where the core file is to be written must be accessible to the owner of the target process.
gcore will not overwrite an existing file, nor will it create missing directories in the path.
EXIT_STATUS
The gcore utility exits 0 on success, and >0 if an error occurs.
FILES
/cores/%N-%P-%T default pathname for the corefile.
BUGS
With the -b flag, gcore writes out as much data as it can up to the specified limit, even if that results in an incomplete core image. Such
a partial core dump may confuse subsequent programs that attempt to parse the contents of such files.
SEE ALSO
lldb(1), core(5), Mach-O(5), sysctl(8), sudo(8).
Darwin May 31, 2019 Darwin