Question
HTTP Status 404 on VMWare Exercises
Hi,
I am getting the following page when I launched the virtual machine on VMware with chrome or firefox.
OVA file : PegaFundamenals_716_2016_10_24
Is there a fix for the below issue?
Thanks in advance
HTTP Status 404 - /
type Status report
message /
description The requested resource is not available.
Apache Tomcat/7.0.72
I noticed similar thread to this which was resolved by re-downloading the .ova, but I didn that and have the same issue.
Also on the thread was advice to log onto the VM server and run "service tomcat status"... I get the following result: "Tomcat is running with pid: 1725"
Any and all help would be appreciated.
Using port 9080 gives a Tomcat 404 message
Tried using 8080 following your message, it gives "Problem loading page" Cannot connect
this could be blocking on your local machine. I am going to assume you are using Windows? If so, open a command window and enter: ping xxx.xxx.xxx.xxx
where xxx.xxx.xxx.xxx is the IP address of the VM. Let me know if your local machine gets a reply.
eddie
Ping results from the local machine and across the network are the same:
Pinging 192.168.0.7 with 32 bytes of data:
Reply from 192.168.0.7: bytes=32 time=3ms TTL=64
Reply from 192.168.0.7: bytes=32 time=1ms TTL=64
Reply from 192.168.0.7: bytes=32 time=4ms TTL=64
Reply from 192.168.0.7: bytes=32 time=1ms TTL=64
Ping statistics for 192.168.0.7:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 4ms, Average = 2ms
Richard,
the good news is it's not just you. I have the same experience when I try to access the URL on this VM.
From the date stamp on the OVA file, I can tell this is a recent update. Not sure what is wrong. Let me check a few things and I will get back to you.
eddie
Well....
Seems the tomcat /ROOT dir is empty. Not sure why that is, but that is why you can't get to the tomcat home page; which is where the http://xxx.xxx.xxx.xxx:9080 URL directs you.
I will get an update out today. In the meantime you can use the VM you already have.
Modify the URL you are using to this:
http://xxx.xxx.xxx.xxx:9080/prweb (replace the xxx's with the IP address from your VM but notice the /prweb at the end of the port number).
let me know how you get along
eddie
Awesome thanks
Yeah..When I observe VM exercise http://xxx.xxx.xxx.xxx:9080/manager/ then page displayed whole information on regard also, I see that here self_start service is in false status without itself "started". All remaining are in up. This is one thing that how we could compile this to start, If at all this is the probem?
Perfect for me
Can you verify which port you are using? Are you accessing port 8080 or port 9080?