Bug 653885
Summary: | Tomcat failed to start properly or the installer ran out of tries. | ||||||
---|---|---|---|---|---|---|---|
Product: | [Community] Spacewalk | Reporter: | Sandro Mathys <sandro> | ||||
Component: | Installation | Assignee: | Jan Pazdziora <jpazdziora> | ||||
Status: | CLOSED CANTFIX | QA Contact: | Red Hat Satellite QA List <satqe-list> | ||||
Severity: | low | Docs Contact: | |||||
Priority: | low | ||||||
Version: | 1.2 | ||||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2010-11-26 15:45:38 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Bug Depends On: | |||||||
Bug Blocks: | 653453 | ||||||
Attachments: |
|
Description
Sandro Mathys
2010-11-16 11:31:31 UTC
Mass-moving to space13. (In reply to comment #0) > Additional info: > tomcat5 seems to start just fine after the upgrade and the catalina.out doesn't > seem to show anything problematic (find log file attached). So this might be a > bug in spacewalk-setup misinterpreting tomcat's return code. Do you have that upgraded Spacewalk still available? After the upgrade, was it immediatelly usable? Are there any error messages in /var/log/httpd/*error_log* from the time of the restart after upgrade? We actually do not check tomcat's return code because tomcat returns long before all the classes are fully loaded. So we do 20 HEAD requests to the server, 5 seconds apart, to see if it returns success. (In reply to comment #2) > Do you have that upgraded Spacewalk still available? yes, it's been updated to 1.2 final now though. > After the upgrade, was it immediatelly usable? Not sure whether I tried *immediately* but it was working when I tried and I didn't do anything about it. > Are there any error messages in /var/log/httpd/*error_log* from the time of the > restart after upgrade? No, just the usual stuff: [Tue Nov 16 12:56:32 2010] [notice] caught SIGTERM, shutting down [Tue Nov 16 12:56:44 2010] [notice] SELinux policy enabled; httpd running as context user_u:system_r:httpd_t:s0 [Tue Nov 16 12:56:44 2010] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) [Tue Nov 16 12:56:44 2010] [notice] Digest: generating secret for digest authentication ... [Tue Nov 16 12:56:44 2010] [notice] Digest: done [Tue Nov 16 12:56:44 2010] [notice] mod_python: Creating 4 session mutexes based on 256 max processes and 0 max threads. [Tue Nov 16 12:56:44 2010] [notice] Apache configured -- resuming normal operations > We actually do not check tomcat's return code because tomcat returns long > before all the classes are fully loaded. So we do 20 HEAD requests to the > server, 5 seconds apart, to see if it returns success. Why don't you do both? ;) (In reply to comment #3) > > We actually do not check tomcat's return code because tomcat returns long > > before all the classes are fully loaded. So we do 20 HEAD requests to the > > server, 5 seconds apart, to see if it returns success. > > Why don't you do both? ;) Well, I assume it was true (0) in your case anyway so there is not much use. Let's assume this was a one-off timeout issue. Closing. Please reopen if you disagree. |