0

HiFiBerryOS beo-server.js Swamping System

Michael Williams

June 15, 2021 20:50

None

Follow

I am using HiFiBerryOS (20210531-pi4) with a Digi2 Pro + DSP daughter board.  Things work fine initially upon startup, but over time (10 minutes or so playing music) the following task:

/usr/bin/node /opt/beocreate/beo-system/beo-server.js vv

pegs one core of the CPU, and the system becomes mostly unresponsive.  In particular, the web interface becomes completely non-responsive.

Otherwise, the system is performing beautifully.  Any advice?  Is there a way to properly restart just this one task?  Is there a log file I can use to find out more about what is happening?

• Facebook
• Twitter
• LinkedIn

5 comments

• 0
  
  Michael Williams June 15, 2021 20:53

  I should add that if I stop playing music, the beo-server task remains pegged at 100% (an entire core), and never recovers.

• 0
  
  Gene October 08, 2021 18:58

  Same issue, running clean install on RP3.

• 0
  
  Sebastien Vajda January 07, 2022 12:38

  Same issue with either a clean install on RPI4b or on a re-build image using buildroot. After a while, node.js use 100% cpu and is completely unresponsive. systemctl restart beocreate2 get the service back.

• 0
  
  Ed June 04, 2022 03:54

  I'm seeing the same issue as well. Any idea if there is a fix?

• 0
  
  Gene June 04, 2022 04:27

  I ended up sshing into the pi and creating a cron to reboot the pi every day at 5 AM.

  That being said, I've had it set to every week without seeing many issues, increased the reboot frequency to every day as it seems to increase airplay responsiveness (most likely a placebo).