Project and Portfolio Management Practitioners Forum
cancel

After ITG HOME FileSystem refresh, services are not starting

Highlighted
Arjun_K
Member

After ITG HOME FileSystem refresh, services are not starting

Hello,

I had the PPM DEV home directory and DB refreshed by PROD home directory & DB. Before the refresh I took back up of server.conf

 

Soon after the refresh - I replaced server.conf (PRD) with server.conf(DEV)

- Executed kUpdateHtml

- Compiled JSP files

- Cleared work and tmp folders

 

But I'm unable to start the services.

 

After executing kStart.sh, when I run kStatus I see the below

 

Checking rmis://wpce16.hot:1098/KintanaServer

--> Error: Unable to connect; nested exception is

java.net.NoRouteToHostException: No route to host

 

I am also attaching the ServerLog.txt file for reference.

Am I missing something in this process? Any comments on this are greatly appreciated.

 

Additional Details:

Server OS - Linux

HP PPM Version - 8.01

Warm Regards,
Mallikarjun.S
7 REPLIES
Akif Saburi
Regular Collector

Re: After ITG HOME FileSystem refresh, services are not starting

Steps you have followed looks good. Can you attach ServerLog.txt

Regards,
Akif
kwood55
Frequent Visitor

Re: After ITG HOME FileSystem refresh, services are not starting

Just a note,check your procedure. I would have:

 

- Deleted the tmp and work folders

- Compile the JSP pages

- run kupdatehtml

 

If it still fails. You need to check the differences between server.conf prod and dev.

A port available on dev may not be available on prod.

AlexSavencu
Honored Contributor

Re: After ITG HOME FileSystem refresh, services are not starting

Hi,

I get this error when java is unable to open the port, hence I use ports above 15000 for the application server.

Change the rmi port, do the above steps again and it should work.

Cheers
Alex

--remember to kudos people who helped solve your problem
Arjun_K
Member

Re: After ITG HOME FileSystem refresh, services are not starting

Thank you  Akif,kwood & Alex. 

 

The issue was with security policies on the server that were rolled out at the time where the PPM DEV was down. 

The security on the server prevented HP PPM Server to connect to it's own IP! Meaning - The IP and HTTP PORT were open for the external entities (Ex: JNLP) but not to connect within.

 

This is new to me! 

 

Assuming we have two nodes : Does HP PPM server connects to it's own ports (HTTP_PORT, APP_SERVER_NAMING_SERVICE_RMI_PORT...etc )  while starting the services? 

 

Thank you,

Mallikarjun

Warm Regards,
Mallikarjun.S
AlexSavencu
Honored Contributor

Re: After ITG HOME FileSystem refresh, services are not starting

Hi, Malik,

Yes, this is normal. The machine has at least 2 ip addresses: the loopback and the " regular" ones. Whenever ppm opens a port in the regular network interface, it is filtered by the local firewall of the machine.

I am posting the below for anyone who reads the post:

As a rule, the error you got has only 2 causes:
1. You are trying to connect to the wrong machine. This occurs when environments are moved from one machine to another, or due to bad entries in the hosts file / DNS.
2. You are not allowed to open the port. This occurs either because of conflicts with another application, either due to local firewall restrictions.

Cheers
Alex

--remember to kudos people who helped solve your problem
Arjun_K
Member

Re: After ITG HOME FileSystem refresh, services are not starting

Hi Alex,

 

Thank you for the details. In my case this was the issue with Firewall settings.

 

This phenomenon compels me to ask another question.

 

When defining more than one node - is it a must to have all the below ports defined? 

 

@node

com.kintana.core.server.SERVER_NAME=
com.kintana.core.server.KINTANA_SERVER_NAME=kintana_n2
com.kintana.core.server.HTTP_PORT=8092
com.kintana.core.server.RMI_URL=rmis://wpce16.hot:1098/KintanaServer
com.kintana.core.server.SERVICES_ENABLED=TRUE
com.kintana.core.server.EXTERNAL_WEB_PORT=10001
#
com.kintana.core.server.APP_SERVER_NAMING_SERVICE_RMI_PORT=
com.kintana.core.server.APP_SERVER_NAMING_SERVICE_BINDING_PORT=
com.kintana.core.server.APP_SERVER_WEBSERVICE_PORT=
com.kintana.core.server.APP_SERVER_JRMP_INVOKER_RMI_PORT=
com.kintana.core.server.APP_SERVER_POOLED_INVOKER_BINDING_PORT=
com.kintana.core.server.APP_SERVER_HAJNDI_RMI_PORT=
com.kintana.core.server.APP_SERVER_HAJNDI_BINDING_PORT=
com.kintana.core.server.APP_SERVER_POOLEDHA_BINDING_PORT=
com.kintana.core.server.APP_SERVER_JMX_RMI_PORT=
com.kintana.core.server.APP_SERVER_UIL2_BINDING_PORT=

 

==============

 

I also notices that EXTERNAL_WEB_PORT must be defined for both the nodes when you are on 9.14 (8.10 worked without defining one!!)

Warm Regards,
Mallikarjun.S
AlexSavencu
Honored Contributor

Re: After ITG HOME FileSystem refresh, services are not starting

Hi, Malik,

Yes, all of those ports need to be defined if your nodes are configured in cluster mode.

And indeed, the external web port was not requested in the previous versions, but now it looks like it is mandatory.

Cheers
Alex

--remember to kudos people who helped solve your problem
//Add this to "OnDomLoad" event