Error on AIX 3

[TheDth]

HI

I have AIX 5.1 rs6000 workstation. but it had some error. this is my errpt result.

---------------------------------------------------------------------------
LABEL: RMCD_INFO_0_ST
IDENTIFIER: A6DF45AA

Date/Time: Mon Mar 5 15:07:00 THAIST 2007
Sequence Number: 17378
Machine Id: 005774BF4C00
Node Id: SBA660_DRC
Class: O
Type: INFO
Resource Name: RMCdaemon

Description
The daemon is started.

Probable Causes
The Resource Monitoring and Control daemon has been started.

User Causes
The startsrc -s ctrmc command has been executed or
the rmcctrl -s command has been executed.

Recommended Actions
Confirm that the daemon should be started.

Detail Data
DETECTING MODULE
RSCT,rmcd.c,1.48,209
ERROR ID
6eKora0Yywu3/8WK//2/S8....................
REFERENCE CODE

---------------------------------------------------------------------------
LABEL: SRC_TRYX
IDENTIFIER: 1BA7DF4E

Date/Time: Mon Mar 5 15:06:55 THAIST 2007
Sequence Number: 17377
Machine Id: 005774BF4C00
Node Id: SBA660_DRC
Class: S
Type: PERM
Resource Name: SRC

Description
SOFTWARE PROGRAM ERROR

Probable Causes
APPLICATION PROGRAM

Failure Causes
SOFTWARE PROGRAM

Recommended Actions
DETERMINE WHY SUBSYSTEM CANNOT RESTART

Detail Data
SYMPTOM CODE
65280
SOFTWARE ERROR CODE
-9020
ERROR CODE
0
DETECTING MODULE
'srchevn.c'@line:'343'
FAILING MODULE
sshd
---------------------------------------------------------------------------
LABEL: SRC_RSTRT
IDENTIFIER: BA431EB7

Date/Time: Mon Mar 5 15:06:54 THAIST 2007
Sequence Number: 17375
Machine Id: 005774BF4C00
Node Id: SBA660_DRC
Class: S
Type: PERM
Resource Name: SRC

Description
SOFTWARE PROGRAM ERROR

Probable Causes
APPLICATION PROGRAM

Failure Causes
SOFTWARE PROGRAM

Recommended Actions
VERIFY SUBSYSTEM RESTARTED AUTOMATICALLY

Detail Data
SYMPTOM CODE
65280
SOFTWARE ERROR CODE
-9035
ERROR CODE
0
DETECTING MODULE
'srchevn.c'@line:'217'
FAILING MODULE
sshd
---------------------------------------------------------------------------
LABEL: REBOOT_ID
IDENTIFIER: 2BFA76F6

Date/Time: Mon Mar 5 14:58:19 THAIST 2007
Sequence Number: 17372
Machine Id: 005774BF4C00
Node Id: SBA660_DRC
Class: S
Type: TEMP
Resource Name: SYSPROC

Description
SYSTEM SHUTDOWN BY USER

Probable Causes
SYSTEM SHUTDOWN

Detail Data
USER ID
0
0=SOFT IPL 1=HALT 2=TIME REBOOT
0
TIME TO REBOOT (FOR TIMED REBOOT ONLY)
0
---------------------------------------------------------------------------
LABEL: ERRLOG_ON
IDENTIFIER: 9DBCFDEE

Date/Time: Mon Mar 5 15:05:56 THAIST 2007
Sequence Number: 17371
Machine Id: 005774BF4C00
Node Id: SBA660_DRC
Class: O
Type: TEMP
Resource Name: errdemon

Description
ERROR LOGGING TURNED ON

Probable Causes
ERRDEMON STARTED AUTOMATICALLY

User Causes
/USR/LIB/ERRDEMON COMMAND

Recommended Actions
NONE

---------------------------------------------------------------------------
LABEL: ERRLOG_OFF
IDENTIFIER: 192AC071

Date/Time: Mon Mar 5 14:57:14 THAIST 2007
Sequence Number: 17370
Machine Id: 005774BF4C00
Node Id: SBA660_DRC
Class: O
Type: TEMP
Resource Name: errdemon

Description
ERROR LOGGING TURNED OFF

Probable Causes
ERRSTOP COMMAND

User Causes
ERRSTOP COMMAND

Recommended Actions
RUN ERRDEAD COMMAND
TURN ERROR LOGGING ON


Please help.
Thank you.

 

[khalidaaa]

IMHO This is due to the machine being rebooted!

do you experience this error all the time or just this time?

Regards,
Khalid

 

[DukeSSD]

Looks like a normal reboot but the sshd fails to start, have you just installed ssh?
Is this the problem you are concerned about?

 

[TheDth]

Error is show when I update new firmware not install program.

 

[DukeSSD]

Which of the six errors you posted are you worried about?

 

[TheDth]

I worry on Error 1(LABEL:RMCD_INFO_0_ST) and Error 2 (LABEL:SRC_TRYX).

 

[khalidaaa]

You don't have to worry about this RMCD_INFO_0_ST message as it is just informational message saying RMCdaemon has started!

The SRC_TRYX error is related to sshd daemon! for some reason it didn't start i guess!

Could you try this lssrc -s sshd?

It's the secure shell service! and it is not of a major impact (unless your application is using it for some reason!)

I think your server is healthy except for the above message (which is weired!) but the rest of the messages were there because of the reboot on that day! that's all!

Regards,
Khalid

 

[p5wizard]

Try to run the sshd in foreground and verbose debug mode, see if it runs and if it doesn't, you can probably find out why... Or post the output back.

/usr/sbin/sshd -d

The sshd run like this will not fork new instances and will consequently only run one connection at a time, but it is handy to do some debugging.


HTH,

p5wizard

 

[TheDth]

I try lssrc -s sshd?
It's show "The sshd? Subsystem is not on file".
and I try sshd -d
It's shoe "ksh: sshd: not found".

 

[p5wizard]

Seems to me you need to (re)install ssh.

And the -d option only works if you run sshd from its full path name as above (and below):

/usr/sbin/sshd -d


HTH,

p5wizard

 

[TheDth]

Thank you very much
i can get it