Instance Hanging
Randy Johnson
charlie arehart
Randy, the FRAM instance (running at port 8087) runs atop an embedded Tomcat deployment, so it will have no affect on CF at all.
That said, are you sure it’s that FRAM instance that you mean to say is hung? Are you confirming it’s port 8087 you see? And what do you mean “hung”? The interface appears but you can’t do anything with it? Or it never appears?
Or might you really mean the FR interface for your CF instance (which might be at port 8088, for instance)? And same question about clarifying “hung”. Tell us what you see.
As for “restarting the fusion reactor service”, let’s be clear: that would restart only the FRAM instance (technically, that embedded Tomcat instance). Again, this would have no effect on CF at all. And to be clear also, there is no FusionReactor service for the FR interface for your CF instance, if you (or anyone) may wonder. The FR interface for your CF instance shows info gathered by the FR that’s embedded within the CF instance itself (when you install FR into it). So if you ever felt you wanted to “restart” “that” FR instance, you would technically need to restart CF.
That said, and though many don’t notice it, there is an option to stop and start FR within a CF (or other monitored) instance. Look at the green button at the very bottom left of the nav bar in the FR interface (for the instance you’re monitoring). If you click that, it takes you to a page that lets you stop or start FR monitoring of that instance. If ever one has a concern about whther FR is causing some issue, consider doing that before uninstalling FR from the instance (or entirely).
Hope some of that helps with your question.
/charlie
--
You received this message because you are subscribed to the Google Groups "FusionReactor" group.
To view this discussion on the web visit https://groups.google.com/d/msg/fusionreactor/-/6LV8Y2vgHqcJ.
To post to this group, send email to fusion...@googlegroups.com.
To unsubscribe from this group, send email to fusionreacto...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/fusionreactor?hl=en.
Randy Johnson
To unsubscribe from this group, send email to fusionreactor+unsubscribe@googlegroups.com.
David Stockton
After installing FusionReactor into the CF instance, you must restart ColdFusion to complete the installation - did you do this step?
Alternatively, could it be that there's a firewall blocking port 8088 between your machine (where the web browser is) and the server - obviously if you're running the test directly on the browser on the server this won't be the case.
Best regards,
David Stockton
Fusion Support Team
Randy Johnson
Hi David,
FR has been installed for months and has been working just fine until last weekend when it stopped responding. I checked it again just now to make sure it wasn’t a firewall issue.
I think the point I am still unclear about is if I have to restart CF in order to get the 8088 instance back online and is there a log file for me to look in to see if there are any clues as to why it is not responding.
Thanks!
Randy
--
You received this message because you are subscribed to the Google Groups "FusionReactor" group.
To view this discussion on the web visit https://groups.google.com/d/msg/fusionreactor/-/TcqGd3bNU3oJ.
To post to this group, send email to fusion...@googlegroups.com.
To unsubscribe from this group, send email to fusionreacto...@googlegroups.com.
charlie arehart
Randy, are you making this request on the machine with the instance in question? It’s an important point. If on a remote machine, there can be all kinds of explanations of what “changed”. But if you can get to it locally, then that helps start where to look for what’s amiss.
And are you getting the link from the Enterprise Dashboard? Or the Instance Manager in FRAM? Either of those could have been changed on you, perhaps. What if you try different URLs?
The FR instance (responding on 8088) is just a web server built-into CF. There’s no way to “restart” it on its own, but yes, restarting CF would “restart” that web server. It shouldn’t be needed, though. As for logs, there is a reactor.log in FR, which would be in the [fr]\instance\[instancename\log or archives directory like all the other FR logs. You may see something there.
Here’s still another idea. If you use the same URL you use to access CF (whatever domain name, IP address, or machine name you use, for CF or the admin), what happens if you add :8088 to that?
Finally, here’s still another idea: you may be able to access FR by REMOVING the 8088 port. By default, FR can respond via an external web server also.
Let us know if/how any of that helps.
/charlie
Randy Johnson
Responses are below.
From: fusion...@googlegroups.com [mailto:fusion...@googlegroups.com] On Behalf Of charlie arehart
Sent: Tuesday, May 15, 2012 3:56 PM
To: fusion...@googlegroups.com
Subject: RE: [fusionreactor] Instance Hanging
Randy, are you making this request on the machine with the instance in question? It’s an important point. If on a remote machine, there can be all kinds of explanations of what “changed”. But if you can get to it locally, then that helps start where to look for what’s amiss.
Randy -> I am making the request on the same machine.
And are you getting the link from the Enterprise Dashboard? Or the Instance Manager in FRAM? Either of those could have been changed on you, perhaps. What if you try different URLs?
Randy -> The link I am using is the one from my bookmarks:
Randy -> http://myip:8088/fusionreactor/fhtml.cfm?mode=login
The FR instance (responding on 8088) is just a web server built-into CF. There’s no way to “restart” it on its own, but yes, restarting CF would “restart” that web server. It shouldn’t be needed, though. As for logs, there is a reactor.log in FR, which would be in the [fr]\instance\[instancename\log or archives directory like all the other FR logs. You may see something there.
Randy -> The heartbeat log has a 1 in the Dirty Shutdown / Start up column. Could that be the culprit? There was nothing in the reactor log that offered any help.
Here’s still another idea. If you use the same URL you use to access CF (whatever domain name, IP address, or machine name you use, for CF or the admin), what happens if you add :8088 to that?
Randy -> I tried using localhost and 127.0.0.1 with no luck. My normal way is to use the machine IP.
Finally, here’s still another idea: you may be able to access FR by REMOVING the 8088 port. By default, FR can respond via an external web server also.
Randy -> I may do this after down the line if I absolutely cannot get it to work.
From: fusion...@googlegroups.com [mailto:fusion...@googlegroups.com] On Behalf Of Randy Johnson
Sent: Tuesday, May 15, 2012 3:37 PM
To: fusion...@googlegroups.com
Subject: RE: [fusionreactor] Instance Hanging
Hi David,
FR has been installed for months and has been working just fine until last weekend when it stopped responding. I checked it again just now to make sure it wasn’t a firewall issue.
I think the point I am still unclear about is if I have to restart CF in order to get the 8088 instance back online and is there a log file for me to look in to see if there are any clues as to why it is not responding.
Thanks!
Randy
--
You received this message because you are subscribed to the Google Groups "FusionReactor" group.
charlie arehart
Randy, as for your last point, please try it right away. It would be an important piece of diagnostic information. If it worked, then it confirms that FR itself is fine, but there may be an issue with the internal web server (or your configuration of it, or an issue in your network). I appreciate that your stance is “nothing changed” and it must be a FR problem. But help us help you to confirm exactly what the problem is. :-)
/charlie
Randy Johnson
Fair enough. How do I remove the port?
Randy
--
charlie arehart
Ah, I see. You thought I meant something more than I did, which may explain why you were saying you wanted to “wait on trying it”.
I’m just saying remove it from the URL you are using when you browse to open FR. :-)
So where you said you’re using:
http://myip:8088/fusionreactor/fhtml.cfm?mode=login
try:
http://myip/fusionreactor/fhtml.cfm?mode=login
Now, it’s possible that such a URL could fail, for reasons having nothing to do with FR. If it does, try this instead: use whatever URL you would to access the CF Admin (or your web site), and then add /fusionreactor/fhtml.cfm?mode=login to that URL. And try it both from your local machine and also from outside the machine. Sometimes folks find they can’t even access their production web sites on the machine itself.
My point is that while you may not think you could possibly access FR using your “public domain”, you may well be able to. Since you have to have a password to access FR, it’s not a real security problem. Let us know how that goes.
Randy Johnson
Removing the port number from the URL worked.
The first question I now have is why? No server updates / FR / CF updates were done.
My second question is why was the port number suggested to use if it worked without the port number?
It is showing that FR is running, I guess it is something with the internal web server eh?
--
charlie arehart
Glad that it helps you at least get working. That was the first and foremost concern. Second, yes, it shows that either there is an issue with the internal web server, or with something else in your environment (firewall on the box, firewall on the network, firewall on your client, VPN blocking ports, etc.), though I realize you may be able to prove conclusively that it’s none of those things.
Here’s another thought: can you get into the FRAM instance (8087)? If so, that helps with 2 things: first, if you could, it would support that it’s less likely a problem with your environment. If you can get to 8087, then you should be able to get to 8088, or whatever is the port for the CF instance.
But the best result of getting to the FRAM instance is that you can then confirm what SHOULD be the port you’re to use for the CF instance. Whereas in FR3 and before, one configured the port for the given FR instance within that instance’s interface (under FR>settings), in FR4 you now configure that in the FRAM instance instead. You can use this to confirm what port you should have been using. See the FRAM Instance Manager, then click the “edit” button for your instance in question.
What port is that? If it’s different than you expected, problem solved perhaps. If it’s what you expected, what is the “IP address” selected? Maybe seeing (or changing) that will help resolve things.
Do let us know how it goes.
/charlie
From: fusion...@googlegroups.com [mailto:fusion...@googlegroups.com] On Behalf Of Randy Johnson
Sent: Thursday, May 17, 2012 6:33 AM
To: fusion...@googlegroups.com
Subject: RE: [fusionreactor] Instance Hanging
Removing the port number from the URL worked.
Randy Johnson
Here’s another thought: can you get into the FRAM instance (8087)? If so, that helps with 2 things: first, if you could, it would support that it’s less likely a problem with your environment. If you can get to 8087, then you should be able to get to 8088, or whatever is the port for the CF instance.
Yes I am able to access the FRAM. Still no luck on the 8088
But the best result of getting to the FRAM instance is that you can then confirm what SHOULD be the port you’re to use for the CF instance. Whereas in FR3 and before, one configured the port for the given FR instance within that instance’s interface (under FR>settings), in FR4 you now configure that in the FRAM instance instead. You can use this to confirm what port you should have been using. See the FRAM Instance Manager, then click the “edit” button for your instance in question.
I found the instance manager and the port is 8088.
The ipaddress is the external ipaddress. Other options are the 10.x.x.x local network ip and 127.0.0.1
Randy
From: fusion...@googlegroups.com [mailto:fusion...@googlegroups.com] On Behalf Of Randy Johnson
Sent: Thursday, May 17, 2012 6:33 AM
To: fusion...@googlegroups.com
Subject: RE: [fusionreactor] Instance Hanging
Removing the port number from the URL worked.
The first question I now have is why? No server updates / FR / CF updates were done.
My second question is why was the port number suggested to use if it worked without the port number?
It is showing that FR is running, I guess it is something with the internal web server eh?
Randy
--
charlie arehart
Good to hear. Thanks for the clarifications. So what happens if you change it to the localhost address and try to access it from localhost?
Also, in all this, have you had occasion to restart the CF instance? It could just be some hiccup which might just go away, never to recur. It’s happened once in a while to others (which makes it hard to debug, of course).
If neither of those help, perhaps then the Intergral folks can dig in more. Now’s a little of a tough time in that respect: some are here at cfobjective this week, and otherwise it was a holiday at the end of the week in Germany.
On top of that, they released 4.5 this week (and part of the lack of news about it has been for the above). There’s always a lot of work and pressure leading up to a new release, and sometimes everyone just needs a break for a few days to recover.
Let’s see what we may hear next week on the release and Randy’s issue, if he reports still having a problem.
/charlie
From: fusion...@googlegroups.com [mailto:fusion...@googlegroups.com] On Behalf Of Randy Johnson
Sent: Friday, May 18, 2012 11:52 AM
To: fusion...@googlegroups.com
Subject: RE: [fusionreactor] Instance Hanging
Here’s another thought: can you get into the FRAM instance (8087)? If so, that helps with 2 things: first, if you could, it would support that it’s less likely a problem with your environment. If you can get to 8087, then you should be able to get to 8088, or whatever is the port for the CF instance.
Darren Pywell
--