Re: Instance manager works, can't view instance itself

[David Stockton]

Hello Pete,

FRAM just holds a link to the instance using the settings configured at install time. However, it could be that settings have changed or similar. The quickest thing to do to fix the link is in FRAM (where you have the "instance link") - on the left hand menu you'll see a sub-section "Enterprise" and within it a link "Manage Servers". Click this and then you'll see a list of the instances. Click the edit icon and update the IP & port number to match your server (i.e. the external IP & 8089). Save that and then you should be good again.

Best regards,

David Stockton

Fusion Team

On Wednesday, 12 September 2012 09:30:18 UTC+1, Comcar wrote:

I recently upgraded to FR 4.5, running on CF9.0.2

I've got into the Instance Manager and used the scan system feature to find my Coldfusion installation, kept all the basic settings, I ticked listen on all IP addresses, but when I click the "Instance Link" in Chrome from my desktop in the office, I get a page not found error.

It's trying to open in an internal IP (127.0.0.1) so if I switch that for our actual site IP, I get exactly the same error message.

The instance manager can be viewed with port 8088 and that works, but the instance link opens with port 8089 in the URL - and fails.

I've restarted my CF9 instance, but that's not helped. I'm not sure what else to do.

Pete

[Charlie Arehart]

Pete, can you clarify first if the browser is running within or outside of
the network, where the IP address is being used? If outside, does it work if
you are inside (on the server running the FRAM and CF instances)? There can
be firewall issues at play here (perhaps allowing your 8088 link while
denying the 8089 one).

Also, you mention that the instance manager is at 8088. The default is for
it to be at 8087. Did you change that (for the FRAM instance, which hosts
the instance manager) during the install? Just curious.

/charlie

-----Original Message-----
From: fusion...@googlegroups.com [mailto:fusion...@googlegroups.com]
On Behalf Of Comcar
Sent: Wednesday, September 12, 2012 4:30 AM
To: fusion...@googlegroups.com
Subject: [fusionreactor] Instance manager works, can't view instance itself

I recently upgraded to FR 4.5, running on CF9.0.2

I've got into the Instance Manager and used the scan system feature to find
my Coldfusion installation, kept all the basic settings, I ticked listen on
all IP addresses, but when I click the "Instance Link" in Chrome from my
desktop in the office, I get a page not found error.

It's trying to open in an internal IP (127.0.0.1) so if I switch that for
our actual site IP, I get exactly the same error message.

The instance manager can be viewed with port 8088 and that works, but the
instance link opens with port 8089 in the URL - and fails.

I've restarted my CF9 instance, but that's not helped. I'm not sure what
else to do.

Pete

--
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/-/cIx2bCocPbUJ.
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.

[Comcar]

When you say the external IP, do you mean the IP that matches the URL? As in Comcar.co.uk is at 89.234.7.152.

Because that option doesn't appear in the drop down when editing the instance, I just get 127.0.0.1 (local host), 192.168.100.152 (which I'm guessing is the local network IP) and 10.222.9.23 (no idea what that is)

Also, I don't have an enterprise sub-section in my navigation, I've got "Instances > Instance Manger".

I feel like I'm getting a lot wrong :S

[Comcar]

If I visit 8087, I log in to version 4.0.5, and get basically the same admin panel, which again has a link to the instance on port 8089.

I think I might have installed the new version next to the older version using a different port - maybe that's the problem.

You might be right on the firewall issue, I get the same issues if I change the port number to 8090, 8091. I've no idea how to open that port, I'll have a look.

I'm viewing from outside the network, I'm just trying to view the admin panel over the internet from our office - the server is off site. I used to be able to do this on the older version, I've just screwed up the upgrade.

Pete

[David Stockton]

Hi Pete,

You're right. You've installed FRAM twice which is a bit of an odd situation I've not come across before. Whilst we could probably help you remove the old FRAM and reconfigure everything, I'd suggest the simplest way forward might be to uninstall both copies of FusionReactor completely and then just install a single fresh copy. Whilst you'd loose your settings and any old log files, it's a simple procedure and will get you the cleanest results.

Best regards,

David Stockton

Fusion Team

[Comcar]

That's genuinely a sensible idea... take "turn it off and on again" to the next level. I will start again with a clean slate and let you know! Thanks.

[Charlie Arehart]

Beyond David’s helpful suggestion, I’ll point out also that you didn’t likely hit the firewall problem before because you were accessing the FR interface via http://yourdomain/fusionreactor/fhtml.cfm (note that I am not using a port there, which means the request is going through your external web server, whether IIS or Apache). That’s still possible in FR 4. If you’ve not yet uninstalled, you may want to try that. (I should add that you are asked during installation of FR into an instance whether you want to allow that access via the external web server. You can also change it by editing the instance in the FRAM instance manager.)

 

