webui not working for me

webui not working for me

[Vijay Khemka]

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

Hi,
I am trying to use webui but not getting anything working. I might be missing some steps.
I did following.

  1.  npm install in repo directory.
  2.  Recompiled bmcweb with BMCWEB_INSECURE_DISABLE_XSS_PREVENTION on and transferred bmcweb to target.
  3.  Run chrome browser with http://bmc-ip
  4.  I see blank page. Then tried with https and accepted certificates.
  5.  But still I see page with “refused to connect”

Please help me what else I need to do. I got 2 warning while installing NPM.


npm WARN bootstrap@4.4.1 requires a peer of jquery@1.9.1 - 3 but none is installed. You must install peer dependencies yourself.

npm WARN bootstrap@4.4.1 requires a peer of popper.js@^1.16.0 but none is installed. You must install peer dependencies yourself.



audited 12116 packages in 4.87s



6 packages are looking for funding

  run `npm fund` for details



found 2 moderate severity vulnerabilities

  run `npm audit fix` to fix them, or `npm audit` for details

I tried fixing this by using “audit fix”  but no success.

Regards
-Vijay

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

Re: webui not working for me

[Gunnar Mills]

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


On 1/3/2020 7:38 PM, Vijay Khemka wrote:
>
>
> I am trying to use webui but not getting anything working. I might be 
> missing some steps.
>
> I did following.
>
>  1. npm install in repo directory.
>  2. Recompiled bmcweb with BMCWEB_INSECURE_DISABLE_XSS_PREVENTION on
>     and transferred bmcweb to target.
>  3. Run chrome browser with http://bmc-ip
>  4. I see blank page. Then tried with https and accepted certificates.
>  5. But still I see page with “refused to connect”
>
Hi Vijay,

Are you trying to run the webui locally (e.g. npm run-script server and 
then browse to http://localhost:8080 )?

If so, something more like:
npm install
npm run-script server
Recompile bmcweb with BMCWEB_INSECURE_DISABLE_XSS_PREVENTION and 
BMCWEB_INSECURE_DISABLE_CSRF_PREVENTION and transfer bmcweb to target.
Go to https://bmc-ip and accept the certificate
Go to http://localhost:8080 (could be running at a different port, check 
npm run-script server output) and point at bmc-ip

If you are trying to build the webui for the BMC (npm run-script build) 
and scp the files over, do you need to include the webui package group?

https://github.com/openbmc/openbmc/commit/fef8abbc78154abbd86ab9f0704e65ccb422f4de

The webui recipe creates the webui directory structure on the BMC.


> Please help me what else I need to do. I got 2 warning while 
> installing NPM.
>
The warnings should not matter.

- Gunnar

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

Re: webui not working for me

[Vijay Khemka]

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

Thanks Gunnar,
I didn’t understand by running webui locally. I am not running on BMC. I am just running in my mac laptop and trying to connect to BMC via browser.

Regards
-Vijay

From: Gunnar Mills <gmills@linux.vnet.ibm.com>
Date: Sunday, January 5, 2020 at 9:39 PM
To: Vijay Khemka <vijaykhemka@fb.com>, "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: Re: webui not working for me



On 1/3/2020 7:38 PM, Vijay Khemka wrote:

I am trying to use webui but not getting anything working. I might be missing some steps.
I did following.

  1.  npm install in repo directory.
  2.  Recompiled bmcweb with BMCWEB_INSECURE_DISABLE_XSS_PREVENTION on and transferred bmcweb to target.
  3.  Run chrome browser with http://bmc-ip<https://urldefense.proofpoint.com/v2/url?u=http-3A__bmc-2Dip&d=DwMDaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=v9MU0Ki9pWnTXCWwjHPVgpnCR80vXkkcrIaqU7USl5g&m=kJtGvuus9oDRupym2EBb90B5bKvSi-pPMLdfIXHUGAM&s=HQJMeAs5VppEftgdpNH7nd7V3Zx4xpf4DEyqto7U7_Q&e=>
  4.  I see blank page. Then tried with https and accepted certificates.
  5.  But still I see page with “refused to connect”


Hi Vijay,

