Skip to main content
D
defaulttetamx74bdq0
Participating Frequently
February 28, 2024
Answered

Cluster setup issue CF2023 Enterprise

  • February 28, 2024
  • 2 replies
  • 962 views

Hoping for some input/help. I have an IIS failover cluster freshly installed across two servers. We purchased CF2023 Enterprise and installed it on both servers. I ran the lockdown software per this document on both servers. When trying to add a remote instance per the instructions here (Registering a Remote Instance), the information seems to take but then the remote instance disappears from the list of servers after the form is submitted (and accepted). When attempting to edit/view the remote instance I just added, I get an error (An error occurred while executing the application. Please try again or contact the administrator.) and it is then removed from the list.

In looking at the coldfusion-error.log file, I see a line "SEVERE: Error storing instances.xml" and an access denied error to the instances.xml file (\cfusion\..\config\instances.xml (Access is denied)). I believe the issue is related to the lockdown tool. I was able to add remote instances before running the lockdown tool.

First question, obviously, is how to resolve this particular problem. Second, and maybe more importantly, is wheter my logic is sound with installing CF2023 on each of my IIS servers in the failover cluster.

This topic has been closed for replies.
Correct answer Charlie Arehart

Well, since you're asking I'll share a few thoughts.

 

First, you don't technically NEED to install cf in each server--if by that you mean for the two clustered iis servers to each have their own cf. You COULD have cf on only ONE server, talked to from BOTH iis servers. That would be a rare setup, BUT it's possible, yes. It's a variation of another notion (also not used that often): the connection of a web server machine to a cf instance running on a machine WITHOUT that web server is what's been traditionally called "distributed cf". There's no button or ui to "make that happen". Instead, there are steps in the cf docs.

 

But I don't think this is necessarily the best way to go. As you've already licensed the two cf servers, you can and probably should just stick with CF on each machine. There's benefit to redundancy and flexibility in being to take one down while the other remains running. 

 

What I MIGHT question is whether you should bother with the registering of remote instances as you've done, which presumes you'd be using cf enterprise's clustering feature. As you already have iis clustering, you don't NEED the load balancing aspect of cf clustering.

 

The other major part of cf's clustering feature is session replication--and some using cf clustering choose not to enable that for various reasons. In that case, you'd REALLY not NEED to use the cf clustering feature. 

 

And some folks who use that Cf session replication feature don't even need that, as cf2016 introduced redis session storage, which can be shared between multiple instances. (Note also that Cf redis sessions does not require use of cf Enterprise.)

 

It's true that Cf session replication REQUIRES use of the cf admin j2ee sessions feature, while cf redis sessions instead requires those be DISABLED. And some folks fear that Cf j2ee sessions "aren't as secure" as traditional cf sessions, but that's only true regarding their default configuration. Cf sessions can be made as secure as j2ee sessions.

 

Finally, I realize clustering is only in cf Enterprise (not Standard)--and without it, you may think "did we waste money then on cf Enterprise?"  But there are MANY more features cf Enterprise offers beyond this, and I've done an entire talk on the topic, available (recording and pdf) at carehart.org/presentations.

 

If somehow I didn't address your last comment seeking thoughts on your situation and any tips, let us know what you may still be seeking to confirm/check. 

2 replies

D
defaulttetamx74bdq0Author
Participating Frequently
July 2, 2024

I wanted to post an update here with more questions. I have an IIS cluster spanning two machines, let's call them web1 and web2. IIS on each machine is configured to share config files via a webstore directory. So a change made in IIS on web1 will be shared on web2.

 

I have ColdFusion Enterprise installed on both machines (two licenses). On web1, I created a cluster consisting of two instances, (one instance hosted on web1 and a second remote instance hosted on web2). Running the wsconfig tool on web1 will see the cluster as an option in the drop down.

 

However, running wsconfig on web2 will not present an option for the cluster since it's not configured on that machine. Is there a way to get this working in my scenario? Do I create a second cluster on web2?

Charlie Arehart
Charlie Arehart
Community Expert
July 2, 2024

Well, no, you don't NEED to create a CF cluster also on your web2 server. Could you? Yes, but the redundancy may not be worth the effort. 

 

Instead, you could setup web2's iis (and run that needed wsconfig tool) by way of using that "distributed cf" approach which I'd mentioned months ago here.

 

