I am getting the following error when I'm starting GenieACS cwmp
. I have also tried to rebuild several times.
Error: Could not locate the bindings file. Tried:
→ /usr/local/lib/node_modules/genieacs/node_modules/libxmljs/build/xmljs.node
→ /usr/local/lib/node_modules/genieacs/node_modules/libxmljs/build/Debug/xmljs.node
→ /usr/local/lib/node_modules/genieacs/node_modules/libxmljs/build/Release/xmljs.node
→ /usr/local/lib/node_modules/genieacs/node_modules/libxmljs/out/Debug/xmljs.node
→ /usr/local/lib/node_modules/genieacs/node_modules/libxmljs/Debug/xmljs.node
→ /usr/local/lib/node_modules/genieacs/node_modules/libxmljs/out/Release/xmljs.node
→ /usr/local/lib/node_modules/genieacs/node_modules/libxmljs/Release/xmljs.node
→ /usr/local/lib/node_modules/genieacs/node_modules/libxmljs/build/default/xmljs.node
→ /usr/local/lib/node_modules/genieacs/node_modules/libxmljs/compiled/0.10.25/linux/x64/xmljs.node
at bindings (/usr/local/lib/node_modules/genieacs/node_modules/libxmljs/node_modules/bindings/bindings.js:88:9)
at Object. (/usr/local/lib/node_modules/genieacs/node_modules/libxmljs/lib/bindings.js:1:99)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Module.require (module.js:364:17)
at require (module.js:380:17)
at Object. (/usr/local/lib/node_modules/genieacs/node_modules/libxmljs/index.js:4:16)
at Module._compile (module.js:456:26)
18 Dec 18:34:26 - Worker 7837 died (8)
I spoke to the developer, and he said that it was a bug in node-gyp, you should simply do the following:
npm install node-gyp
if that didn't solve the issue, then you can install libxmljs again just to be sure
npm install libxmljs
i just tried it, worked like a charm
I had this issue before
I downgraded the dependency of libxmljs to @0.11.0 (package.json) and ran sudo npm install libxmljs
I did all the actions from this thread and many others but without success. then I just removed my 'node_modules' folder and run "npm install" again an it solved an issue. So you can also try this ;)
I just went around the houses to resolve this issue.
I was using PM2 and had multiple node apps running on the one server, I'm not sure why, but when I killed all the apps and then did an 'npm i' in the troublesome project, it all went through fine. No sudo, no deleting node_modules and all running the latest version of node.
Hope this helps
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With