Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

FC3 CFMX

0 views
Skip to first unread message

PatNM

unread,
Dec 15, 2004, 6:56:56 PM12/15/04
to
Trying to get CFMX working on my developer box running Fedora Core 3. Apache
balks with the following message after re-compiling the connector: Starting
httpd: Syntax error on line 518 of /etc/httpd/conf/httpd.conf: Cannot load
/opt/coldfusionmx/runtime/lib/wsconfig/1/mod_jrun20.so into server:
/opt/coldfusionmx/runtime/lib/wsconfig/1/mod_jrun20.so: failed to map segment
from shared object: Permission denied I tried various permissions for
mod_jrun20.so with no luck. Can anyone tell me what might be my problem?

louisbrauer

unread,
Dec 16, 2004, 11:33:45 AM12/16/04
to
I've installed CFMX6.1 with the newest updaters today also on Fedora Core 3 and I get exactly the same error message.

You're not alone, but I have no solution yet.

Regards
Louis

cf_menace

unread,
Dec 29, 2004, 4:57:27 PM12/29/04
to
We've got CFMX 6.1 w/ updaters running just fine on Fedora Core 3. Can't tell
you why though.

I did find this thread on CF-Talk that mentions changing a couple of settings:
http://www.houseoffusion.com/cf_lists/messages.cfm/threadid:36878/forumid:4

HTH

Andrew Dixon

unread,
Feb 1, 2005, 4:37:14 AM2/1/05
to
Hi.

Try removing the connector and reinstalling it. I have CFMX running on
FC3 with no issues. If you go into /opt/coldfusionmx/bin/connectors/
there is a script called remove_all_connectors.sh. Run this and it will
remove all the connectors. Then edit the apache_connector.sh so that the
section below is the same as this (leave the rest of the file as is):

$JAVA_EXECUTABLE -jar $CF_DIR/runtime/lib/wsconfig.jar \
-ws apache \
-dir /etc/httpd/conf \
-bin /usr/sbin/httpd \
-script /etc/init.d/httpd \
-coldfusion -v

exit $#

The run this and it will create the connector. The see if it works.

Best Regards

Andrew.

serat

unread,
Feb 4, 2005, 5:06:56 PM2/4/05
to
FC3 comes with SELinux. You probably have it configured for Strict/Enforcing
mode. If you don't really care about SELinux, you can change the security
policy to disabled. Q: How do I turn enforcing on/off at boot? A: You can
specify the SELinux mode using the configuration file /etc/sysconfig/selinux
# This file controls the state of SELinux on the system. # SELINUX= can
take one of these three values: # enforcing - SELinux security
policy is enforced. # permissive - SELinux prints warnings instead
of enforcing. # disabled - No SELinux policy is loaded.
SELINUX=enforcing # SELINUXTYPE= type of policy in use. Possible values
are: # targeted - Only targeted network daemons are protected.
# strict - Full SELinux protection. SELINUXTYPE=targeted
http://www.nsa.gov/selinux/
http://www.redhat.com/magazine/001nov04/features/selinux/
http://fedora.redhat.com/docs/selinux-faq-fc3/index.html

skooch

unread,
Mar 9, 2005, 6:12:10 PM3/9/05
to
I am experiencing the same issues with RedHat AS 4.0. I followed the TechNote
regarding compiling the connectors for AS 3.0 and I am not having any luck. I
remove all connectors and recompile it. I then either get an error that
Apache cannot load mod_jrun20.so into server: failed to map segment from shared
object: Permission denied. Or I can get Apache running but not parsing .cfm
files. ANy help is greatly appreciated.

serat

unread,
Mar 9, 2005, 6:18:37 PM3/9/05
to
Red Hat 4 is not supported for ColdFusion MX 6 or 7. The reason for the
permission deined error is because SELinux is enabled in enforcing mode with
eitehr a strict or targeted policy. The solution is either to change SELinux
to Permissive mode (from enforcing mode) by editing its config file, or
reconfigure the SELinux policy to add the ColdFusion connector to the Apache
domain. Take your pick.

skooch

unread,
Mar 10, 2005, 8:45:52 AM3/10/05
to
I realized that CFMX was not compatible with AS 4.0 after I spent all day
upgrading the server. I checked the compatiblity for everything else but I
never even considered CF because I normally have no problems with it. Changing
the SELinux policies as described did the trick. I'm not sure exactly what this
SELinux is but it has caused me numerous problems. Thank you very much for
your help. You have saved me another day of reinstalling and reconfiguring the
server with AS 3.0. Thanks again!

0 new messages