Bug 1253432 - Some upgrades are failing on RHEL 6 with an error about tomcat
Some upgrades are failing on RHEL 6 with an error about tomcat
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Upgrades (Show other bugs)
Unspecified Unspecified
unspecified Severity high (vote)
: Unspecified
: --
Assigned To: Stephen Benjamin
Sachin Ghai
: Triaged
Depends On:
  Show dependency treegraph
Reported: 2015-08-13 13:04 EDT by Stephen Benjamin
Modified: 2017-02-23 14:47 EST (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2015-08-26 15:47:07 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
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 Knowledge Base (Solution) 1575103 None None None Never
Red Hat Product Errata RHBA-2015:1688 normal SHIPPED_LIVE Satellite 6.1 bug fix update 2015-08-26 19:46:50 EDT

  None (edit)
Description Stephen Benjamin 2015-08-13 13:04:04 EDT
Description of problem:
Stopping tomcat6: waiting for processes 2787 to exit
   killing 2787 which did not stop after 60 seconds [WARNING]
                                                              [ OK  ]
   Starting tomcat6:                                          [ OK  ]
   Stopping httpd:                                            [ OK  ]
   Starting httpd:                                            [ OK  ]
   Starting foreman-tasks:                                    [ OK  ]
   Some services failed: tomcat6

   [ERROR 2015-08-12 12:22:53 main] Upgrade step restart_services failed.
Check logs for more information.
   [DEBUG 2015-08-12 12:22:53 main] Exit with status code: 1 (signal was 1)
   [ERROR 2015-08-12 12:22:53 main] Repeating errors encountered during run:
   [ERROR 2015-08-12 12:22:53 main] mongod is stopped

*[ERROR 2015-08-12 12:22:53 main] <NilClass> nil*
   [ERROR 2015-08-12 12:22:53 main] httpd is stopped
Comment 1 Stephen Benjamin 2015-08-13 14:27:55 EDT
I am not able to reproduce this on my own systems, not matter what I do to tomcat.  If anyone encounters this, it would be very helpful to see what step it's failing on, and what state tomcat is in.  This script gathers that data:


time service tomcat6 stop
echo "Exit code: " $?

time service tomcat6 start
echo "Exit code: " $?

# maximum time to wait (in seconds)

wait_for_url() {
    echo $(date)

    time /usr/bin/wget --timeout=1 --tries=$WAIT_MAX --retry-connrefused -qO- --no-check-certificate $1
    echo "wget exit code ${?}"

    time /usr/bin/curl -ks --retry $WAIT_MAX --retry-delay 1 $1

    echo ""
    echo "curl exit code ${?}"

    if ! [ $? = '0' ]; then

time wait_for_url $TOMCAT_TEST_URL
echo "wait_for_url exit code ${?}"

time service-wait tomcat6 restart
echo "service-wait exit code ${?}"
Comment 2 Dylan Gross 2015-08-13 14:48:43 EDT
Customer experiencing the issue in (Case 01491540) ran Tomcat stop/start script from Comment #1.   Results....

Stopping tomcat6: waiting for processes 28198 to exit
                                                           [  OK  ]

real	0m3.344s
user	0m0.311s
sys	0m0.049s
Exit code:  0
Starting tomcat6:                                          [  OK  ]

real	0m0.078s
user	0m0.018s
sys	0m0.017s
Exit code:  0
Thu Aug 13 14:38:31 EDT 2015

real	0m0.014s
user	0m0.012s
sys	0m0.002s
wget exit code 4

real	0m0.004s
user	0m0.000s
sys	0m0.002s

curl exit code 0

real	0m0.019s
user	0m0.012s
sys	0m0.004s
wait_for_url exit code 0
Stopping tomcat6: waiting for processes 28938 to exit
killing 28938 which did not stop after 60 seconds          [WARNING]
                                                           [  OK  ]
Starting tomcat6:                                          [  OK  ]

real	1m1.994s
user	0m0.496s
sys	0m0.390s
service-wait exit code 5
Comment 4 Michael Orlov 2015-08-14 08:54:51 EDT
As a workaround I commented out the tomcat6 call in /usr/sbin/service-wait.
That allows me to upgrade the Satellite.
Comment 6 Stephen Benjamin 2015-08-14 10:17:26 EDT
Created redmine issue http://projects.theforeman.org/issues/11353 from this bug
Comment 7 Stephen Benjamin 2015-08-14 10:53:14 EDT
Thanks for those who supplied the output of that, it helped understand what was going wrong.

There's a brief window where tomcat's listening on 8443, but not responding 200 to /candlepin/status.  Sometimes, we end up calling wget in that window, which exits immediately with a failure.

wget does not obey the --tries there in this case.

It's generally reproducible if you do this as one command, you'll see wget does NOT retry:

service tomcat6 stop; service tomcat6 start; /usr/bin/wget --timeout=1 --tries=30 --retry-connrefused -qO- --no-check-certificate https://localhost:8443/candlepin/status; echo $?
Comment 8 Bryan Kearney 2015-08-14 13:53:24 EDT
Upstream bug assigned to stbenjam@redhat.com
Comment 9 Bryan Kearney 2015-08-14 13:53:25 EDT
Moving to POST since upstream bug http://projects.theforeman.org/issues/11353 has been closed
Comment 13 Sachin Ghai 2015-08-19 07:35:44 EDT
Ok, I was trying to verify this bz. I installed sat6.0.8 and populated some content (along with capsule/provisioning conf) and upgraded the server with snap17.

Upgrade is completed successfully.

[root@cloud-qe-9 yum.repos.d]# katello-installer --upgrade
Upgrade Step: stop_services...
Upgrade Step: start_mongo...
Upgrade Step: migrate_pulp...
Upgrade Step: start_httpd...
Upgrade Step: migrate_candlepin...
Upgrade Step: migrate_foreman...
Upgrade Step: Running installer...
Installing             Done                                               [100%] [..................................................................]
  The full log is at /var/log/katello-installer/katello-installer.log
Upgrade Step: restart_services...
Upgrade Step: db_seed...
Upgrade Step: errata_import (this may take a while) ...
Upgrade Step: update_gpg_urls (this may take a while) ...
Upgrade Step: update_repository_metadata (this may take a while) ...
Katello upgrade completed!
Comment 14 Sachin Ghai 2015-08-19 07:36:22 EDT
I'm curious to know  if there is any other way to know whether the original issue is really fixed with new snap ?

I can see the changes in `/usr/share/katello/script/service-wait` but still would like to double check. thanks
Comment 17 Sachin Ghai 2015-08-19 08:05:36 EDT
Based on comments 13 and 15. Moving this to verified. Thanks
Comment 19 errata-xmlrpc 2015-08-26 15:47:07 EDT
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.


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