Hello Maceik,
the file /usr/local/pf/conf/httpd.conf.d/httpd.webservices is not a file that make a conf file for apache in /usr/local/pf/var/conf, but it´s the configuration file for apache.
http://perl.apache.org/docs/2.0/api/Apache2/PerlSections.html

Regards
Fabrice

Le 2013-06-14 07:32, Maciej Uhlig a écrit :
Sallee, Stephen (Jake) - 2013-06-13 18:57:


I am doing a new install of PFv4.0.1 and every time I start the PF services I get the following output:

...

httpd.webservices|start

[Thu Jun 13 11:43:30 2013] [warn] NameVirtualHost *:443 has no VirtualHosts

[Thu Jun 13 11:43:30 2013] [warn] NameVirtualHost *:80 has no VirtualHosts

httpd.portal|start


AFAICS there is a single line in /usr/local/pf/conf/httpd.conf.d/httpd.webservices:

$NameVirtualHost => "*:$PfConfig->{'ports'}{'soap'}";

However there is no generated file in /usr/local/pf/var/conf/ which contains lines which could be generated with the above template.

This could be a config problem or even a generator problem.

Actually the error message is Apache error message. Read more in first g..gle link: http://www.cyberciti.biz/faq/apache2-namevirtualhost-80-has-no-virtualhosts/

MU



------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev


_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users


--
Fabrice Durand
[email protected] ::  +1.514.447.4918 (x135) ::  www.inverse.ca
Inverse inc. :: Leaders behind SOGo (http://www.sogo.nu) and PacketFence 
(http://packetfence.org)

------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users

Reply via email to