bmc_booted LED group was not asserted when BMC started up

Wed Jul 17 15:22:05 AEST 2019

Hi Vishwa,
Thanks for the hint.
This issue is related to BMC State Not Ready. I will look into this part.

# obmcutil status
CurrentBMCState     : xyz.openbmc_project.State.BMC.BMCState.NotReady

Thanks.
Stanley

From: vishwa [mailto:vishwa at linux.vnet.ibm.com]
Sent: Tuesday, July 16, 2019 5:13 PM
To: CS20 YSChu; openbmc at lists.ozlabs.org
Subject: Re: bmc_booted LED group was not asserted when BMC started up

Hmm.,,

Clearly, the systemd unit did not run / was not loaded successfully etc. Below line is telling me that some edits were done.

Warning: The unit file, source configuration file or drop-ins of obmc-led-group-start at bmc_booted.service<mailto:obmc-led-group-start at bmc_booted.service> changed on disk. Run 'systemctl daemon-reload' to reload units.

Have you tried to reload systemd ?

Jul 11 04:54:06 runbmc-nuvoton systemd[1]: Started Wait for /xyz/openbmc_project/led/groups/bmc_booted.

That is telling me that, it is waiting for the precondition to be met.. I thought you won't reach BMCReady state while having this stuck.  What is the "obmcutil state" saying ?.

Also, can you try "systemctl start obmc-led-group-start at bmc_booted.service<mailto:obmc-led-group-start at bmc_booted.service>" and see how it behaves.

If it's a one-off, I would suggest retry.. If this is persisting, open a girhub issue with needed information on  how to recreate.

!! Vishwa !!
On 7/16/19 9:20 AM, CS20 YSChu wrote:

Hi Vishwa,

-- The o/p of "systemctl status obmc-led-group-start at bmc_booted.service<mailto:obmc-led-group-start at bmc_booted.service>"

obmc-led-group-start at bmc_booted.service<mailto:obmc-led-group-start at bmc_booted.service> - Assert bmc_booted LED
   Loaded: loaded (/lib/systemd/system/obmc-led-group-start at .service<mailto:/lib/systemd/system/obmc-led-group-start at .service>; static; vendor preset: enabled)
  Drop-In: /lib/systemd/system/obmc-led-group-start at bmc_booted.service.d<mailto:/lib/systemd/system/obmc-led-group-start at bmc_booted.service.d>
           └─bmc_booted.conf
   Active: inactive (dead)
Warning: The unit file, source configuration file or drop-ins of obmc-led-group-start at bmc_booted.service<mailto:obmc-led-group-start at bmc_booted.service> changed on disk. Run 'systemctl daemon-reload' to reload units.

-- Properties of /xyz/openbmc_project/led/groups/bmc_booted
   array [
      dict entry(
         string "Asserted"
         variant             boolean false
      )
   ]

-- properties of xyz/openbmc_project/led/physical/heartbeat ?
   array [
      dict entry(
         string "State"
         variant             string "xyz.openbmc_project.Led.Physical.Action.Off"
      )
      dict entry(
         string "DutyOn"
         variant             byte 50
      )
      dict entry(
         string "Color"
         variant             string "xyz.openbmc_project.Led.Physical.Palette.Unknown"
      )
      dict entry(
         string "Period"
         variant             uint16 1000
      )
   ]

Thanks.
Stanley

From: vishwa [mailto:vishwa at linux.vnet.ibm.com]
Sent: Monday, July 15, 2019 5:48 PM
To: CS20 YSChu; openbmc at lists.ozlabs.org<mailto:openbmc at lists.ozlabs.org>
Subject: Re: bmc_booted LED group was not asserted when BMC started up

Hi Stanley,

Could you tell:

-- The o/p of "systemctl status obmc-led-group-start at bmc_booted.service<mailto:obmc-led-group-start at bmc_booted.service>"

-- Properties of /xyz/openbmc_project/led/groups/bmc_booted

-- properties of xyz/openbmc_project/led/physical/heartbeat ?

