Bug 51920
| Summary: | piranha-gui refuses to start | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Tom "spot" Callaway <tcallawa> |
| Component: | piranha | Assignee: | Phil Copeland <copeland> |
| Status: | CLOSED RAWHIDE | QA Contact: | Brian Brock <bbrock> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7.3 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2001-08-17 19:13:56 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: | |||
Tom, do a cvs co of piranha and in teh directory, type 'make rpms' -24/25 should have that one fixed Phil =--= Changing product. This defect is considered MUST-FIX for Fairfax This was a RPM spec file error, it is fixed in the current CVS as of 0.5.5-24 Closing. |
Description of Problem: [root@localhost root]# service piranha-gui start Starting piranha-gui: Syntax error on line 17 of /etc/sysconfig/ha/conf/httpd.conf: Cannot load /etc/sysconfig/ha/modules/mod_vhost_alias.so into server: /etc/sysconfig/ha/modules/mod_vhost_alias.so: cannot open shared object file: No such file or directory [FAILED] Version-Release number of selected component (if applicable): piranha-0.5.5-19 How Reproducible: Always Steps to Reproduce: 1. /sbin/service piranha-gui start Actual Results: piranha-gui doesnt start, crashes as above Expected Results: piranha-gui starts. Additional Information: the reason this is crashing is due to the fact that the /etc/sysconfig/ha/conf/httpd.conf file has modules with non-absolute paths, and the "ServerRoot" directive is set to /etc/sysconfig/ha, which does not have the modules needed to start httpd. a workaround is to set the absolute path on all the LoadModule directives.