Bug 812003
| Summary: | Monitoring Scout will not start: Certificate verify failed. | ||
|---|---|---|---|
| Product: | [Community] Spacewalk | Reporter: | William Brown <william> |
| Component: | Server | Assignee: | Jan Pazdziora (Red Hat) <jpazdziora> |
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Red Hat Satellite QA List <satqe-list> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 1.7 | CC: | jpazdziora |
| 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: | 2013-05-10 07:18:52 UTC | Type: | Bug |
| 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: | 1484117 | ||
|
Description
William Brown
2012-04-12 13:57:01 UTC
(In reply to comment #0) > Description of problem: > After enabling monitoring, when the spacewalk server is restarted the > Monitoring Scout will not launch, citing an SSL verification error. > > Version-Release number of selected component (if applicable): > Fedora 17 x86_64 What Fedora and LWP versions are these exactly? > Error on attempt 4: Status: '500 Can't connect to > spacewalk.dev.firstyear.id.au:443 (certificate verify failed)'; content: > 'Can't connect to spacewalk.dev.firstyear.id.au:443 (certificate verify > failed) If you do export PERL_LWP_SSL_VERIFY_HOSTNAME=0 before running that spacewalk-service restart, does it seem to help? This BZ closed some time during 2.5, 2.6 or 2.7. Adding to 2.7 tracking bug. |