Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*2\.4\.1\:\s+TCP\s+assertion\s+failed\s*$/: 36 ]

Total 36 documents matching your query.

1. es? (score: 1)
Author: Petru Paler <ppetru@xxxxxxxxxx>
Date: Thu, 15 Feb 2001 17:14:45 +0200
Moderately-high (couple hundred thousand hits a day) loaded web server running 2.4.1 (no other patches). I got this twice in the syslog after 15 days uptime: KERNEL: assertion (tp->lost_out == 0) fai
/archives/netdev/2001-02/msg00114.html (8,307 bytes)

2. es? (score: 1)
Author: kuznet@xxxxxxxxxxxxx
Date: Thu, 15 Feb 2001 21:25:49 +0300 (MSK)
This is harmless. And this is not harmless. If you can identify client shrinking window, please, do this. Alexey
/archives/netdev/2001-02/msg00116.html (8,220 bytes)

3. led (score: 1)
Author: Petru Paler <ppetru@xxxxxxxxxx>
Date: Thu, 15 Feb 2001 20:29:08 +0200
Ok. Identify, what ? Do you want me to paste the actual numbers (I've got plenty of them in all my web and mail server logs). -- Petru Paler, mailto:ppetru@xxxxxxxxxx http://www.ppetru.net - ICQ: 418
/archives/netdev/2001-02/msg00117.html (9,185 bytes)

4. led (score: 1)
Author: kuznet@xxxxxxxxxxxxx
Date: Thu, 15 Feb 2001 21:33:21 +0300 (MSK)
What OS do they use. Until now curcumstances when window is shrunk are unknown. Absolutely. No known OSes make such shit. Alexey
/archives/netdev/2001-02/msg00118.html (8,201 bytes)

5. led (score: 1)
Author: Petru Paler <ppetru@xxxxxxxxxx>
Date: Thu, 15 Feb 2001 20:37:37 +0200
I have no way to do that, these servers do mail and web service for a couple hundred thousand domains so clients are all over the world.. Looks like theory is different from practice again :) -- Petr
/archives/netdev/2001-02/msg00119.html (9,207 bytes)

6. led (score: 1)
Author: Bogdan Costescu <bogdan.costescu@xxxxxxxxxxxxxxxxxxxxx>
Date: Thu, 15 Feb 2001 19:42:34 +0100 (CET)
You said that you have IPs. You can use nmap (http://www.nmap.org) to identify the OS. You do need however direct link to the hosts, it doesn't work if they are dialed-up... Sincerely, Bogdan Costesc
/archives/netdev/2001-02/msg00120.html (9,229 bytes)

7. led (score: 1)
Author: kuznet@xxxxxxxxxxxxx
Date: Thu, 15 Feb 2001 21:52:17 +0300 (MSK)
Usual story. I hope soon or early we will be luck with this and someone will reply: "Hey, indeed, I see one address, which is in one hop of us! Wait awhile, I am making some calls..." 8) Alexey
/archives/netdev/2001-02/msg00121.html (8,742 bytes)

8. led (score: 1)
Author: Andi Kleen <ak@xxxxxx>
Date: Thu, 15 Feb 2001 20:49:24 +0100
My personal guess is that it's one of the TCP bandwidth limiter proxy boxes again. These are unfortunately rather hard to detect, and it's not the client's fault. -Andi
/archives/netdev/2001-02/msg00122.html (9,289 bytes)

9. k-local (score: 1)
Author: kuznet@xxxxxxxxxxxxx
Date: Thu, 15 Feb 2001 23:24:43 +0300 (MSK)
Yes. If it is true, this can be ignored. Transient shrinks are harmless. If this is client's stack or some mobile agent... Alexey
/archives/netdev/2001-02/msg00125.html (8,877 bytes)

10. use link-local (score: 1)
Author: jamal <hadi@xxxxxxxxxx>
Date: Fri, 16 Feb 2001 10:48:18 -0500 (EST)
I smell a packeteer somewhere along the path. cheers, jamal
/archives/netdev/2001-02/msg00129.html (9,201 bytes)

