https://bugzilla.redhat.com/show_bug.cgi?id=1051743
Bug ID: 1051743 Summary: tomcat-jsvc service fails to start server Product: Fedora Version: 19 Component: tomcat Assignee: ivan.afonichev@gmail.com Reporter: wdouglascampbell@hotmail.com QA Contact: extras-qa@fedoraproject.org CC: akurtako@redhat.com, ivan.afonichev@gmail.com, java-sig-commits@lists.fedoraproject.org, krzysztof.daniel@gmail.com
Description of problem:
Systemd does not successfully start tomcat daemon after upgrade to fc19
Version-Release number of selected component (if applicable):
tomcat-jsvc-7.0.47-1.fc19.noarch
How reproducible:
Always fails to work since upgrade.
Steps to Reproduce: 1. systemctl start tomcat-jsvc.service 2. 3.
Actual results:
No response. No Tomcat running. The following line appears to catalina.out:
Service exit with a return value of 143
Expected results:
Tomcat server daemon running
Additional info:
While this isn't working using system, if I type:
/usr/sbin/tomcat-jsvc-sysd start
the tomcat daemon starts and works fine.
https://bugzilla.redhat.com/show_bug.cgi?id=1051743
--- Comment #1 from wdouglascampbell@hotmail.com --- Upgraded to FC20, problem persists. It actually got worse as I had to modify /usr/sbin/tomcat-jsvc to explicitly set TOMCAT_USER and CATALINA_BASE as otherwise they are empty and cause even my workaround to fail.
https://bugzilla.redhat.com/show_bug.cgi?id=1051743
--- Comment #2 from Ivan Afonichev ivan.afonichev@gmail.com --- Yes on FC20 jsvc support was degradated. But it is strange that it is not works on FC19.
https://bugzilla.redhat.com/show_bug.cgi?id=1051743
--- Comment #3 from wdouglascampbell@hotmail.com --- One more thing to note after the upgrade to FC20 is that tomcat does start after a long wait on the initial system boot now BUT if I try to stop it using the systemctl stop tomcat-jsvc.service, it fails and I cannot restart it using this method and even if I kill the processes and try to start using systemctl, it fails.
I also notice that the /var/run/tomcat.pid file is empty. I thought it usually should contain the pid of the tomcat process. I mention it in case it is helpful.
---
Your comment came in as I was typing. Why was it degradated? Any good option for me since I use this?
Thanks!
https://bugzilla.redhat.com/show_bug.cgi?id=1051743
--- Comment #4 from Ivan Afonichev ivan.afonichev@gmail.com --- We will work to restore this feature, as it is appeared to be used by you and may be others.
As an option you can consider using some frontend server on your privileged ports, like nginx or httpd, and use tomcat as backend server behind of them. Or use iptables to nat your privileged ports to tomcat's unprivileged. Or use xinetd to redirect traffic of your privileged ports to tomcat's unprivileged.
We can create tomcat-nginx and/or tomcat-httpd subpackages with tomcat frontend vhosts for nginx and/or httpd if you think it would be helpful.
I think using frontend server is generally the best solution, much better then using jsvc. But nevertheless I'll try to restore it in F19 and F20 too.
https://bugzilla.redhat.com/show_bug.cgi?id=1051743
--- Comment #5 from wdouglascampbell@hotmail.com --- If you can restore the functionality that would be great. Thanks!
https://bugzilla.redhat.com/show_bug.cgi?id=1051743
--- Comment #6 from Fedora End Of Life endoflife@fedoraproject.org --- This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'.
Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
https://bugzilla.redhat.com/show_bug.cgi?id=1051743
Fedora Update System updates@fedoraproject.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |MODIFIED
https://bugzilla.redhat.com/show_bug.cgi?id=1051743
--- Comment #7 from Fedora Update System updates@fedoraproject.org --- tomcat-7.0.59-1.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/tomcat-7.0.59-1.fc21
https://bugzilla.redhat.com/show_bug.cgi?id=1051743
Fedora Java SIG java-sig-commits@lists.fedoraproject.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC|java-sig-commits@lists.fedo | |raproject.org |
Fedora Update System updates@fedoraproject.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|MODIFIED |ON_QA
--- Comment #8 from Fedora Update System updates@fedoraproject.org --- Package tomcat-7.0.59-1.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing tomcat-7.0.59-1.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-2109/tomcat-7.0.59-1.fc2... then log in and leave karma (feedback).
java-sig-commits@lists.fedoraproject.org