Project and Portfolio Management Practitioners Forum
cancel
Showing results for 
Search instead for 
Did you mean: 

PPM9.10 SP4 startup problem

Highlighted
WissenCarquest
Regular Collector

PPM9.10 SP4 startup problem

Hello Friends,

 

Today We have upgrade the PPM application 8.0 to 9.10. We have succesfulley upgrade and the start up application. After that We have immediatley applied SP4 patch. Even we have succesfulley applied SP4 patch. While we start the application we got below error. Please find the server.conf file.

 

Java(TM) SE Runtime Environment (build 1.6.0_07-b06)
Java HotSpot(TM) Server VM (build 10.0-b23, mixed mode)
STATUS server:main:SystemOut:2012/06/19-13:48:06.875 EDT: Logging reconfiguration complete
STATUS server:main:com.kintana.core.server.ServerStartupSanity:2012/06/19-13:48:06.877 EDT: Running pre-startup checks for node kintana in clustered mode
STATUS server:main:com.kintana.core.server.ServerStartupSanity:2012/06/19-13:48:06.915 EDT: Checking: /home/mitg/ITGQA_HOME/server.conf
ERROR server:main:com.kintana.core.server.ServerStartupSanity:2012/06/19-13:48:06.984 EDT:
================================================================================
The following errors were found which prevent this node starting
kintana: Can't specify SERVER_NAME twice for a node
Node kintana sanity failed.  See server log for detail.
PPM failed the pre-startup sanity checks and will not start

 

8 REPLIES
Jim Esler
Honored Contributor

Re: PPM9.10 SP4 startup problem

As indicated by the error message, you have multiple directives for SERVER_NAME. The following appears three times in the file (two before the node directive and one after):

 

com.kintana.core.server.SERVER_NAME=10.35.5.193

 

A node can be named only once and node names need to be unique.

WissenCarquest
Regular Collector

Re: PPM9.10 SP4 startup problem

Hello Team,

 

As per you suggestion, We have changed Server_name and able to start the Service_node. But while start user node it start properly. it is showing upto this point, beyond this it is not moving to next step.

 

