Skip to main content
ilssac
ilssac
Inspiring
November 23, 2010
Question

New Apache sites return 500 Internal Server Error for all CFML requests

  • November 23, 2010
  • 1 reply
  • 1025 views

This is an ugly one.  I think it is an Apache2 - ColdFusion 9 web server connector problem.

I have two Solaris Unix web servers.  Each of these servers have a dozen and a half Apache web sites each one connected to one of five ColdFusion instances.

All, but TWO of them are working properly.  We created two new Apache web sites and connected them to a new ColdFusion instance.  This worked fine on one of our boxes, the development one, but not on the other, production of course.

Whenever we try to request a cfm url from one of these sites on the production server we get a 500 Internal Server Error.  HTML pages serve up just fine, and the new instance's Administrator runs fine on its 8305 port.  So both Apache and ColdFusion seem to be working independently, but they are not talking to each other.  All the other Apache sites connected to the other four ColdFusion instances also work properly.

This has led me to investigate the web server connectors.  They have always been tricky and problematic to set up on these boxes.  The built in tools have never worked for us on these boxes and we have always had to manually compile the connectors and configure the connections in the web sites..

But, as far as I can tell, all the connection setups are the same between working examples and these non-working sites.

Any insights into what else I should be checking and|or how web server connectors actually work (they have alwasy been mysterious black boxes to me) would be greatly appreciated.

TIA

Ian

    This topic has been closed for replies.

    1 reply

    ilssac
    ilssacAuthor
    Inspiring
    November 23, 2010

    Some more information.

    I took a closer look at the logs (I wasn't looking 
    in the Apache logs before).  I found this block for the last attempt to 
    request a cfm page.

    [Tue Nov 23 15:17:17 2010] [notice] jrApache[18177: 60758]  could not 
    open serverstore "/opt/jrun4/lib/wsconfig/www/jrunserver.store": No such 
    file or directory[Tue Nov 23 15:17:17 2010] [notice] jrApache[18177: 
    60758]  Couldn't initialize from remote server, JRun server(s) probably 
    down.

    What I don't understand is why could it not open that file, it is there 
    and it has the same permissions as all the other web server connectors.

    /opt/jrun4/lib/wsconfig/www
    $ ls -al
    total 166
    drwxr-xr-x   2 root     root         512 May 29 13:51 .
    drwxr-xr-x   8 root     root         512 May 29 13:51 ..
    -rw-r--r--   1 root     root          14 May 29 13:51 jrunservers.store
    -rwxr-xr-x   1 root     root       81528 May 29 13:51 mod_jrun20.so

    The following is the 'calpip' connector folder that is working just fine.

    /opt/jrun4/lib/wsconfig/calpip
    $ ls -al
    total 166
    drwxr-xr-x   2 root     root         512 May 29 13:51 .
    drwxr-xr-x   8 root     root         512 May 29 13:51 ..
    -rw-r--r--   1 root     root          14 May 29 13:51 jrunservers.store
    -rwxr-xr-x   1 root     root       81528 May 29 13:51 mod_jrun20.so

    D
    Community Expert
    Dave WattsCommunity Expert
    Community Expert
    November 23, 2010

    According to your directory list, you have files named "jrunservers.store". They should be named "jrunserver.store", I think. Try renaming them, restarting the Apache instances, and see what happens.

    Dave Watts, CTO, Fig Leaf Software

    http://www.figleaf.com/

    http://training.figleaf.com/

    Fig Leaf Software is a Veteran-Owned Small Business (VOSB) on

    GSA Schedule, and provides the highest caliber vendor-authorized

    instruction at our training centers, online, or onsite.

    Read this before you post:

    http://forums.adobe.com/thread/607238

    Dave Watts, Eidolon LLC
    ilssac
    ilssacAuthor
    Inspiring
    November 23, 2010

    Dave Watts wrote:

    According to your directory list, you have files named "jrunservers.store". They should be named "jrunserver.store", I think. Try renaming them, restarting the Apache instances, and see what happens.

    I am reluctant to try that since all them have "jrunservers.store" and only the "www" one is the one that is not working.

    As well as, since this is the production server, it takes an official publicly announced server outage|interruption notice signed off by management and directors to restart apache.  (Well they have to at least be informed and give a verbal OK)

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices