Bug 1051743 - tomcat-jsvc service fails to start server
Summary: tomcat-jsvc service fails to start server
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: tomcat
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ivan Afonichev
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-11 06:54 UTC by wdouglascampbell
Modified: 2015-02-23 08:02 UTC (History)
2 users (show)

Fixed In Version: tomcat-7.0.59-1.fc21
Clone Of:
Environment:
Last Closed: 2015-02-18 11:19:37 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description wdouglascampbell 2014-01-11 06:54:28 UTC
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.

Comment 1 wdouglascampbell 2014-01-11 22:29:34 UTC
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.

Comment 2 Ivan Afonichev 2014-01-11 22:35:24 UTC
Yes on FC20 jsvc support was degradated. But it is strange that it is not works on FC19.

Comment 3 wdouglascampbell 2014-01-11 22:38:00 UTC
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!

Comment 4 Ivan Afonichev 2014-01-11 23:07:54 UTC
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.

Comment 5 wdouglascampbell 2014-01-12 14:50:23 UTC
If you can restore the functionality that would be great.  Thanks!

Comment 6 Fedora End Of Life 2015-01-09 21:06:09 UTC
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.

Comment 7 Fedora Update System 2015-02-14 21:45:04 UTC
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

Comment 8 Fedora Update System 2015-02-15 13:58:33 UTC
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.fc21
then log in and leave karma (feedback).

Comment 9 Fedora End Of Life 2015-02-18 11:19:37 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 10 Fedora Update System 2015-02-23 08:02:42 UTC
tomcat-7.0.59-1.fc21 has been pushed to the Fedora 21 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.