Martin, Dale and Scott
Thanks a lot for quick answer. I am using Fedora 4 core.
I commented the LoadModule lines in httpd.conf
Execution proceded further.
In the next step its getting stcuk with below error log.
Check apache
Syntax error on line 23 of /usr/local/sipx/etc/sipxpbx/httpd-sipxchange-configserver.conf:
Invalid command 'AddCPPHandler', perhaps mis-spelled or defined by a module not included in the server configuration
So looks "AddCPPHandler" command is not recognised. What should I do for this?
The other question is can I start sipxpbx as root.
I assume sipxpbx can be executed either from root or from user sipxchange.
Please clarify.
If I am running as sipxchange, then below modules are running properly.
Still there are number of permission issues.
Checking rpm configuration file updates: [
OK ]
Checking selinux: [ OK ]
Checking apache: [FAILED]
Checking hostname: [ OK ]
Checking ssl
configuration: [ OK ]
Checking watchdog: [ OK ]
Checking sipproxy: [ OK ]
Checking
sipxconfig: [FAILED]
Checking sipXvxml: [ OK ]
Checking sipxpark: [ OK ]
Checking
sipxpresence: [ OK ]
Checking sipstatus: [ OK ]
Checking sipregistrar: [FAILED]
Checking sipauthproxy:
[FAILED]
Checking keepalive: [ OK ]
If I execute the sipxpbx as root, number of modules are failing.
Checking rpm configuration file updates: [ OK ]
Checking selinux: [ OK ]
Checking
apache: [FAILED]
Checking hostname: [ OK ]
Checking ssl configuration: [ OK ]
Checking watchdog:
[FAILED]
Checking sipproxy: [FAILED]
Checking sipxconfig: [FAILED]
Checking sipXvxml: [FAILED]
Checking
sipxpark: [FAILED]
Checking sipxpresence: [FAILED]
Checking sipstatus: [FAILED]
Checking
sipregistrar: [FAILED]
Checking sipauthproxy: [FAILED]
Checking keepalive: [FAILED]
Whats the cause, with root why so many sipx modules are faling.
Regards
Kamal
"Dale R. Worley" <dworley (at) pingtel.com> wrote:
> > > Apache is not starting and corresponding error log is -
> > > "module mod_ssl is built-in and can't be loaded"
>
> On SuSE 10.0 mod_ssl is built into the Apache RPM and therefore cannot
> be loaded separately (it's already there).
As a general rule, Apache gets upset when it is told to load an external
module that is already built in. You can run ".../httpd -l" to get a
list of all the built-in modules, and then manually comment out the
corresponding LoadModule lines in .../etc/sipxpbx/httpd.conf.
The 'install-fix-apache-modules' command group
in .../sipXpbx/doc/developer/Makefile.config may be suitable to do this
automatically for you.
Dale
_______________________________________________
sipx-dev mailing list
sipx-dev (at) list.sipfoundry.org
List Archive:
http://list.sipfoundry.org/archive/sipx-dev