> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Krzeminski, Damian (BL60:9D30) > Sent: Monday, October 06, 2008 9:00 AM > To: [EMAIL PROTECTED] > Subject: Re: [sipX-dev] Also having errors about > httpd-sipxchange-common.conf and httpd-sipxchange-common-ssl.conf > > Dale Worley wrote: > > On Thu, 2008-10-02 at 16:27 -0400, Joseph Attardi wrote: > >> Martin sent an email about this the other day but there > was no reply. > >> Now I am having the same problem. I'm trying to get sipX up and > >> running on a Fedora 8 virtual machine. It builds and > installs without > >> a hitch, but when I try to start it, I get the same > problem Martin described: > >> > >> Starting httpd: httpd: Syntax error on line 1049 of > >> /usr/local/sipx/etc/sipxpbx/httpd.conf: Could not open > configuration > >> file > /usr/local/sipx/etc/sipxpbx/httpd-sipxchange-common-ssl.conf: No > >> such file or directory > >> > >> This is on Fedora 8, on the latest (svn 13583). > >> > >> Any ideas what's up here? There are corresponding .in files in > >> /usr/local/sipx/etc/sipxpbx (httpd-sipxchange-common.conf.in, > >> httpd-sipxchange-common-ssl.conf.in) but not the files themselves. > > > > I ran into this myself. The problem is that sipXconfig isn't yet > > generating these files. What I did was copy-and-edit the > files from > > another working copy with a very similar code base. You could also > > manually translate the .in files. > > > > Dale > > > > > > sipXconfig does not try to generate those file, but whatever > method was used to generate them should still work (after all > we did not switch off config files preprocessing for all the > other files until sipXconfig started generating them). > > I was under impression that sipXconfig is not going to > generate httpd config files, since httpd usage in sipX is > phased out. If that's not true we need a JIRA issue to cover that. > D. >
Thanks for posting this - I also had this problem Friday and wondered what I had done to provoke it. In addition to the httpd*.in's not being generated, the location of the modules in httpd.conf has changed, so that I get the error "Starting httpd: httpd2: Syntax error on line 234 of /home/cbeeton/test/out/main/etc/sipxpbx/httpd.conf: Cannot load /usr/lib64/apache2/mod_ssl.so into server: /usr/lib64/apache2/mod_ssl.so: cannot open shared object file: No such file or directory" In the new version of the file, I see LoadModule foo_module /usr/lib64/apache2/mod_foo.so while the old (working) one has LoadModule foo_module /usr/lib64/apache2-prefork/mod_foo.so On my system /usr/lib64/apache2 does not exist, but /usr/lib64/apache2-prefork does. So the httpd.conf file was generated, but incorrectly? Carolyn _______________________________________________ sipx-dev mailing list sipx-dev@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
