Proxy Time out error in the DIST system

Discussions about product bugs & problems!
Note: This is no replacement for the Official ETM Support!
3 posts • Page 1 of 1
paramesh1985
Posts:81
Joined: Thu Sep 25, 2014 6:03 am

Proxy Time out error in the DIST system

Post by paramesh1985 »

Hi,


We have configured the three distributed system ; it was working when i have configured with 2 distributed system .

Afterwards always i am getting proxy time out error.

WinCC OA version which we are using is v3.15 P015.



WCCILevent (0), 2020.04.29 07:55:49.711, SYS, INFO, 1/event, Received message from MAN: (SYS: 40 Dist -num 1 CONN: 1) with and ID 38 smaller than the ID 211542 of the last received message, assuming manager has been restarted
WPMON_BCR (1), 2020.04.29 07:56:39.350, SYS, WARNING, 36/pmon, Blocking Manager WCCILdist(1) detected. No heartbeat since 30 seconds.
WPMON_BCR (1), 2020.04.29 07:56:56.871, SYS, WARNING, 39/pmon, Manager WCCILdist(1) is no longer blocking.
WPMON_BCR (1), 2020.04.29 07:57:26.896, SYS, WARNING, 36/pmon, Blocking Manager WCCILdist(1) detected. No heartbeat since 30 seconds.
WPMON_BCR (1), 2020.04.29 07:57:33.054, SYS, WARNING, 39/pmon, Manager WCCILdist(1) is no longer blocking.
WCCILproxy (1), 2020.04.29 07:57:34.757, SYS, WARNING, 5, Connection not possible, Closing connection to peer: ::ffff:10.50.110.51:60280. Reason: [proxy] acceptTimeout = 100 expired before configuration arrived.
WPMON_BCR (1), 2020.04.29 07:58:03.088, SYS, WARNING, 36/pmon, Blocking Manager WCCILdist(1) detected. No heartbeat since 30 seconds.
WPMON_BCR (1), 2020.04.29 07:58:19.578, SYS, WARNING, 39/pmon, Manager WCCILdist(1) is no longer blocking.
WPMON_BCR (1), 2020.04.29 07:58:49.658, SYS, WARNING, 36/pmon, Blocking Manager WCCILdist(1) detected. No heartbeat since 30 seconds.
WCCILdist (1), 2020.04.29 07:58:56.557, SYS, INFO, 0, , Connection from X862KS5551.SOUTHSTREAM.pccs.local expired; did not receive any init message
WPMON_BCR (1), 2020.04.29 07:58:56.651, SYS, WARNING, 39/pmon, Manager WCCILdist(1) is no longer blocking.
WPMON_BCR (1), 2020.04.29 07:59:46.268, SYS, WARNING, 36/pmon, Blocking Manager WCCILdist(1) detected. No heartbeat since 30 seconds.
WPMON_BCR (1), 2020.04.29 08:00:02.738, SYS, WARNING, 39/pmon, Manager WCCILdist(1) is no longer blocking.
WPMON_BCR (1), 2020.04.29 08:00:32.832, SYS, WARNING, 36/pmon, Blocking Manager WCCILdist(1) detected. No heartbeat since 30 seconds.
WPMON_BCR (1), 2020.04.29 08:00:40.007, SYS, WARNING, 39/pmon, Manager WCCILdist(1) is no longer blocking.
WCCILproxy (1), 2020.04.29 08:01:03.546, SYS, WARNING, 5, Connection not possible, Closing connection to peer: ::ffff:10.50.110.51:60394. Reason: [proxy] acceptTimeout = 100 expired before configuration arrived.
WPMON_BCR (1), 2020.04.29 08:01:10.046, SYS, WARNING, 36/pmon, Blocking Manager WCCILdist(1) detected. No heartbeat since 30 seconds.

thanks.

Regards,

R.Paramesh

leoknipp
Posts:2928
Joined: Tue Aug 24, 2010 7:28 pm

Re: Proxy Time out error in the DIST system

Post by leoknipp »

The cause for the blocking manager is possibly related to problems with the name resolution.
Can you please check if you have defined the hostnames/IP addresses for the computers used in the distributed system in the "hosts" file of the operating system.

Best Regards
Leopold Knipp
Senior Support Specialist

paramesh1985
Posts:81
Joined: Thu Sep 25, 2014 6:03 am

Re: Proxy Time out error in the DIST system

Post by paramesh1985 »

Hi Knipp,

Thanks its working .

There is wrong name entry in the host file ; that name is not matching with the config entry host name .

After i have fixed the host name in the config file and host file its working.

Regards,

R.Paramesh

3 posts • Page 1 of 1