Re: [cisco-ttl] merhaba

From: serhat aslan <serhataslan22_at_....>
Date: Wed, 14 Nov 2007 07:09:26 -0800 (PST)

 Bu tur bir hata protokolle ait bir hata degil, bu hata switch yazilimini yapan kisilerin durum analizi olarak kendi koyduklari bilgi hatalarina benziyor. O yuzden bu kisimlar mumkunse direk yada indirek ureticiye direk sorulmasi gerekiyor. Bahsi gecen seviye "3.derece hatalari" normalde onemli bir derece. Burda ise benim anladigim hardware yazilim bugina yada eksik kaynak kullanimina isaret ediyor. Sistem muhtemel schedule islemi icin belli bir cpu/ram kullanacaktir anormal durumlarda memory-leak durumlarinda ise cok krik hataya sebep olucaktir(sistem cakilmasi diyelim) ama burdaki hata bi tur bug degilde sanki sistem eksikligi durumunda urettigi bir tur hata/bilgi koduna benziyor.  Sorunu uretici ile degil kendiniz cozmek istiyorsaniz(tafsiye edilmeyen metod) sistem kaynaklarinin kullanimini ve cpu/ram/interface istatisliklerinin durumlarini detayli kontrol ederek daha cok sistem kaynagini bosa cikarin mumkunse kullanabildiginiz en basit IOS'u yukleyin.

kolay gelsin,
Serhat Aslan  

kaynak:  

link:http://www.cisco.com/warp/public/63/scheduler_12422.html

ozetle: "These messages are not always caused by a software bug. They may be issued in response to either instantaneous or sustained demand on the router. Increased or persistent messages may indicate that the traffic load needs to be reviewed"

genis:

SCHED-3-THRASHING This message means that the indicated process has relinquished control 50 consecutive times and there are still outstanding events to be processed.

The following messages on the console indicate such a problem:

    %SCHED-3-THRASHING: Process thrashing on watched queue 'ARP queue' (count 54).     -Process= "ARP Input", ipl= 5, pid= 6     -Traceback= 6020589C 60205BC4 60236520 601F4FD8 601F4FC4

These thrashing checks are intended to determine if a process is, for some reason, not doing its job. The thrashing check on watched queues (which is the troublesome message which is signaling) checks the number of elements on the queue. If this number remains the same for a given number of schedulings, the message is printed.

Unfortunately, some queues are length-limited, meaning that if the router gets very busy, the queues always stay at the maximum. As a result, the thrashing code in the scheduler gets confused and thinks that these queues have not been handled. The thrashing code has determined that the process which was supposed to handle the queue was not doing its job and prints the thrashing message.

The scheduler has been changed in later Cisco IOS software code. To keep track of whether the queues have been changed (so it can better determine whether or not the process is thrashing), the scheduler now notes whenever an item is removed from the queue, and only prints the thrashing message if nothing gets removed for a while.

Most of the time, the queue thrashing message is simply cosmetic.

These messages are not always caused by a software bug. They may be issued in response to either instantaneous or sustained demand on the router. Increased or persistent messages may indicate that the traffic load needs to be reviewed.

Note: These code changes are reported under CSCdj68470. If you are a registered user, you may use the Bug Toolkit to watch this bugID.

ali yorulmaz <blue49_49_at_yahoo.com> wrote:                               kendi sorunuma kendim çözüm bulayım.
    

   The following error messages might appear on the console and in the log:    

  %SCHED-3-THRASHING: Process thrashing on watched message event.  

-Process= "TTY Background", ipl= 6, pid= 20
 

-Traceback= 801BA4D4 801BA798 80114D94 801CEF34
 

 This message indicates a situation that does not appear to affect any system service. The system generates these log messages when you enter the terminal monitor command and encounter excessive SSH traffic (such as debug messages). This problem is resolved in Release 12.2(18)SXF. (CSCdy80670)                

 ali yorulmaz <blue49_49_at_yahoo.com> wrote:

           Arkadaşlar merhaba  

 cisco catalyst 6500 şaselerde  

 Nov 7 09:13:42.427: %SCHED-3-THRASHING: Process thrashing on watched message event.
-Process= "TTY Background", ipl= 5, pid= 35
-Traceback= 40EAE80C 40EAEA84 40361154
 

 şeklinde bir hata alıyorum
 daha önce bir arkadaş daha yazmış aynı hatayı ancak kimse cevap yazamamış.  ben araştırdım aşırı ssh bağlantısı olduğunda böyle bir hata oluşur demiş cisco. Tehlikeli değil demiş.  Ama yine de ben bu hatayı kaldırmak istiyorum  bir çözümü olan varsa sevinirim..  



 Do You Yahoo!?
 Tired of spam? Yahoo! Mail has the best spam protection around  http://mail.yahoo.com  

 [Non-text portions of this message have been removed]  



 Be a better sports nut! Let your teams follow you with Yahoo Mobile. Try it now.  

 [Non-text portions of this message have been removed]    

     
                               

       
---------------------------------

Be a better pen pal. Text or chat with friends inside Yahoo! Mail. See how.

[Non-text portions of this message have been removed] Received on Wed Nov 14 2007 - 16:09:33 CET

This archive was generated by hypermail 2.2.0 : Wed Nov 14 2007 - 16:09:34 CET