Project and Portfolio Management Practitioners Forum
cancel

Bug at starting the PPM clustered server and kSupport issue

Highlighted
Abhi_Agrawal
Respected Contributor.

Bug at starting the PPM clustered server and kSupport issue

Hi,

 

We have recently upgraded system to PPM v9.13. At 9.13, we are not able to get kSupport script result because this script is giving following error: -

Could not connect to database via JDBC. Please verify that the password is correct.

 

Although, I have verified that db password is correct and we can even connect to db through sqlplus.

 

We have clustered environment (4 nodes connected through hardware load balancer and using http_port 8035 on all servers) and since 9.13 we are using only 1 server.conf (which is in sharable folder) among all servers.

 

Also, I'm not able to start node# 2 & 3, its giving following error: -

STATUS server:main:com.kintana.core.server.ServerStartupSanity:2012/02/01-11:17:27.339 EST: Running pre-startup checks for node ppmtest2.mhe.mhc in clustered mode
STATUS server:main:com.kintana.core.server.ServerStartupSanity:2012/02/01-11:17:27.363 EST: Checking: /ppm04/var/config/server.conf
ERROR server:main:com.kintana.core.server.ServerStartupSanity:2012/02/01-11:17:27.812 EST:
================================================================================
The following errors were found which prevent this node starting
ppmtest2.mhe.mhc: Port 8035 for HTTP_PORT=8035 is not available for PPM.
ppmtest2.mhe.mhc: Port 8010 for EXTERNAL_WEB_PORT=8010 is not available for PPM.
Node ppmtest2.mhe.mhc sanity failed
PPM failed the pre-startup sanity checks and will not start

 

Attach is the server.conf file.

I'm wondering if anyone has face this issue or know the solution for this?

Thank you.

 

Regards,

Abhi

11 REPLIES
TurboMan
Honored Contributor.

Re: Bug at starting the PPM clustered server and kSupport issue

Hi,

 

You need to run kConfig to set the password.

 

Regards

TM

Etienne_Canaud
Outstanding Contributor.

Re: Bug at starting the PPM clustered server and kSupport issue

Hi Abhi,

 

If you have at least one PPM server node up and running, since PPM 9.12 kSupport is accessible through the admin console interface. It's the last option in the Admin Console menu.

 

About the error displayed, the error message looks quite self-descriptive: For this Server node, you have configured ports 8035 and 8010  to be used, unfortunately another application is already using them (I would bet, another PPM instance running on the same physical machine).

If all your PPM Server nodes are on different physical machines, then it's possible that a previous PPM instance may not have shutdown correctly. 

From your server.conf, you are using the same value for HTTP_PORT and EXTERNAL_WEB_PORT for all your PPM nodes. Unfortunately, one port can only be used by one application on one physical machine. The fix is simple: Assign one different (and unused) port to each PPM node if they are on the same physical server. As said previously, if you are using only one PPM node per physical server, then it means another application is already using these ports, so you should change them anyway or close the application that is using them.

 

Kind Regards,

Etienne.

Abhi_Agrawal
Respected Contributor.

Re: Bug at starting the PPM clustered server and kSupport issue

TM - I've already tried this, but still getting same error.
Abhi_Agrawal
Respected Contributor.

Re: Bug at starting the PPM clustered server and kSupport issue

Etienne,

No other PPM instance is running on the same physical server.
We are not using EXTERNAL_WEB_PORT in the server.conf and we don't have same value for it.
Although, we have upgraded to 9.13, but kSupport through Admin console menu is showing that 9.10 upgrade is failed although PPM upgrade log shows that we successfully completed, its weird.
Abhi_Agrawal
Respected Contributor.

Re: Bug at starting the PPM clustered server and kSupport issue

FYI,
We have found that after we stopped PPM app, port 8035 is acquire by some other process hence PPM is not able to access this port.
Solution for port release: - They've suggested us to bounce the server to free this port.
Etienne_Canaud
Outstanding Contributor.

Re: Bug at starting the PPM clustered server and kSupport issue

Hi,

 

Restarting the server will solve this temporarily, but you are always at risk of the issue occuring again next time you restart your PPM Server. I would advise to either find which process took this port and configure the related application not to pick up PPM ports, or to update your PPM config to use another port that is not supposed to be picked up by other processes.

 

If the process that picked up the PPM port can't be configured to use other ports, it means that either this port is hard coded in the application (and then you should change PPM port), or the PPM port has been chosen in the ephemeral port range, and if that is the case any process might pick up this port in the future when PPM server is down. This seems unlikely as 8035 is usually not in the ephemeral port range, but you should double check your config to make sure that this is the case (you can refer to http://www.ncftp.com/ncftpd/doc/misc/ephemeral_ports.html to find out what is your ephemeral port range based on your flavor of *nix).

 

Kind Regards,

Etienne.

Erik Cole
Acclaimed Contributor.

Re: Bug at starting the PPM clustered server and kSupport issue

If you're running on Windows as a service, be aware that although the service stops pretty quickly the underlying Java process can take a while - even a few minutes - to shut down. It's easy to step on yourself if you don't watch the logs for the telltale "halting VM" line before you restart.

LoisLasguignes
Frequent Contributor.

Re: Bug at starting the PPM clustered server and kSupport issue

Hello everybody,

 

We are on HP PPM 9.13, and when we do a kSupport.sh, we have the following error:

 

java.lang.Exception: Mising database information: username, password, jdbc url!
        at com.kintana.ismp.ksupport.db.DbConnectionManager.setupConnection(DbConnectionManager.java:56)
        at com.kintana.ismp.ksupport.db.DbConnectionManager.getDbConnection(DbConnectionManager.java:40)
        at com.kintana.ismp.ksupport.actions.SetProperties.action(SetProperties.java:91)
        at com.kintana.ismp.bean.actions.KintanaAction.execute(KintanaAction.java:90)
 
We've checked that DB Username and password are present in server.conf. We even made a kConfig.sh to reenter those parameters. But unsuccessfully.
 
I've also attached the full error of the kSupport.sh
 
Thanks everyone for your help!
 
Loïs
Erik Cole
Acclaimed Contributor.

Re: Bug at starting the PPM clustered server and kSupport issue

Did you also set

 

com.kintana.core.server.JDBC_URL=jdbc:oracle:thin:@<hostname>:<port>:<SID>

 

in server.conf?

LoisLasguignes
Frequent Contributor.

Re: Bug at starting the PPM clustered server and kSupport issue

Hello,

 

Thanks for you answer. Yes, JDBC_URL is already set.

 

Loïs

LoisLasguignes
Frequent Contributor.

Re: Bug at starting the PPM clustered server and kSupport issue

Hello Everybody !

 

About our kSupport issue, HP Support gave us a hotfix that solve the problem. Now, it works fine.

I attach the hotfix and the procedure.

 

Thanks.

 

Loïs