$ sh kStart.sh -name kintana -partition ITG_cluster
JAVA_HOME = /usr/java/jdk1.6.0_07
java version "1.6.0_07"
Java(TM) SE Runtime Environment (build 1.6.0_07-b06)
Java HotSpot(TM) Server VM (build 10.0-b23, mixed mode)
Server will start in cluster mode...
JAVA_HOME = /usr/java/jdk1.6.0_07
java version "1.6.0_07"
Java(TM) SE Runtime Environment (build 1.6.0_07-b06)
Java HotSpot(TM) Server VM (build 10.0-b23, mixed mode)
STATUS server:main:SystemOut:2012/06/20-08:32:14.489 EDT: Logging reconfiguration complete
STATUS server:main:com.kintana.core.server.ServerStartupSanity:2012/06/20-08:32:14.490 EDT: Running pre-startup checks for node kintana in clustered mode
STATUS server:main:com.kintana.core.server.ServerStartupSanity:2012/06/20-08:32:14.495 EDT: Checking: /home/mitg/ITGQA_HOME/server.conf
STATUS server:main:com.kintana.core.server.ServerStartupSanity:2012/06/20-08:32:14.566 EDT: All pre-startup checks completed for node kintana
Node kintana sanity passed.  See server log for detail.
$ STATUS server:main:SystemOut:2012/06/20-07:32:17.041 CDT: Logging reconfiguration complete
STATUS server:main:SystemOut:2012/06/20-07:32:27.045 CDT:
---------------------------------------------------------
GMS: address is 127.0.0.1:38760 (cluster=ITG_cluster)
---------------------------------------------------------
STATUS server:main:com.mercury.itg.core.jms.service:2012/06/20-07:32:27.342 CDT: Started PPMClusterPartition
STATUS server:main:com.mercury.itg.core.debug.monitor.PPMJbossMonitor:2012/06/20-07:32:29.223 CDT: Starting web context: ROOT
STATUS server:main:com.mercury.itg.core.debug.monitor.PPMJbossMonitor:2012/06/20-07:32:30.037 CDT: Completed start of web context: ROOT
STATUS server:main:com.mercury.itg.core.debug.monitor.PPMJbossMonitor:2012/06/20-07:32:31.486 CDT: Starting web context: admin-jmx
STATUS server:main:com.mercury.itg.core.debug.monitor.PPMJbossMonitor:2012/06/20-07:32:31.607 CDT: Completed start of web context: admin-jmx
STATUS server:main:com.mercury.itg.core.debug.monitor.PPMJbossMonitor:2012/06/20-07:32:31.715 CDT: Starting web context: dashboard
STATUS server:main:com.mercury.itg.core.debug.monitor.PPMJbossMonitor:2012/06/20-07:32:33.333 CDT: Completed start of web context: dashboard
STATUS server:main:com.mercury.itg.core.debug.monitor.PPMJbossMonitor:2012/06/20-07:32:33.599 CDT: Starting web context: itg
STATUS server:main:com.mercury.itg.core.debug.monitor.PPMTomcatMonitor:2012/06/20-07:32:35.223 CDT: Starting listener: com.mercury.itg.servlet.ServletContextListenerImpl
STATUS server:main:com.mercury.itg.core.debug.monitor.PPMTomcatMonitor:2012/06/20-07:32:35.226 CDT: Completed Start of listener: com.mercury.itg.servlet.ServletContextListenerImpl
STATUS server:main:com.mercury.itg.core.debug.monitor.PPMTomcatMonitor:2012/06/20-07:32:35.227 CDT: Starting listener: com.kintana.core.web.listener.ServerStartListener
STATUS server:main:com.kintana.core.server:2012/06/20-07:32:35.231 CDT: Servlet container: Apache Tomcat/5.5.31
STATUS server:main:com.kintana.core.server:2012/06/20-07:32:38.327 CDT: Starting RMI on port 2095
STATUS server:main:com.kintana.core.server:2012/06/20-07:32:38.357 CDT: HP Project and Portfolio Management v9.1.4 SP4
STATUS server:main:com.kintana.core.server:2012/06/20-07:32:38.466 CDT: Local IP address = 10.35.5.193
STATUS server:main:com.kintana.core.server:2012/06/20-07:32:38.760 CDT: License accepted.
STATUS server:main:com.kintana.core.server:2012/06/20-07:32:38.762 CDT: Wed Jun 20 08:32:38 EDT 2012
STATUS server:main:com.kintana.core.cache:2012/06/20-07:32:38.799 CDT: cache: initializing multicast [clusterName - http://10.35.5.193:8082]
STATUS server:main:SystemOut:2012/06/20-07:32:39.029 CDT:
---------------------------------------------------------
GMS: address is 127.0.0.1:49159 (cluster=http://10.35.5.193:8082)
---------------------------------------------------------
STATUS server:main:com.kintana.core.server:2012/06/20-07:32:40.561 CDT: Oracle Oracle Database 11g Release 11.1.0.0.0 - Production
STATUS server:main:com.kintana.core.server:2012/06/20-07:32:40.562 CDT: Oracle JDBC driver 11.1.0.6.0-Production+
STATUS server:main:com.kintana.core.server:2012/06/20-07:32:40.562 CDT: jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=oraqa1.gpi.com)(PORT=1521))(CONNECT_DATA=(SERVER=dedicated)(SERVICE_NAME=CQPPMQ.gpi.com)))
STATUS server:main:com.kintana.core.server:2012/06/20-07:32:40.959 CDT: Starting multicast on cluster http://10.35.5.193:8082
STATUS server:main:com.kintana.core.server.cluster.MulticastAgent:2012/06/20-07:32:40.962 CDT: Binding MULTICAST_PORT to default NIC
STATUS server:main:com.kintana.core.server:2012/06/20-07:32:41.139 CDT: Recording interrupted executions and marking them as 'Failed Interrupted'...
STATUS server:MulticastAgent.DeliveryThread:com.kintana.core.server.cluster.MulticastCommsFailureMonitor:2012/06/20-07:32:41.185 CDT: Node service_node is reachable on MULTICAST_PORT
STATUS server:main:com.kintana.core.server:2012/06/20-07:32:41.316 CDT: Finished recording interrupted executions
STATUS server:main:com.kintana.core.server:2012/06/20-07:32:41.316 CDT: JBoss version: 4.0.5.GA (build: CVSTag=Branch_4_0 date=200610162339)
STATUS server:main:com.kintana.core.server:2012/06/20-07:32:41.316 CDT: JGroups 2.6.15.GA [$Id: Version.java,v 1.59.2.30 2010/04/30 12:15:07 belaban Exp $]
STATUS server:main:com.kintana.core.server:2012/06/20-07:32:41.317 CDT: Java Version: 1.6.0_07, Sun Microsystems Inc.
STATUS server:main:com.kintana.core.server:2012/06/20-07:32:41.317 CDT: Java VM: Java HotSpot(TM) Server VM, 10.0-b23, Sun Microsystems Inc.
STATUS server:main:com.kintana.core.server:2012/06/20-07:32:41.317 CDT: OS-System: Linux, 2.6.18-194.el5PAE, i386
STATUS server:main:com.kintana.core.server:2012/06/20-07:32:41.318 CDT: Number of available processors: 1
STATUS server:main:com.kintana.core.server:2012/06/20-07:32:41.318 CDT: Free/total/max JVM memory (Mb): 1234/1262/1262
STATUS server:main:com.kintana.core.server:2012/06/20-07:32:41.319 CDT: Free/total physical RAM (Mb): 335/4050
STATUS server:main:com.kintana.core.server:2012/06/20-07:32:41.319 CDT: Free/total OS swap space (Mb): 7026/7071
STATUS server:main:com.kintana.core.server:2012/06/20-07:32:41.320 CDT: System load average: 0.97
STATUS server:main:com.kintana.core.server:2012/06/20-07:32:41.321 CDT: JGroups bound to network interface: lo ('lo') IP addresses=/127.0.0.1  Interfaces=/127.0.0.1/0 [null]
ERROR server:main:com.kintana.core.server:2012/06/20-07:32:41.321 CDT: Warning! JGroups is bound to a loopback adapter. If there are nodes on other physical servers, JGroups traffic from this node will not reach them
ERROR server:main:com.kintana.core.server:2012/06/20-07:32:41.330 CDT: Warning! JGroups is bound to a network adapter that reports it does not support multicast.
STATUS server:main:SystemOut:2012/06/20-07:32:41.348 CDT: HibernateUtil starting...
STATUS server:main:SystemOut:2012/06/20-07:33:00.753 CDT: HibernateUtil started in 19.40 seconds
STATUS server:main:com.mercury.itg.core.debug.monitor.PPMTomcatMonitor:2012/06/20-07:33:00.760 CDT: Completed Start of listener: com.kintana.core.web.listener.ServerStartListener
STATUS server:main:com.mercury.itg.core.debug.monitor.PPMTomcatMonitor:2012/06/20-07:33:00.761 CDT: Starting listener: org.springframework.web.context.ContextLoaderListener
STATUS server:pool-6-thread-1:com.kintana.core.server:2012/06/20-07:33:00.790 CDT: Loading PFM Request types
STATUS server:pool-6-thread-1:com.kintana.core.server:2012/06/20-07:33:06.449 CDT: Done Loading PFM Request types
STATUS server:main:com.mercury.itg.core.scheduler:2012/06/20-07:33:17.877 CDT: User node
STATUS server:main:com.mercury.itg.core.jms.service:2012/06/20-07:33:21.451 CDT: PPM Heavy Service Listener will not be started
STATUS server:main:com.mercury.itg.core.jms.service:2012/06/20-07:33:21.454 CDT: PPM Light Service Listener will not be started
STATUS server:main:com.mercury.itg.core.debug.monitor.PPMTomcatMonitor:2012/06/20-07:33:21.748 CDT: Completed Start of listener: org.springframework.web.context.ContextLoaderListener
STATUS server:main:com.mercury.itg.core.debug.monitor.PPMJbossMonitor:2012/06/20-07:33:32.173 CDT: Completed start of web context: itg
STATUS server:main:com.mercury.itg.core.debug.monitor.PPMJbossMonitor:2012/06/20-07:33:32.573 CDT: Starting web context: redirect
STATUS server:main:com.mercury.itg.core.debug.monitor.PPMJbossMonitor:2012/06/20-07:33:32.768 CDT: Completed start of web context: redirect
STATUS server:main:com.mercury.itg.core.debug.monitor.PPMJbossMonitor:2012/06/20-07:33:32.807 CDT: Starting web context: utility_portlets
STATUS server:main:com.mercury.itg.core.debug.monitor.PPMJbossMonitor:2012/06/20-07:33:33.296 CDT: Completed start of web context: utility_portlets
STATUS server:main:com.mercury.itg.core.debug.monitor.PPMJbossMonitor:2012/06/20-07:33:33.774 CDT: *** Ready!

