We are running CF2018 Update 3 with external web server (Apache) and we are getting ready to update the server to Update 5. I understand that I’ll have to upgrade to Update 4 before we go to 5. I was reading through documentation (https://helpx.adobe.com/coldfusion/kb/coldfusion-2018-update-5.html#Connectorconfiguration) and it says that we have to “Recreate Connector”.
After upgrading to Update 5 I ran the connector and got message that it was already configured:
[root@server1]# ./wsconfig -ws Apache -bin /usr/sbin/httpd -script /usr/sbin/apachectl -dir /etc/httpd/conf/ -v
command line: -ws Apache -bin /usr/sbin/httpd -script /usr/sbin/apachectl -dir /etc/httpd/conf/ -v
This web server is already configured for ColdFusion.
Do we have to run wsconfig just to make sure mod_jk.so gets updated?
I'm not sure if you have to run wsconfig for the mod_jk.so, but I do know that you have to remove the current connector and then recreate the connector in order for this to work. At least, that's been my experience, and I just recently switched from CF11 to CF2016.
^ _ ^
Run wsconfig, remove the current connector, then add the new one pointing at your Apache folders.
^ _ ^
I have a lot of experience with this. I don't recommend update to new mod_jk.so. You can do the Update 5 without updating to Update 4 before it because all CF updates are cumulative. However recreation of mod_jk.so file with wsconfig cause the problems with HTTPD service in CentOS 7 for me. That's why I can not recommend wsconfig update. I am currently researching Update 5. If you need more help PM me. Also do you speak Serbian? Might be easier that way 🙂
Before giving up entirely on the update (and the updated connector), note that Adobe has created a blog post today where they offer an updated connector (.dll file for IIS, .so file for Apache). While the title of the post may not make it seem it applies to you, I would recommend folks in this thread at least try it before deciding not to update (since the update does add important security fixes). And if it somehow does NOT work, then report that to Adobe at email@example.com (yes, that's one "L"):
Even that "updated" version of mod_jk.so creates the same problem for me.
Here is the whole email I have already sent to Adobe Support:
"Hi Adobe Support,
I have found an error with CF 2018 Update 5.
I am running CentOS 7 and CF 2018 and with Update 5 Connector recreation is required which actually causes the problem.
After extracting and updating mod_jk.so my Apache started failing to start/restart randomly.
I did some research and found out that latest mod_jk.so causes those Apache problems.
Version of mod_jk.so before the Update 5 works w/o problems.
So mod_jk.so 1.2.46 – 314600 cause Apache in CentOS 7 problem (comes with Update 5 and recreation is required),
while mod_jk.so 1.2.46 – 312584 works just fine (came with previous updates starting with Update 2).
I was (probably not the only one) person that found out vulnerability in long time ago used mod_jk.so 1.2.41 after what you pushed Update 7 for CF 2016 and Update 2 for CF 2018 with 1.2.46.
However I have servers with CF 2016 on CentOS 7 with Apache. One of them got updated to latest Update 12 and mod_jk.so 1.2.46 – 314600 works with Apache totally fine.
- I have problem with combination: CF 2018 – CentOS 7 – Apache 2.4.6 90.el7.centos – mod_jk.so 1.2.46 – 314600
- I don’t have problem with combination: CF 2016 – CentOS 7 – Apache 2.4.6 90.el7.centos – mod_jk.so 1.2.46 – 314600
I resolved the problem with using older version of mod_jk.so 1.2.46 – 312584.
If you find out this as interesting please let me know but this might need some fix."
It took me some time testing everything, going through the snapshots, reinstalling CF and updates, one by one, thorough research you can say. So that's why I answered with confidence.
Yes, you are right, I have fixed the error I made with CF 2017 where I meant CF 2016, and the only problem is combination of CF 2018 - CentOS 7 - Apache and mod_jk.so that Update 5 brought, also the mod_jk.so that they post as a replacement so people can use remote port. Both those mod_jk.so files make Apache not start/start randomly which is unstable environment.
These are errors that I am getting with those 2 different mod_jk.so files (read them with dmesg command):
[ 7.168752] httpd: segfault at 7f114c680e10 ip 00007f114c680e10 sp 00007f114bc2c268 error 14 in mod_cgi.so[7f114c8b5000+6000]
[ 71.645658] httpd: segfault at 7f3264436e20 ip 00007f3264436e20 sp 00007f3263a0edd8 error 14 in libbz2.so.1.0.6[7f3264898000+f000]
[ 83.935579] httpd: segfault at 7f37944f4961 ip 00007f37a0d0f66c sp 00007f3793a7e560 error 4 in libapr-1.so.0.4.8[7f37a0d02000+2d000]