!! Vishwa !!
On 7/15/19 1:57 PM, CS20 YSChu wrote:
Hi,

In normal case, we will see bmc_booted LED group been asserted when bmc starts up.

Apr 08 04:56:30 evb-npcm750 systemd[1]: Starting Wait for /xyz/openbmc_project/led/groups/bmc_booted...
Apr 08 04:56:31 evb-npcm750 systemd[1]: Started Wait for /xyz/openbmc_project/led/groups/bmc_booted.
Apr 08 04:56:35 evb-npcm750 systemd[1]: Starting Assert bmc_booted LED...
Apr 08 04:56:35 evb-npcm750 systemd[1]: Started Assert bmc_booted LED.

Recently, I update to newer commit (don’t know what exact commit cause this), the wanted service was started but bmc-led-group-start service itself was not started. As a result, bmc heartbeat led was not blinked.
Can anyone please advise how to investigate such kind of issue?

Jul 11 04:54:03 runbmc-nuvoton systemd[1]: Starting Wait for /xyz/openbmc_project/led/groups/bmc_booted...
Jul 11 04:54:06 runbmc-nuvoton systemd[1]: Started Wait for /xyz/openbmc_project/led/groups/bmc_booted.

------
Below is unit file of obmc-led-group-start at bmc_booted.service<mailto:obmc-led-group-start at bmc_booted.service> in /lib/systemd/system/multi-user.target.wants
[Unit]
Description=Assert %i LED
Wants=mapper-wait at -xyz-openbmc_project-led-groups-%i.service<mailto:Wants=mapper-wait at -xyz-openbmc_project-led-groups-%25i.service>
After=mapper-wait at -xyz-openbmc_project-led-groups-%i.service<mailto:After=mapper-wait at -xyz-openbmc_project-led-groups-%25i.service>
Conflicts=obmc-led-group-stop@%i.service<mailto:Conflicts=obmc-led-group-stop@%25i.service>

[Service]
Type=oneshot
RemainAfterExit=yes
Restart=no
ExecStart=/bin/sh -c "busctl call `mapper get-service /xyz/openbmc_project/led/groups/%i` /xyz/openbmc_project/led/groups/%i org.freedesktop.DBus.Properties Set ssv xyz.openbmc_project.Led.Group Asserted b true"
SyslogIdentifier=obmc-led-group-start

Thanks.
Stanley

________________________________
The privileged confidential information contained in this email is intended for use only by the addressees as indicated by the original sender of this email. If you are not the addressee indicated in this email or are not responsible for delivery of the email to such a person, please kindly reply to the sender indicating this fact and delete all copies of it from your computer and network server immediately. Your cooperation is highly appreciated. It is advised that any unauthorized use of confidential information of Nuvoton is strictly prohibited; and any information in this email irrelevant to the official business of Nuvoton shall be deemed as neither given nor endorsed by Nuvoton.
________________________________
The privileged confidential information contained in this email is intended for use only by the addressees as indicated by the original sender of this email. If you are not the addressee indicated in this email or are not responsible for delivery of the email to such a person, please kindly reply to the sender indicating this fact and delete all copies of it from your computer and network server immediately. Your cooperation is highly appreciated. It is advised that any unauthorized use of confidential information of Nuvoton is strictly prohibited; and any information in this email irrelevant to the official business of Nuvoton shall be deemed as neither given nor endorsed by Nuvoton.
________________________________
The privileged confidential information contained in this email is intended for use only by the addressees as indicated by the original sender of this email. If you are not the addressee indicated in this email or are not responsible for delivery of the email to such a person, please kindly reply to the sender indicating this fact and delete all copies of it from your computer and network server immediately. Your cooperation is highly appreciated. It is advised that any unauthorized use of confidential information of Nuvoton is strictly prohibited; and any information in this email irrelevant to the official business of Nuvoton shall be deemed as neither given nor endorsed by Nuvoton.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20190717/93d71ad6/attachment-0001.htm>