tracker issue : CF-4207163

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

The Hotfix Installer should offer the option to "Restart ColdFusion after install?" - Yes/No

| View in Tracker

Status/Resolution/Reason: Open//

Reporter/Name(from Bugbase): John D. / ()

Created: 02/14/2020

Components: Installation/Config, Hotfix Installer

Versions: 2018

Failure Type:

Found In Build/Fixed In Build: /

Priority/Frequency: Normal /

Locale/System: / Win 2016

Vote Count: 1

The Hotfix Installer tries to start Cold Fusion in every case when the hotfix installation completes.

For those doing manual installs with CF services stopped, this hotfix automatic restart can cause serious problems, including starting as process under the installer's account and causing attempts to start the service with the "Services" tool to fail. It also confuses the installer who doesn't understand why CF is "working" (likely under the wrong account), yet can't be started as a service.

Instead, the Hotfix Installer should offer the user the option to "Restart ColdFusion after install? - Yes/No" as part of the install dialog.

This option would enable the administrator to take control of installation and prevent incorrect startup. It also allows checking update logs and things before putting ColdFusion back into production.



I should have clarified that I'm running the hotfix update jar at the command line with CF services stopped.
Comment by John D.
33124 | February 14, 2020 09:56:09 PM GMT
I would add that yet another possibility would be for it to ask whether to start CF as the service or not. The real problem is that it's a 50/50 chance whether it will or will not. As John added in his follow-up, this is indeed only an issue for those doing manual updates from the command line, not about those running the updater from within the CF Admin. I have seen the very confusion he refers to, many times. I have wondered if the problem may also be specifically related to whether someone (who does run CF as a service) may or may not have stopped the service before proceeding with that manual updater. Perhaps it's that if they do NOT, then it DOES try to start it as a service, whereas if they DO (stop the service, hoping to help the updater more likely be able to proceed), then maybe that's when CF decides it should just start CF as the user running the updater. I have not been able to test that theory. But one way or another, this problem (where it starts CF as the user running the update, rather than starting the service) is something that needs to be resolved, whether with a problem or a choice or a confirmation of whatever has happened.
Comment by Charlie A.
33174 | February 24, 2020 06:47:05 PM GMT
In my last sentence, I meant of course to say "whether with a *prompt*, or a choice, or a confirmation of whatever had happened".
Comment by Charlie A.
33175 | February 24, 2020 06:49:22 PM GMT