trying to install 3.1.2 on Companion Pi. Configuration page load crashes repeatedly.
any ideas?
24.01.27 22:04:42 Instance/ModuleHost: Instance “yamaha-CLQL” failed to init: Error: Call timed out Error: Call timed out
at t.IpcWrapper.sendWithCb (/opt/companion/main.js:2:2165956)
at Object.init (/opt/companion/main.js:2:7902222)
at l. (/opt/companion/main.js:2:7911209)
at l.emit (node:events:514:28)
at l.emit (node:domain:489:12)
at ChildProcess. (/opt/companion/main.js:2:2153461)
at ChildProcess.emit (node:events:514:28)
at ChildProcess.emit (node:domain:489:12)
at emit (node:internal/child_process:937:14)
at process.processTicksAndRejections (node:internal/process/task_queues:83:21)
Copy that. Have you tried the companion beta 3.2.2?
Basically, companion is timing out trying to load the module, which can happen on low power RPIs, which is why I was asking. An RPI4 with 4g shouldn’t have a problem.
Might be a bug fixed in the beta, so give it a try if you can.
Well, 3.2.2 now.
Still the same. There is no desk in the network now though.
24.04.15 12:33:49 Instance/ModuleHost: Instance “yamaha-CLQL” failed to init: Error: Call timed out Error: Call timed out
at t.IpcWrapper.sendWithCb (/opt/companion/main.js:2:2450560)
at se.init (/opt/companion/main.js:2:2792889)
at l.s (/opt/companion/main.js:2:2803654)
at l.emit (node:events:517:28)
at l.emit (node:domain:489:12)
at ChildProcess. (/opt/companion/main.js:2:2437855)
at ChildProcess.emit (node:events:517:28)
at ChildProcess.emit (node:domain:489:12)
at emit (node:internal/child_process:944:14)
at process.processTicksAndRejections (node:internal/process/task_queues:83:21)
24.04.15 12:33:49 Instance/ModuleHost: Unhandled error restarting connection: Error: Restart forced
Weird!
Desktop version of Companion seems to still be fine, so not sure what the issue is.
Can you send me the “support bundle” so I can see if there’s a hint in the logs as to what’s going wrong?
Trying to get the MIDI running in 3.5.4 . Module is in Dev folder and loaded, but configuration can’t start with this error:
25.04.25 17:58:53 Instance/ModuleHost: Instance “yamaha-MIDI” failed to init: Error: Call timed out Error: Call timed out
at t.IpcWrapper.sendWithCb (/opt/companion/main.js:2:2761785)
at k.init (/opt/companion/main.js:2:3649235)
at V.o (/opt/companion/main.js:2:3664316)
at V.emit (node:events:524:28)
at ChildProcess. (/opt/companion/main.js:2:3661428)
at ChildProcess.emit (node:events:524:28)
at emit (node:internal/child_process:949:14)
at process.processTicksAndRejections (node:internal/process/task_queues:91:21)
25.04.25 17:58:53 Instance/ModuleHost: Unhandled error restarting connection: Error: Restart forced
Is this giving any clue? Same happens with the sysex Module.
The RCP module is trying to connect to a console at 192.168.1.128 and it’s not seeing it.
The CLQL module is crashing, but you’re running an old version. You should try the latest from here, 3.1.3.
When I copied the support bundle the console was linked to my computer. IP was correct.
I will try the newer module next time I get a hand on a CL/QL (or would DM3 be enough to test it?).
Thanks for your efforts.
The RCP module will work with the CL/QL, TF, DM3, DM7 and Rivage. The CLQL module (only available from this website) will ONLY work with the CL and QL consoles.
Hi Andy,
just to let you know: I have upgraded my CompanionPi to 4.0 (running on RasPi4)
I have updated the CLQL Midi Module to 3.1.3 by putting it into the dev module folder.
But still no luck: Help page shows 3.1.3. but I still get a “Connection config unavailable” “Retry” error and can’t type in any configuration.
Log is showing:
25.06.10 21:58:12 Instance/ModuleHost : Failed to get module api version: “-oLv2IIIQ9glvRH8BcB9q” Error: Cannot find module ‘@companion-module/base/package.json’ Require stack: - /home/runner/work/companion/companion/companion/dist/Instance/Host.js
Does this give you any hint what is going wrong here?
I just have reset my companion 4.0 config on my MacBookPro M1Max to factory default and installed 3.1.3. No luck, doesn’t work, same error. RCP is starting up but missing a console (none at home).
It leaves me absolutely clueless. It worked one day (remember when I froze my desk on a job?) but now on no machine? This makes me feel like I am missing something very basic here.
I did this at 8:43. Please see that the API key has changed but the error persisted.
25.06.11 08:42:03 Instance/ModuleHost: Failed to get module api version: “TgXQhZWpMMZAm6Fle8PYz” Error: Cannot find module ‘@companion-module/base/package.json’ Require stack: - /Users/runner/work/companion/companion/companion/dist/Instance/Host.js
25.06.11 08:44:14 Instance/ModuleHost: Failed to get module api version: “kKKGvfhFryZUCwWqIgjnO” Error: Cannot find module ‘@companion-module/base/package.json’ Require stack: - /Users/runner/work/companion/companion/companion/dist/Instance/Host.js
I am now able to reproduce the problem. The module will work on 3.5 (with a small change), but it fails in the way you describe on v4.x.
It’s something in the way Companion is bundling the module that v4 doesn’t like. Thank you for reporting this and for your patience while I get to the bottom of this issue!