Skip to main content
R
RichardG
Inspiring
March 22, 2008
Answered

CF8 Install on Mac OS x

  • March 22, 2008
  • 4 replies
  • 705 views
I installed v8 as a single standard web server, pointed it to my existing Apache web server (installed by MAMP). Apache is working fine serving up php and html.

The Apache server was running on port 80, but somehow the CF install reported it was port 8888 at the end and could not set up its connectors to the Apache server.

When I changed the port in httpd.conf to 8888, cfm pages are found but do not run. The Coldfusion service IS running when I check with "ps -eaf | grep coldfusion8ps" and I'm able to stop & resart the service using
/Applications/ColdFusion8/bin/coldfusion start | stop in terminal
so that's all working.

The apache httpd.conf file does have the following:
DirectoryIndex index.cfm index.html index.php
but is there anything else that needs adjusting in the file so it tuns over cfm pages to Coldfusion to render?

I'm a total Mac and unix newbie but having been usng CF in Windows for many years.

Or might it be as simple as a CF configuration file with conflicting ports?

I could really use some help, I'm pretty much at sea here...

Thanks.
    This topic has been closed for replies.
    Correct answer RichardG
    Followup:

    After more uninstalls, reboots, and reinstalls, trying every variation and following advice from multiple blogs, I finally gave up and got it to work using its own webserver on port 8500. Not my first choice, but at least it's working. I can't help thinking though that it shouldn't have been this difficult. I've set it up dozens of times in windows without trouble.

    4 replies

    O
    Oğuz Demirkapı
    Participating Frequently
    March 24, 2008
    As I know there will be a major update for CF8 in April as Ben Forta mentioned in CFUnited Europe. :)
    R
    RichardGAuthor
    Inspiring
    March 24, 2008
    Orguz - Now *that's* something to get excited about. Thanks. I wonder what's coming?
    P
    paulpayne
    Participant
    March 24, 2008
    What version of OS X are you using? 10.4 or 10.5. Coldfusion is not support 10.5.2 Leopard at this time..anybody know when it will be supported.
    R
    RichardGAuthor
    Inspiring
    March 24, 2008
    Hi Paul,

    It's 10.5.2

    Thanks.
    O
    Oğuz Demirkapı
    Participating Frequently
    March 24, 2008
    I have XAMPP and Windows and works without any problem. I know not directly related with MAC but I think there would be a problem on your Apache config file.

    I have following lines in my Apache httpd.conf file.

    # JRun Settings
    LoadModule jrun_module "C:/ColdFusion8/runtime/lib/wsconfig/1/mod_jrun22.so"
    <IfModule mod_jrun22.c>
    JRunConfig Verbose false
    JRunConfig Apialloc false
    JRunConfig Ignoresuffixmap false
    JRunConfig Serverstore "C:/ColdFusion8/runtime/lib/wsconfig/1/jrunserver.store"
    JRunConfig Bootstrap 127.0.0.1:51800
    #JRunConfig Errorurl url <optionally redirect to this URL on errors>
    #JRunConfig ProxyRetryInterval 600 <number of seconds to wait before trying to reconnect to unreachable clustered server>
    #JRunConfig ConnectTimeout 15 <number of seconds to wait on a socket connect to a jrun server>
    #JRunConfig RecvTimeout 300 <number of seconds to wait on a socket receive to a jrun server>
    #JRunConfig SendTimeout 15 <number of seconds to wait on a socket send to a jrun server>
    AddHandler jrun-handler .jsp .jws .cfm .cfml .cfc .cfr .cfswf
    </IfModule>


    You may consider to check your config file for an equivalence. Or Try to run the Web Server configuration tool again.

    R
    RichardGAuthor
    Inspiring
    March 24, 2008
    Thanks for the info but I have killed sooo much time on this and "if it ain't broke....". I'll stick with the builtin server.

    Much obliged!
    R
    RichardGAuthorCorrect answer
    Inspiring
    March 24, 2008
    Followup:

    After more uninstalls, reboots, and reinstalls, trying every variation and following advice from multiple blogs, I finally gave up and got it to work using its own webserver on port 8500. Not my first choice, but at least it's working. I can't help thinking though that it shouldn't have been this difficult. I've set it up dozens of times in windows without trouble.
    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices