"loading logs using native method..." hangs raspberry pi

[ssllii]

Describe The Bug:
After logging in to the UI, the raspberry pi hangs. I can still get a ping response, but no response with putty. The remote desktop session that I was on just sits there, did not disconnect but also no response. Power off/on seems like the only recovery possible.
This happened with homebridge v1.0.4 and v1.1.0.

To Reproduce:
Seems to happen whenever the Config-UI idle timeouts. Then I tried to log back in as Admin. As the status screen showed up, the log screen started showing "loading logs using native method...", then it happens. It does not fail the first time after reboot. Forcing a logout and then logging back in is also ok.

Expected behavior:

Logs:

Show the Homebridge / Homebridge Config UI X logs here.

Homebridge Config:

Show your homebridge config.json here

Screenshots:

Environment:

• Node.js Version:
• NPM Version:
• Homebridge Version: v1.1.0
• Homebridge Config UI X Version: v4.19.0
• Operating System: Raspbian / Ubuntu / Debian / Windows / macOS / Docker
• Process Supervisor: Docker / Systemd / init.d / pm2 / launchctl / hb-service / other / none

[oznu]

Hi @ssllii can you try the current @test version of the UI to see if this helps?

I've made some changes to the way the log file is managed by hb-service.

https://github.com/oznu/homebridge-config-ui-x/wiki/How-To-Test-Upcoming-Changes

[ssllii]

thanks for the quick response.
It did not fail this morning. I will let it run with v1.1.0/v4.19.0 for a few more days before trying out your test version. Hope that's alright with you.

[jp-lno]

I have tried the @test version (4.21.1-test.4) but Ihave the same issue. Can’t solve it by rolling back both homebridge and Homebridge ux.

An abort signal is sent from main.js:29123 when trying to show log. And Homebridge service is restarted. This is why we receive a request timeout.
There is an open request on Homebridge github repo .

But I think the issue come from Homebridge-ux.

Any idea about this issue ??

[jp-lno]

I complete my post and after two restart I can confirm that the 4.21.1-test.4 solve the issue when loading log file.
But there is a side effect and my devices stop working. I have them in my Home app but open/close actions don’t do anything.

Is there a way to disable/remove homebridge-Ux and only use console to manage it ?

I will check your code and try to find an issue in debug mode.

[ssllii]

@oznu , I don't believe the issue here is exactly the same as #718, when my "hang" happens, ping is the only thing that works, not even PUTTY gets any response. Homebridge is out cold.

@jplongo, have you tracked down the cause of the side effect of the test version, 4.2.1.1-test.4?

[ssllii]

I tried a different experiment.

1. open putty session first
2. log in to homebridge-config-ui, the first time went fine. Then I clicked on plug-in status as I noticed some errors in the log regarding connection taking too long. that hung the system.
3. curious thing is input still got echo'ed on my putty, e.g. I typed "sudo reboot" and it showed up on putty but no action. The raspberry did not reboot but it is still happily responding to ping.
4. after like minutes, the shell prompt on the putty actually return! but still no reboot.

[oznu]

Is this still an issue on the latest versions?

[ssllii]

It is still happening to me with v1.1.6.
The system responds to ping but I can't get a response with SSH.
So it has crashed but it only responds to ping.