Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Alfian Hapsa (dorkyark) SINARMASMSIGLIFE
SINARMASMSIGLIFE
ID
dorkyark Member since 2015 7 posts
SINARMASMSIGLIFE
Posted: Feb 1, 2017
Last activity: Feb 9, 2017
Posted: 1 Feb 2017 22:42 EST
Last activity: 9 Feb 2017 5:07 EST
Closed
Solved

Pega cannot run after restart server

Hi,

Why my pega server cannot start after restart server? I used, v721, JBOSS, Oracle and RedHat Linux.

In log, there's an info

[LOCAL] [564462a54e8efab83241814626c1214c] [3.4.1] Interfaces is disabled, trying to pick one address from TCP-IP config addresses: []

I has tried to truncate PR_SYS_STATUSNODES database table, based on this post https://community.pega.com/support/support-articles/hazelcast-errors-observed-log-server-startup​ but it still same.

Can you help me?

Thanks

Alfian

***Updated by moderator: Lochan to update Categories; added SR details***

To see attachments, please log in.
Data Integration System Administration Support Case Created

Accepted Solution

Posted: 7 years ago
Posted: 9 Feb 2017 5:07 EST
Alfian Hapsa (dorkyark) SINARMASMSIGLIFE
SINARMASMSIGLIFE
ID

Hi All,

Everything done, I can load pega again.

The real problem is timed out when Jboss start to deploy prweb. So I change some configurations in standalone-full.xml

1. Change configuration

<property name="-Djboss.as.management.blocking.timeout" value="600"/>

to

<property name="jboss.as.management.blocking.timeout" value="10800"/>

2. Comment xml tag <deployments> and it’s contents

3. Start Jboss

4. Redeploy all apps sequentially,

  • prpc_j2ee14_jboss61JBM.ear
  • prsysmgmt.war
  • prhelp.war

As for the real question is, how it takes a long times to deploy prpc in our system.

Thank you for your help.

Regards,

Alfian

To see attachments, please log in.
Posted: 7 years ago
Posted: 1 Feb 2017 22:56 EST
Sudhish Othoyoth Puthiyapurayil (othos) Senior Technical Solutions Engineer
Pegasystems Inc.
IN

Hi Alfian,

It seems to be hazelcast not able to bind with port and IP address mentioned. Please check manually whether it is able to listen with port which is configured.

 

To see attachments, please log in.
Posted: 7 years ago
Posted: 1 Feb 2017 23:32 EST
Alfian Hapsa (dorkyark) SINARMASMSIGLIFE
SINARMASMSIGLIFE
ID

Hi othos,

In manual, it need to open port 5701-5800 and I already open it. From a few months ago, there is not a problem for hazelcast but it happen yesterday after restart server.

To see attachments, please log in.
Posted: 7 years ago
Posted: 2 Feb 2017 0:40 EST
Sudhish Othoyoth Puthiyapurayil (othos) Senior Technical Solutions Engineer
Pegasystems Inc.
IN

Hi Alfian,

Can you please check the previous established connection is properly shutdown? Is there any  process still alive using the same port. May be you can use the  command ps -aef | grep port number to find out.

 

To see attachments, please log in.
Posted: 7 years ago
Posted: 2 Feb 2017 2:32 EST
Alfian Hapsa (dorkyark) SINARMASMSIGLIFE
SINARMASMSIGLIFE
ID

Hi Othos,

I already check, there is no process at port 5701 and just made sure, I kill the port using # fuser -k 5701/tcp.

When I check table PR_SYS_STATUSNODES, and it have a column name pycleanshutdown with value is false after I tried to start pega again. Is it mean that the connection not properly shutdown?

To see attachments, please log in.
Posted: 7 years ago
Posted: 2 Feb 2017 6:14 EST
Sudhish Othoyoth Puthiyapurayil (othos) Senior Technical Solutions Engineer
Pegasystems Inc.
IN

As per my understanding, if the node is in run state it will be false and if the node is in shutdown or stopped state the value will be true

To see attachments, please log in.
Posted: 7 years ago
Posted: 2 Feb 2017 21:10 EST
Alfian Hapsa (dorkyark) SINARMASMSIGLIFE
SINARMASMSIGLIFE
ID

So it means, the node is in shutdown properly. What else is need? if I must change the prconfig.xml file, what is the configuration that I need to add?

Thanks

To see attachments, please log in.
Posted: 7 years ago
Posted: 3 Feb 2017 1:42 EST
Sudhish Othoyoth Puthiyapurayil (othos) Senior Technical Solutions Engineer
Pegasystems Inc.
IN

Hi Alfian,

I have analyzed your complete log file and couldn't find any other error which can point to root cause.

For cross verifying, I have shared the log with Hazelcast SME for his inputs.

 

 

To see attachments, please log in.
Posted: 7 years ago
Posted: 3 Feb 2017 2:02 EST
Sudhish Othoyoth Puthiyapurayil (othos) Senior Technical Solutions Engineer
Pegasystems Inc.
IN

Hi Alfian,

SME also confirmed that he couldn't find any other error which can point to root cause. This require additional effort to analyze. Hence, kindly request you to raise an SR for this.

 

To see attachments, please log in.
Posted: 7 years ago
Posted: 3 Feb 2017 2:26 EST
Lochana Durgada Vijayakumar (Lochan_DV) PEGA Senior Manager, Knowledge Management
Pegasystems Inc.
IN

Hi Alfian,

Please let us know if you do log an SR for this and its ID. That way we can track it and follow-up this discussion with the resolution.

Thanks,
Lochan  |  Community Moderator  |  Pegasystems Inc.

 

To see attachments, please log in.
Posted: 7 years ago
Posted: 6 Feb 2017 1:21 EST
Lochana Durgada Vijayakumar (Lochan_DV) PEGA Senior Manager, Knowledge Management
Pegasystems Inc.
IN

Thanks Alfian,

I have updated the original post above with this information. I have also added a pulse post on the SR so that these two are effectively linked.

Regards,
Lochan  |  Community Moderator  |  Pegasystems Inc.

To see attachments, please log in.

Accepted Solution

Posted: 7 years ago
Posted: 9 Feb 2017 5:07 EST
Alfian Hapsa (dorkyark) SINARMASMSIGLIFE
SINARMASMSIGLIFE
ID

Hi All,

Everything done, I can load pega again.

The real problem is timed out when Jboss start to deploy prweb. So I change some configurations in standalone-full.xml

1. Change configuration

<property name="-Djboss.as.management.blocking.timeout" value="600"/>

to

<property name="jboss.as.management.blocking.timeout" value="10800"/>

2. Comment xml tag <deployments> and it’s contents

3. Start Jboss

4. Redeploy all apps sequentially,

  • prpc_j2ee14_jboss61JBM.ear
  • prsysmgmt.war
  • prhelp.war

As for the real question is, how it takes a long times to deploy prpc in our system.

Thank you for your help.

Regards,

Alfian

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice