Highlighted

ColdFusion installer

Community Beginner ,
Jul 20, 2020

Copy link to clipboard

Copied

Does the ColdFusion 2018 installer now available contain all the latest hotfixes? I downloaded the installer a few months ago, and it was a very old version with no hotfixes installed. Installing hotfixes caused the server to become corrupted and I had to reinstall the original. This happened on two different machines.

 

Tom Muck

TOPICS
Installation

Views

80

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

ColdFusion installer

Community Beginner ,
Jul 20, 2020

Copy link to clipboard

Copied

Does the ColdFusion 2018 installer now available contain all the latest hotfixes? I downloaded the installer a few months ago, and it was a very old version with no hotfixes installed. Installing hotfixes caused the server to become corrupted and I had to reinstall the original. This happened on two different machines.

 

Tom Muck

TOPICS
Installation

Views

81

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Jul 20, 2020 0
Community Beginner ,
Jul 21, 2020

Copy link to clipboard

Copied

I reinstalled ColdFusion 2018 and ran updates one by one. Updates 4, 5, 6, 7 worked, but after installed hotfix 8, the installation failed again.  Back to the drawing board. It would be nice to have an installer that contains the updates.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jul 21, 2020 0
Guide ,
Jul 22, 2020

Copy link to clipboard

Copied

Hi Tom,

 

What do you mean by install failed after update 8? Do the CF web served pages fail? Does CFadmin page fail? 

 

I suspect your web served pages are failing - if so did you run WSCONFIG to upgrade the tomcat connector?

 

Regards, Carl. 

 

 

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jul 22, 2020 0
Community Beginner ,
Jul 23, 2020

Copy link to clipboard

Copied

I will try that next. The CF admin comes up, so CF is running, but the web server connector failed. Why would a CF update cause a connector to fail though?

 

Tom

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jul 23, 2020 0
Adobe Community Professional ,
Jul 23, 2020

Copy link to clipboard

Copied

There's been a significant security patch to Tomcat, the J2EE server that runs CF and talks to your web server. You need to upgrade the connectors so that they know how to talk to the new version of Tomcat. There have been a bunch of blog posts and comments here about that process, but it's usually pretty simple if you just upgrade the connectors. Here's a good start.

 

https://www.carehart.org/blog/client/index.cfm/2019/11/13/when_how_update_cf_web_connector

 

Dave Watts, Eidolon LLC

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jul 23, 2020 0
Community Beginner ,
Jul 23, 2020

Copy link to clipboard

Copied

Thanks, Dave. I did try that, no luck. It did upgrade the mod_jk.so, but still getting "service unavailable". A couple other things I noted:

  • The hotfix updates (run manually from a command line) restart the CF server in standalone mode and do not restart the Windows service. I had to run the cfstop.bat file and restart the service to get the service going again. 
  • Uninstalling a specific update restores the server to operation. 

The environment I'm working in does not have outside Internet access, so I can use the automatic updater, or look for updates.

I wish this process was easier. I have to get it working and document it for our operations people to install in production.

Tom

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jul 23, 2020 0
Adobe Community Professional ,
Jul 23, 2020

Copy link to clipboard

Copied

The next step for me would be to completely uninstall and reinstall the connectors, instead of upgrading them. That's more of a pain. But if you're trying to create a documentable process starting from a base without CF even installed yet, you could simply hold off on installing connectors until you get to the latest upgrade.

 

Dave Watts, Eidolon LLC

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jul 23, 2020 0
Community Beginner ,
Jul 23, 2020

Copy link to clipboard

Copied

Thanks, Dave. That would have been optimal, except that we have CF 2018 already installed and running. I'll keep at it.

 

Tom

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jul 23, 2020 0
New Here ,
Jul 23, 2020

Copy link to clipboard

Copied

I downloaded the (an?) installer a couple days ago and it was still missing updates 4-10. I'm hoping I'm missing a more up-to-date installer, as it'd be much faster to have the latest version available as we start building more CF environments.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jul 23, 2020 0
Adobe Community Professional ,
Jul 23, 2020

Copy link to clipboard

Copied

Tom, about the update to the connector, that's not enough for everyone. More in a moment, but it may require only 1 or 2 changes to the server.xml.file (and won't be solved by burning or down and reinstalling).
 
