Hello Aaron, I'm glad port issue was resolved. According to startup/shutdown these scripts are bundled with Tomcat and should work I'm planning to investigate what is wrong, since it affects demo server (I'm using Ubuntu and something like this should work [1]) Unfortunately my time is very limited these days :(
What I already have tried: 1) use catalina.sh to start Tomcat, provide valid CATALINA_PID 2) use `kill -9 <with-saved-pid>` for some reason this is not working right now (was working as expected) and this method will not work on non-debian distros and other OSes Additional investigation is required [1] https://linuxize.com/post/how-to-install-tomcat-9-on-ubuntu-18-04/ On Fri, 18 Jan 2019 at 19:15, Aaron Hepp <aaron.h...@gmail.com> wrote: > downloaded and unzipped the latest nightly build for OM5 (#2690). cd to > /opt/om5/bin and ran sh startup.sh. Service started up and nmap showed > port 5080 and 8009 listening. Redirection worked to port 5443. Issue I > was having with the cert not working was failed to change the password for > the keystore file in server.xml. Once that changed no longer had the bad > cert error. I was able to change the default ports in server.xml and > listening and redirection worked fine. > > Question are you supposed to start and stop using the startup.sh and > shutdown.sh files in om5/bin? startup works fine and gets it running, but > when running shutdown it stops listening on the ports, but leaves java > process running in the background. If you run startup again it creates a > second java process (see attached), and each time you shutdown and start it > creates a new. > > -- WBR Maxim aka solomax
