Bug 1174749
Summary: | Failed to start httpd service on Fedora 20 (with packstack utility) | ||
---|---|---|---|
Product: | [Community] RDO | Reporter: | velmohit <velmohit> |
Component: | openstack-packstack | Assignee: | Martin Magr <mmagr> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | yeylon <yeylon> |
Severity: | urgent | Docs Contact: | |
Priority: | unspecified | ||
Version: | Havana | CC: | aortega, apevec, derekh, gchamoul, gdubreui, ichavero, itamar, jkaluza, jorton, karlthered, mmagr, package-review, pahan, p, social, srevivo, velmohit, yeylon |
Target Milestone: | --- | Keywords: | Triaged |
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-08-10 21:51:51 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: |
Description
velmohit
2014-12-16 12:23:11 UTC
I think this is because of non-existing "/var/cache/mod_ssl/scache". In Fedora, we are using following SSLSessionCache by default: SSLSessionCache shmcb:/run/httpd/sslcache(512000) If you supply different directory to your httpd.conf (or if another utility does that), you should created that directory manually (or the utility should do that for you). (In reply to Jan Kaluža from comment #1) > I think this is because of non-existing "/var/cache/mod_ssl/scache". In > Fedora, we are using following SSLSessionCache by default: > > SSLSessionCache shmcb:/run/httpd/sslcache(512000) > > If you supply different directory to your httpd.conf (or if another utility > does that), you should created that directory manually (or the utility > should do that for you). Thanks for reply ...but I got confused here..you mean to say that I need to create a new directory for "/run/httpd/sslcache(512000)"..? at new location (instead of /run) and supply that path in the ssl.conf file? |