A strange message from errpt.
Johnny Chen
IDENTIFIER: C60BB505
Date/Time: Sun Apr 2 18:35:51
Sequence Number: 613
Machine Id: 000113814C00
Node Id: hsh70
Class: S
Type: PERM
Resource Name: SYSPROC
Description
SOFTWARE PROGRAM ABNORMALLY TERMINATED
Probable Causes
SOFTWARE PROGRAM
User Causes
USER GENERATED SIGNAL
Recommended Actions
CORRECT THEN RETRY
Failure Causes
SOFTWARE PROGRAM
Recommended Actions
RERUN THE APPLICATION PROGRAM
IF PROBLEM PERSISTS THEN DO THE FOLLOWING
CONTACT APPROPRIATE SERVICE REPRESENTATIVE
Detail Data
SIGNAL NUMBER
0
USER'S PROCESS ID:
0
FILE SYSTEM SERIAL NUMBER
-1
INODE NUMBER
-1
PROGRAM NAME
ADDITIONAL INFORMATION
Unable to generate symptom string.
//////////////////////////////////////////
who can tell me is there anything wrong with my system?
Friedhelm Neyer
... try to locate the core_cump (it is a file named core).
Then execute the following in the directory, where the core is located:
lquerypv -h core 6b0 64
.. and you will see, which program causes the coredump
Friedhelm
William Peckham
"Nicholas Dronen" <ndr...@io.frii.com> wrote in message
news:3ea2bc9d$0$53001$7586...@news.frii.net...
> Friedhelm Neyer <Friedhe...@t-online.de> wrote:
> FN> Then execute the following in the directory, where the core is
located:
>
> FN> lquerypv -h core 6b0 64
>
> FN> .. and you will see, which program causes the coredump
>
> The reason for the original post is that all of the detail
> data -- where one would ususally find information to aid
> in locating the core file -- is meaningless. There's no
> program name, the signal number is 0, the inode and file
> system serial numbers are invalid.
>
> With that in mind, it misses the point to suggest that he
> run lquerypv against the core file.
>
> That being said, I wouldn't worry much about the error. A
> core dump is no big deal. The system shouldn't log an error
> that's incomplete like this one. That's about all that's
> wrong, AFAICT. If it happens often, have someone (like
> an administrator or tech support person) help you figure
> out what's causing the error. Perhaps it's just spurious.
>
> Regards,
>
> Nicholas
>
> --
> "Why shouldn't I top-post?" http://www.aglami.com/tpfaq.html
> "Meanings are another story." http://www.ifas.org/wa/glossolalia.html
Nicholas:
Actually I believe the earlier answer appropriate, just incomplete.
I do agree that the error is probably meaningless.
Why else have 'respawn' as an option in inittab? ;-)
Still, the man deserves a more meaningful answer than that.
----------------
Johnny:
To find the core dump try using the find command, something like
find / -fstype jfs -name core -print
or
find / -fstype jfs -name core -exec ls -l {} \;
and look for the file with the same date/time as the error (or very close).
Then against it run the lquerypv command mentioned earlier to find what
program failed.
From there, you will have to make a judgement call: is this or is this not
something worth pursuing?
If it is a program that runs from cron or inittab and has never failed
again, it may have been a meaningless one-off error that will cause no
ongoing problems.
Luck!
William Peckham
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.471 / Virus Database: 269 - Release Date: 2003-04-10
Johnny Chen
Thank all you two very much!
With your help I can tell my boss that there is nothing wrong with my Server.
It help me much !
Thanks!