On 22/03/23 03:45, Stephen Borrill wrote:
On Sat, 18 Mar 2023, Lloyd Parkes wrote:
On 18/03/23 05:14, Stephen Borrill wrote:
On an HP Microserver Gen10 Plus, I found that soon after booting, I
get the following alert:
...
Current CritMax WarnMax WarnMin CritMin
On Sat, 18 Mar 2023, Lloyd Parkes wrote:
On 18/03/23 05:14, Stephen Borrill wrote:
On an HP Microserver Gen10 Plus, I found that soon after booting, I get the
following alert:
...
Current CritMax WarnMax
WarnMin CritMin Unit
[ipmi0]
11-LOM-CORE: 59.253
net...@precedence.co.uk (Stephen Borrill) writes:
> Current CritMax WarnMax WarnMin CritMin Unit
>[ipmi0]
>11-LOM-CORE:59.2530.000 110.471degC
>Seen on 9.3_STABLE, but also in 10 BETA.
>I suppose one simple fix would be to ensure
On 18/03/23 05:14, Stephen Borrill wrote:
On an HP Microserver Gen10 Plus, I found that soon after booting, I get
the following alert:
...
Current CritMax WarnMax WarnMin CritMin Unit
[ipmi0]
11-LOM-CORE: 59.253 0.000 110.471 degC
Stephen Borrill writes:
> On an HP Microserver Gen10 Plus, I found that soon after booting, I get
> the following alert:
>
> ipmi0: critical over limit on '11-LOM-CORE'
>
> If powerd is running (the default), it shuts the machine down (so
> basically as soon as it hits multi-user).
>
> envstat
On an HP Microserver Gen10 Plus, I found that soon after booting, I get
the following alert:
ipmi0: critical over limit on '11-LOM-CORE'
If powerd is running (the default), it shuts the machine down (so
basically as soon as it hits multi-user).
envstat shows that CritMax is zero: