core icon indicating copy to clipboard operation
core copied to clipboard

Cannot access System page after 10.1 upgrade

Open gretske47 opened this issue 1 year ago • 32 comments

The problem

After upgrading to 10.1, I get the following error message when I click on the System page - "Error while loading page system."

What version of Home Assistant Core has the issue?

10.1

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Core

Integration causing the issue

No response

Link to integration documentation on our website

No response

Diagnostics information

home-assistant.log

Example YAML snippet

No response

Anything in the logs that might be useful for us?

I attached the log file above.

Additional information

No response

gretske47 avatar Oct 05 '24 11:10 gretske47

Can you try rebooting in safe mode?

joostlek avatar Oct 05 '24 11:10 joostlek

And also, does the rest of the system work like normal?

joostlek avatar Oct 05 '24 11:10 joostlek

How do I do that? Remember I cannot access the System page. Can I do it by CLI?

On Oct 5, 2024, at 07:51, Joost Lekkerkerker @.***> wrote:

Can you try rebooting in safe mode?

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/127635#issuecomment-2395030908, or unsubscribe https://github.com/notifications/unsubscribe-auth/A47ZEZW65HYO3EPK3KIUR6TZZ7HFRAVCNFSM6AAAAABPNI2MY2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJVGAZTAOJQHA. You are receiving this because you authored the thread.

gretske47 avatar Oct 05 '24 11:10 gretske47

Yes, the rest of the system seems to be OK.

Thanks for your help!

On Oct 5, 2024, at 07:53, Joost Lekkerkerker @.***> wrote:

And also, does the rest of the system work like normal?

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/127635#issuecomment-2395031160, or unsubscribe https://github.com/notifications/unsubscribe-auth/A47ZEZTGZFSHUI3SNWQBMILZZ7HJ3AVCNFSM6AAAAABPNI2MY2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJVGAZTCMJWGA. You are receiving this because you authored the thread.

gretske47 avatar Oct 05 '24 11:10 gretske47

Can you access the settings page?

joostlek avatar Oct 05 '24 11:10 joostlek

Yes

On Oct 5, 2024, at 07:56, Joost Lekkerkerker @.***> wrote:

Can you access the settings page?

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/127635#issuecomment-2395031853, or unsubscribe https://github.com/notifications/unsubscribe-auth/A47ZEZQK2TB67H5DBYQH45DZZ7HXDAVCNFSM6AAAAABPNI2MY2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJVGAZTCOBVGM. You are receiving this because you authored the thread.

gretske47 avatar Oct 05 '24 11:10 gretske47

There's a reboot button at the top right, if you click more it will show reboot in safe mode

joostlek avatar Oct 05 '24 11:10 joostlek

OK, I rebooted in Safe Mode, and I get the same error message when I try to access the System page, "Error while loading page system.”

On Oct 5, 2024, at 08:00, Joost Lekkerkerker @.***> wrote:

There's a reboot button at the top right, if you click more it will show reboot in safe mode

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/127635#issuecomment-2395032588, or unsubscribe https://github.com/notifications/unsubscribe-auth/A47ZEZTPZAOS4EYRUXAZEQLZZ7IFDAVCNFSM6AAAAABPNI2MY2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJVGAZTENJYHA. You are receiving this because you authored the thread.

gretske47 avatar Oct 05 '24 12:10 gretske47

Do you have a screenshot of that? Please use github for that by the way, as I see you respond via email :)

joostlek avatar Oct 05 '24 12:10 joostlek

Screenshot 2024-10-05 at 08 08 06

gretske47 avatar Oct 05 '24 12:10 gretske47

Anything more in the logs? Can you also try checking the frontend logs when you're accessing the page?

joostlek avatar Oct 05 '24 12:10 joostlek

Hey there @home-assistant/frontend, mind taking a look at this issue as it has been labeled with an integration (frontend) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of frontend can trigger bot actions by commenting:

  • @home-assistant close Closes the issue.
  • @home-assistant rename Awesome new title Renames the issue.
  • @home-assistant reopen Reopen the issue.
  • @home-assistant unassign frontend Removes the current integration label and assignees on the issue, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


frontend documentation frontend source (message by IssueLinks)

