Constant restarts with rooExtend

Audio Gear Talk rooExtend
1

Using rooExtend 3.3.1 (either with rooNuimo or rooDial) on a Raspberry Pi 4 hardwired to switch.

I’ve noticed that rooExtend got stuck in a loop of exiting abnormally and restarting afterwards. There might be some time in between loops where it’s working again, but the cycle may also repeat itself rapidly. In the logs I see many occurrences of the following:

    Feb 07 22:09:49 isis systemd[1]: Started rooExtend service.
    Feb 07 22:09:49 isis rooExtend[7335]: Verifying archive integrity...
    Feb 07 22:09:50 isis rooExtend[7373]: [160B blob data]
    Feb 07 22:09:50 isis rooExtend[7335]:  MD5 checksums are OK. All good.
    Feb 07 22:09:50 isis rooExtend[7335]: Uncompressing rooExtend
    Feb 07 22:09:52 isis rooExtend[7435]: [160B blob data]
    Feb 07 22:09:52 isis rooExtend[7490]: --------------------------------------------------
    Feb 07 22:09:52 isis rooExtend[7490]: rooExtend 3.3.1 started...
    Feb 07 22:09:52 isis rooExtend[7490]: Config Path:   /config.json
    Feb 07 22:09:52 isis rooExtend[7490]: Hostname:      isis
    Feb 07 22:09:52 isis rooExtend[7490]: Restarted:     true
    Feb 07 22:09:52 isis rooExtend[7490]: Timesync:      skipped, restated
    Feb 07 22:09:52 isis rooExtend[7490]: Ethernet:       not connected
    Feb 07 22:09:54 isis rooExtend[7490]: Has Bluetooth: true hci0 UART D8:3A:DD:0F:49:4D
    Feb 07 22:09:54 isis rfkill[7557]: unblock set for id 1
    Feb 07 22:09:54 isis rooExtend[7490]: TV name:       --
    Feb 07 22:09:54 isis rooExtend[7490]: Found:         Raspberry Pi 4 Model B Rev 1.5
    Feb 07 22:09:54 isis rooExtend[7490]: Production:    true
    Feb 07 22:09:54 isis rooExtend[7490]: Interface:     wlan0
    Feb 07 22:09:54 isis rooExtend[7490]: Has WiFi:      true
    Feb 07 22:09:54 isis rooExtend[7490]: Is NanoPi:     false
    Feb 07 22:09:54 isis rooExtend[7490]: Has Linux 64:  true
    Feb 07 22:09:54 isis rooExtend[7490]: Has GPIO:      true
    Feb 07 22:09:54 isis rooExtend[7490]: --------------------------------------------------
    Feb 07 22:09:54 isis rooExtend[7490]: init LED
    Feb 07 22:09:54 isis rooExtend[7490]: ##### Start: License Manager
    Feb 07 22:09:54 isis rooExtend[7490]: ***** Started HTTP-Server at Port :80
    Feb 07 22:10:15 isis rooExtend[7490]: ***** rooExtend got paired with CORE
    Feb 07 22:10:28 isis rooExtend[7490]: ----- License Manager initialized...
    Feb 07 22:10:28 isis rooExtend[7490]: ##### Stop: Network Audio
    Feb 07 22:10:28 isis rooExtend[7490]: ##### Stop: Roon Bridge
    Feb 07 22:10:28 isis rooExtend[7765]: ***** set HighSpeed 0
    Feb 07 22:10:28 isis rooExtend[7765]: ##### Start: rooDial 1.5.7
    Feb 07 22:10:28 isis rooExtend[7765]: ***** events disconnected
    Feb 07 22:10:28 isis rooExtend[7765]: ***** rooDial got paired with CORE
    Feb 07 22:11:07 isis rooExtend[7765]: ***** startEventCapture
    Feb 07 22:11:08 isis rooExtend[7765]: ***** set HighSpeed 1
    Feb 07 22:11:08 isis rooExtend[7765]: ***** set HighSpeed 1
    Feb 07 22:15:35 isis rooExtend[7765]: +++++++++++++++++++++++++ TIMEOUT ++++++++++++++++++++++
    Feb 07 22:15:36 isis rooExtend[7490]: +++++++++++++++++++++++++ TIMEOUT ++++++++++++++++++++++
    Feb 07 22:15:36 isis systemd[1]: rooExtend.service: Main process exited, code=exited, status=1/FAILURE
    Feb 07 22:15:36 isis systemd[1]: rooExtend.service: Failed with result 'exit-code'.
    Feb 07 22:15:36 isis systemd[1]: rooExtend.service: Consumed 14.966s CPU time.
    Feb 07 22:15:46 isis systemd[1]: rooExtend.service: Scheduled restart job, restart counter is at 9.
    Feb 07 22:15:46 isis systemd[1]: Stopped rooExtend service.
    Feb 07 22:15:46 isis systemd[1]: rooExtend.service: Consumed 14.966s CPU time.

It’s only the second time or so I’ve observed this behavior. Can’t recall when I first noticed it, but it was quite a while back. Any idea what might cause this and how to fix?

2

Temperature based restarts maybe?

3

Temperature of the device is reported as 36° by rooExtend. I have the feeling the device itself is also not rebooting. Just the service.

4

@DrCWO can you weigh in?

5

Whi h release of rooExtend, wired or WiFi, which Pi?
I Need more information…

Edit:
Timeout means an internet connection issue…

6

See initial post: 3.3.1, wired, rpi 4

That’s odd, but not ruling it out. All devices on the same switch don’t seem to experience an issue (verified by running an infinite ping to the internet).

I’ve temporarily replaced the rooExtend rpi with another rpi 4 (non rooExtend) while the restarts were happening. Ran some pings from that device and it doesn’t show any connection issue (nor do the other devices in my home network).

7

Strangly enough the logs (see excerpt in original post) say it’s using wlan0 and that ethernet is not connected. That is odd, because I’m pinging the ip address of the ethernet port.

8

Now I also saw that :thinking:
Please reboot the Pi. If it discoveres Ethernet it should use this. Maybe flashing a fresch SD card might ne a good idea…