And dshuffma (and Tom, to your original post), you're right that the problem is that even with a cf2018 installer downloaded today, you must do all this: update it to update 4, then then the latest (currently 10), and after that (or any update from 8 on), one must upgrade the web connector. This won't be solved until Adobe creates a new cf2018 installer. Let's hope they will. It's supported to 2023, so it's reasonable to expect they will. 
 
Tom, in addition to upgrading the connector, some folks have to go further to get their site's working again--especially those on apache as you are. 

 

As Dave noted, this is about TOMCAT changes (which underlies cf and which Adobe implemented). He kindly ponted out my 2019 post on the need to upgrade connectors, after most cf updates. But in March of 2020 the aforementioned tomcat security changes were folded into cf update 8 (and update 12 for cf2016), and the technote then elaborated the possible need of other changes (such as perhaps a need to add allowedrequestattributespattern and address attributes to the server.xml).

 

I drew out and elaborated the issues in a couple of posts then:

 

https://coldfusion.adobe.com/2020/03/three-reasons-sites-may-break-fix-applying-mar-2020-update-cf20...

 

I hope both you and dshuffma will let us know how things go.

/Charlie (server troubleshooter, carehart.org)

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jul 23, 2020 0
Community Beginner ,
Jul 23, 2020

Copy link to clipboard

Copied

Thanks, Charlie, reading now! I'm hopeful.

 

 

Tom

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jul 23, 2020 0
Community Beginner ,
Jul 23, 2020

Copy link to clipboard

Copied

Still no luck. No ip address is configured in Apache, using loopback. Pasting tail end of mod_jk.log below, hoping someone sees a potential problem.

[Thu Jul 23 12:38:57 2020] [6304:4724] [debug] ajp_get_endpoint::jk_ajp_common.c (3753): (cfusion) acquired connection pool slot=0 after 0 retries
[Thu Jul 23 12:38:57 2020] [6304:4724] [debug] ajp_marshal_into_msgb::jk_ajp_common.c (745): (cfusion) ajp marshaling done
[Thu Jul 23 12:38:57 2020] [6304:4724] [debug] ajp_service::jk_ajp_common.c (2791): processing cfusion with 2 retries
[Thu Jul 23 12:38:57 2020] [6304:4724] [debug] ajp_send_request::jk_ajp_common.c (1805): (cfusion) no usable connection found, will create a new one.
[Thu Jul 23 12:38:57 2020] [6304:4724] [debug] jk_open_socket::jk_connect.c (674): socket TCP_NODELAY set to On
[Thu Jul 23 12:38:57 2020] [6304:4724] [debug] jk_open_socket::jk_connect.c (798): trying to connect socket 1204 to ::1:8018
[Thu Jul 23 12:38:58 2020] [6304:3392] [debug] wc_get_worker_for_name::jk_worker.c (157): found a worker cfusion
[Thu Jul 23 12:38:58 2020] [6304:4724] [info] jk_open_socket::jk_connect.c (816): connect to ::1:8018 failed (errno=61)
[Thu Jul 23 12:38:58 2020] [6304:4724] [info] ajp_connect_to_endpoint::jk_ajp_common.c (1140): (cfusion) Failed opening socket to (::1:8018) (errno=61)
[Thu Jul 23 12:38:58 2020] [6304:4724] [error] ajp_send_request::jk_ajp_common.c (1811): (cfusion) connecting to backend failed. Tomcat is probably not started or is listening on the wrong port (errno=61)
[Thu Jul 23 12:38:58 2020] [6304:4724] [info] ajp_service::jk_ajp_common.c (2982): (cfusion) sending request to tomcat failed (recoverable), because of error during request sending (attempt=1)
[Thu Jul 23 12:38:58 2020] [6304:4724] [debug] ajp_service::jk_ajp_common.c (2831): (cfusion) retry 1, sleeping for 100 ms before retrying
[Thu Jul 23 12:38:59 2020] [6304:4724] [debug] ajp_send_request::jk_ajp_common.c (1805): (cfusion) no usable connection found, will create a new one.
[Thu Jul 23 12:38:59 2020] [6304:4724] [debug] jk_open_socket::jk_connect.c (674): socket TCP_NODELAY set to On
[Thu Jul 23 12:38:59 2020] [6304:4724] [debug] jk_open_socket::jk_connect.c (798): trying to connect socket 1204 to ::1:8018
[Thu Jul 23 12:38:59 2020] [6304:3392] [debug] wc_get_worker_for_name::jk_worker.c (157): found a worker cfusion
[Thu Jul 23 12:39:00 2020] [6304:4724] [info] jk_open_socket::jk_connect.c (816): connect to ::1:8018 failed (errno=61)
[Thu Jul 23 12:39:00 2020] [6304:4724] [info] ajp_connect_to_endpoint::jk_ajp_common.c (1140): (cfusion) Failed opening socket to (::1:8018) (errno=61)
[Thu Jul 23 12:39:00 2020] [6304:4724] [error] ajp_send_request::jk_ajp_common.c (1811): (cfusion) connecting to backend failed. Tomcat is probably not started or is listening on the wrong port (errno=61)
[Thu Jul 23 12:39:00 2020] [6304:4724] [info] ajp_service::jk_ajp_common.c (2982): (cfusion) sending request to tomcat failed (recoverable), because of error during request sending (attempt=2)
[Thu Jul 23 12:39:00 2020] [6304:4724] [error] ajp_service::jk_ajp_common.c (3003): (cfusion) connecting to tomcat failed (rc=-3, errors=1, client_errors=0).
[Thu Jul 23 12:39:00 2020] [6304:4724] [debug] ajp_reset_endpoint::jk_ajp_common.c (912): (cfusion) resetting endpoint with socket -1 (socket shutdown)
[Thu Jul 23 12:39:00 2020] [6304:4724] [debug] ajp_abort_endpoint::jk_ajp_common.c (882): (cfusion) aborting endpoint with socket -1
[Thu Jul 23 12:39:00 2020] [6304:4724] [debug] ajp_done::jk_ajp_common.c (3684): recycling connection pool for worker cfusion and socket -1
[Thu Jul 23 12:39:00 2020] [6304:4724] [info] jk_handler::mod_jk.c (3443): Service error=-3 for worker=cfusion

 

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jul 23, 2020 0
Adobe Community Professional ,
Jul 23, 2020

