Re: rc.powerfail / machstat issues

• Previous message: Lamar Saxon: "Re: rc.powerfail / machstat issues"
• Maybe in reply to: F. Even: "rc.powerfail / machstat issues"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Date:         Wed, 18 May 2005 08:53:07 -0700
To: aix-l@Princeton.EDU

The resource you'd log a repair action against is sysplanar0 for power
problems on a 6C4. That will stop the crontab entries and you should
then be able to reset the alert indicator... unless of course there
really IS a power problem, in which case it should pop back up... you
have checked the lights on the power supplies, right? ;)

--rm

-----Original Message-----
From: IBM AIX Discussion List [mailto:aix-l@Princeton.EDU]On Behalf Of
Lamar Saxon
Sent: Wednesday, May 18, 2005 8:32 AM
To: aix-l@Princeton.EDU
Subject: Re: rc.powerfail / machstat issues

Actually, you can still log a repair action and look @ previous
diagnostics results in diags under Tasks Selections.

>From a p690 AIX 5.2 diags screen:

--- SNIP ---

 Display Previous Diagnostic Results
 Display Resource Attributes
 Display Service Hints
 Display Software Product Data
 Display or Change Bootlist
 Download Microcode
 Format Media
 Gather System Information
 Generic Microcode Download
 Hot Plug Task
 Identify and Attention Indicators
 Local Area Network Analyzer
 Log Repair Action

--- SNIP ---

Look @ the previous diagnostics results. You can log a repair action
against the resource, not an actual error log entry.

Lamar

-----Original Message-----
From: IBM AIX Discussion List [mailto:aix-l@Princeton.EDU] On Behalf Of
F. Even
Sent: Wednesday, May 18, 2005 3:22 AM
To: aix-l@Princeton.EDU
Subject: Re: rc.powerfail / machstat issues

No errors currently in errpt, and diags run clean...nothing to log a
repair action against.

Anyone?

Thanks!

Lamar Saxon wrote:
> Can you go through diags and log a repair action against the hardware
> error ?
>
> Lamar
>
> -----Original Message-----
> From: IBM AIX Discussion List [mailto:aix-l@Princeton.EDU] On Behalf
Of
> F. Even
> Sent: Monday, May 16, 2005 6:02 PM
> To: aix-l@Princeton.EDU
> Subject: rc.powerfail / machstat issues
>
> OK, I've got a box that had an rc.powerfail warning added to root's
> crontab due to the secondary power supply losing power (due to
building
> maintenance knocking out one of it's power feeds). The server is a
> pSeries 630 Model 6C4. Now...I've cleared the cron entries, etc.
What
> I
> would like to know though is how do I clear whatever registers that
are
> indicating there still is a power problem? If I execute "rc.powerfail
> -h," it shoots back this:
>
> [quote]
> rc.powerfail -h
>
>
> Broadcast message from root@ (pts/96) at 13:40:35 ...
>
> rc.powerfail: init has received a SIGPWR signal.
> The system is now operating with a non-critical power problem.
> Execute rc.powerfail -h as the root user for more information.
> ^G^G^G^G
>
>
>
>
> Broadcast message from root@ (pts/96) at 13:40:57 ...
>
> rc.powerfail:
> This command is used to handle power problems with the system.
> There are several different states that the system can be in when
> the signal SIGPWR is received by init. The action taken will be
> determined by the value of the power status. The following table
> shows the values of the power status and action taken.
> Power
> Status Indication
> ------
----------------------------------------------------------------
> 0 System is running normally, there is no action taken.
> 1 A non-critical cooling problem exists.
> 2 A non-critical power problem exists.
> 3 System facing a critical condition. Will start shutdown in 10
> minutes.
> 4 System facing a severe condition. Will be halted in the next
20
> seconds.
> 255 ERROR with the machstat command, system shutdown starts
> immediately. ^G^G^G^G
> [/quote]
>
>
> ...and re-adds the wall entry to root's crontab. NOW...if I check the
> documented flags to machstat:
>
>
>>machstat -p
>
>
>>echo $?
>
> 0
>
> Everything seems like it should be fine (unless someone else can tell
me
> a
> way to check the power supply status on this platform..."uesensor -l"
is
> not supported).
>
> Now...looking through the rc.powerfail and rc.powerfail_chrp, I see
> references to an undocumented use of machstat, "machstat -f," which
> seems
> to be pulling a stored value of some sort:
>
>
>>/usr/sbin/machstat -f
>
> 2 0
>
> ...now the question is...how do I get that to read as it does on a
> "well"
> system:
>
>
>>machstat -f
>
> 0 0
>
> ....how do I reset that value? The box is remote, and it cannot be
> rebooted just for this, but the local hardware support has checked it
> out
> and can't see any issues with the power supply. It lost power over
the
> weekend, that seems to have been what caused this...but it is good
> now...how do I get the system to recognize that?
>
> P.S. There are currently no errors in errpt for this issue...I think
> some
> entries might have been cleared out by co-workers before I looked at
> it...so there are no entries relating to this power issue currently in
> errpt.
>
> Thanks for any input anyone might have,
> Frank
>
>
> Privileged and Confidential. This e-mail, and any attachments there
to, is intended only for use by the addressee(s) named herein and may
contain privileged or confidential information. If you have received
this e-mail in error, please notify me immediately by a return e-mail
and delete this e-mail. You are hereby notified that any dissemination,
distribution or copying of this e-mail and/or any attachments thereto,
is strictly prohibited.

• Previous message: Lamar Saxon: "Re: rc.powerfail / machstat issues"
• Maybe in reply to: F. Even: "rc.powerfail / machstat issues"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]