Log is outdated

Hey all,

I’ve been running into an issue since upgrading my HA install earlier this week.
The log shown on the webpage is outdated and does not reflect the latest changes. This morning (7th december) it still showed the logging from the 5th. The logging ends where the it ended that day when i opened the page.
The log file on the RPi is accurate though and is recreated with every service restart, thus i can open it through SMB or the terminal.

Where is the logging, shown on the webpage, cached? Clearing my browser didn’t slve it

To give you an example, this is the top part of my webpage log:

The following errors have been logged this session:
16-12-05 23:03:39 homeassistant.config: Upgrading config directory from 0.32.2 to 0.34.2
16-12-05 23:03:40 homeassistant.core: Bus:Handling <Event service_registered[L]: domain=homeassistant, service=turn_off>
16-12-05 23:03:40 homeassistant.core: Bus:Handling <Event service_registered[L]: domain=homeassistant, service=turn_on>
16-12-05 23:03:40 homeassistant.core: Bus:Handling <Event service_registered[L]: domain=homeassistant, service=toggle>
16-12-05 23:03:40 homeassistant.core: Bus:Handling <Event service_registered[L]: domain=homeassistant, service=reload_core_config>
16-12-05 23:03:40 homeassistant.core: Bus:Handling <Event service_registered[L]: domain=persistent_notification, service=create>
16-12-05 23:03:40 homeassistant.bootstrap: Home Assistant core initialized
16-12-05 23:03:40 homeassistant.loader: Loaded notify from homeassistant.components.notify
16-12-05 23:03:41 homeassistant.loader: Loaded logbook from homeassistant.components.logbook
16-12-05 23:03:41 homeassistant.loader: Loaded recorder from homeassistant.components.recorder
16-12-05 23:03:41 homeassistant.loader: Loaded frontend from homeassistant.components.frontend
16-12-05 23:03:41 homeassistant.loader: Loaded api from homeassistant.components.api
16-12-05 23:03:41 homeassistant.loader: Loaded http from homeassistant.components.http

This is the more recent one from this morning directly through opening the file via SMB:

16-12-07 10:09:16 homeassistant.core: Bus:Handling <Event service_registered[L]: service=turn_off, domain=homeassistant>
16-12-07 10:09:16 homeassistant.core: Bus:Handling <Event service_registered[L]: service=turn_on, domain=homeassistant>
16-12-07 10:09:16 homeassistant.core: Bus:Handling <Event service_registered[L]: service=toggle, domain=homeassistant>
16-12-07 10:09:16 homeassistant.core: Bus:Handling <Event service_registered[L]: service=reload_core_config, domain=homeassistant>
16-12-07 10:09:16 homeassistant.core: Bus:Handling <Event service_registered[L]: service=create, domain=persistent_notification>
16-12-07 10:09:16 homeassistant.bootstrap: Home Assistant core initialized
16-12-07 10:09:16 homeassistant.loader: Loaded sensor from homeassistant.components.sensor
16-12-07 10:09:16 homeassistant.loader: Loaded input_select from homeassistant.components.input_select
16-12-07 10:09:17 homeassistant.loader: Loaded history from homeassistant.components.history
16-12-07 10:09:17 homeassistant.loader: Loaded recorder from homeassistant.components.recorder
16-12-07 10:09:17 homeassistant.loader: Loaded http from homeassistant.components.http
16-12-07 10:09:17 homeassistant.loader: Loaded updater from homeassistant.components.updater

Kind regards.

Confirming I have had similar behaviour - seemingly for a while although it is more prevalent now - I am on .34.1

I have cleared the cache on my browser on a couple of machines and this has helped for the first reload after the clear.

Seems to be something with how caching is working with the browser to my mind.

I am using chrome on windows and ipad (don’t have versions at hand)

Yeah it is a browser cache issue. You can open up in a different browser, use incognito mode, or clear your cache and it should resolve the issue.

I have the same issue.

With port forwarding from the web it always shows the wrong log. however on my lan accessing it directly it shows the correct log.

Have not gotten to the bottom of it.

It seems like the issue has been solved in 0.34.4
Don’t forget to clear the cashed data in your browser.

2 Likes

Worked for me. Had to clear browser cache as well.