openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Brad Chou <bradc@hyvedesignsolutions.com>
To: Anton Kachalov <rnouse@google.com>
Cc: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: RE: Redfish Virtual Media return InternalError
Date: Mon, 12 Oct 2020 08:50:22 +0000	[thread overview]
Message-ID: <CY4PR04MB10338C493D4B90BA27ABAA11B9070@CY4PR04MB1033.namprd04.prod.outlook.com> (raw)
In-Reply-To: <CADVsX883MJzB9bP0xKNOqxv=uHs0OeH87BnFfejXHULW8coVNA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2412 bytes --]

Hi Anton,
I found some clue about this problem.
https://github.com/openbmc/bmcweb/blob/b0ad4de61ddd7872894b6f741156104f0a0c0ee6/redfish-core/lib/virtual_media.hpp#L1062
In virtual_media.hpp, the ObjectMapper failed because it cannot find the "/xyz/openbmc_project/VirtualMedia” object path.
So the problem is why there is no such object available ?
Do I need to start any service that depends by virtual media ?

Thanks
From: Anton Kachalov <rnouse@google.com>
Sent: Thursday, October 8, 2020 3:19 AM
To: Brad Chou <bradc@hyvedesignsolutions.com>
Cc: openbmc@lists.ozlabs.org
Subject: Re: Redfish Virtual Media return InternalError


[External E-mail]

CAUTION: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.

Hey, Brad.

Try to log into the bmc and check the bmcweb logs:

# systemctl status -n 100 bmcweb.status

If it doesn't show anything meaningful, get the "Main PID" and try to strace it (you need to include strace into the builded image).

On Tue, 6 Oct 2020 at 11:20, Brad Chou <bradc@hyvedesignsolutions.com<mailto:bradc@hyvedesignsolutions.com>> wrote:
Hi,
I enable the “DBMCWEB_ENABLE_VM_NBDPROXY” flag in bmcweb by bbappend it :
EXTRA_OECMAKE_append = " \
    -DBMCWEB_ENABLE_VM_NBDPROXY=ON \
"

Then try to use redfish virtual media.
But I got an error return when get into the collection :

$  curl -k -H "X-Auth-Token: $token" https://${bmc}/redfish/v1/Managers/bmc/VirtualMedia<https://$%7bbmc%7d/redfish/v1/Managers/bmc/VirtualMedia>
{
  "@odata.id<http://odata.id>": "/redfish/v1/Managers/bmc/VirtualMedia/",
  "@odata.type": "#VirtualMediaCollection.VirtualMediaCollection",
  "Name": "Virtual Media Services",
  "error": {
    "@Message.ExtendedInfo": [
      {
        "@odata.type": "#Message.v1_0_0.Message",
        "Message": "The request failed due to an internal service error.  The service is still operational.",
        "MessageArgs": [],
        "MessageId": "Base.1.4.0.InternalError",
        "Resolution": "Resubmit the request.  If the problem persists, consider resetting the service.",
        "Severity": "Critical"
      }
    ],
    "code": "Base.1.4.0.InternalError",
    "message": "The request failed due to an internal service error.  The service is still operational."
  }
}


Any idea ?



[-- Attachment #2: Type: text/html, Size: 8364 bytes --]

      reply	other threads:[~2020-10-12  8:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-06  9:19 Redfish Virtual Media return InternalError Brad Chou
2020-10-07 19:19 ` Anton Kachalov
2020-10-12  8:50   ` Brad Chou [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CY4PR04MB10338C493D4B90BA27ABAA11B9070@CY4PR04MB1033.namprd04.prod.outlook.com \
    --to=bradc@hyvedesignsolutions.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=rnouse@google.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).