Bug 947421 - Failed to start httpd while using SSLSessionCache module
Summary: Failed to start httpd while using SSLSessionCache module
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: httpd
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Joe Orton
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-04-02 11:34 UTC by Rami Vaknin
Modified: 2014-01-12 23:55 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-05-13 10:49:09 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Rami Vaknin 2013-04-02 11:34:30 UTC
openstack-packstack package adds the following to /etc/httpd/conf.d/ssl.conf and httpd start fails on syntax error, the problematic line is:
SSLSessionCache         shmcb:/run/httpd/sslcache(512000)

Additional Information:
# ls /run/httpd/
htcacheclean

From journalctl's output:
httpd[15696]: AH00526: Syntax error on line 23 of /etc/httpd/conf.d/ssl.conf:
httpd[15696]: SSLSessionCache: 'shmcb' session cache not supported (known names: ). Maybe you need to load the appropriate socache module (mod_socache_shmcb?).
systemd[1]: httpd.service: main process exited, code=exited, status=1/FAILURE
httpd[15697]: AH00526: Syntax error on line 23 of /etc/httpd/conf.d/ssl.conf:
httpd[15697]: SSLSessionCache: 'shmcb' session cache not supported (known names: ). Maybe you need to load the appropriate socache module (mod_socache_shmcb?).
httpd.service: control process exited, code=exited status=1
Failed to start The Apache HTTP Server.

Comment 1 Jan Kaluža 2013-05-10 06:56:05 UTC
Is mod_socache_shmcb module loaded? Check that in /etc/httpd/conf.modules.d/00-base.conf?

Comment 2 Rami Vaknin 2013-05-12 10:07:43 UTC
Sorry, I don't have that env anymore.
Anyone, if you've encountered the same error, could you please provide the requested information?

Comment 3 Jan Kaluža 2013-05-13 10:49:09 UTC
I'm pretty sure personally that it was because of missing module in config file. I will close this bug for now and if you will be able to reproduce this problem, feel free to reopen this bug.


Note You need to log in before you can comment on or make changes to this bug.