Skip to content
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

CAS service start failed on Ubuntu 14.04 #253

Closed
dmogn opened this issue Jan 17, 2017 · 1 comment
Closed

CAS service start failed on Ubuntu 14.04 #253

dmogn opened this issue Jan 17, 2017 · 1 comment
Labels
bug issue in existing feature or functionality
Milestone

Comments

@dmogn
Copy link
Contributor

dmogn commented Jan 17, 2017

GLUU.root@ce:# service cas start
Starting Jetty: FAILED Tue Jan 17 15:09:12 UTC 2017
GLUU.root@ce:
# service cas stop
Stopping Jetty: start-stop-daemon: warning: failed to kill 3386: No such process
1 pids were not killed
No process in pidfile '/var/run/cas.pid' found running; none killed.
OK
GLUU.root@ce:~#

No files in ...../cas/logs/ directory.

@yurem told me, that on redhat the service works well, so the problem is ubuntu-specific.
The problem detected since ~ 3.0.0 beta2. Early builds works well.

PS. CAS will be removed in v3.1 #247.

@dmogn dmogn added this to the CE 3.0.0 milestone Jan 17, 2017
@dmogn dmogn added the bug issue in existing feature or functionality label Jan 17, 2017
@yurem
Copy link
Contributor

yurem commented Jan 18, 2017

I fixed this in: bccaee7

It happened when we installed all CE components with 3Gb only: As result java parameters were wrong:
-Xms256m -Xmx153m

After fix:
-Xms128m -Xmx153m

2.Beta3 contains this fix

Also lack of VM memory led to random applications shutdowns when during CE initial we specified more memory than VM can physically allocate.

@yurem yurem closed this as completed Jan 18, 2017
madumlao pushed a commit to madumlao/gluu-community-edition-setup that referenced this issue Mar 7, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug issue in existing feature or functionality
Projects
None yet
Development

No branches or pull requests

2 participants