-
Notifications
You must be signed in to change notification settings - Fork 104
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In APE_Server-1.1.2-i386.bin, on running aped getting error.. Failed to load ../modules/lib/libmod_spidermonkey.so #56
Comments
Probably the compiled library was build on a system with MySQL support available. Try installing the mysql lib package ( I'll see when I get a minute if I can upload a binary without MySQL support. A more permanent fix would be to have APE check if MySQL is available while the server is starting and load the correct module. If someone knows how to code that 😅 |
The version number is fine. I remember the version number was not changed. You can see this in /Source/Core/Ape.js As for the error, check server log and make sure you updated the server side scripts.
|
Thanks. Now both the server and client are working. Is there a way to get rid of the frequency getting added to the ape server url. Can this be made optional. http://0.ape.local.ape-project.org:6969/ |
No, this is required for sessions support. You could edit the JSF source code if you don't plan on using sessions support. Envoyé de mon iPhone
|
In APE_Server-1.1.2-i386.bin, on running aped getting error.
[Module] Failed to load ../modules/lib/libmod_spidermonkey.so [Invalid library](libmysqlclient_r.so.16: cannot open shared object file: No such file or directory)
I am currently using APE Server 1.1, I don't have any issues in using the current version. After so many years found a new version. Thought there will be improvements but i could not upgrade to latest stable version.
I don't connect to MySQL / execute any MySQL query in my APE Client but why the spider monkey is looking for mysql client.
Can you please help me to resolve this issue.
The text was updated successfully, but these errors were encountered: