Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 950647 - error in the checkpidfile() function of the init script
error in the checkpidfile() function of the init script
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: tomcat6 (Show other bugs)
6.0
Unspecified Linux
unspecified Severity low
: rc
: ---
Assigned To: David Knox
tomcat-qe
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-04-10 10:51 EDT by Fabrice Bessettes
Modified: 2015-11-01 19:18 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-11-21 18:51:04 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:1721 normal SHIPPED_LIVE tomcat6 bug fix update 2013-11-20 16:51:34 EST

  None (edit)
Description Fabrice Bessettes 2013-04-10 10:51:46 EDT
Description of problem:
The output of the status option of the init script is always "lockfile exists but process is not running"

Version-Release number of selected component (if applicable):
tomcat6-6.0.24-52.el6_4.noarch

How reproducible:
Run a tomcat instance, and try service tomcat6 status

Patch:
*************** function checkpidfile()
*** 231,236 ****                       
--- 231,237 ----                       
        if [ -d "/proc/${kpid}" ]; then
  # The pid file exists and the process is running  
            RETVAL="0"                              
+         return                                    
        else                                        
  # The pid file exists but the process is not running
           RETVAL="1"
Comment 4 errata-xmlrpc 2013-11-21 18:51:04 EST
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-1721.html

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