0

UI is unreachable

Philipp Leser-Wolf

August 23, 2021 09:59

None

Follow

Hi,

I'm using HifiBerryOS on a Pi4 with the DAC+DSP board. I have been using it successfully for about a month now (configuring things in the UI and listening to music) and have now discovered that the web UI is not reachable any more. I have tried the following steps to find out what is wrong, but haven't been successful yet:

• just listen to music (Toslink in, Toslink out) => Ok
• ssh into the system => Ok
• Check if beocreate2.service is up and running (using systemctl / journalctl) => It complains about "Error loading extension music" (data isn't mounted. I only use Toslink in), but otherwise seems to start up fine, loading the DSP program and applying the filters I initially entered in the UI

I have not made any configuration changes or performed any updates recently (Installation was at the end of July with the newest image).

I'm at a loss currently, because the services seem happy, the music pipeline works, but the UI doesn't. Any ideas what I could try next?

Thanks!

Best,

  Philipp

 

• Facebook
• Twitter
• LinkedIn

7 comments

• 0
  
  Philipp Leser-Wolf August 23, 2021 10:09

  I forgot to define what "unreachable" means in this case: Using a web browser to connect to http://ip:80 I get a time-out error after a while. Telnetting to ip:80 and issueing GET / gives no response at all. (ip:81 gives a 404, so audiocontrol2 seems to be up and answering requests; AirPlay also works).

  The Pi4 is connected using Ethernet.

• 0
  
  HiFiBerry team August 23, 2021 11:02

  Looks like a problem in your installation if /data isn't mounted.
  
  What's the output of

  df -k

   

• 0
  
  Philipp Leser-Wolf August 23, 2021 11:07

  # df -k
  Filesystem 1K-blocks Used Available Use% Mounted on
  /dev/root 7871448 815076 6715860 11% /
  devtmpfs 1815648 0 1815648 0% /dev
  tmpfs 1947744 0 1947744 0% /dev/shm
  tmpfs 779100 10452 768648 2% /run
  tmpfs 4096 0 4096 0% /sys/fs/cgroup
  tmpfs 1947744 88 1947656 1% /tmp
  /dev/mmcblk0p1 65390 8630 56760 14% /boot

  Also, /etc/fstab:

  # cat /etc/fstab
  /dev/root / ext4 rw,noatime 0 1
  proc /proc proc defaults 0 0
  devpts /dev/pts devpts defaults,gid=5,mode=620,ptmxmode=0666 0 0
  tmpfs /dev/shm tmpfs mode=0777 0 0
  tmpfs /tmp tmpfs mode=1777 0 0
  tmpfs /run tmpfs mode=0755,nosuid,nodev 0 0
  sysfs /sys sysfs defaults 0 0
  /dev/mmcblk0p1 /boot vfat defaults,noatime,quiet 0 2

  There's also this in dmesg, not sure if this is maybe the (corrupt?) volume that should be mounted to /data?

  [ 5.472173] F2FS-fs (mmcblk0p4): Found nat_bits in checkpoint
  [ 5.576236] F2FS-fs (mmcblk0p4): inconsistent node block, nid:3, node_footer[nid:4294967295,ino:4294967295,ofs:536870911,cpver:18446744073709551615,blkaddr:4294967295]
  [ 5.576315] F2FS-fs (mmcblk0p4): Failed to read root inode

  fdisk:

  Device Boot Start End Sectors Size Id Type
  /dev/mmcblk0p1 * 1 131072 131072 64M c W95 FAT32 (LBA)
  /dev/mmcblk0p2 131073 16131072 16000000 7.6G 83 Linux
  /dev/mmcblk0p3 16131073 32131072 16000000 7.6G 83 Linux
  /dev/mmcblk0p4 32133120 62521343 30388224 14.5G 83 Linux

• 0
  
  HiFiBerry team August 23, 2021 11:09

  Looks like some SD card corruption. You might try another SD card.

• 0
  
  Philipp Leser-Wolf August 23, 2021 12:34

  I have picked up a new SD card and put a fresh OS image on it. The behavior is as follows: After startup the UI can be used for a very short time (10 seconds or so), after that the node process is at 100% CPU usage and the UI becomes unreachable.

  This is the same behavior as with the image on the other SD card.

  I tried launching the server app manually using

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

  but there is nothing in the log that seems like an error.

   

• 0
  
  Philipp Leser-Wolf August 23, 2021 14:31

  This might be a problem in my network setup. I deactivated the mDNS repeater (Avahi-based) in my pfSense router and that has "solved" the problem.

• 0
  
  HiFiBerry team August 23, 2021 14:32

  Ok, this is good to know. HiFiBerryOS uses mDNS for some things, but as long as your repeater didn't send the packages back to the same network, it should not be a problem.