Celil
Esteemed Contributor

Re: PPM9.10 SP4 startup problem

What the mean "not moving to next step" ?
I see everthing fine, but It seems there is no network adapter so ppm connect to loopback adapter. Please check that.



PS: Please keep alive our forum via KUDOS the professionals
Celil

IT Governance Professional
& PPM Solution Architect
Deep Mehta
Regular Collector

Re: PPM9.10 SP4 startup problem

Start the User node as well ;)
Acamargo
Regular Collector

Re: PPM9.10 SP4 startup problem

Anyone had this problem? Recording interrupted executions and marking

d4y4n4
Frequent Visitor

Re: PPM9.10 SP4 startup problem


From the logs I am able to see the following error messages:
ERROR server:main:com.kintana.core.server:2012/06/20-07:32:41.330 CDT: Warning! JGroups is bound to a network adapter that reports it does not support multicast.

We have two known causes for this:

1. In the /etc/hosts or c:\windows\drivers\etc\hosts file, server name is set as 127.0.0.1

2. kClusterDeploy.sh needs to re-deploy out of sync cluster configuration

For #1, comment out the line with server name which is equivalent to 127.0.0.1 as there is no need for it.

For #2, follow the Admin Guide for running kClusterDeploy.sh (check installation guide attached on page 475).

Regards,
Dayana Campos
sdef
Member

Re: PPM9.10 SP4 startup problem

Hi dayana,

I believe the host file is in c:\windows\system32\drivers\etc
Are there any complications using 127.0.0.1, ins't it the localhost? Because im using the localhost to call my PPM instance , i also tried to use 127.0.0.1 and it also works.

-feds
d4y4n4
Frequent Visitor

Re: PPM9.10 SP4 startup problem

Hi,

Yes, it is the localhost, however when you have set it, then it affects the communication between the server as windows reports the server name is as 127.0.0.1

Regards,
Dayana

//Add this to "OnDomLoad" event