Hello Peers,
Greetings! I am unable to bring up our repository service. I have tried every possible way, using some help online ( for example: http://www.cool-bi.com/Infa/InfaDomainPWD.php) but in vain. I have attached logs from three files: catalina.out, node.log, exceptions.log files for your reference. Can you please help me figure out the problem at your convenience.
Just FYI, I can share my nodemeta.xml contents if you want.
Log contents:
-----------Catalina.out file contents-----------
[2016-Feb-12 12:38:36.788] Log service deinit method is called.
[2016-Feb-12 12:38:36.789] Domain Configuration service deinit method is called.
Feb 12, 2016 12:42:23 PM org.apache.coyote.AbstractProtocol init
SEVERE: Failed to initialize end point associated with ProtocolHandler ["http-bio-6005"]
java.net.BindException: Address already in use <null>:6005
at org.apache.tomcat.util.net.JIoEndpoint.bind(JIoEndpoint.java:406)
at org.apache.tomcat.util.net.AbstractEndpoint.init(AbstractEndpoint.java:610)
at org.apache.coyote.AbstractProtocol.init(AbstractProtocol.java:429)
at org.apache.coyote.http11.AbstractHttp11JsseProtocol.init(AbstractHttp11JsseProtocol.java:119)
at org.apache.catalina.connector.Connector.initInternal(Connector.java:981)
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
at org.apache.catalina.core.StandardService.initInternal(StandardService.java:559)
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
at org.apache.catalina.core.StandardServer.initInternal(StandardServer.java:814)
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
at org.apache.catalina.startup.Catalina.load(Catalina.java:633)
at org.apache.catalina.startup.Catalina.load(Catalina.java:658)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:281)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:455)
Caused by: java.net.BindException: Address already in use
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:383)
at java.net.ServerSocket.bind(ServerSocket.java:328)
at java.net.ServerSocket.<init>(ServerSocket.java:194)
at java.net.ServerSocket.<init>(ServerSocket.java:150)
at org.apache.tomcat.util.net.DefaultServerSocketFactory.createSocket(DefaultServerSocketFactory.java:49)
at org.apache.tomcat.util.net.JIoEndpoint.bind(JIoEndpoint.java:393)
... 17 more
Feb 12, 2016 12:42:23 PM org.apache.catalina.core.StandardService initInternal
SEVERE: Failed to initialize connector [Connector[HTTP/1.1-6005]]
org.apache.catalina.LifecycleException: Failed to initialize component [Connector[HTTP/1.1-6005]]
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:106)
at org.apache.catalina.core.StandardService.initInternal(StandardService.java:559)
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
at org.apache.catalina.core.StandardServer.initInternal(StandardServer.java:814)
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
at org.apache.catalina.startup.Catalina.load(Catalina.java:633)
at org.apache.catalina.startup.Catalina.load(Catalina.java:658)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:281)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:455)
Caused by: org.apache.catalina.LifecycleException: Protocol handler initialization failed
at org.apache.catalina.connector.Connector.initInternal(Connector.java:983)
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
... 12 more
Caused by: java.net.BindException: Address already in use <null>:6005
at org.apache.tomcat.util.net.JIoEndpoint.bind(JIoEndpoint.java:406)
at org.apache.tomcat.util.net.AbstractEndpoint.init(AbstractEndpoint.java:610)
at org.apache.coyote.AbstractProtocol.init(AbstractProtocol.java:429)
at org.apache.coyote.http11.AbstractHttp11JsseProtocol.init(AbstractHttp11JsseProtocol.java:119)
at org.apache.catalina.connector.Connector.initInternal(Connector.java:981)
... 13 more
Caused by: java.net.BindException: Address already in use
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:383)
at java.net.ServerSocket.bind(ServerSocket.java:328)
at java.net.ServerSocket.<init>(ServerSocket.java:194)
at java.net.ServerSocket.<init>(ServerSocket.java:150)
at org.apache.tomcat.util.net.DefaultServerSocketFactory.createSocket(DefaultServerSocketFactory.java:49)
at org.apache.tomcat.util.net.JIoEndpoint.bind(JIoEndpoint.java:393)
... 17 more
2016-Feb-12 12:43:16.291 Starting Tomcat on HTTP port [6005].
[2016-Feb-12 12:43:16.366] Domain service init method is called.
[2016-Feb-12 12:43:25.163] Enabling master Core services.
[2016-Feb-12 12:43:25.166] Domain Configuration service init method is called.
[2016-Feb-12 12:43:26.606] Log service init method is called.
[2016-Feb-12 12:43:26.654] User Management service init method is called.
[2016-Feb-12 12:43:27.571] Edr service init method is called.
[2016-Feb-12 12:43:28.288] Called the alert domain function init method.
[2016-Feb-12 12:43:28.337] Licensing service init method is called.
[2016-Feb-12 12:43:28.584] Monitoring service init method is called.
[2016-Feb-12 12:43:29.325] Plugin Registry service init method is called.
[2016-Feb-12 12:43:29.368] Master Core services enabled.
[2016-Feb-12 12:43:29.774] LogServiceAgent init method is called.
-----------Exceptions.log file contents-----------
2016-02-12 12:43:25,769 ERROR [Monitor Guaranteed Message Logger Thread] [CCM_10322] While logging messages to the Log Service, the following error occurred: [[DOM_10022] The master
gateway node for the domain is not available. Electing another master gateway. Wait for the election of the master gateway node to complete. If the problem persists, verify that the
master gateway node is running.]. Fix the errors written to the node.log file.
com.informatica.isp.domainservice.exceptions.ISPMasterNotAvailableException: [DOM_10022] The master gateway node for the domain is not available. Electing another master gateway. Wait for
the election of the master gateway node to complete. If the problem persists, verify that the master gateway node is running.
at com.informatica.isp.domainservice.DomainServiceImpl.nameServiceLookup(DomainServiceImpl.java:2961)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.informatica.pcsf.servicesframework.service.impl.ServiceRequestHandler.getMethodResult(ServiceRequestHandler.java:321)
at com.informatica.pcsf.servicesframework.service.impl.ServiceRequestHandler.onReceiveRequest(ServiceRequestHandler.java:214)
at com.informatica.pcsf.datatransport.impl.RequestHandlerImpl.receiveMSG(RequestHandlerImpl.java:39)
at org.beepcore.beep.core.ChannelImpl.run(ChannelImpl.java:386)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:662)
2016-02-12 12:43:25,809 ERROR [Monitor Guaranteed Message Logger Thread] [CCM_10322] While logging messages to the Log Service, the following error occurred: [[DOM_10022] The master
gateway node for the domain is not available. Electing another master gateway. Wait for the election of the master gateway node to complete. If the problem persists, verify that the
master gateway node is running.]. Fix the errors written to the node.log file.
com.informatica.isp.domainservice.exceptions.ISPMasterNotAvailableException: [DOM_10022] The master gateway node for the domain is not available. Electing another master gateway. Wait for
the election of the master gateway node to complete. If the problem persists, verify that the master gateway node is running.
at com.informatica.isp.domainservice.DomainServiceImpl.nameServiceLookup(DomainServiceImpl.java:2961)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.informatica.pcsf.servicesframework.service.impl.ServiceRequestHandler.getMethodResult(ServiceRequestHandler.java:321)
at com.informatica.pcsf.servicesframework.service.impl.ServiceRequestHandler.onReceiveRequest(ServiceRequestHandler.java:214)
at com.informatica.pcsf.datatransport.impl.RequestHandlerImpl.receiveMSG(RequestHandlerImpl.java:39)
at org.beepcore.beep.core.ChannelImpl.run(ChannelImpl.java:386)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:662)
2016-02-12 12:43:29,314 ERROR [Monitor Guaranteed Message Logger Thread] [CCM_10322] While logging messages to the Log Service, the following error occurred: [[DOM_10022] The master
gateway node for the domain is not available. Electing another master gateway. Wait for the election of the master gateway node to complete. If the problem persists, verify that the
master gateway node is running.]. Fix the errors written to the node.log file.
com.informatica.isp.domainservice.exceptions.ISPMasterNotAvailableException: [DOM_10022] The master gateway node for the domain is not available. Electing another master gateway. Wait for
the election of the master gateway node to complete. If the problem persists, verify that the master gateway node is running.
at com.informatica.isp.domainservice.DomainServiceImpl.nameServiceLookup(DomainServiceImpl.java:2961)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.informatica.pcsf.servicesframework.service.impl.ServiceRequestHandler.getMethodResult(ServiceRequestHandler.java:321)
at com.informatica.pcsf.servicesframework.service.impl.ServiceRequestHandler.onReceiveRequest(ServiceRequestHandler.java:214)
at com.informatica.pcsf.datatransport.impl.RequestHandlerImpl.receiveMSG(RequestHandlerImpl.java:39)
at org.beepcore.beep.core.ChannelImpl.run(ChannelImpl.java:386)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:662)
2016-02-12 12:43:29,342 ERROR [Monitor Guaranteed Message Logger Thread] [CCM_10322] While logging messages to the Log Service, the following error occurred: [[DOM_10022] The master
gateway node for the domain is not available. Electing another master gateway. Wait for the election of the master gateway node to complete. If the problem persists, verify that the
master gateway node is running.]. Fix the errors written to the node.log file.
com.informatica.isp.domainservice.exceptions.ISPMasterNotAvailableException: [DOM_10022] The master gateway node for the domain is not available. Electing another master gateway. Wait for
the election of the master gateway node to complete. If the problem persists, verify that the master gateway node is running.
at com.informatica.isp.domainservice.DomainServiceImpl.nameServiceLookup(DomainServiceImpl.java:2961)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.informatica.pcsf.servicesframework.service.impl.ServiceRequestHandler.getMethodResult(ServiceRequestHandler.java:321)
at com.informatica.pcsf.servicesframework.service.impl.ServiceRequestHandler.onReceiveRequest(ServiceRequestHandler.java:214)
at com.informatica.pcsf.datatransport.impl.RequestHandlerImpl.receiveMSG(RequestHandlerImpl.java:39)
at org.beepcore.beep.core.ChannelImpl.run(ChannelImpl.java:386)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:662)
2016-02-12 12:43:29,362 ERROR [Monitor Guaranteed Message Logger Thread] [CCM_10322] While logging messages to the Log Service, the following error occurred: [[DOM_10022] The master
gateway node for the domain is not available. Electing another master gateway. Wait for the election of the master gateway node to complete. If the problem persists, verify that the
master gateway node is running.]. Fix the errors written to the node.log file.
com.informatica.isp.domainservice.exceptions.ISPMasterNotAvailableException: [DOM_10022] The master gateway node for the domain is not available. Electing another master gateway. Wait for
the election of the master gateway node to complete. If the problem persists, verify that the master gateway node is running.
at com.informatica.isp.domainservice.DomainServiceImpl.nameServiceLookup(DomainServiceImpl.java:2961)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.informatica.pcsf.servicesframework.service.impl.ServiceRequestHandler.getMethodResult(ServiceRequestHandler.java:321)
at com.informatica.pcsf.servicesframework.service.impl.ServiceRequestHandler.onReceiveRequest(ServiceRequestHandler.java:214)
at com.informatica.pcsf.datatransport.impl.RequestHandlerImpl.receiveMSG(RequestHandlerImpl.java:39)
at org.beepcore.beep.core.ChannelImpl.run(ChannelImpl.java:386)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:662)
2016-02-12 12:43:29,385 ERROR [Monitor Guaranteed Message Logger Thread] [CCM_10322] While logging messages to the Log Service, the following error occurred: [[DOM_10022] The master
gateway node for the domain is not available. Electing another master gateway. Wait for the election of the master gateway node to complete. If the problem persists, verify that the
master gateway node is running.]. Fix the errors written to the node.log file.
com.informatica.isp.domainservice.exceptions.ISPMasterNotAvailableException: [DOM_10022] The master gateway node for the domain is not available. Electing another master gateway. Wait for
the election of the master gateway node to complete. If the problem persists, verify that the master gateway node is running.
at com.informatica.isp.domainservice.DomainServiceImpl.nameServiceLookup(DomainServiceImpl.java:2961)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.informatica.pcsf.servicesframework.service.impl.ServiceRequestHandler.getMethodResult(ServiceRequestHandler.java:321)
at com.informatica.pcsf.servicesframework.service.impl.ServiceRequestHandler.onReceiveRequest(ServiceRequestHandler.java:214)
at com.informatica.pcsf.datatransport.impl.RequestHandlerImpl.receiveMSG(RequestHandlerImpl.java:39)
at org.beepcore.beep.core.ChannelImpl.run(ChannelImpl.java:386)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:662)
-----------node.log file contents-----------
2016-02-12 12:38:35,756 INFO [Master Elect Data Writer] [DOM_10161] Stopped the writer thread for the master gateway node election. Deleting the data from the domain configuration repository.
2016-02-12 12:38:35,759 INFO [Master Elect Data Writer] [DOM_10146] Obtained the row level lock on the ISP_MASTER_ELECT_LOCK table.
2016-02-12 12:38:35,760 INFO [Master Elect Data Writer] [DOM_10147] Deleting the row for node [node01_hhvappetld02.tmh.tmhs] in the domain configuration repository.
2016-02-12 12:38:35,761 INFO [Master Elect Data Writer] [DOM_10147] Deleting the row for node [node01_hhvappetld02.tmh.tmhs] in the domain configuration repository.
2016-02-12 12:38:35,761 INFO [Master Elect Data Writer] [DOM_10151] Released row level lock on the ISP_MASTER_ELECT_LOCK table.
2016-02-12 12:43:16,404 INFO [localhost-startStop-1] [NODE_10020] Initializing node configuration for Informatica services version [9.5.1 HotFix2], build [1,637].
2016-02-12 12:43:16,404 INFO [localhost-startStop-1] [NODE_10018] Loading the node configuration metadata from configuration file [/apps/obiee/Informatica/9.5.1/isp/config/nodemeta.xml].
2016-02-12 12:43:16,426 INFO [localhost-startStop-1] [NODE_10021] Node [node01_hhvappetld02.tmh.tmhs] at host address [hhvappetld02.tmh.tmhs:6006] in domain [Domain_hhvappetld02.tmh.tmhs] is initialized.
2016-02-12 12:43:16,426 INFO [localhost-startStop-1] [NODE_10024] Node [node01_hhvappetld02.tmh.tmhs] is set up as a gateway node in domain [Domain_hhvappetld02.tmh.tmhs].
2016-02-12 12:43:16,965 INFO [localhost-startStop-1] [NODE_10022] Node contains predefined resource: [NodeName:node01_hhvappetld02.tmh.tmhs].
2016-02-12 12:43:16,965 INFO [localhost-startStop-1] [NODE_10022] Node contains predefined resource: [VirtualMachine:1].
2016-02-12 12:43:16,965 INFO [localhost-startStop-1] [NODE_10022] Node contains predefined resource: [HyperThreading:-1].
2016-02-12 12:43:16,965 INFO [localhost-startStop-1] [NODE_10022] Node contains predefined resource: [CPUModel: Intel(R) Xeon(R) CPU E7- 4820 @ 2.00GHz].
2016-02-12 12:43:16,966 INFO [localhost-startStop-1] [NODE_10022] Node contains predefined resource: [CPUCores:4].
2016-02-12 12:43:16,966 INFO [localhost-startStop-1] [NODE_10022] Node contains predefined resource: [CPUSockets:1].
2016-02-12 12:43:16,966 INFO [localhost-startStop-1] [NODE_10022] Node contains predefined resource: [HostName:hhvappetld02.tmh.tmhs].
2016-02-12 12:43:16,966 INFO [localhost-startStop-1] [NODE_10022] Node contains predefined resource: [LogicalCPUs:4].
2016-02-12 12:43:16,966 INFO [localhost-startStop-1] [NODE_10022] Node contains predefined resource: [CPUBusSize:64].
2016-02-12 12:43:16,966 INFO [localhost-startStop-1] [NODE_10022] Node contains predefined resource: [OSType:Linux].
2016-02-12 12:43:16,967 INFO [localhost-startStop-1] [NODE_10019] Node configuration initialized successfully.
2016-02-12 12:43:18,880 INFO [localhost-startStop-1] [DOM_10134] Node [node01_hhvappetld02.tmh.tmhs] has become active in the domain.
2016-02-12 12:43:18,883 INFO [Domain Monitor] [DOM_10186] The heartbeat interval between nodes is [15,000] milliseconds. A node without a heartbeat is considered to have timed out after an interval of [90,000] milliseconds.
2016-02-12 12:43:18,884 INFO [Domain Monitor] [DOM_10073] Start domain master election.
2016-02-12 12:43:19,084 INFO [Domain Monitor] [DOM_10142] The update and timeout properties for the master gateway node is set in the domain configuration repository. The row update interval time is set to [8000] milliseconds and the out-of-date row timeout is set to [32000] milliseconds.
2016-02-12 12:43:19,322 INFO [Domain Monitor] [DOM_10146] Obtained the row level lock on the ISP_MASTER_ELECT_LOCK table.
2016-02-12 12:43:19,322 INFO [Domain Monitor] [DOM_10148] Starting to read master gateway election row from the domain configuration repository.
2016-02-12 12:43:19,326 INFO [Domain Monitor] [DOM_10151] Released row level lock on the ISP_MASTER_ELECT_LOCK table.
2016-02-12 12:43:19,327 INFO [Domain Monitor] [DOM_10146] Obtained the row level lock on the ISP_MASTER_ELECT_LOCK table.
2016-02-12 12:43:19,328 INFO [Domain Monitor] [DOM_10147] Deleting the row for node [node01_hhvappetld02.tmh.tmhs] in the domain configuration repository.
2016-02-12 12:43:19,329 INFO [Domain Monitor] [DOM_10147] Deleting the row for node [node01_hhvappetld02.tmh.tmhs] in the domain configuration repository.
2016-02-12 12:43:19,329 INFO [Domain Monitor] [DOM_10148] Starting to read master gateway election row from the domain configuration repository.
2016-02-12 12:43:19,330 INFO [Domain Monitor] [DOM_10149] Completed reading the master gateway election rows in the domain configuration repository.
2016-02-12 12:43:19,330 INFO [Domain Monitor] [DOM_10151] Released row level lock on the ISP_MASTER_ELECT_LOCK table.
2016-02-12 12:43:19,330 INFO [Domain Monitor] [DOM_10145] Cannot find a gateway node running in the domain. Starting the master gateway node election.
2016-02-12 12:43:19,331 INFO [Domain Monitor] [DOM_10146] Obtained the row level lock on the ISP_MASTER_ELECT_LOCK table.
2016-02-12 12:43:19,331 INFO [Domain Monitor] [DOM_10148] Starting to read master gateway election row from the domain configuration repository.
2016-02-12 12:43:19,332 INFO [Domain Monitor] [DOM_10149] Completed reading the master gateway election rows in the domain configuration repository.
2016-02-12 12:43:19,332 INFO [Domain Monitor] [DOM_10155] No master gateway found in the domain configuration repository. Setting this node to master gateway node.
2016-02-12 12:43:19,334 INFO [Domain Monitor] [DOM_10152] Updated data row for node [node01_hhvappetld02.tmh.tmhs].
2016-02-12 12:43:19,335 INFO [Domain Monitor] [DOM_10151] Released row level lock on the ISP_MASTER_ELECT_LOCK table.
2016-02-12 12:43:19,335 INFO [Domain Monitor] [DOM_10159] The master gateway node election is complete. Setting the status to [Election Complete].
2016-02-12 12:43:19,335 INFO [Master Elect Data Writer] [DOM_10160] Started the writer thread for the master gateway node election.
2016-02-12 12:43:19,335 INFO [Domain Monitor] [DOM_10075] Domain master election has completed. Node [node01_hhvappetld02.tmh.tmhs] has been elected as master gateway node.
2016-02-12 12:43:19,335 INFO [Domain Monitor] [DOM_10075] Domain master election has completed. Node [node01_hhvappetld02.tmh.tmhs] has been elected as master gateway node.
2016-02-12 12:43:19,336 INFO [Domain Monitor] [DOM_10106] Initializing the master gateway node [node01_hhvappetld02.tmh.tmhs].
2016-02-12 12:43:25,164 INFO [Domain Monitor] [DOM_10066] Enabling the domain functionality [DomainService].
2016-02-12 12:43:25,165 INFO [Domain Monitor] [DOM_10067] The domain functionality [DomainService] has been enabled.
2016-02-12 12:43:25,165 INFO [Domain Monitor] [DOM_10066] Enabling the domain functionality [DomainConfigurationService].
2016-02-12 12:43:25,182 INFO [Domain Monitor] [DCS_0039] Loading the configuration for domain [Domain_hhvappetld02.tmh.tmhs].
2016-02-12 12:43:25,774 ERROR [Monitor Guaranteed Message Logger Thread] [CCM_10322] While logging messages to the Log Service, the following error occurred: [[DOM_10022] The master gateway node for the domain is not available. Electing another master gateway. Wait for the election of the master gateway node to complete. If the problem persists, verify that the master gateway node is running.]. Fix the errors written to the node.log file.
com.informatica.isp.domainservice.exceptions.ISPMasterNotAvailableException: [DOM_10022] The master gateway node for the domain is not available. Electing another master gateway. Wait for the election of the master gateway node to complete. If the problem persists, verify that the master gateway node is running.
2016-02-12 12:43:25,810 ERROR [Monitor Guaranteed Message Logger Thread] [CCM_10322] While logging messages to the Log Service, the following error occurred: [[DOM_10022] The master gateway node for the domain is not available. Electing another master gateway. Wait for the election of the master gateway node to complete. If the problem persists, verify that the master gateway node is running.]. Fix the errors written to the node.log file.
com.informatica.isp.domainservice.exceptions.ISPMasterNotAvailableException: [DOM_10022] The master gateway node for the domain is not available. Electing another master gateway. Wait for the election of the master gateway node to complete. If the problem persists, verify that the master gateway node is running.
2016-02-12 12:43:26,596 INFO [Domain Monitor] [DCS_0040] The configuration for domain [Domain_hhvappetld02.tmh.tmhs] loaded successfully.
2016-02-12 12:43:26,605 INFO [Domain Monitor] [DOM_10067] The domain functionality [DomainConfigurationService] has been enabled.
2016-02-12 12:43:26,606 INFO [Domain Monitor] [DOM_10066] Enabling the domain functionality [LogService].
2016-02-12 12:43:26,613 INFO [Domain Monitor] [CCM_10403] The log directory [/apps/obiee/Informatica/9.5.1/isp/logs] is successfully validated.
2016-02-12 12:43:26,636 INFO [Domain Monitor] [LGS_10066] Initializing run log manager. Periodicity - [24] hrs; Max request threshold -by [1,000]
2016-02-12 12:43:26,653 INFO [Domain Monitor] [DOM_10067] The domain functionality [LogService] has been enabled.
2016-02-12 12:43:26,653 INFO [Domain Monitor] [DOM_10066] Enabling the domain functionality [UserManagementService].
2016-02-12 12:43:27,570 INFO [Domain Monitor] [DOM_10067] The domain functionality [UserManagementService] has been enabled.
2016-02-12 12:43:27,571 INFO [Domain Monitor] [DOM_10066] Enabling the domain functionality [EdrService].
2016-02-12 12:43:28,287 INFO [Domain Monitor] [DOM_10067] The domain functionality [EdrService] has been enabled.
2016-02-12 12:43:28,288 INFO [Domain Monitor] [DOM_10066] Enabling the domain functionality [AlertService].
2016-02-12 12:43:28,336 INFO [Domain Monitor] [DOM_10067] The domain functionality [AlertService] has been enabled.
2016-02-12 12:43:28,337 INFO [Domain Monitor] [DOM_10066] Enabling the domain functionality [LicensingService].
2016-02-12 12:43:28,343 INFO [Domain Monitor] [LIC_10045] Loading license keys for the domain.
2016-02-12 12:43:28,401 INFO [Domain Monitor] [LIC_10047] License keys loaded successfully for the domain.
2016-02-12 12:43:28,583 INFO [Domain Monitor] [DOM_10067] The domain functionality [LicensingService] has been enabled.
2016-02-12 12:43:28,584 INFO [Domain Monitor] [DOM_10066] Enabling the domain functionality [MonitoringService].
2016-02-12 12:43:29,315 ERROR [Monitor Guaranteed Message Logger Thread] [CCM_10322] While logging messages to the Log Service, the following error occurred: [[DOM_10022] The master gateway node for the domain is not available. Electing another master gateway. Wait for the election of the master gateway node to complete. If the problem persists, verify that the master gateway node is running.]. Fix the errors written to the node.log file.
com.informatica.isp.domainservice.exceptions.ISPMasterNotAvailableException: [DOM_10022] The master gateway node for the domain is not available. Electing another master gateway. Wait for the election of the master gateway node to complete. If the problem persists, verify that the master gateway node is running.
2016-02-12 12:43:29,315 INFO [Domain Monitor] [DOM_10067] The domain functionality [MonitoringService] has been enabled.
2016-02-12 12:43:29,321 INFO [Domain Monitor] [DOM_10066] Enabling the domain functionality [PluginRegistryService].
2016-02-12 12:43:29,342 ERROR [Monitor Guaranteed Message Logger Thread] [CCM_10322] While logging messages to the Log Service, the following error occurred: [[DOM_10022] The master gateway node for the domain is not available. Electing another master gateway. Wait for the election of the master gateway node to complete. If the problem persists, verify that the master gateway node is running.]. Fix the errors written to the node.log file.
com.informatica.isp.domainservice.exceptions.ISPMasterNotAvailableException: [DOM_10022] The master gateway node for the domain is not available. Electing another master gateway. Wait for the election of the master gateway node to complete. If the problem persists, verify that the master gateway node is running.
2016-02-12 12:43:29,350 INFO [Domain Monitor] [PR_10000] [2016-Feb-12 12:43:29.332] Plugin Registry initializing
2016-02-12 12:43:29,362 INFO [Domain Monitor] [PR_10001] [2016-Feb-12 12:43:29.359] Plugin Registry Initialization Completed. List of plugins : [, com.informatica.adapter.datasift:com.informatica.reg.plugin.Feature, com.informatica.adapter.linkedin:com.informatica.reg.plugin.Feature, com.informatica.adapter.kapow:com.informatica.reg.plugin.Feature, com.informatica.adapter.twitter:com.informatica.reg.plugin.Feature, com.informatica.adapter.hive:com.informatica.reg.plugin.Feature, com.informatica.adapter.hdfs:com.informatica.reg.plugin.Feature, com.informatica.adapter.teradata:com.informatica.reg.plugin.Feature, com.informatica.adapter.facebook:com.informatica.reg.plugin.Feature, com.informatica.adapter.TwitterStreaming:com.informatica.reg.plugin.Feature]
2016-02-12 12:43:29,362 ERROR [Monitor Guaranteed Message Logger Thread] [CCM_10322] While logging messages to the Log Service, the following error occurred: [[DOM_10022] The master gateway node for the domain is not available. Electing another master gateway. Wait for the election of the master gateway node to complete. If the problem persists, verify that the master gateway node is running.]. Fix the errors written to the node.log file.
com.informatica.isp.domainservice.exceptions.ISPMasterNotAvailableException: [DOM_10022] The master gateway node for the domain is not available. Electing another master gateway. Wait for the election of the master gateway node to complete. If the problem persists, verify that the master gateway node is running.
2016-02-12 12:43:29,362 INFO [Domain Monitor] [DOM_10067] The domain functionality [PluginRegistryService] has been enabled.
2016-02-12 12:43:29,374 INFO [Domain Monitor] [DOM_10100] Getting the linked domain information from the domain configuration repository.
2016-02-12 12:43:29,374 INFO [Domain Monitor] [DOM_10102] The linked domains were successfully loaded from the domain configuration repository.
2016-02-12 12:43:29,385 ERROR [Monitor Guaranteed Message Logger Thread] [CCM_10322] While logging messages to the Log Service, the following error occurred: [[DOM_10022] The master gateway node for the domain is not available. Electing another master gateway. Wait for the election of the master gateway node to complete. If the problem persists, verify that the master gateway node is running.]. Fix the errors written to the node.log file.
com.informatica.isp.domainservice.exceptions.ISPMasterNotAvailableException: [DOM_10022] The master gateway node for the domain is not available. Electing another master gateway. Wait for the election of the master gateway node to complete. If the problem persists, verify that the master gateway node is running.
2016-02-12 12:43:29,432 INFO [Domain Monitor] [DOM_10104] Nodes [node01_hhvappetld02.tmh.tmhs] are loaded from the domain configuration repository.
2016-02-12 12:43:29,432 INFO [Domain Monitor] [DOM_10105] Nodes successfully loaded from the domain configuration repository.
2016-02-12 12:43:29,437 INFO [Domain Monitor] [DOM_10113] Getting service definitions from the domain configuration repository.
2016-02-12 12:43:29,507 INFO [Domain Monitor] [DOM_10108] Registering the node with the master gateway node located at host address [hhvappetld02.tmh.tmhs:6006].
2016-02-12 12:43:29,587 INFO [pool-1-thread-3] [DOM_10083] Node [node01_hhvappetld02.tmh.tmhs] has started and is registered with domain [Domain_hhvappetld02.tmh.tmhs].
2016-02-12 12:43:29,588 INFO [pool-1-thread-3] [DOM_10134] Node [node01_hhvappetld02.tmh.tmhs] has become active in the domain.
2016-02-12 12:43:29,773 INFO [Domain Monitor] [DOM_10066] Enabling the domain functionality [LogServiceAgent].
2016-02-12 12:43:51,201 INFO [Thread 6 of 6 in DomainServiceThreadPool] [SPC_10018] Request to start process for service [_AdminConsole] was successful.