RBM
(René)
April 29, 2018, 11:20am
#1
This morning, Ropieee was stuck on the clock when playing audio. After reboot, it complained about Connection Failure. The extension has disappeared from Roon.
Flashed a new card – same story: no extension shown in Roon.
Feedback ID: 7bed9a59e3d6f597
Any ideas, @spockfish ?
seagull
(Wim)
April 29, 2018, 11:28am
#2
I had to enable the extension again. Maybe related to the update to v99?
RBM
(René)
April 29, 2018, 11:51am
#3
This appears to be the culprit:
Apr 29 13:48:31 ropieee systemd[1]: Starting RoPieee Remote Control...
-- Subject: Unit ropieee-remote.service has begun start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit ropieee-remote.service has begun starting up.
Apr 29 13:48:32 ropieee ropieee-remote[29230]: defaultZone = Living Roon
Apr 29 13:48:32 ropieee ropieee-remote[29230]: debugLog = 0
Apr 29 13:48:32 ropieee ropieee-remote[29230]: /opt/RoPieee/remotectl/node_modules/bindings/bindings.js:88
Apr 29 13:48:32 ropieee ropieee-remote[29230]: throw e
Apr 29 13:48:32 ropieee ropieee-remote[29230]: ^
Apr 29 13:48:32 ropieee ropieee-remote[29230]: Error: /opt/RoPieee/remotectl/node_modules/sd-notify/build/Release/notify.node: undefined symbol: _ZN2v816FunctionTemplate3NewEPNS_7IsolateEPFvRKNS_20FunctionCa>
Apr 29 13:48:32 ropieee ropieee-remote[29230]: at Object.Module._extensions..node (internal/modules/cjs/loader.js:707:18)
Apr 29 13:48:32 ropieee ropieee-remote[29230]: at Module.load (internal/modules/cjs/loader.js:589:32)
Apr 29 13:48:32 ropieee ropieee-remote[29230]: at tryModuleLoad (internal/modules/cjs/loader.js:528:12)
Apr 29 13:48:32 ropieee ropieee-remote[29230]: at Function.Module._load (internal/modules/cjs/loader.js:520:3)
Apr 29 13:48:32 ropieee ropieee-remote[29230]: at Module.require (internal/modules/cjs/loader.js:626:17)
Apr 29 13:48:32 ropieee ropieee-remote[29230]: at require (internal/modules/cjs/helpers.js:20:18)
Apr 29 13:48:32 ropieee ropieee-remote[29230]: at bindings (/opt/RoPieee/remotectl/node_modules/bindings/bindings.js:81:44)
Apr 29 13:48:32 ropieee ropieee-remote[29230]: at Object.<anonymous> (/opt/RoPieee/remotectl/node_modules/sd-notify/index.js:3:37)
Apr 29 13:48:32 ropieee ropieee-remote[29230]: at Module._compile (internal/modules/cjs/loader.js:678:30)
Apr 29 13:48:32 ropieee ropieee-remote[29230]: at Object.Module._extensions..js (internal/modules/cjs/loader.js:689:10)
Apr 29 13:48:32 ropieee systemd[1]: ropieee-remote.service: Main process exited, code=exited, status=1/FAILURE
Apr 29 13:48:32 ropieee systemd[1]: ropieee-remote.service: Failed with result 'exit-code'.
Apr 29 13:48:32 ropieee systemd[1]: Failed to start RoPieee Remote Control.
-- Subject: Unit ropieee-remote.service has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit ropieee-remote.service has failed.
spockfish
(Harry ten Berge)
April 29, 2018, 5:31pm
#4
Yes that’s the problem. My friends at ArchLinux updated stuff with results in this…
On it, will provide an update asap.
1 Like
spockfish
(Harry ten Berge)
April 29, 2018, 6:07pm
#5
Ok @RBM , update is out there (100). Would be great if you or @Dick_Vliek can report back whether it works for you guys.
spockfish
(Harry ten Berge)
April 29, 2018, 6:08pm
#7
No regular update, no need to reflash. Reboot is enough and wait for it for 20 minutes.
RBM
(René)
April 29, 2018, 6:13pm
#9
OK… Just rebooted. Connection failure screen again, but I’ll wait for the magic to happen in the background.
Dick_Vliek
(Dick Vliek)
April 29, 2018, 6:14pm
#10
Maybe you have to reanable the extension in roon settings, i had to
spockfish
(Harry ten Berge)
April 29, 2018, 6:14pm
#11
Sorry this took a day guys. I was out for some hiking and missed the first post by @Dick_Vliek .
Dick_Vliek
(Dick Vliek)
April 29, 2018, 6:15pm
#12
Whaat, you were superfast in my book
RBM
(René)
April 29, 2018, 6:17pm
#13
Nope – I checked. But it booted right through… So I guess it has not updated yet. GUI says 99 still.
No prob @spockfish – this all adds to the fun. Never wondered why you didn’t choose a more conservative distro for Ropieee?
BTW: Why does booting halt for ~2 mins on network config?
Dick_Vliek
(Dick Vliek)
April 29, 2018, 6:18pm
#14
I set the update interval to daily in the ropiee webinterface
RBM
(René)
April 29, 2018, 6:20pm
#15
Same here, Dick. I see next sync is scheduled for Sun 2018-04-29 20:26:55 CEST. That’s in 7 minutes.
1 Like
spockfish
(Harry ten Berge)
April 29, 2018, 6:23pm
#16
Yeah. The heuristics will change in the near future. As in: ‘daily’ means directly on boot.
spockfish
(Harry ten Berge)
April 29, 2018, 6:26pm
#17
The last point: are you by any change on wireless? I see it there too on my device.
Wrt to ArchLinux: yeah, I’ve could have gone for a more conservative distro, but that means (for the Pi at least) basically Debian which I consider not very healthy as every other solution is already using it.
However, I’m in the midst of resolving these issues by taking basically a ‘snapshot’ of ArchLinux. Idea is that if I do that a few times a year (say every quarter or so), I’m in control of what’s being pushed to the RoPieee devices and that software does not stop working ‘out of the blue’.
Dick_Vliek
(Dick Vliek)
April 29, 2018, 6:26pm
#18
Thx Harry, now renaming the host and on to install my second ropieee
RBM
(René)
April 29, 2018, 6:33pm
#19
Yup… Though I noticed it on wired as well, but for a shorter time. No biggie.
I just put Arch on my Core NUC (and like it quite a bit), but snapshotting with timed releases sounds like the ticket for an appliance like Ropieee.
BTW: Next Sync has changed to n/a, but there does not seem to be anything special going on on the Pi. What should the update process look like?
spockfish
(Harry ten Berge)
April 29, 2018, 6:34pm
#20
please reload the webpage. I think it’s already done.