Skip to main content
Participant
May 24, 2009
Question

Coldfusion 8 Standard on RHEL 5 Apache Connector Fails to install

  • May 24, 2009
  • 1 reply
  • 1239 views

I'm having a heck of a time getting Coldfusion 8 Standard installed on a newly provisioned RHEL 5 server.   I am installing as root.

On the initial start I get Coldfusion not started, will retry connector and then it counts down.

Contents of ConnectorInstall0.txt 

Macromedia JRun 4.0 (Build 108673)

os.name: Linux

os.version: 2.6.18-8.1.14.el5_HPTRAID

os.arch: i386

platform: intel-linux

Could not connect to any JRun/ColdFusion servers on host localhost.

Possible causes:

o Server not running

  -Start Macromedia JRun4 or ColdFusion 8 server

o Server running

  -JNDI listen port in jndi.properties blocked by TCP/IP filtering or firewall

   on server

  -host restriction in security.properties blocking communication with server

My apache_connector.sh file contains (I had to manually add as post installation, this file was not correct based on prompted install.
#!/bin/sh
#
# Configure the Apache connector.
#       -dir should be the *directory* which contains httpd.conf
#       -bin should be the path to the apache *executable*
#       -script should be the path to the script which is used to
#               start/stop apache
#
../../runtime/bin/wsconfig \
        -server coldfusion \
    -ws apache \
        -dir /etc/httpd/conf \
        -bin /usr/sbin/httpd \
        -script /etc/rc.d/init.d/httpd \
        -coldfusion
exit $#
I also notice that it doesn't update the httpd.conf file either. When I compared my other install that I'm migrating servers from, it updated the httpd.conf file with a number of items to include pointers to the wsconfig/1/ directory which is currently not populated on this machine.
Any help appreciated.  Kind of surprised this isn't well documented somewhere for such as standard and supported platform.
Jim

This topic has been closed for replies.

1 reply

jhankinsAuthor
Participant
May 25, 2009

Ok, so I was in the process of moving to a new server, I had the advantage of having a working system to reference.  I had to manually build the apache connector script which was not a surprise as the docs spell that out.  What was not obvious is that I had to build my own wsconfig/1/ directory for it to include all the files including a ./libs directory within it  /opt/coldfusion8/runtime/libs/wsconfig/1/.libs 

My system did not have a /1/ directory created so I did this manually and populated the files.

I also had to manually fix update the httpd.conf file (which again I had from the other system to reference).

Royal Pain indeed but it was fixed this way.  Lesson learned.  I'm going to tarbal up that directory and save in case I need to recover from this again in the future.  Hopefully next time I'll be using Coldfusion 9 and hopefully they'll have drastically improved the installation on Linux.