Process: 9754 ExecStart=/opt/tomcat/bin/startup.sh (code=exited, status=0/SUCCESS) Process: 9767 ExecStop=/bin/kill -15 $MAINPID (code=exited, status=1/FAILURE) Loaded: loaded (/etc/systemd/system/rvice enabled vendor preset: disabled)Īctive: activating (auto-restart) (Result: exit-code) since Sun 12:49:15 UTC 3s ago I get this output from 'systemctl status tomcat -l': rvice - Apache Tomcat Web Application Container Then if I run it like this: systemctl daemon-reload I added this file to /etc/systemd/system/rvice: ĭescription=Apache Tomcat Web Application ContainerĮnvironment=JAVA_HOME=/usr/local/jdk-11.0.1Įnvironment=CATALINA_PID=/opt/tomcat/temp/tomcat.pidĮnvironment='CATALINA_OPTS=-Xms512M -Xmx1024M -server -XX:+UseParallelGC'Įnvironment='JAVA_OPTS=true =file:/dev/./urandom'
Sudo chown -R tomcat webapps/ work/ temp/ logs/ #Make tomcat user ownership of required directories #Give tomcat user execute access and reursive read access to conf #Give tomcat group recursive ownership of the installation directory Tar -zxvf apache-tomcat-9.0.14.tar.gz -C /opt/tomcat/ -strip-components=1 Sudo useradd -m -g tomcat -d /opt/tomcat -s /bin/nologin tomcat #Add Tomcat user, creating a home directory. I have set up downloaded and installed Tomcat with this script: #Add Tomcat group Whereas if I manually call startup.sh then it's fine.
When running 'sudo systemctl start tomcat', it seems to call shutdown.sh immediately after startup.sh: Feb 03 19:36:49 xxxxx startup.sh: Tomcat started.įeb 03 19:36:49 xxxxx shutdown.sh: NOTE: Picked up JDK_JAVA_OPTIONS: -add-opens=java.base/java.lang=ALL-UNNAMED -add-opens=java.base/java.io=ALL-UNNAMED -add-opens=java.rmi/=ALL-UNNAMEDįeb 03 19:36:54 xxxxx shutdown.sh: 7:36:53 PM .Catalina stopServer
0 kommentar(er)
