DX Application Performance Management

Expand all | Collapse all

TIM 10.5.2.15 non generate BT

Jump to Best Answer
  • 1.  TIM 10.5.2.15 non generate BT

    Posted 03-14-2018 04:55 PM
    Wed Mar 14 17:36:11 2018 30562   w7: HttpProto: DB: TransactionInspection/LanguageTagEnabled = 0 Wed Mar 14 17:36:11 2018 30537   w4: HttpProto: DB: TransactionInspection/ClientIpAddrEnabled = 0 Wed Mar 14 17:36:11 2018 30555   w6: HttpProto: DB: TransactionInspection/ClientIpAddr = "" Wed Mar 14 17:36:11 2018 30562   w7: HttpProto: DB: TransactionInspection/LanguageTag = "en-us,af*" Wed Mar 14 17:36:11 2018 30555   w6: HttpProto: DB: TransactionInspection/LanguageTagEnabled = 0 Wed Mar 14 17:36:11 2018 30537   w4: HttpProto: DB: TransactionInspection/ClientIpAddr = "" Wed Mar 14 17:36:11 2018 30555   w6: HttpProto: DB: TransactionInspection/LanguageTag = "en-us,af*" Wed Mar 14 17:36:11 2018 30537   w4: HttpProto: DB: TransactionInspection/LanguageTagEnabled = 0 Wed Mar 14 17:36:11 2018 30537   w4: HttpProto: DB: TransactionInspection/LanguageTag = "en-us,af*" Wed Mar 14 17:36:29 2018 30464   hub: WebServer: GET request for /GetSslServerStatus from 127.0.0.1 Wed Mar 14 17:36:31 2018 30464   hub: WebServer: GET request for /GetSslServerStatus from 127.0.0.1 Wed Mar 14 17:37:31 2018 30464   hub: WebServer: GET request for /GetSslServerStatus from 127.0.0.1 Wed Mar 14 17:38:31 2018 30464   hub: WebServer: GET request for /GetSslServerStatus from 127.0.0.1 Wed Mar 14 17:39:31 2018 30464   hub: WebServer: GET request for /GetSslServerStatus from 127.0.0.1Wed Mar 14 17:40:00 2018 30464 ! Warning: hub: ProbeStats: 258246 packets dropped by apmpacket because of errors in the last 300 secondsWed Mar 14 17:40:31 2018 30464   hub: WebServer: GET request for /GetSslServerStatus from 127.0.0.1 Wed Mar 14 17:41:21 2018 30464   hub: Service: running: tim-ageout -data /opt/CA/APM/tim/data -minFreePercent 25 -reclaimPercent 10 Wed Mar 14 17:41:21 2018 30464   hub: Service: tim-ageout exited with status 0 Wed Mar 14 17:41:30 2018 30464   hub: WebServer: GET request for /GetSslServerStatus from 127.0.0.1 Wed Mar 14 17:42:31 2018 30464   hub: WebServer: GET request for /GetSslServerStatus from 127.0.0.1 Wed Mar 14 17:43:31 2018 30464   hub: WebServer: GET request for /GetSslServerStatus from 127.0.0.1 Wed Mar 14 17:44:31 2018 30464   hub: WebServer: GET request for /GetSslServerStatus from 127.0.0.1Wed Mar 14 17:45:00 2018 30464 ! Warning: hub: ProbeStats: 223996 packets dropped by apmpacket because of errors in the last 300 secondsWed Mar 14 17:45:31 2018 30464   hub: WebServer: GET request for /GetSslServerStatus from 127.0.0.1 Wed Mar 14 17:46:31 2018 30464   hub: WebServer: GET request for /GetSslServerStatus from 127.0.0.1 Wed Mar 14 17:47:31 2018 30464   hub: WebServer: GET request for /GetSslServerStatus from 127.0.0.1 Wed Mar 14 17:47:59 2018 30464   hub: WebServer: GET request for /tess/settimtime?servertime=1521060480 from 127.0.0.1 Wed Mar 14 17:47:59 2018 30464   hub: WebServer: request forwarded from 167.28.131.184 Wed Mar 14 17:47:59 2018 30464   hub: WebServer: tess time is Wed Mar 14 17:48:00 2018 Wed Mar 14 17:48:31 2018 30464   hub: WebServer: GET request for /GetSslServerStatus from 127.0.0.1 Wed Mar 14 17:49:31 2018 30464   hub: WebServer: GET request for /GetSslServerStatus from 127.0.0.1Wed Mar 14 17:50:00 2018 30464 ! Warning: hub: ProbeStats: 246101 packets dropped by apmpacket because of errors in the last 300 secondsWed Mar 14 17:50:31 2018 30464   hub: WebServer: GET request for /GetSslServerStatus from 127.0.0.1 Wed Mar 14 17:51:22 2018 30464   hub: Service: running: tim-ageout -data /opt/CA/APM/tim/data -minFreePercent 25 -reclaimPercent 10 Wed Mar 14 17:51:22 2018 30464   hub: Service: tim-ageout exited with status 0 Wed Mar 14 17:51:31 2018 30464   hub: WebServer: GET request for /GetSslServerStatus from 127.0.0.1


  • 2.  Re: TIM 10.5.2.15 non generate BT
    Best Answer

    Posted 03-14-2018 07:32 PM

    Hi Fernando,

    I see:

    "! Warning: hub: ProbeStats: 246101 packets dropped by apmpacket because of errors in the last 300 seconds"

    That indicates a problem with the TIM packet processing from the NIC by apmpacket service.

    This could be due to bad traffic e.g. out of order bytes or perhaps too high throughput.

    Or the apmpacket buffer may need to be increased: Seeing dropped packets in Protocolstats.log and ho - CA Knowledge 

    However I would first suggest restart of apmpacket service to see if that will help i.e.

    service apmpacket restart

     

    Is this a new TIM installation or had it been previously working successfully? 

    If not resolved by restart probably best to raise a support case ( https://comm.support.ca.com/csupport/CaseManagement/cases/new ) for deeper analysis of TIM logs (with all trace options enabled and log file size increased in TIM settings MaxLogSizeInMB to 300)

     

    Thanks

     

    Lynn