Could not execute the Node.js binary. You may need to set the path to a working binary manually. #1214
Comments
|
Hello 👋 Thank you for taking the time to open this issue with recognize. I know it's frustrating when software I look forward to working with you on this issue |
|
Hi, I have just noticed I'm experiencing same issue witm my snap Nextcloud installation. It seems recognize failed after NC update in September. I've checked following issues:
I'm using Recognize ver. 7.1.0 with Nextcloud 29.0.9 installed via snap on Ubuntu 22.04.5 LTS Unfortunetly problem still persist. After changing paths log error: edit: in case choosing /var/snap/nextcloud/current/nextcloud/extra-apps/recognize/bin/node in Nextcloud log there is:
but binary file is present in the directory... Any ideas ? |
|
Yes, for me also, it started to fail in september 10/09/2024 Could not execute the Node.js binary. You may need to set the path to a working binary manually. |
|
Same error here. Tried to install my own Node binary and it won't use it. nextcloud.occ maintenance:repair gives the error: - Install recognize dependencies |
|
same error for me :-(
PATH is set to working node: /snap/bin/node bust still: |
|
A workaround might be to push a built binary of node, in the worst situation - statically linked, otherwise built for same distro as the libc is. There are Docker based build examples. |
|
"Latest Recognize versions, when in WASM mode, require Node.js 20, which in turn requires a version of glibc >= 2.28 (...) The nextcloud snap is still using glibc 2.27 (from core18), so Recognize's WASM mode won't work with the snap (...)" so concluding the only way is to use Tensorflow with GPU commands, but instructions are given only for NVIDIA (while I have Radeon...), or to wait until snap version of NC will be updated to use newer glibc... What I don't understand - in the same notice there is written that I should expect the same using Memories. In my case I use this app without problems. @szaimen is it maybe due to fact that Memories use Recognize for face recognition ? Anyway - it is another snap issue killing some functionalities (for instance Face Recognition App - no pdlib library aviable)... Probably it is a time to resign from Snap and install NC in direct way... |
Agreed. Docker containers are possible als alternative if you still like containerization. |
Which version of recognize are you using?
8.1.1
Enabled Modes
Face recognition, Object recognition
TensorFlow mode
GPU mode
Downstream App
Memories App
Which Nextcloud version do you have installed?
Nextcloud Hub 9 (30.0.2)
Which Operating system do you have installed?
Ubuntu 24.04.1 LTS
Which database are you running Nextcloud on?
mysql Ver 8.0.40 for Linux on x86_64 (Source distribution)
Which Docker container are you using to run Nextcloud? (if applicable)
it's a snap install
How much RAM does your server have?
Dynamic memory between 8 GB and 16 GB RAM
What processor Architecture does your CPU have?
x86_64
Describe the Bug
Nodejs stopped working after OS upgrade inside snap package Could not execute the Node.js binary. You may need to set the path to a working binary manually.
I tried to Set Library Path Manually LD_LIBRARY_PATH environment variable to include the directory where the libraries are located. For example:
export LD_LIBRARY_PATH=/usr/lib/x86_64-linux-gnu:$LD_LIBRARY_PATH
then I tried running the Node.js binary again, but still fails /var/snap/nextcloud/current/nextcloud/extra-apps/recognize/bin/node --version
I also tried to symlink the node from host in the recognize folder, but it does't work
root@nextcloud:/home/nextcloud# /root/.nvm/versions/node/v20.17.0/bin/node --version
v20.17.0
root@nextcloud:/home/nextcloud
Expected Behavior
Nodejs is working with ubuntu 24.04 and nextcloud snap version Nextcloud Hub 9 (30.0.2)
To Reproduce
Install Recognize in nextcloud snap version Nextcloud Hub 9 (30.0.2) with ubuntu 24.04
Debug log
Node.js
Could not execute the Node.js binary. You may need to set the path to a working binary manually.
If the shipped Node.js binary doesn't work on your system for some reason you can set the path to a custom node.js binary. Currently supported is Node v20.9 and newer v20 releases.
/snap/bin/node
For Nextcloud Snap users, you need to adjust this path to point to the snap's "current" directory as the pre-configured path will change with each update. For example, set it to "/var/snap/nextcloud/current/nextcloud/extra-apps/recognize/bin/node" instead of "/var/snap/nextcloud/9337974/nextcloud/extra-apps/recognize/bin/node"
The text was updated successfully, but these errors were encountered: