Welcome to Knowage Q&A, where you can ask questions and receive answers from other members of the community.
0 votes
1 view
Hi

I wanted to use a python script unfortunately knowage checks the wrong directory for a python install

The error is

java.lang.UnsatisfiedLinkError: Can't load library: /home/spagobi/PythonJpy/jpy/build/lib.linux-x86_64-3.4/jpy.cpython-34m.so

The user spagobi doesn't exist for me after the installation of knowage. Where can I set the correct paths for python in Knowage? Or what do I have to install?
Python is correctly installed also other programs find it under the correct path
in Analyses by (710 points)
The same bug seems to exist also for the docker image

https://github.com/KnowageLabs/Knowage-Server-Docker/issues/4

If somebody good tip me where to adjust the python environment i would be very thankful.

1 Answer

+1 vote

Please find update the documentation on readthedocs at the following link:

https://knowage.readthedocs.io/en/latest/admin/README/index.html#integration-with-python-environment

by (15.2k points)
Thanks a lot.

Will try it this week.

Well the problem for me seems that I still can't press the execute demo button:

When I click it I get this Jacascript error:

SyntaxError: Unexpected token < in JSON at position 0
    at JSON.parse (<anonymous>)
    at fromJson (angular.js:1271)
    at defaultHttpResponseTransform (angular.js:9694)
    at angular.js:9785
    at forEach (angular.js:340)
    at transformData (angular.js:9784)
    at transformResponse (angular.js:10553)
    at processQueue (angular.js:15054)
    at angular.js:15070
    at Scope.$eval (angular.js:16321)

So I don't think the backend gets ever tested. Any Idea how I can fix this to test thy python configuration?

So I installed everything and now have the following error:

Can't load library: /home/spagobi/PythonJpy/jpy/build/lib.linux-x86_64-3.4/jpy.cpython-34m.so

This is due to me not using Python 3.4 but Python 3.5.

This is what it says in the manual:

You will need: - Python 3.3 or higher (3.2 may work as well but is not tested

So I guess something is hardcoded to check for 3.4? Also it says it was only tested under 3.4.

Will this be fixed and is there any news on a new docker release? On the Github issue it says a new version is expected in March.

Kind regards

Did you follow alla the steps? In particular, what it seems to be missing is 

To use JPY you need to replace the jpyconfig.properties file on your project, with the one generated by the build process that is present in your JPY built folder jpy-master\build\lib.<SO-CPU-PYTHON_versions>. 
Properties file to replace is located in knowagedataminingengine\src\. 
For some reason my knowagedataminingengine directory has no src directory and the bigger problem is that no file named jpyconfig.properties exists in the jpy install. Guess I will have to rebuild it...
Btw for the docker image there is no release date yet in sight?
Ok I rebuild it with the instructions from the jpy git page and now everything works.

Unfortunately I still have the same error as above.

The correct jpyconfig.properties file is in the directory now and the paths are correct.
...