/charlie

[Comcar]

I did try accessing without the port, I was getting "fhtml.cfm does not exist" errors.

I've started un-installing now though.

[Charlie Arehart]

Pete, did you end up sorting things out? It seemed one of your problems was that you somehow had two implementations of the FRAM instance, which is not supposed to happen. :-) Hope uninstalling (both) and reinstalling FR worked out.

/charlie

 

From: fusion...@googlegroups.com [mailto:fusion...@googlegroups.com] On Behalf Of Comcar
Sent: Wednesday, September 12, 2012 6:02 AM
To: fusion...@googlegroups.com
Subject: Re: [fusionreactor] Instance manager works, can't view instance itself

 

I did try accessing without the port, I was getting "fhtml.cfm does not exist" errors.

[Comcar]

Ok I'm back on this now.

I've run the installer and it's worked, but if I visit http://comcar.co.uk:8087, I get nothing.

I've opened this port up to accept traffic my IP address, so I'm not sure why I can't load the FRAM

Pete

[David Stockton]

Hello Pete,

Did you choose an alternative port number (rather than the default 8087) during the install?

Can you open http://127.0.0.1:8087 on the local machine itself?

Is "framd" (Linux) / "FusionReactor AM" service (Windows) running?

Thanks,

David Stockton

Fusion Team

--

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/-/Nk6mzLyDTUkJ.

[Comcar]

I stuck with port 8087, framd is running (it comes up if I do ps -lax | grep framd).

I'm no a headless linux box - but if I use lynx and try to connect to 127.0.0.1:8087 I get "Alert! Unable to connect to remote host"

If I try to connect to port 8088, I get redirect to a 404 page saying "/fusionreactor/" not available - does that mean I've not properly uninstalled the old installation then?

Pete

[David Stockton]

Hello Pete,

That sounds likely. You've probably got the old FusionReactor running on 8088 still and for some reason FRAM isn't truly starting yet.

Can you use the "netstat" to command to see whether the FRAMd process is even listening on port 8087 please?

Additionally, can you use the netstat command to see which process is listening on port 8088?

Best regards,

David Stockton

Fusion Team

[Comcar]

Hi David, 

I've run the following:

$ /etc/init.d/framd start

Starting framd

$ netstat -lptu | grep 8087

$ netstat -lptu | grep 8088

I get nothing back from the last 2 commands - not sure if they're the best commands to use?

Pete

[David Stockton]

Hello Pete,

I think the quickest thing to do would be to jump on a quick screen-share & conference call. If you drop us an email sup...@fusion-reactor.com with your email address, phone number and reference/link to this thread then someone (likely me) will be able to help later this morning.

Many thanks,

David Stockton

Fusion Support Team

To view this discussion on the web visit https://groups.google.com/d/msg/fusionreactor/-/mup8DCUep_UJ.

[Comcar]

Scrap that last comment, I did:

$ /etc/init.d/framd restart

And now the FRAM is running. I've scanned the system and installed my instance, and FRAM has chosen port 8088. 

So I'm back to where I was before, I have the FRAM but can't view the stats for my instance.

Running these now:

$ netstat -lptu | grep 8087

tcp        0      0 *:8087                      *:*                         LISTEN      313/java

$ netstat -lptu | grep 8088

So nothign on port 8088.

I've tried accessing (via lynx on the command line) http://127.0.0.1 and it doesn't work, and I can't access it through the web browser on my computer either.

I can get to http:127.0.0.1:8087 using lynx though.

For the instance set up, I've got:

IP Address: 127.0.0.1

Listen on all addresses: ticked

Port: 8088

Enable web server: ticked

Listen on external web server: ticked

I appreciate both your help on this long running topic.

Pete

[Comcar]

Ok, I uninstalled everything again.

I killed anything listening on port 8087.

I reinstalled it and got it running as the same user as Coldfusion - which I wasn't doing before hand, it was running as root.

I followed the guide here and added my instance: http://docs.intergral.com/display/FR452/Installing+FusionReactor+in+Locked+Down+Environments

I installed the FR coldfusion extensions and added my instance.

Then I restarted CF (hopefully for the last time today) and everything is running fine now.

In conclusion:

 - I didn't uninstall and STOP v3 before upgrading, so the ports were still being used by processes from v3

 - When I sorted that out, I was getting my runtime users and permissions wrong

Sorry for taking so long, thanks for all the help!

Pete