I've been playing Rift a lot recently. I like the game. There is a lot to do, tons of options.. it's fun. While playing a new ranger, I happened to get these rather cool shots of the sunrise in Rift. Hope you like them too.
Entries for month: April 2012
Sunrise in Rift
Posted by Jordan Michaels
ColdFusion 9 CentOS 6 Connector Issues
Posted by Jordan Michaels
Just had an experience installing ColdFusion 9 on to a CentOS 6 system and ran into an issue installing the web connector. I'll step through the process I went through and maybe it will help others installing Adobe ColdFusion on to CentOS 6.
Right after the installation, I got the following error message:
Running apache connector wizard...
=======================================
There was an error while running the connector wizard
Connector installation was not successful
=======================================
This is the output of the cf-connectors.sh script, located here:
/opt/coldfusion9/bin/cf-connectors.sh
You can manually run that script and get the same error message. Looking at the script, I saw I kept a log of it's issues in the following file:
/opt/coldfusion9/ConnectorInstall0.txt
So I naturally checked it out. The first error I got had to do with Apache APXS not being installed. Again, my CentOS 6 install was a "minimal" install, so I was used to installing additional packages to get things to work properly. To address this issue, I just ran the following:
yum -y install httpd-devel
Then ran the cf-connectors.sh file again, and ran into a different issue this time. This one was more peculiar:
Starting httpd: httpd: Syntax error on line 892 of /etc/httpd/conf/httpd.conf: Cannot load /opt/coldfusion9/runtime/lib/wsconfig/1/mod_jrun22.so into server: /opt/coldfusion9/runtime/lib/wsconfig/1/mod_jrun22.so: failed to map segment from shared object: Permission denied
That's odd... I'm running as "root", I shouldn't be getting permission issues. As it turns out, this error is due to SELinux being enabled. However, I an not at liberty to disable SELinux for this particular project, so I had to find a different way. Turns out, the fix just ended up being a simple one-liner to adjust the SELinux config:
chcon --reference=/usr/sbin/httpd /opt/coldfusion9/runtime/lib/wsconfig/1/mod_jrun22.so
After that, Apache started right up and my SELinux rules are still happily in place!
Hope this helps.
