-
Notifications
You must be signed in to change notification settings - Fork 38
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
Very Helpful #1
Comments
I don't see why the cursor would be captured. Try and put a few echos into the script to see how far its coming and whether it stops somewhere. |
I have the same issue as kibbled, its stuck in this loop on "start" while { pid_of_spring_boot > /dev/null ; } && |
please check what the output of your server is when it boots up. The goal here is to find a line that says something like "Started XXX in Ys". Aparently your log levels are different which prevents this message from showing up. You might need to adapt your log levels or grep for some other log line to figure out whether the server has finished booting. |
Sorry, I'm not much of a bash scripter. But, here's the line I think you're grepping for: 2015-02-19 13:18:29.692 INFO 4044 --- [main] com.xxx.yyy.Application : Started Application in 18.421 seconds (JVM running for 19.248) I am using Spring Boot default logging, in my application.properties file I'm setting: |
the script expects the log file to go to
If you configure the app to some other log file, then you need to change this value.
|
Changing the grep -q fixed this issue. Thanks! |
Thanks for this template it was very helpful. One thing I have noticed with this script is that when I start my service: "sudo service my-spring-boot start" is that the cursor is not released so I have to hit CTRL-C. This is on Amazon's Linux (RHEL), any ideas?
Also for some reason the script has a hard time resolving the $JAVA_HOME, even root and the current user has it set (probably an environment issue). I just worked around this one by modifying the script.
The text was updated successfully, but these errors were encountered: