NODE Restarting after 4.10.11
Answered
Since the upgrade yesterday, my Node is plain broken, plays for 10 minutes then starts dropping, restarts for a bit then is done until a reboot.
This is happening with either the library or TuneIn.
Can the firmware be reverted to the previous working version?
-
Official comment
Hi Marc
Please select Settings, Send Support Request so our Support Crew may review your log to help understand why your NODE may have restarted.
-
I have the same problem with my Node 2i - since the 4.10.11 update it plays for 5 - 10 mins, then sound starts dropping out and playback stops completely. My Pulse Mini 2i and PowerNode Edge are still working fine when playing exactly the same streams.
I'd suggest the title of this post is a bit misleading though - it's not that the device is spontaneously rebooting: the device needs needs a user-initiated reboot to get it back to a working state.
I've sent a support request through the controller app.
4 -
It's exactly the behaviour I have!
As for the title, it's not the one I originally entered, it looks like they changed it.
My original title was something like "Another post about Bluos 4.10.11 breaking things"
But, after re-reading my message, I see how it would be understood as the Node restarting automatically, which it's not.
2 -
I think the problem I was having was actually overheating. Last year I moved the Node to a more concealed location and when I checked today it was very warm indeed, as we're having some very hot weather at the moment. I've now moved it to where there's better air circulation and it's now played for 1.5 hours with no problems.
Could a similar thing be happening in your case?
-1 -
I highly doubt that heat is the issue, the Node has been sitting at the same place for years and the issue started the minute after the installation of 4.10.11
1 -
UPDATE
it is very highly unlikely it is heat related.
We are continuing to investigate. In speaking with our Quality Assurance and Product Development Teams, it may be related to an update to DIRAC.
0 -
Hello,
Is there any update regarding this issue ?
I'm facing the same symptoms, even on 4.10.13. After ~10 minutes, audio drops, the Node becomes slow or completely unresponsive. The IR remote also shows signs of hardware slowness, with the Node blue LED reacting very slowly.
Only a reboot temporarily restores functionality, but the issue reappears shortly after resuming playback.
0 -
Just for fun, I installed 4.10.13 and it still has the issue.
1 -
Adrien, mapaq, do you have anything connected to the optical input of your Node?
I've realised that when I moved my Node out of the cupboard because I thought it was overheating I disconnected the TOSLINK connection from my TV. Since I've reconnected it it has started playing up again.
As long as the optical input is disconnected or the TV is off, the device seems to work properly. If I turn my TV on, playback of TuneIn starts cutting out after 10 minutes, and the Node gets into a state where it can't play reliably until it is rebooted.
I've tried these steps twice now with the same result - it could of course just be coincidence but I'd be interested to hear if use of the optical input is a common factor for others experiencing this issue.
0 -
On my side, I do have a TV connected to the Node’s optical input, but the issue was happening even when the TV was off.
When the issue occurred, the Node became overloaded on the CPU side, with the load average climbing above 12. The logs were showing high CPU usage errors, especially for the
dspoutprocess:```
<b>uptime</b>
23:42:12 up 27 min, 0 users, load average: 12.69, 8.86, 4.55[...]
Jul 16 23:38:47 (none) user.info dspout: [error] CPU use last minute 95%
```I had a remote access session with Bluesound support yesterday. While we couldn’t pinpoint the exact cause, it seems that performing a factory reset may have resolved the issue on my side.
So far, the problem hasn't come back, whereas I was previously able to reproduce it consistently. CPU load is back to ~1 and no error logs anymore.
Edit: I should mention, I have a Node 2i, not a Node.
0 -
Hi Adrien,
I also have a Node 2i. The TV does not have to be on to affect playback, I think if the optical input has been active for ~10 minutes since the last reboot the device will be in a state where it can't play reliably. In other words, after you have watched some TV, and then try to play some audio on the Bluesound device, I'd expect the problem to reoccur. It's as if having the optical input active causes some resource leak or infinite loop which makes the device unstable.
If you see the problem again, you could try disconnecting the optical input entirely [Edit: and do a reboot], which seems to have "fixed" it for me.
I remember there used to be a way to get access to the output of some Linux commands like ps and top through the diagnostics page, were you able to access that? Or did the Bluesound engineer actually log in to the device? It would be very interesting to see if activating the optical input causes the load average to shoot up.
0 -
Hi Bailo,
I will definitely check if it happens again. If that's the case, it will be a new behaviour, as the TV has been connected to the Node via the optical input for more than 4 years now.
Regarding diagnostics, I'm able to access those via the browser on `node-ip/diag?print=true`.
Edit: I see some additional threads are coming in for similar symptoms: https://support1.bluesound.com/hc/en-us/community/posts/33631051678103-Streaming-with-Radio-Paradise-and-Spotify-stuttering-with-BlueOS-4-10-13-Node-2i
0 -
Tony, I have created https://support1.bluesound.com/hc/en-us/requests/478337 with some more info as the original support request was closed
Adrien: thanks for the tip about the diagnostics
1
Please sign in to leave a comment.
Comments
13 comments