Are you trying to run the webui locally (e.g. npm run-script server and then browse to http://localhost:8080<https://urldefense.proofpoint.com/v2/url?u=http-3A__localhost-3A8080&d=DwMDaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=v9MU0Ki9pWnTXCWwjHPVgpnCR80vXkkcrIaqU7USl5g&m=kJtGvuus9oDRupym2EBb90B5bKvSi-pPMLdfIXHUGAM&s=r_P53gY50VmvMsyQPhxD35FdzONyzQNBH3GUYTerV4M&e=> )?

If so, something more like:
npm install
npm run-script server
Recompile bmcweb with BMCWEB_INSECURE_DISABLE_XSS_PREVENTION and BMCWEB_INSECURE_DISABLE_CSRF_PREVENTION and transfer bmcweb to target.
Go to https://bmc-ip<https://urldefense.proofpoint.com/v2/url?u=https-3A__bmc-2Dip&d=DwMDaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=v9MU0Ki9pWnTXCWwjHPVgpnCR80vXkkcrIaqU7USl5g&m=kJtGvuus9oDRupym2EBb90B5bKvSi-pPMLdfIXHUGAM&s=gdm3UjRQnu_XRVgmp5SVt9W82Tl-uoCarovDoHDdD1Y&e=> and accept the certificate
Go to http://localhost:8080<https://urldefense.proofpoint.com/v2/url?u=http-3A__localhost-3A8080&d=DwMDaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=v9MU0Ki9pWnTXCWwjHPVgpnCR80vXkkcrIaqU7USl5g&m=kJtGvuus9oDRupym2EBb90B5bKvSi-pPMLdfIXHUGAM&s=r_P53gY50VmvMsyQPhxD35FdzONyzQNBH3GUYTerV4M&e=> (could be running at a different port, check npm run-script server output) and point at bmc-ip

If you are trying to build the webui for the BMC (npm run-script build) and scp the files over, do you need to include the webui package group?

https://github.com/openbmc/openbmc/commit/fef8abbc78154abbd86ab9f0704e65ccb422f4de

The webui recipe creates the webui directory structure on the BMC.


Please help me what else I need to do. I got 2 warning while installing NPM.

The warnings should not matter.

- Gunnar


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

Re: webui not working for me

[Vijay Khemka]

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

Hi Gunnar,
Now I am following below steps. I am running all these from my mac laptop. Nothing on BMC, just copied bmcweb on BMC.

  1.  npm install in repo directory.
  2.  npm run-script server
  3.  Recompiled bmcweb with BMCWEB_INSECURE_DISABLE_XSS_PREVENTION and BMCWEB_INSECURE_DISABLE_CSRF_PREVENTION and transfered bmcweb to target.
  4.  Go to https://bmc-ip<https://urldefense.proofpoint.com/v2/url?u=https-3A__bmc-2Dip&d=DwMDaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=v9MU0Ki9pWnTXCWwjHPVgpnCR80vXkkcrIaqU7USl5g&m=kJtGvuus9oDRupym2EBb90B5bKvSi-pPMLdfIXHUGAM&s=gdm3UjRQnu_XRVgmp5SVt9W82Tl-uoCarovDoHDdD1Y&e=>, no certificates asked, says certificate expired on Dec 29 1979.
Go to http://localhost:8080<https://urldefense.proofpoint.com/v2/url?u=http-3A__localhost-3A8080&d=DwMDaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=v9MU0Ki9pWnTXCWwjHPVgpnCR80vXkkcrIaqU7USl5g&m=kJtGvuus9oDRupym2EBb90B5bKvSi-pPMLdfIXHUGAM&s=r_P53gY50VmvMsyQPhxD35FdzONyzQNBH3GUYTerV4M&e=>, Don’t see any port as output for “npm run-script server”.


vijaykhemka-mbp:phosphor-webui vijaykhemka$ npm run-script server

> phosphor-webui@2.8.0-dev server /Users/vijaykhemka/proj/lf/gh/new-gh/gh-repo/phosphor-webui
> webpack-dev-server --history-api-fallback --inline --progress --devtool source-map --mode development

10% building 1/1 modules 0 activeℹ ｢wds｣: Project is running at http://localhost:18898/
ℹ ｢wds｣: webpack output is served from /
ℹ ｢wds｣: Content not from webpack is served from ./src/public
ℹ ｢wds｣: 404s will fallback to /index.html
10% building 1/3 modules 2 active ...babel-loader/lib/index.js??ref--4!/Users/vijaykhemka/proj/lf/gh/new-gh/gh-repo/phosphor-webui/node_modules/webpack-dev-server/client/index.js?http://localhost:18898Browserslist: caniuse-lite is outdated. Please run next command `npm update`
67% building 545/571 modules 26 active /Users/vijaykhemka/proj/lf/gh/new-gh/gh-repo/phosphor-webui/node_modules/core-js/modules/es.reflect.is-extensible.js[BABEL] Note: The code generator has deoptimised the styling of /Users/vijaykhemka/proj/lf/gh/new-gh/gh-repo/phosphor-webui/node_modules/angular/angular.js as it exceeds the max of 500KB.
66% building 557/590 modules 33 active /Users/vijaykhemka/proj/lf/gh/new-gh/gh-repo/phosphor-webui/node_modules/core-js/modules/es.object.to-string.js[BABEL] Note: The code generator has deoptimised the styling of /Users/vijaykhemka/proj/lf/gh/new-gh/gh-repo/phosphor-webui/node_modules/text-encoding/lib/encoding-indexes.js as it exceeds the max of 500KB.
ℹ ｢wdm｣:    761 modules
ℹ ｢wdm｣: Compiled successfully.

Regards
-Vijay



From: Gunnar Mills <gmills@linux.vnet.ibm.com>
Date: Sunday, January 5, 2020 at 9:39 PM
To: Vijay Khemka <vijaykhemka@fb.com>, "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: Re: webui not working for me



On 1/3/2020 7:38 PM, Vijay Khemka wrote:

I am trying to use webui but not getting anything working. I might be missing some steps.
I did following.

  1.  npm install in repo directory.
  2.  Recompiled bmcweb with BMCWEB_INSECURE_DISABLE_XSS_PREVENTION on and transferred bmcweb to target.
  3.  Run chrome browser with http://bmc-ip<https://urldefense.proofpoint.com/v2/url?u=http-3A__bmc-2Dip&d=DwMDaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=v9MU0Ki9pWnTXCWwjHPVgpnCR80vXkkcrIaqU7USl5g&m=kJtGvuus9oDRupym2EBb90B5bKvSi-pPMLdfIXHUGAM&s=HQJMeAs5VppEftgdpNH7nd7V3Zx4xpf4DEyqto7U7_Q&e=>
  4.  I see blank page. Then tried with https and accepted certificates.
  5.  But still I see page with “refused to connect”


Hi Vijay,

Are you trying to run the webui locally (e.g. npm run-script server and then browse to http://localhost:8080<https://urldefense.proofpoint.com/v2/url?u=http-3A__localhost-3A8080&d=DwMDaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=v9MU0Ki9pWnTXCWwjHPVgpnCR80vXkkcrIaqU7USl5g&m=kJtGvuus9oDRupym2EBb90B5bKvSi-pPMLdfIXHUGAM&s=r_P53gY50VmvMsyQPhxD35FdzONyzQNBH3GUYTerV4M&e=> )?

If so, something more like:
npm install
npm run-script server
Recompile bmcweb with BMCWEB_INSECURE_DISABLE_XSS_PREVENTION and BMCWEB_INSECURE_DISABLE_CSRF_PREVENTION and transfer bmcweb to target.
Go to https://bmc-ip<https://urldefense.proofpoint.com/v2/url?u=https-3A__bmc-2Dip&d=DwMDaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=v9MU0Ki9pWnTXCWwjHPVgpnCR80vXkkcrIaqU7USl5g&m=kJtGvuus9oDRupym2EBb90B5bKvSi-pPMLdfIXHUGAM&s=gdm3UjRQnu_XRVgmp5SVt9W82Tl-uoCarovDoHDdD1Y&e=> and accept the certificate
Go to http://localhost:8080<https://urldefense.proofpoint.com/v2/url?u=http-3A__localhost-3A8080&d=DwMDaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=v9MU0Ki9pWnTXCWwjHPVgpnCR80vXkkcrIaqU7USl5g&m=kJtGvuus9oDRupym2EBb90B5bKvSi-pPMLdfIXHUGAM&s=r_P53gY50VmvMsyQPhxD35FdzONyzQNBH3GUYTerV4M&e=> (could be running at a different port, check npm run-script server output) and point at bmc-ip

If you are trying to build the webui for the BMC (npm run-script build) and scp the files over, do you need to include the webui package group?

https://github.com/openbmc/openbmc/commit/fef8abbc78154abbd86ab9f0704e65ccb422f4de

The webui recipe creates the webui directory structure on the BMC.


Please help me what else I need to do. I got 2 warning while installing NPM.

The warnings should not matter.

- Gunnar


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

Re: webui not working for me

[Gunnar Mills]

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


On 1/6/2020 1:27 PM, Vijay Khemka wrote:
>
> Hi Gunnar,
>
> Now I am following below steps. I am running all these from my mac 
> laptop. Nothing on BMC, just copied bmcweb on BMC.
>
>  1. npm install in repo directory.
>  2. npm run-script server
>  3. Recompiled bmcweb with BMCWEB_INSECURE_DISABLE_XSS_PREVENTION and
>     BMCWEB_INSECURE_DISABLE_CSRF_PREVENTION and transfered bmcweb to
>     target.
>  4. Go to https://bmc-ip
>     <https://urldefense.proofpoint.com/v2/url?u=https-3A__bmc-2Dip&d=DwMDaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=v9MU0Ki9pWnTXCWwjHPVgpnCR80vXkkcrIaqU7USl5g&m=kJtGvuus9oDRupym2EBb90B5bKvSi-pPMLdfIXHUGAM&s=gdm3UjRQnu_XRVgmp5SVt9W82Tl-uoCarovDoHDdD1Y&e=>,
>     no certificates asked, says certificate expired on Dec 29 1979.
>     Go to http://localhost:8080
>     <https://urldefense.proofpoint.com/v2/url?u=http-3A__localhost-3A8080&d=DwMDaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=v9MU0Ki9pWnTXCWwjHPVgpnCR80vXkkcrIaqU7USl5g&m=kJtGvuus9oDRupym2EBb90B5bKvSi-pPMLdfIXHUGAM&s=r_P53gY50VmvMsyQPhxD35FdzONyzQNBH3GUYTerV4M&e=>,
>     Don’t see any port as output for “npm run-script server”.
>
Looks like it is :18898 for you. "Project is running at 
http://localhost:18898/"


> vijaykhemka-mbp:phosphor-webui vijaykhemka$ npm run-script server
>
> > phosphor-webui@2.8.0-dev server 
> /Users/vijaykhemka/proj/lf/gh/new-gh/gh-repo/phosphor-webui
>
> > webpack-dev-server --history-api-fallback --inline --progress 
> --devtool source-map --mode development
>
> *10% building 1/1 modules 0 active*ℹ｢wds｣: Project is running at 
> http://localhost:18898/
>
> ℹ｢wds｣: webpack output is served from /
>
> ℹ｢wds｣: Content not from webpack is served from ./src/public
>
> ℹ｢wds｣: 404s will fallback to /index.html
>
> *10% building 1/3 modules 2 active 
> ...babel-loader/lib/index.js??ref--4!/Users/vijaykhemka/proj/lf/gh/new-gh/gh-repo/phosphor-webui/node_modules/webpack-dev-server/client/index.js?http://localhost:18898*Browserslist: 
> caniuse-lite is outdated. Please run next command `npm update`
>
> *67% building 545/571 modules 26 active 
> /Users/vijaykhemka/proj/lf/gh/new-gh/gh-repo/phosphor-webui/node_modules/core-js/modules/es.reflect.is-extensible.js*[BABEL] 
> Note: The code generator has deoptimised the styling of 
> /Users/vijaykhemka/proj/lf/gh/new-gh/gh-repo/phosphor-webui/node_modules/angular/angular.js 
> as it exceeds the max of 500KB.
>
> *66% building 557/590 modules 33 active 
> /Users/vijaykhemka/proj/lf/gh/new-gh/gh-repo/phosphor-webui/node_modules/core-js/modules/es.object.to-string.js*[BABEL] 
> Note: The code generator has deoptimised the styling of 
> /Users/vijaykhemka/proj/lf/gh/new-gh/gh-repo/phosphor-webui/node_modules/text-encoding/lib/encoding-indexes.js 
> as it exceeds the max of 500KB.
>
> ℹ｢wdm｣: 761 modules
>
> ℹ｢wdm｣: Compiled successfully.
>
> Regards
>
> -Vijay
>

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

Re: webui not working for me

[Vijay Khemka]

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

Yes, I am able to get it but I can’t see any sensors or, event logs as well as system logs. I discussed with Kathy and it seems she has different patch for sensors to work from intel-bmc branch. But that patch doesn’t seem to apply in this upstream repo.

Do you have any ideas what could be wrong with sensors. I am using dbus-sensors.

Regards
-Vijay

From: Gunnar Mills <gmills@linux.vnet.ibm.com>
Date: Monday, January 6, 2020 at 3:53 PM
To: Vijay Khemka <vijaykhemka@fb.com>, "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: Re: webui not working for me



On 1/6/2020 1:27 PM, Vijay Khemka wrote:
Hi Gunnar,
Now I am following below steps. I am running all these from my mac laptop. Nothing on BMC, just copied bmcweb on BMC.

  1.  npm install in repo directory.
  2.  npm run-script server
  3.  Recompiled bmcweb with BMCWEB_INSECURE_DISABLE_XSS_PREVENTION and BMCWEB_INSECURE_DISABLE_CSRF_PREVENTION and transfered bmcweb to target.
  4.  Go to https://bmc-ip<https://urldefense.proofpoint.com/v2/url?u=https-3A__bmc-2Dip&d=DwMDaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=v9MU0Ki9pWnTXCWwjHPVgpnCR80vXkkcrIaqU7USl5g&m=kJtGvuus9oDRupym2EBb90B5bKvSi-pPMLdfIXHUGAM&s=gdm3UjRQnu_XRVgmp5SVt9W82Tl-uoCarovDoHDdD1Y&e=>, no certificates asked, says certificate expired on Dec 29 1979.
Go to http://localhost:8080<https://urldefense.proofpoint.com/v2/url?u=http-3A__localhost-3A8080&d=DwMDaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=v9MU0Ki9pWnTXCWwjHPVgpnCR80vXkkcrIaqU7USl5g&m=kJtGvuus9oDRupym2EBb90B5bKvSi-pPMLdfIXHUGAM&s=r_P53gY50VmvMsyQPhxD35FdzONyzQNBH3GUYTerV4M&e=>, Don’t see any port as output for “npm run-script server”.


Looks like it is :18898 for you. "Project is running at http://localhost:18898/<https://urldefense.proofpoint.com/v2/url?u=http-3A__localhost-3A18898_&d=DwMDaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=v9MU0Ki9pWnTXCWwjHPVgpnCR80vXkkcrIaqU7USl5g&m=ZNcKeBTnd2pStghg3o_6zvefHFDgsJYCFAR7g5N2ThU&s=T-XmLi5Z4UaCVOMuVGsVc4u7OPlEmoCjubR_sLUMSjA&e=>"



vijaykhemka-mbp:phosphor-webui vijaykhemka$ npm run-script server

> phosphor-webui@2.8.0-dev<mailto:phosphor-webui@2.8.0-dev> server /Users/vijaykhemka/proj/lf/gh/new-gh/gh-repo/phosphor-webui
> webpack-dev-server --history-api-fallback --inline --progress --devtool source-map --mode development

10% building 1/1 modules 0 activeℹ ｢wds｣: Project is running at http://localhost:18898/<https://urldefense.proofpoint.com/v2/url?u=http-3A__localhost-3A18898_&d=DwMDaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=v9MU0Ki9pWnTXCWwjHPVgpnCR80vXkkcrIaqU7USl5g&m=ZNcKeBTnd2pStghg3o_6zvefHFDgsJYCFAR7g5N2ThU&s=T-XmLi5Z4UaCVOMuVGsVc4u7OPlEmoCjubR_sLUMSjA&e=>
ℹ ｢wds｣: webpack output is served from /
ℹ ｢wds｣: Content not from webpack is served from ./src/public
ℹ ｢wds｣: 404s will fallback to /index.html
10% building 1/3 modules 2 active ...babel-loader/lib/index.js??ref--4!/Users/vijaykhemka/proj/lf/gh/new-gh/gh-repo/phosphor-webui/node_modules/webpack-dev-server/client/index.js?http://localhost:18898<https://urldefense.proofpoint.com/v2/url?u=http-3A__localhost-3A18898&d=DwMDaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=v9MU0Ki9pWnTXCWwjHPVgpnCR80vXkkcrIaqU7USl5g&m=ZNcKeBTnd2pStghg3o_6zvefHFDgsJYCFAR7g5N2ThU&s=RLBMFH13z8E8EK1cMfgTM5gNvoBUmW6fEjR3EsnszzA&e=>Browserslist: caniuse-lite is outdated. Please run next command `npm update`
67% building 545/571 modules 26 active /Users/vijaykhemka/proj/lf/gh/new-gh/gh-repo/phosphor-webui/node_modules/core-js/modules/es.reflect.is-extensible.js[BABEL] Note: The code generator has deoptimised the styling of /Users/vijaykhemka/proj/lf/gh/new-gh/gh-repo/phosphor-webui/node_modules/angular/angular.js as it exceeds the max of 500KB.
66% building 557/590 modules 33 active /Users/vijaykhemka/proj/lf/gh/new-gh/gh-repo/phosphor-webui/node_modules/core-js/modules/es.object.to-string.js[BABEL] Note: The code generator has deoptimised the styling of /Users/vijaykhemka/proj/lf/gh/new-gh/gh-repo/phosphor-webui/node_modules/text-encoding/lib/encoding-indexes.js as it exceeds the max of 500KB.
ℹ ｢wdm｣:    761 modules
ℹ ｢wdm｣: Compiled successfully.

Regards
-Vijay


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

Re: webui not working for me

[Gunnar Mills]

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


On 1/6/2020 6:19 PM, Vijay Khemka wrote:
>
> Yes, I am able to get it but I can’t see any sensors or, event logs as 
> well as system logs. I discussed with Kathy and it seems she has 
> different patch for sensors to work from intel-bmc branch. But that 
> patch doesn’t seem to apply in this upstream repo.
>
> Do you have any ideas what could be wrong with sensors. I am using 
> dbus-sensors.
>
Anything in the browser console?

The sensors page is making a call to 
`/xyz/openbmc_project/sensors/enumerate`
https://github.com/openbmc/phosphor-webui/blob/f70f42553615972163b36c9b4d77be07e4399122/app/common/services/api-utils.js#L916

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

Re: webui not working for me

[Vijay Khemka]

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


From: Gunnar Mills <gmills@linux.vnet.ibm.com>
Date: Monday, January 6, 2020 at 4:24 PM
To: Vijay Khemka <vijaykhemka@fb.com>, "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: Re: webui not working for me



On 1/6/2020 6:19 PM, Vijay Khemka wrote:
Yes, I am able to get it but I can’t see any sensors or, event logs as well as system logs. I discussed with Kathy and it seems she has different patch for sensors to work from intel-bmc branch. But that patch doesn’t seem to apply in this upstream repo.

Do you have any ideas what could be wrong with sensors. I am using dbus-sensors.

Anything in the browser console?

It says on page “there are no sensors available”


The sensors page is making a call to `/xyz/openbmc_project/sensors/enumerate`
https://github.com/openbmc/phosphor-webui/blob/f70f42553615972163b36c9b4d77be07e4399122/app/common/services/api-utils.js#L916

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

Re: webui not working for me

[Gunnar Mills]

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


On 1/6/2020 6:29 PM, Vijay Khemka wrote:
>
> It says on page “there are no sensors available”
>
>
A curl call to /xyz/openbmc_project/sensors/enumerate returns all the 
sensors correctly ?

If so, probably will need to add some console.log()s to that function
https://github.com/openbmc/phosphor-webui/blob/f70f42553615972163b36c9b4d77be07e4399122/app/common/services/api-utils.js#L912



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

Re: webui not working for me

[Vijay Khemka]

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



From: Gunnar Mills <gmills@linux.vnet.ibm.com>
Date: Monday, January 6, 2020 at 4:40 PM
To: Vijay Khemka <vijaykhemka@fb.com>, "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: Re: webui not working for me



On 1/6/2020 6:29 PM, Vijay Khemka wrote:

It says on page “there are no sensors available”


A curl call to /xyz/openbmc_project/sensors/enumerate returns all the sensors correctly ?

I have not used any curl command here. Please let me know what curl command to use. But intel is using redfish method to get these data.

https://github.com/Intel-BMC/phosphor-webui/blob/e34f46c191a4c993608ac64a867920fb640e8133/app/common/services/api-utils.js#L932


If so, probably will need to add some console.log()s to that function
https://github.com/openbmc/phosphor-webui/blob/f70f42553615972163b36c9b4d77be07e4399122/app/common/services/api-utils.js#L912


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

Re: webui not working for me

[Vijay Khemka]

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

Alright I am getting data from curl command
curl -k -H "X-Auth-Token: $token" -X GET https://${bmc}/xyz/openbmc_project/sensors/enumerate

    "/xyz/openbmc_project/sensors/temperature/Core_16_CPU1": {
      "Associations": [
        [
          "chassis",
          "all_sensors",
          "/xyz/openbmc_project/inventory/system/board/TiogaPass_Baseboard"
        ]
      ],
      "CriticalAlarmHigh": false,
      "CriticalHigh": 89.0,
      "MaxValue": 127.0,
      "MinValue": -128.0,
      "Value": 21.0,
      "WarningAlarmHigh": false,
      "WarningHigh": 79.0
    },
    "/xyz/openbmc_project/sensors/temperature/Core_16_CPU1/chassis": {
      "endpoints": [
        "/xyz/openbmc_project/inventory/system/board/TiogaPass_Baseboard"
      ]
    },

Regards
-Vijay

From: Gunnar Mills <gmills@linux.vnet.ibm.com>
Date: Monday, January 6, 2020 at 4:40 PM
To: Vijay Khemka <vijaykhemka@fb.com>, "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: Re: webui not working for me



On 1/6/2020 6:29 PM, Vijay Khemka wrote:

It says on page “there are no sensors available”


A curl call to /xyz/openbmc_project/sensors/enumerate returns all the sensors correctly ?

If so, probably will need to add some console.log()s to that function
https://github.com/openbmc/phosphor-webui/blob/f70f42553615972163b36c9b4d77be07e4399122/app/common/services/api-utils.js#L912


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

RE: webui not working for me

[Pine, Kathryn ElaineX]

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

Hi,

I’ve uploaded a work in progress patch with the sensors page using Redfish data.

I pulled most of the Intel downstream UI off so it’s a bit plain looking, but should have the functionality needed for using Redfish for sensors:

https://gerrit.openbmc-project.xyz/c/openbmc/phosphor-webui/+/28342<https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.openbmc-2Dproject.xyz_c_openbmc_phosphor-2Dwebui_-2B_28342&d=DwMFAg&c=5VD0RTtNlTh3ycd41b3MUw&r=v9MU0Ki9pWnTXCWwjHPVgpnCR80vXkkcrIaqU7USl5g&m=JkVnc6xcsrOQFOz3T-1BDffQOJNyNF4wVA5bKw8bIhA&s=tAWerk9BOa0ESN6g41fJ4pT5FsvVhIDygTBrFzQVf8Q&e=>

If there’s value in getting this into upstream, please let me know – would require a bit more coordinating and UI tweaks to get this to match upstream, which is why for now I just uploaded as WIP.

Best,
Kathy


From: openbmc <openbmc-bounces+kathryn.elainex.pine=intel.com@lists.ozlabs.org> On Behalf Of Vijay Khemka
Sent: Monday, January 6, 2020 4:46 PM
To: Gunnar Mills <gmills@linux.vnet.ibm.com>; openbmc@lists.ozlabs.org
Subject: Re: webui not working for me



From: Gunnar Mills <gmills@linux.vnet.ibm.com<mailto:gmills@linux.vnet.ibm.com>>
Date: Monday, January 6, 2020 at 4:40 PM
To: Vijay Khemka <vijaykhemka@fb.com<mailto:vijaykhemka@fb.com>>, "openbmc@lists.ozlabs.org<mailto:openbmc@lists.ozlabs.org>" <openbmc@lists.ozlabs.org<mailto:openbmc@lists.ozlabs.org>>
Subject: Re: webui not working for me



On 1/6/2020 6:29 PM, Vijay Khemka wrote:

It says on page “there are no sensors available”


A curl call to /xyz/openbmc_project/sensors/enumerate returns all the sensors correctly ?

I have not used any curl command here. Please let me know what curl command to use. But intel is using redfish method to get these data.

https://github.com/Intel-BMC/phosphor-webui/blob/e34f46c191a4c993608ac64a867920fb640e8133/app/common/services/api-utils.js#L932


If so, probably will need to add some console.log()s to that function
https://github.com/openbmc/phosphor-webui/blob/f70f42553615972163b36c9b4d77be07e4399122/app/common/services/api-utils.js#L912

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

Re: webui not working for me

[Vijay Khemka]

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

It does work for me. I don’t find any reason that why it is not a value as it is enabling redfish interface. If it is breaking existing phosphor sensor implementation then we need to fix that but we should definitely support both dbus-sensor as well as phosphor-sensors.

Regards
-Vijay

From: "Pine, Kathryn ElaineX" <kathryn.elainex.pine@intel.com>
Date: Thursday, January 9, 2020 at 2:09 PM
To: Vijay Khemka <vijaykhemka@fb.com>, Gunnar Mills <gmills@linux.vnet.ibm.com>, "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: RE: webui not working for me

Hi,

I’ve uploaded a work in progress patch with the sensors page using Redfish data.

I pulled most of the Intel downstream UI off so it’s a bit plain looking, but should have the functionality needed for using Redfish for sensors:

https://gerrit.openbmc-project.xyz/c/openbmc/phosphor-webui/+/28342<https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.openbmc-2Dproject.xyz_c_openbmc_phosphor-2Dwebui_-2B_28342&d=DwMFAg&c=5VD0RTtNlTh3ycd41b3MUw&r=v9MU0Ki9pWnTXCWwjHPVgpnCR80vXkkcrIaqU7USl5g&m=JkVnc6xcsrOQFOz3T-1BDffQOJNyNF4wVA5bKw8bIhA&s=tAWerk9BOa0ESN6g41fJ4pT5FsvVhIDygTBrFzQVf8Q&e=>

If there’s value in getting this into upstream, please let me know – would require a bit more coordinating and UI tweaks to get this to match upstream, which is why for now I just uploaded as WIP.

Best,
Kathy


From: openbmc <openbmc-bounces+kathryn.elainex.pine=intel.com@lists.ozlabs.org> On Behalf Of Vijay Khemka
Sent: Monday, January 6, 2020 4:46 PM
To: Gunnar Mills <gmills@linux.vnet.ibm.com>; openbmc@lists.ozlabs.org
Subject: Re: webui not working for me



From: Gunnar Mills <gmills@linux.vnet.ibm.com<mailto:gmills@linux.vnet.ibm.com>>
Date: Monday, January 6, 2020 at 4:40 PM
To: Vijay Khemka <vijaykhemka@fb.com<mailto:vijaykhemka@fb.com>>, "openbmc@lists.ozlabs.org<mailto:openbmc@lists.ozlabs.org>" <openbmc@lists.ozlabs.org<mailto:openbmc@lists.ozlabs.org>>
Subject: Re: webui not working for me



On 1/6/2020 6:29 PM, Vijay Khemka wrote:

It says on page “there are no sensors available”


A curl call to /xyz/openbmc_project/sensors/enumerate returns all the sensors correctly ?

I have not used any curl command here. Please let me know what curl command to use. But intel is using redfish method to get these data.

https://github.com/Intel-BMC/phosphor-webui/blob/e34f46c191a4c993608ac64a867920fb640e8133/app/common/services/api-utils.js#L932


If so, probably will need to add some console.log()s to that function
https://github.com/openbmc/phosphor-webui/blob/f70f42553615972163b36c9b4d77be07e4399122/app/common/services/api-utils.js#L912

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

RE: webui not working for me

[Giles, Joshua]

Hello Kathryn,

The gerrit link you had below is returning a 404; Can you point me to a location where I can see this patch?

-Josh

From: openbmc <openbmc-bounces+kathryn.elainex.pine=intel.com at lists.ozlabs.org> On Behalf Of Vijay Khemka
Sent: Monday, January 6, 2020 4:46 PM
To: Gunnar Mills <gmills at linux.vnet.ibm.com>; openbmc at lists.ozlabs.org
Subject: Re: webui not working for me

Hi,

I’ve uploaded a work in progress patch with the sensors page using Redfish data.

I pulled most of the Intel downstream UI off so it’s a bit plain looking, but should have the functionality needed for using Redfish for sensors:

https://gerrit.openbmc-project.xyz/c/openbmc/phosphor-webui/+/28342<https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.openbmc-2Dproject.xyz_c_openbmc_phosphor-2Dwebui_-2B_28342&d=DwMFAg&c=5VD0RTtNlTh3ycd41b3MUw&r=v9MU0Ki9pWnTXCWwjHPVgpnCR80vXkkcrIaqU7USl5g&m=JkVnc6xcsrOQFOz3T-1BDffQOJNyNF4wVA5bKw8bIhA&s=tAWerk9BOa0ESN6g41fJ4pT5FsvVhIDygTBrFzQVf8Q&e=>

If there’s value in getting this into upstream, please let me know – would require a bit more coordinating and UI tweaks to get this to match upstream, which is why for now I just uploaded as WIP.

Best,
Kathy


From: openbmc <openbmc-bounces+kathryn.elainex.pine=intel.com at lists.ozlabs.org> On Behalf Of Vijay Khemka
Sent: Monday, January 6, 2020 4:46 PM
To: Gunnar Mills <gmills at linux.vnet.ibm.com>; openbmc at lists.ozlabs.org
Subject: Re: webui not working for me



From: Gunnar Mills <gmills at linux.vnet.ibm.com<mailto:gmills at linux.vnet.ibm.com>>
Date: Monday, January 6, 2020 at 4:40 PM
To: Vijay Khemka <vijaykhemka at fb.com<mailto:vijaykhemka at fb.com>>, "openbmc at lists.ozlabs.org<mailto:openbmc at lists.ozlabs.org>" <openbmc at lists.ozlabs.org<mailto:openbmc at lists.ozlabs.org>>
Subject: Re: webui not working for me



On 1/6/2020 6:29 PM, Vijay Khemka wrote:

It says on page “there are no sensors available”


A curl call to /xyz/openbmc_project/sensors/enumerate returns all the sensors correctly ?

I have not used any curl command here. Please let me know what curl command to use. But intel is using redfish method to get these data.

https://github.com/Intel-BMC/phosphor-webui/blob/e34f46c191a4c993608ac64a867920fb640e8133/app/common/services/api-utils.js#L932


If so, probably will need to add some console.log()s to that function
https://github.com/openbmc/phosphor-webui/blob/f70f42553615972163b36c9b4d77be07e4399122/app/common/services/api-utils.js#L912
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20200109/e883ab7b/attachment.htm>
Previous message (by thread): webui not working for me
Next message (by thread): webui not working for me
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the openbmc mailing list