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
LEARN ABOUT FREEBSD
crashinfo
CRASHINFO(8) BSD System Manager's Manual CRASHINFO(8)
NAME
crashinfo -- analyze a core dump of the operating system
SYNOPSIS
crashinfo [-d crashdir] [-n dumpnr] [-k kernel] [core]
DESCRIPTION
The crashinfo utility analyzes a core dump saved by savecore(8). It generates a text file containing the analysis in the same directory as
the core dump. For a given core dump file named vmcore.XX the generated text file will be named core.txt.XX.
By default, crashinfo analyzes the most recent core dump in the core dump directory. A specific core dump may be specified via either the
core or dumpnr arguments. Once crashinfo has located a core dump, it analyzes the core dump to determine the exact version of the kernel
that generated the core. It then looks for a matching kernel file under each of the subdirectories in /boot. The location of the kernel
file can also be explicitly provided via the kernel argument.
Once crashinfo has located a core dump and kernel, it uses several utilities to analyze the core including dmesg(8), fstat(1), iostat(8),
ipcs(1), kgdb(1), netstat(1), nfsstat(1), ps(1), pstat(8), and vmstat(8).
The options are as follows:
-d crashdir
Specify an alternate core dump directory. The default crash dump directory is /var/crash.
-n dumpnr
Use the core dump saved in vmcore.dumpnr instead of the latest core in the core dump directory.
-k kernel
Specify an explicit kernel file.
SEE ALSO
textdump(4), savecore(8)
HISTORY
The crashinfo utility appeared in FreeBSD 6.4.
BSD
June 28, 2008 BSD