Project

General

Profile

Bug #390

Problems Setting Up Apache in a FreeNAS Jail

Added by Daniel Curtis over 10 years ago. Updated almost 10 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Web Server
Target version:
Start date:
05/08/2014
Due date:
% Done:

100%

Estimated time:
0.50 h
Spent time:

Description

I encountered a problem while setting up a new apache server which prevented apache from starting altogether. The following command was used to debug apache, but only received the following error:

apachectl -f /usr/local/etc/apache22/httpd.conf

[Thu May 08 14:37:05 2014] [warn] (2)No such file or directory: Failed to enable the 'dataready' Accept Filter
[Thu May 08 14:37:05 2014] [warn] (2)No such file or directory: Failed to enable the 'dataready' Accept Filter
[Thu May 08 14:37:05 2014] [warn] (2)No such file or directory: Failed to enable the 'httpready' Accept Filter
[Thu May 08 14:37:05 2014] [warn] (2)No such file or directory: Failed to enable the 'httpready' Accept Filter

This was due to the fact that FreeNAS is currently not including the accf_http and accf_data kernel modules, and setting them up as a Tunable in the FreeNAS web interface would not work since the kernel modules are not compiled in. And since I am a lazy sysadmin, I would rather not compile the modules on another machine and move the modules into FreeNAS. So I decided to disable the accf declarations. This was done by doing 2 things:
  1. Disable the modules in /etc/rc.conf
  2. Adding an apache configuration to disable accf

Disable the modules in /etc/rc.conf

I needed to add the following lines to my /etc/rc.conf:

apache22_http_accept_enable="NO" 
apache22_data_accept_enable="NO" 

Adding an apache configuration to disable accf

Then I needed to add a declaration to handle accf being disabled:

<IfDefine NOHTTPACCEPT>
   AcceptFilter http none
   AcceptFilter https none
</IfDefine>

Once these were set, I was able to start apache proper:

service apache22 start

Also available in: Atom PDF