Copy link to clipboard

Copied

See the ::1 within the log? Did you try that as the address? I had suggested it in the post as something that had fixed things for others.

 

And if that does not work, what about the allowedRequestAttributesPattern=".*"? Did you try adding that? (See my blog post for more, and it's case-sensitive. And make sure the quotes are not "formatted", if you try it.)

 

You may need both, or one or the other. Let us know how it goes.

/Charlie (server troubleshooter, carehart.org)

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jul 23, 2020 0
Community Beginner ,
Jul 24, 2020

Copy link to clipboard

Copied

Genius. Thanks, Charlie. I read the post wrong initially -- I thought it
said to use ::1 if you are using IPv6, but adding that as the address made
the connector work. I'm good now. I still wish the installer had updates
already included.

Thanks again. I'm not really a server guy, just a coder.

Tom Muck

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jul 24, 2020 0
Adobe Community Professional ,
Jul 24, 2020

Copy link to clipboard

Copied

Great to hear that it's solved, Tom. And yep, the ::1 IS an ipv6 address (and since it was shown in your log, and now is set by you for that address attribute in server.xml, that indicates that your machine was using IPV6). But like you said, you're not a "server guy" so it's understandable that you've have no reason to know it was.

 

And yep, again, I agree 100% that it would be very helpful if/when Adobe would offer a new CF installer (for 2016 and 2018) so that people don't need to hassle with all the updates needed (such as, for CF2018, update 4 and then 2016, and the updated connector after update 8).

 

That said, that fact this updated connector MAY require such a change to the server.xml to work (for some folks, like you found with Apache) DOES mean that as soon as they DO offer one, things "won't work". They (Adobe) are not going to presume to put that ::1 in there for you.  So really, just getting an updated installer will simply push this problem on to anyone who DOES install CF "out of the box" with that new installer.

 

What's really needed is for CF (whether itself or the wsconfig tool) to detect this problem and offer this solution (or that allowedRequesstAttributesPattern change that some will need.) Again, these are Tomcat problems really (that anyone using Tomcat will face). Our challenge as CFers is that this tool and CF itself try to set these Tomcat things for us (because many folks using CF are "not server guys"). Here's a place where they need to do MORE than they do currently, and perhaps that's why they are not yet offering a fully updated CF installer. So this problem will continue for some time, until they do resolve it "for us".

/Charlie (server troubleshooter, carehart.org)

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jul 24, 2020 0
tommuck1 LATEST
Community Beginner ,
Jul 24, 2020

Copy link to clipboard

Copied

Thanks, Charlie, agree with all that. I wouldn't mind seeing some
documentation or FAQ or potential issues right on the hotfix page.

Tom

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jul 24, 2020 0