Sadly there's no longer a good cf doc page for the topic (the old technote here is from the cf7 timeframe and no longer useful since cf10 in 2012). 

 

Instead checkout this Adobe blog post from 2015 (notice also the comments from myself and others):

 

https://coldfusion.adobe.com/2015/07/setting-up-coldfusion-in-distributed-envionment/

 

Then in 2022 Adobe created another post, which while more recent is also in less detail:

 

https://coldfusion.adobe.com/2022/09/coldfusion-in-distributed-environment-windows/

 

Let us know if this approach may seem to better suit your challenge. 

/Charlie (troubleshooter, carehart. org)
D
defaulttetamx74bdq0Author
Participating Frequently
July 3, 2024

Thanks for reply and continued input. I had started moving towards setting up the distributed model back in March but I wasn't seeing where I would get the redundancy we're looking for so moved back towards clustering after purchasing a second license.

 

I read through the post and replies and that sounds like a solution on my second web server.  The only potential rub I see is that I have ColdFusion installed on the G:/ drive on both machines. Aren't the tie-ins between IIS and ColdFusion already in place on web2 or will the wsconfig tool, running from the C:/ drive, dictate the connection and how CF pages are handled?

D
defaulttetamx74bdq0Author
Participating Frequently
February 28, 2024

I was able to figure out part 1 of my issue. I needed to give the local ColdFusion account rights to the /config folder. After doing that, I was able to add the remote instance. Would still like to hear about whether my logic here is sound and whether there are any other tips/documentation available for similar scenarios.

Charlie Arehart
Charlie ArehartCorrect answer
Community Expert
February 29, 2024

Well, since you're asking I'll share a few thoughts.

 

First, you don't technically NEED to install cf in each server--if by that you mean for the two clustered iis servers to each have their own cf. You COULD have cf on only ONE server, talked to from BOTH iis servers. That would be a rare setup, BUT it's possible, yes. It's a variation of another notion (also not used that often): the connection of a web server machine to a cf instance running on a machine WITHOUT that web server is what's been traditionally called "distributed cf". There's no button or ui to "make that happen". Instead, there are steps in the cf docs.

 

But I don't think this is necessarily the best way to go. As you've already licensed the two cf servers, you can and probably should just stick with CF on each machine. There's benefit to redundancy and flexibility in being to take one down while the other remains running. 

 

What I MIGHT question is whether you should bother with the registering of remote instances as you've done, which presumes you'd be using cf enterprise's clustering feature. As you already have iis clustering, you don't NEED the load balancing aspect of cf clustering.

 

The other major part of cf's clustering feature is session replication--and some using cf clustering choose not to enable that for various reasons. In that case, you'd REALLY not NEED to use the cf clustering feature. 

 

And some folks who use that Cf session replication feature don't even need that, as cf2016 introduced redis session storage, which can be shared between multiple instances. (Note also that Cf redis sessions does not require use of cf Enterprise.)

 

It's true that Cf session replication REQUIRES use of the cf admin j2ee sessions feature, while cf redis sessions instead requires those be DISABLED. And some folks fear that Cf j2ee sessions "aren't as secure" as traditional cf sessions, but that's only true regarding their default configuration. Cf sessions can be made as secure as j2ee sessions.

 

Finally, I realize clustering is only in cf Enterprise (not Standard)--and without it, you may think "did we waste money then on cf Enterprise?"  But there are MANY more features cf Enterprise offers beyond this, and I've done an entire talk on the topic, available (recording and pdf) at carehart.org/presentations.

 

If somehow I didn't address your last comment seeking thoughts on your situation and any tips, let us know what you may still be seeking to confirm/check. 

/Charlie (troubleshooter, carehart. org)
D
defaulttetamx74bdq0Author
Participating Frequently
February 29, 2024

Thanks so much for laying this out. I wish I had posted to this group before recommending purchasing the Enterprise license. I had tried reaching out to Adobe support/sales before making the purchase and thought I understood things well enough to move forward with purchasing the one license for Enterprise.

 

Through your response, it's obvious that I would need a second license to run the software as I intended. I'm not going to be able to sell the idea to purchase a second license as it's not a small investment for the school I work for. I think a distributed install is the way to go here. I will dig in to the documentation and pivot accordingly.

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