-
Notifications
You must be signed in to change notification settings - Fork 4
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
CentOS 6.7 (and possibly others) incompatibility of the jsvc
binary shipped with capsule-daemon
#6
Comments
I uploaded a new |
Please forgive my ignorance but what is the best method to acquire the 0.2.0-SNAPSHOT? Thanks! :) |
No problem. For Gradle just add SonaType shapshots to your repositories:
|
I've been testing the new 0.2.0-SNAPSHOT build and jsvc no longer complains about GLIBC_2.14 not being found. Jsvc now appears to correctly launch however it later fails with the error message:
I'm not sure if this is a problem with jsvc (which appears to be running correctly) or my own application "aridmud-1.0-SNAPSHOT". Although I think this is most likely a problem with my application code or server configuration. I will keep testing and keep you updated. Full output:
|
I've just reproduced the same issue so I don't think it's a problem with your app, rather the static binary solution might not work. I'll have a further look. |
…ded one through the `capsule.daemon.jsvc` property (#6)
I've just published a new Thanks, supporting our users is a pleasure. |
I compiled a local version of jsvc and tested your new feature '''Dcapsule.daemon.jsvc''. |
Excellent! I'll leave the issue open as OS (and binary) detection can be improved (and/or possibly a |
jsvc
binary shipped with capsule-daemon
I've noticed something a little strange with the latest 0.2.0-SNAPSHOT.
|
Is this happening only with the latest |
Unfortunately I only have the latest SNAPSHOT running successfully under Linux and so I'm unable to test any previous versions to compare them. However, from reading the jsvc documentation that you linked it does look like expected behavior. EDIT: |
Hi there,
I'm experiencing a compatibility issue with capsule-daemon and CentOS 6.7.
When executing my capsule.jar I receive the following error message:
I believe this is occurring because the jsvc executable that is embedded in capsule-daemon is not compatible with the version of glibc that CentOS 6.7 uses. If this is the case would it be possible to either embed a compatible version of jsvc in capsule-daemon or allow the user to specify an external jsvc executable?
CentOS release 6.7 (Final)
x86_64 GNU/Linux
GLIBC version: 2.12-1.166.el6_7.3
Many thanks for your assistance :)
The text was updated successfully, but these errors were encountered: