Thanks, Olaf, for your remarks. My first attempt to start tomcat9 as a service failed.
/opt/tomcat/logs is empty. This I find in syslog: 2026-10-08T15:19:48.039843+02:00 mail (artup.sh)[5205]: tomcat9.service: Failed to execute /opt/tomcat/bin/startup.sh: Permission denied Everything under /opt/tomcat is owned by root:root I have a user "tomcat". Also group "tomcat" is existing. /opt/tomcat/bin/startup.sh is -rw-r-x--- root. root Sep 10 08:55 startup.sh Any clues? Is the service started under user tomcat? Wouldn't be wrong. OTOH the tomcat tree should be owned by tomcat then. -- Christoph > Am 08.10.2026 um 15:12 schrieb Olaf Kock <[email protected]>: > > > Am 08.10.26 um 12:49 schrieb Christoph Kukulies via users: >> I'm planning to install (reinstall) tomcat9 on my Ubuntu 24.04 server. I had >> installed it manually before but since Ubuntu 24.04 the service got masked. >> >> When unpacking the tar distribution of tomcat9 it usually goes to >> /opt/tomcat(9) or this is at least the recommended location. In my >> /etc/tomcat9 directory >> there still is my configuration (server.xml). How do I best integrate my >> existing configuration into the newly installed one in /opt/tomcat? Symlink >> to server.xml? > > It's your decision how much you want to mirror the Unix-integration to have > all configuration files available in /etc, or if you accept to have all > tomcat9-related files in /opt/tomcat9. Personally, for a self-installed (and > updated) version, I'd either leave it all in one place (/opt/tomcat9), or > create a script for a repeatable installation (that extracts the files to the > same locations for future upgrades). > > Well, as I said "personally": I'd leave everything in /opt/tomcat9 (see below > for caveats). > > How to best integrate the existing settings? I'd diff the existing server.xml > against the downloaded one, and mirror whatever your personal settings are. > >> Are there other configurations files to take care of? > > Any and all that you have changed yourself. Again, a diff tool is your > friend. For your own installation, you might want to create bin/setenv.sh, > which can set environment variables. I'm not sure how and/or if this was > handled a different way in the Ubuntu package. > > Pay attention to repeatability (e.g. backup and documentation): The next > upgrade will overwrite all the files, including server.xml and webapps/ROOT, > if you just unzip it on top of the existing installation. Depending on your > preferences, you can make /opt/tomcat9 a symlink to /opt/tomcat-9.0.x and use > this as staging ground for upgrades, so that you never overwrite, but have > the opportunity to diff the next with the current version before you change > the symlink's target. > > Of course, when you make this a daemon, make sure to create a dedicated user > for it and don't run Tomcat as root. > > Olaf > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] >
