Edit - Server Fault

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

That's a fantastic answer. Thanks mcjeff, it confirms what I was thinking. The server goes away for a while and then comes back yes. I've checked the logs when it happened and saw nothing. There is not enough visitors yet to say if we were the only one affected but last time I asked them to verify what happened, they found a faulty network adapter and changed it. This time, they say they didn't find anything faulty on their end except maybe a few error on our switch port that didn't seem recent. That's when they talked about the lacking memory and conntrack table size. Faulty cable possible?

lpfavreau
– lpfavreau

2010-03-16 20:48:42 +00:00
Commented Mar 16, 2010 at 20:48
1

Faulty cable is possible -- but you just said something else that makes sense, too... "conntrack table size." I've had situations on systems where that has caused the machine to just drop traffic, much like you're seeing. Though, the cluster I'm referring to was pumping out ~2000 hits/sec. You probably wouldn't see anything unless you had a lot of IP tables rules or you were doing a tremendous amount of traffic. You can check, though: sysctl net.ipv4.netfilter | grep conntrack

McJeff
– McJeff

2010-03-16 21:35:21 +00:00
Commented Mar 16, 2010 at 21:35
2

ip_conntrack_count is the number you have, ip_conntrack_max is the total amount possible. Are they close? IF you were dropping packets due to a full connection tracking table, then 'dmesg' would report that. To suggest that on a system doing such a small amount of traffic sounds off to me, though.

McJeff
– McJeff

2010-03-16 21:36:26 +00:00
Commented Mar 16, 2010 at 21:36
My $10 says it's a network related. Faulty cable, bad NIC, screwy ARP handling on an access switch.

McJeff
– McJeff

2010-03-16 21:39:30 +00:00
Commented Mar 16, 2010 at 21:39
net.ipv4.netfilter.ip_conntrack_count = 7, net.ipv4.netfilter.ip_conntrack_max = 1048576... doesn't sound close to me... You are confirming what I thought: a lot of bogus diagnosis even with access to the machine to check that out... I would put another 10$ they changed something else while giving me all this food for thought with a recommendation for RAM upgrade ($). I don't have proof but I found every other diagnosis doubtful with how little traffic we are currently handling on this development machine.

lpfavreau
– lpfavreau

2010-03-16 22:46:05 +00:00
Commented Mar 16, 2010 at 22:46

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)

<https://example.com>

[example](https://example.com)

<a href="https://example.com">example</a>

formatting help »
answering help »