cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
367
Views
0
Helpful
2
Replies

logging service status change in sys or traplog

sthon-dbsys
Level 1
Level 1

is there any possibility to generate a log for a service status change to "dying".

The only status change which are logged are service "up/down".

I have no chance to see, at what time or how often the service was dying.

2 Replies 2

Gilles Dufour
Cisco Employee
Cisco Employee

We have an Ask The Expert Event currently for CSS questions, please join us there if you have more questions.

To answer this question, the solution is to increase the logging level for the keepalive to DEBUG.

The dying status is only displayed in a level 7/debug message.

the global config command is 'logging subsystem keepalive level debug'

Regards,

Gilles.

Hi Gilles,

the command:

logging subsystem keepalive level debug-7

does not solve my problem.

I get no log info, for a dying service :-(

ffmcss02-01# show clock

Date: 01-21-2004

Time: 13:51:25

TimeZone: CET: +01:+00:+00

ffmcss02-01# show service cpujd03a

Name: cpujd03a Index: 10

Type: Local State: Dying

Rule ( 172.24.36.28 ANY ANY )

Session Redundancy: Disabled

Redirect Domain:

Redirect String:

Keepalive: (TCP-8903 10 3 30 )

Last Clearing of Stats Counters: 10/24/2003 05:50:49

Mtu: 1500 State Transitions: 1

Total Local Connections: 2 Total Backup Connections: 0

Current Local Connections: 0 Current Backup Connections: 0

Total Connections: 2 Max Connections: 65534

Total Reused Conns: 0

Weight: 1 Load: 2

DFP: Disable

ffmcss02-01#

ffmcss02-01# show log sys.log tail 5

JAN 20 09:47:31 1/1 159 NETMAN-1: TRAP:Authentication:Generated by: 172.17.97.164

JAN 21 12:49:39 1/1 160 NETMAN-2: Enterprise:Service Transition:cpujd03a -> suspended

JAN 21 12:49:47 1/1 161 NETMAN-2: Enterprise:Service Transition:cpujd03a -> down