Enterprise:Service Transition:

Unanswered Question
Apr 2nd, 2008

i have the log on the below :

03/24/2008 02:21:50:Enterprise:Service Transition:APPSVR_DC_2 -> down

03/24/2008 02:26:46:Enterprise:Service Transition:APPSVR_DC_2 -> alive

03/24/2008 03:27:40:Enterprise:Service Transition:APPSVR_DC_2 -> down

03/24/2008 03:32:19:Enterprise:Service Transition:APPSVR_DC_2 -> alive

03/24/2008 04:12:20:Enterprise:Service Transition:APPSVR_DC_2 -> down

03/24/2008 04:16:56:Enterprise:Service Transition:APPSVR_DC_2 -> alive

03/24/2008 07:47:48:Enterprise:Service Transition:CBS_DC_1 -> down

03/24/2008 07:51:23:Enterprise:Service Transition:CBS_DC_1 -> alive

03/24/2008 07:55:18:Enterprise:Service Transition:CBS_DC_2 -> down

03/24/2008 07:57:58:Enterprise:Service Transition:CBS_DC_2 -> alive

03/24/2008 08:12:19:Enterprise:Service Transition:CBS_DC_2 -> down

03/24/2008 08:12:24:Enterprise:Service Transition:CBS_DC_2 -> alive

03/24/2008 08:14:24:Enterprise:Service Transition:CBS_DC_1 -> down

03/24/2008 08:14:34:Enterprise:Service Transition:CBS_DC_1 -> alive

03/24/2008 21:09:33:Enterprise:Service Transition:APPSVR_DC_1 -> down

What the mean from above, the server problem or load balancer problem ?

We using health check 443.

Because with this log, my customer suspect the problem from CSS. but from my perspective the service in server problem/busy.

anyone can help me for explanation my log.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Gilles Dufour Wed, 04/02/2008 - 08:44

the log can only tells you there is a communication issue between the CSS and the servers.

Only a sniffer trace of the traffic between the 2 devices will give you an indication about which side is in trouble.

Gilles.

Actions

This Discussion