epam / Indigo-ELN-v.-2.0

Indigo - The Open-Source Chemistry Electronic Lab Notebook
MIT License
25 stars 18 forks source link

Server side missing indigo: Unable to load library '.../libindigo.so': Native library not found in resource path #9

Closed bazitur closed 5 days ago

bazitur commented 1 year ago

Hi, I managed to get the whole bundle up and running using docker compose up. However, I have encountered a problem regarding what seems to be an error on the side of Indigo toolkit: whenever I try to save or import a structure in the Ketcher editor, nothing seems to happen. For example, nothing changes in the reaction scheme window: image At the same time, JS browser console and terminal log the same error, here is a link to a gist. It seems that somehow ELN application cannot locate Indigo library.

I've tried tinkering around the code, but I wasn't able to resolve this probem. Any help would be greatly appreciated!

HeDo88TH commented 1 year ago

I encountered this error too. Is there a solution? @mkviatkovskii

saurabhgayali commented 7 months ago

I encountered this error too. Is there a solution? @mkviatkovskii

Could you provide proper link!

bdeadman commented 4 months ago

I have also encountered this issue recently. I don't have a fix, but my suspicion is a problem with the BingoDB cartridge. Text, numerical and files are all saved to the DB, but the chemical structures (from Ketcher) aren't getting into the DB. As reported by others, I see the same error when attempting to save a Ketcher structure to the ELN:

2024-04-10 17:00:37 indigoeln-server-1 | java.lang.UnsatisfiedLinkError: Unable to load library '/tmp/indigo8da420a34c5340161cbe4c60a8df4dc8/libindigo.so': Native library (tmp/indigo8da420a34c5340161cbe4c60a8df4dc8/libindigo.so) not found in resource path

denis-dzenskevich commented 5 days ago

Fixed by https://github.com/epam/Indigo-ELN-v.-2.0/pull/15

saurabhgayali commented 4 days ago

the problem did not encounter in docker version.

denis-dzenskevich commented 4 days ago

@saurabhgayali Do you mean it's fixed now under docker? Or it never appeared under docker? If latter, I had the same error with docker until it was fixed

saurabhgayali commented 2 hours ago

@saurabhgayali Do you mean it's fixed now under docker? Or it never appeared under docker? If latter, I had the same error with docker until it was fixed

Docker has all obsolete versions. In other words, docker version never had the problem. There is separate issue there with chemical structure, but I have raised a separate ticket for that.