home-assistant[bot] avatar Oct 05 '24 12:10 home-assistant[bot]

Where is the frontend log? The only logs I see are the homeassistant log. I looked through that, but I don't see any references to System page.

gretske47 avatar Oct 05 '24 12:10 gretske47

Here is the homeassistant, log home-assistant.log

gretske47 avatar Oct 05 '24 12:10 gretske47

You can open the developer tools of your browser (I don't recognize the browser so I don't know how that exactly works) and see the console.

Do you see anything similar to

2024-10-05 07:42:49.812 ERROR (MainThread) [frontend.js.modern.202410022] Uncaught error from Safari 18.0 on Mac OS 10.15.7
Error: Failed to execute 'define' on 'CustomElementRegistry': the name "swipe-card" has already been used with this registry
message (node_modules/core-js/modules/web.dom-exception.stack.js:25:24)
src/scoped-custom-element-registry.js:45:10
/gh/bramkragten/custom-ui@master/swipe-card/swipe-card.js:1:173644
/gh/bramkragten/custom-ui@master/swipe-card/swipe-card.js:1:122
module code (/gh/bramkragten/custom-ui@master/swipe-card/swipe-card.js:1:125)

in the logs?

joostlek avatar Oct 05 '24 12:10 joostlek

OK, here is the homeassistant.log.1. There are several references to frontend. (I had to change the filename to upload.) home-assistant-1.log

gretske47 avatar Oct 05 '24 12:10 gretske47

But this log is not with safe mode on because it has references to custom components and cards

joostlek avatar Oct 05 '24 12:10 joostlek

Yes, that is the previous log. Do you want me to boot in normal mode and look at the log?

gretske47 avatar Oct 05 '24 12:10 gretske47

No I mean, the log you just uploaded (with -1) has references to custom components and custom cards, and they are disabled in safe mode, so in theory when you boot in safe mode it should not mention them.

joostlek avatar Oct 05 '24 12:10 joostlek

Yes, that is the previous log, which was in normal mode.

gretske47 avatar Oct 05 '24 12:10 gretske47

Do you have one from safe mode?

joostlek avatar Oct 05 '24 12:10 joostlek

home-assistant.log Here is the safe mode log.

gretske47 avatar Oct 05 '24 12:10 gretske47

I don't see any references to "frontend" and the only references to "System" are about security pages,

gretske47 avatar Oct 05 '24 12:10 gretske47

Okay I don't see anything that could help me, so I this is either a frontend issue (which I don't know enough about to debug) or something else going wrong with your system. I did tag this issue with frontend, so someone who works on the frontend gets notified. (as alternative, you can always create a new issue on the frontend issue tracker, where it will at least have more attention from the right people who know what could cause this).

A few points of notice: 2024-10-05 08:31:12.202 ERROR (MainThread) [homeassistant.components.binary_sensor] The workday platform for the binary_sensor integration does not support platform setup. Please remove it from your config. And double check what version of Alexa_media you are using, since 4.13.3 (the version released on the day of 2024.10 release) is causing memory issues.

joostlek avatar Oct 05 '24 12:10 joostlek

OK, thanks for your patience. I am back to v8.3 and it works for me. I wish there was a simple way to find out the slug # on a running system.

gretske47 avatar Oct 05 '24 12:10 gretske47

Does 2024.9 not work also?

joostlek avatar Oct 05 '24 12:10 joostlek

I FOUND IT!

There was an entry in the config.yaml that said (without the '#')

#frontend:
#  themes: !include_dir_merge_named themes
#  extra_module_url:
#    - /local/card-mod.js

I commented this out and the problem is gone. I don't remember what this was supposed to be, but it caused the problem.

gretske47 avatar Oct 05 '24 12:10 gretske47

But wait, this worked on 2024.8.3?

joostlek avatar Oct 05 '24 13:10 joostlek

I don't know. It appears that I did not upgrade, so I am upgrading again. I need to take notes!

gretske47 avatar Oct 05 '24 13:10 gretske47

No, I upgraded to 10.1 with the lines commented out, and I cannot get the Systems page. I thought I had found it.

gretske47 avatar Oct 05 '24 13:10 gretske47