3 ms·
> it took a 10 line unit file to get YouTrack configured as a proper service on my CentOS 7 VM If you did it the way that other people have done it, wrapping y
by JdeBP 10y ago
> it took a 10 line unit file to get YouTrack configured as a proper service on my CentOS 7 VM
If you did it the way that other people have done it, wrapping youtrack.sh start and youtrack.sh stop in a systemd service unit, with a sprinkling of erroneous Type=forking to get around the fact that that ends up running the Java process as a quickly orphaned grandchild of where systemd expects the daemon to be, and with log output explicitly redirected away from where service management could handle it into an ever-growing private log file under /usr ... then you have entered systemd House of Horror territory. "proper" is not really the word.
* http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/systemd-house-of-horror/ http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/sy...
* http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/systemd-house-of-horror/tomcat.html http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/sy...
- snuxoll 10y agoI initially tried the Type=forking method, but systemd kept yelling at me (as it should have) because it doesn't really fork correctly. I actually just run the service in simple mode with a launcher script that contains this abomination of a command: /opt/jetbrains/youtrack/internal/java/linux-x64/jre/bin/java -Dlauncher.app.home=/opt/jetbrains/youtrack/ -Djl.service=YouTrack -Djl.home=/opt/jetbrains/youtrack -ea -XX:+HeapDumpOnOutOfmoryError -XX:HeapDumpPath=logs -XX:ErrorFile=logs/hs_err_pid%p.log -Dfile.encoding=UTF-8 -XX:MaxMetaspaceSize=250m -Xmx1024m -Dorg.eclipse.jetty.server.Request.maxFormContentSize=5000000 -Dorg.eclipse.jetty.server.Request.maxFormKeys=10000 -Djetbrains.jetpass.admin.name=default_admin_name -jar launcher/lib/app-wrapper/app-wrapper.jar AppStarter com.jetbrains.bundle.bootstrap.Bundle
- JdeBP 10y agoJust remember to do things the daemontools way, and chain to the final daemon binary from that script with the shell's exec command, and systemd should be happy. Contrast: * https://plone.lucidsolutions.co.nz/software-development/issue-tracking/youtrack/youtrack-v6.5-on-centos-7.1-as-a-zip-install https://plone.lucidsolutions.co.nz/software-development/issu... And the redirection to $LOG and Poor Man's Daemon Supervisor in some people's youtrack.sh: * https://www.howtoforge.com/running-youtrack-issue-and-project-tracking-tool-on-nginx-debian-wheezy https://www.howtoforge.com/running-youtrack-issue-and-projec...