Skip to main content
Participating Frequently
May 21, 2012
Answered

CF 10 with Apache on Centos 5.8

  • May 21, 2012
  • 1 reply
  • 8480 views

Hi,

Cannot get my install to render the CF Admin pages succesfully, keep getting a 503 - Service temporarily unavailable.

Log files all look clean with the exception of the Tomcat log file which gives a load of the below:

[Mon May 21 21:54:30 2012] [3457:47024938890000] [info] init_jk::mod_jk.c (3299)

: mod_jk/1.2.32 () initialized

[Mon May 21 21:54:30 2012] [3458:47024938890000] [info] init_jk::mod_jk.c (3299)

: mod_jk/1.2.32 () initialized

[Mon May 21 22:02:54 2012] [3461:47024938890000] [error] jk_open_socket::jk_conn

ect.c (448): socket() failed (errno=22)

[Mon May 21 22:02:54 2012] [3461:47024938890000] [info] ajp_connect_to_endpoint:

:jk_ajp_common.c (1027): Failed opening socket to (127.0.0.1:8012) (errno=22)

[Mon May 21 22:02:54 2012] [3461:47024938890000] [error] ajp_send_request::jk_aj

p_common.c (1649): (cfusion) connecting to backend failed. Tomcat is probably no

t started or is listening on the wrong port (errno=22)

[Mon May 21 22:02:54 2012] [3461:47024938890000] [info] ajp_service::jk_ajp_comm

on.c (2629): (cfusion) sending request to tomcat failed (recoverable), because o

f error during request sending (attempt=1)

[Mon May 21 22:02:54 2012] [3461:47024938890000] [error] jk_open_socket::jk_conn

ect.c (448): socket() failed (errno=22)

[Mon May 21 22:02:54 2012] [3461:47024938890000] [info] ajp_connect_to_endpoint:

:jk_ajp_common.c (1027): Failed opening socket to (127.0.0.1:8012) (errno=22)

[Mon May 21 22:02:54 2012] [3461:47024938890000] [error] ajp_send_request::jk_aj

p_common.c (1649): (cfusion) connecting to backend failed. Tomcat is probably no

t started or is listening on the wrong port (errno=22)

To confirm some of my settings:

[root@web-dev4 1]# sestatus

SELinux status:                 disabled

[root@web-dev4 1]# service iptables status

Firewall is stopped.

[root@web-dev4 1]# more /etc/hosts

# Do not remove the following line, or various programs

# that require network functionality will fail.

127.0.0.1               localhost.localdomain localhost web-dev4

::1             localhost6.localdomain6 localhost6

[root@web-dev4 1]# hostname

web-dev4

[root@web-dev4 1]# telnet localhost 8012

Trying 127.0.0.1...

Connected to localhost.localdomain (127.0.0.1).

Escape character is '^]'.

Connection closed by foreign host.

Really have no ideas at this point, installation repeated a few times, looks all clean. Anybody?

Thanks

This topic has been closed for replies.
Correct answer Charlie Arehart

This is by design, as part of various CF10 security enhancements.

For instance, in this article on CF10 Security enhancements (http://www.adobe.com/devnet/coldfusion/articles/security-improvements.html), it notes this with respect to changes about CFLOGIN, which the CF Admin uses under the covers:

Now you can have only one active session open for one user for a given application that uses the cflogin tag.

For example, you can now access the Administrator console one user at a time with a given set of UserIDs and passwords.

It’s also in the CF10 docs, though not worded as obviously applying to this situation. At the bottom of http://help.adobe.com/en_US/ColdFusion/10.0/Developing/WSe61e35da8d3185183e145c0d1353e31f559-7ff7.html, it says:

You are logged out from one of the ColdFusion administrators, if:

From the same host, you log in to the ColdFusion (10) Administrator and the ColdFusion Administrator of an older version.

HTH.

/charlie


I should have added that while you may think, "but that doesn't explain why another user and I can't use it at once", actually it does. Note that the login is not "per user" but "per account". And by default, there is one account used for logging into the CF Admin, called the Admin user (we normally don't even notice or use that, and only need to enter the password for that account).

So it's saying that "2 users of the same account can't be logged into the CF Admin at one time." I agree it's an annoyance, but I'm sure there's a worthy security problem for which it was the solution. Maybe someone from Adobe will chime in with more thoughts.

1 reply

Participant
June 2, 2012

I get exact same error on Centos 5.8 .

Tried with few apache version , same issue .

SeLinux & Firewall completely disabled .

Not doing anything fancy , clean install , default server install with apache .

[root@mel-survey-dev conf]# cat mod_jk.conf

# Load mod_jk module

LoadModule    jk_module  "/opt/coldfusion10/config/wsconfig/1/mod_jk.so"

# Where to find workers.properties

JkWorkersFile "/opt/coldfusion10/config/wsconfig/1/workers.properties"

JkMountFile "/opt/coldfusion10/config/wsconfig/1/uriworkermap.properties"

# Where to put jk logs

JkLogFile "/opt/coldfusion10/config/wsconfig/1/mod_jk.log"

# Where to put jk shared memory

JkShmFile "/opt/coldfusion10/config/wsconfig/1/jk_shm"

# Set the jk log level [debug/error/info]

JkLogLevel info

# Select the timestamp log format

JkLogStampFormat "[%a %b %d %H:%M:%S %Y] "

AddHandler jakarta-servlet .cfm .cfml .cfc .cfr .cfswf

Alias /CFIDE "/opt/coldfusion10/cfusion/wwwroot/CFIDE"

<Directory "/opt/coldfusion10/cfusion/wwwroot/CFIDE">

Options Indexes FollowSymLinks

AllowOverride None

Order allow,deny

Allow from all

</Directory>

<Files ~ ".hbmxml$">

Order allow,deny

Deny from all

</Files>

Adobe Employee
June 5, 2012
MeintDAuthor
Participating Frequently
June 5, 2012

Sorry, I am afraid I don't understand this position. Looking at the list I see that Red Hat Enterprise version 5.6 x64 is fully supported. If you install this and fully update it with "yum update" you will actually end up on version 5.8 and cat /etc/redhat-release will give the new version. Centos is 100% binary compatible and entirely built from Red Hat sources (with the proprietary stuff removed), but ignoring this, are you saying that Red Hat 5.8 is not supported either? If not, this leaves users in the unenviable position of either not being able to update or not being supported? I understand the difficulty in supporting different flavours and versions of Linux distros but it would help if this could be clarified?

Regards

Meint