11. FTP site down? (score: 1)
Author: Chris Wedgwood <cw@xxxxxxxx>
Date: Sun, 18 Feb 2001 21:20:24 +1300
My personal guess is that it's one of the TCP bandwidth limiter proxy boxes again. These are unfortunately rather hard to detect, and it's not the client's fault. as far as i know, Packeteer are the
/archives/netdev/2001-02/msg00139.html (9,634 bytes)

12. ssertion failed (score: 1)
Author: kuznet@xxxxxxxxxxxxx
Date: Sun, 18 Feb 2001 20:29:48 +0300 (MSK)
Yes! Actually it is enough that you made some ftp download from dust.inr.ac.ru from host sitting behind this device and tell me time to find message easier. Alexey
/archives/netdev/2001-02/msg00140.html (9,017 bytes)

13. ssertion failed (score: 1)
Author: Cacophonix <cacophonix@xxxxxxxxx>
Date: Sun, 18 Feb 2001 09:51:28 -0800 (PST)
If possible you may want to test in the presence of asymmetric routing - that often causes problems with devices like these that rewrite tcp window advertisements in the middle of the network - i.e,
/archives/netdev/2001-02/msg00141.html (9,531 bytes)

14. ssertion failed (score: 1)
Author: jamal <hadi@xxxxxxxxxx>
Date: Sun, 18 Feb 2001 12:55:55 -0500 (EST)
Actually, route asymmetry may not be much of a factor here. Most of these devices are at the client's edge as opposed to the server end i.e they protect the client's network portion of the resources.
/archives/netdev/2001-02/msg00142.html (9,170 bytes)

15. ssertion failed (score: 1)
Author: Cacophonix <cacophonix@xxxxxxxxx>
Date: Sun, 18 Feb 2001 10:20:24 -0800 (PST)
Depends. I've seen networks where the device was on the ethernet prior to the routers attaching to the WAN - in larger networks there tend to be multiple such ethernet "hub LANs" and multiple WAN lin
/archives/netdev/2001-02/msg00143.html (9,721 bytes)

16. ssertion failed (score: 1)
Author: Chris Wedgwood <cw@xxxxxxxx>
Date: Mon, 19 Feb 2001 07:33:26 +1300
Yes! Actually it is enough that you made some ftp download from dust.inr.ac.ru from host sitting behind this device and tell me time to find message easier. I will go dig one up later today and let y
/archives/netdev/2001-02/msg00144.html (8,695 bytes)

17. ssertion failed (score: 1)
Author: Chris Wedgwood <cw@xxxxxxxx>
Date: Mon, 19 Feb 2001 07:35:31 +1300
If possible you may want to test in the presence of asymmetric routing - that often causes problems with devices like these that rewrite tcp window advertisements in the middle of the network - i.e,
/archives/netdev/2001-02/msg00145.html (9,151 bytes)

18. ssertion failed (score: 1)
Author: jamal <hadi@xxxxxxxxxx>
Date: Sun, 18 Feb 2001 13:35:39 -0500 (EST)
Policy management sounds like hell in the scenario you describe (if you cant enforce single point of entry/exit into the network for a flow) Mostly because you have stateful policies that dont get pr
/archives/netdev/2001-02/msg00146.html (9,571 bytes)

19. 2.4.1: TCP assertion failed (score: 1)
Author: Petru Paler <ppetru@xxxxxxxxxx>
Date: Thu, 15 Feb 2001 17:14:45 +0200
Moderately-high (couple hundred thousand hits a day) loaded web server running 2.4.1 (no other patches). I got this twice in the syslog after 15 days uptime: KERNEL: assertion (tp->lost_out == 0) fai
/archives/netdev/2001-02/msg00356.html (8,367 bytes)

20. Re: 2.4.1: TCP assertion failed (score: 1)
Author: kuznet@xxxxxxxxxxxxx
Date: Thu, 15 Feb 2001 21:25:49 +0300 (MSK)
Hello! This is harmless. And this is not harmless. If you can identify client shrinking window, please, do this. Alexey
/archives/netdev/2001-02/msg00358.html (8,248 bytes)


This search system is powered by Namazu