Skip to main content
damned_virus
Participating Frequently
September 17, 2025
Answered

Apache intermittently fails to start when coldfusion installed

Afternoon folks

 

New build of coldfusion 2025 on Ubuntu. Apache version 2.4.52.

 

On starting the apache service, I periodically get this:


Sep 17 16:01:00 intranet01.tectcorp.com systemd[1]: Starting The Apache HTTP Server...
Sep 17 16:01:00 intranet01.tectcorp.com apachectl[1813]: Segmentation fault (core dumped)
Sep 17 16:01:00 intranet01.tectcorp.com apachectl[1813]: Action 'start' failed.
Sep 17 16:01:00 intranet01.tectcorp.com apachectl[1813]: The Apache error log may have more information.
Sep 17 16:01:00 intranet01.tectcorp.com systemd[1]: apache2.service: Control process exited, code=exited, status=139/n/a
Sep 17 16:01:00 intranet01.tectcorp.com systemd[1]: apache2.service: Failed with result 'exit-code'.
Sep 17 16:01:00 intranet01.tectcorp.com systemd[1]: Failed to start The Apache HTTP Server.

 

This only happens every few times that I try to start apache. If I try to start it again after the failure, it usually starts without error. Then after a couple of times of stopping and starting the apache service, I get the error again.

 

If I take the following config out of apache2.conf:

 


Include "/etc/apache2/mod_jk.conf"
Include "/opt/coldfusion2025/config/wsconfig/1/mod_jk_vhost.conf"

 

It works 100% of the time, so coldfusion appears to be at fault. I have looked through the log files, but don't see anything that stands out as being useful. Anyone seen this before?

    Brian BockholdCorrect answer
    Participant
    September 24, 2025

    I ran into this about a month ago with Ubuntu and the same Apache version. This is a bug with the mod-jk drivers that Adobe and I had to get a new mod-jk.so file from support to get it resolved. They told me they would provide the fix in the next update, but Adobe Support should be able to get you the updated .so file. 

    View reply

    22 replies

    Brian BockholdCorrect answer
    Participant
    September 24, 2025

    I ran into this about a month ago with Ubuntu and the same Apache version. This is a bug with the mod-jk drivers that Adobe and I had to get a new mod-jk.so file from support to get it resolved. They told me they would provide the fix in the next update, but Adobe Support should be able to get you the updated .so file. 

    Translate
    damned_virusAuthor
    Participating Frequently
    September 24, 2025

    Thank you Brian. Do you have the ticket #? I have a ticket in with support, but they seemed entirely unaware of this. I will give them your ticket # for reference.

    Translate
    damned_virusAuthor
    Participating Frequently
    October 9, 2025

    @damned_virus , thanks for the new update.

    Nevertheless, I am surprised that Adobe Support is continuing a dialogue about a fix for Apache version 2.4.52 on ColdFusion 2025, without mentioning an Apache upgrade.

     

    The support matrix for ColdFusion 2025 clearly states that you should use Apache 2.4.62 or newer. In other words, it is inadvisable to use Apache 2.4.52 on ColdFusion 2025. So, the fix is actually to upgrade Apache.

     




    I'm actually on 2.4.58 now. With that said, while I appreciate what you're saying, I'm using the latest version of Ubuntu LTS. If I want to remain supported with Ubuntu, I need to stick to the version provided by the official respository, which is currently 2.4.58. There is no LTS version of ubuntu currently that comes with Apache 2.4.62 or newer

    Translate
    Charlie Arehart
    Community Expert
    Charlie ArehartCommunity Expert
    Community Expert
    September 17, 2025

    While there may be more diagnostic info in any of various logs (apache or cf), it may prove rather simple to solve.

     

    Do you find a workers.properties file in your /opt/coldfusion2025/config/wsconfig/1/ folder? In that change the value of heartbeat_interval to 0, which disables the connector heartbeat mechanism (used only by the cf pmt, which you may not even be using to monitor this cf instance). Restart apache, which will reload and pickup the change to that file. Let us know if that helps.

     

    Or let us know if you may dig further into the various logs, to find any additional detail. 

    Translate
    /Charlie (troubleshooter, carehart. org)
    damned_virusAuthor
    Participating Frequently
    September 17, 2025

    There is no workers.properties file in that location. Not sure if there is supposed to be? I'll review the log files again and see if I missed anything the first time around.

    Translate
    damned_virusAuthor
    Participating Frequently
    September 17, 2025

    Found it in \etc\apache2. Making change and testing

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