tracker issue : CF-4167033

select a category, or use search below
(searches all categories and all time range)

AWS AMI Crashes After Connector Upgrade

| View in Tracker

Status/Resolution/Reason: Closed/Withdrawn/

Reporter/Name(from Bugbase): Christopher Tierney / Christopher Tierney (Christopher Tierney)

Created: 06/22/2016

Components: Installation/Config, Connector

Versions: 11.0

Failure Type: Crash

Found In Build/Fixed In Build: CF11_Final /

Priority/Frequency: Major / All users will encounter

Locale/System: English / Win 2012 Server x64

Vote Count: 0

Problem Description:
Update 9 was applied to version 11.0.0 provided with the AWS AMI. Then the connector was upgraded as required. wsconfig could not correctly upgrade connector, making ColdFusion administrator unusable.

Steps to Reproduce:
1. Clean install of AWS Linux AMI allowing all upgrades upon first boot
2. Login as Ubuntu user
3. Install ColdFusion 11 using automated installed provided
4. Update AWS AMI to update #9
5. cd /opt/coldfusion11/cfusion/bin/connectors
6. run "sudo ./"

Actual Result:
AH00526: Syntax error on line 6 of /etc/apache2/mod_jk.conf

Expected Result:
Connectors to upgrade

Any Workarounds:
remove and re-add connectors

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	4167033

External Customer Info:
External Company:  
External Customer Name: Christopher Tierney
External Customer Email:  
External Test Config: My Hardware and Environment details: Linux AWS AMI v11


  1. June 23, 2016 00:00:00: 1_Screenshot_2016-06-22_17.34.57.png


Two attempts with clean installs gave same results. See attached screen shot.
Comment by External U.
2289 | June 22, 2016 05:51:55 PM GMT
Coldfusion update modifies connector binaries. There is need to update apache mod_jk.conf file which will happen when re-add connector is done.Please follow the Post installation steps present in the doc The user has to do the recommended steps when update to/after # 3 is done. When new AMI for coldfusion will be available, this will not be an issue then.
Comment by Poonam J.
2290 | June 28, 2016 01:54:12 AM GMT
Thanks @Poonam. I will note that reference document. It would still be best however to update the AMI to update version 9 to avoid this issue for other users. When the update states it's a cumulative update, the person should not be expected to go back through 9 different install version notes to apply one update. Update notes should take this into account.
Comment by External U.
2291 | June 28, 2016 10:12:35 AM GMT
@Poonam, I just read the document you suggested. It makes no mention of updating apache mod_jk.conf. Please reevaluate your response as it appears to be incorrect.
Comment by External U.
2292 | June 28, 2016 10:16:27 AM GMT
@Christopher : Thanks for the response. I clearly understand your point here. This issue will not be there when a new version of AMI will released. For mod_jk.conf query you asked, user have to remove and re-add connector using wsconfig tool.The only step require is to remove and re-add connector and this issue will be resolved.
Comment by Poonam J.
2293 | June 28, 2016 09:59:39 PM GMT
@Christopher : If your doubts are clear, then I can go head and close this bug?
Comment by Poonam J.
2294 | June 30, 2016 09:32:42 PM GMT
@poonam as I am aware that this AMI will be discontinued shortly, feel free to close out the track. Thanks.
Comment by External U.
2295 | July 01, 2016 11:57:55 AM GMT
Thanks Christopher. Closing this chain.
Comment by Poonam J.
2296 | July 03, 2016 09:31:41 PM GMT