Bug 505612
Summary: | s390x invalid error about tomcat restarting during install | ||
---|---|---|---|
Product: | Red Hat Satellite 5 | Reporter: | wes hayutin <whayutin> |
Component: | Installer | Assignee: | Jan Pazdziora <jpazdziora> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Pavel StudenÃk <pstudeni> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 530 | CC: | cperry, jpazdziora, pstudeni |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | na | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-10-01 21:56:23 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: | 924232 |
Description
wes hayutin
2009-06-12 15:21:54 UTC
* Restarting services. Installation complete. Visit https://lister.z900.redhat.com to create the RHN Satellite administrator account. You have new mail in /var/spool/mail/root [root@lister satiso]# Is this speedy hardware? Also was the application actually working shortly after this or was it actually unreachable? Has this happened multiple times or just once? [root@rhndev5 ~]# cat /proc/cpuinfo vendor_id : IBM/S390 # processors : 2 bogomips per cpu: 3270.24 processor 0: version = FF, identification = 070AFE, machine = 2094 processor 1: version = FF, identification = 070AFE, machine = 2094 [root@rhndev5 ~]# [root@rhndev5 ~]# free total used free shared buffers cached Mem: 4118580 1415984 2702596 0 196668 559380 -/+ buffers/cache: 659936 3458644 Swap: 1048552 0 1048552 [root@rhndev5 ~]# tomcat eventually started ok. Our time out may not have been long enough for this hardware Alright let's ON_QA this one for a retest? Satellite 5.6 has been released. This bug was tracked under the release. This bug was either VERIFIED or RELEASE_PENDING (re-verified prior shortly before release). Moving to CLOSED CURRENT_RELEASE. Text from Upgrade Erratum follows: 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/RHEA-2013-1395.html |