Pega Server in LSA 8.5 VM Virtual Box is down
Hi All,
I have downloaded the PEGA 8.5 Exercise system and running it in VirtualBox on Mac device. I am able to login into the Server. But when i hit http://localhost:port/prweb , it says the service is unavailable.
I am able to access the http://localhost:9080
Also i am not sure of password of the tomcat manger or host manger. Please help
Pegasystems Inc.
US
@kumav6 if you can get to localhost, but not ./prweb this tells me tomcat is not running. Check the status of tomcat from the command line: service tomcat status or service tomcat7 status (I forget how they installed tomcat for the LSA VMs).
if the result is Tomcat not running, then you need to start tomcat: service tomcat start
then, if this turns out to be the issue (tomcat not starting on boot), after you start tomcat, set tomcat to autostart: chkconfig --level 3 tomcat on
let me know how you get along
STG Inc
US
Hi @eddie.jm - I am also facing the above pega login issue. When i checked the tomcat homepage i.e., localhost:9080 some apps are running perfect. But "prweb" is not running and when i try to run it i'm getting the below error message on the screen --
FAIL - Application at context path [/prweb] could not be started.
Also one more observation with respect to postgresql. Not sure whether this relates to the same issue - I tried login to postgresql - via localhost:91/phppgadmin/ with the default credentails - username - "postgres" and password - "postgres" and getting a message as "login failed".
I tried to analyse this DB issue with below source, asking to modify something "pg_hba.conf". But dont have permissions to do so for architect.
https://stackoverflow.com/questions/23194369/how-to-use-phppgadmin-with-postgres
Appreciate your help and thanks in advance... !
Pegasystems Inc.
US
@NaveenP Hi Naveen, apologize for the delayed response.
You do not need to access the postgres db to edit the pg_hba.conf file. Log in to the VM console and use VI, or use an app such as PuTTy, FileZilla, CyberDuck, or - my favorite - Atom to connect to the VM and edit the file.
But...I do not believe db access is the issue. The error message you posted indicates tomcat is not started. Log in to the VM console and enter the command service tomcat status (or service tomcat7 status; I forget which they used). If tomcat is not running, then we can go from there.
I suspect this is a RAM issue. The VM may be set to use more RAM than you have available on your local system.
STG Inc
US
@eddie.jm Sorry for coming back so late but glad that I found the fix. :)
Thanks for your guess on RAM and Indeed its memory issue. I have upgraded my laptop hardware RAM from 8 GB to 24 GB by adding new 16 GB stick. I have reinstalled the VM image with configuration 2 CPU and 16 GB RAM memory. After that i see working everything perfect and no additional configurations.
Cheers - NP