#29672: trac gets overwhelmed
----------------------------------------------+------------------------
Reporter: anarcat | Owner: qbi
Type: defect | Status: closed
Priority: High | Milestone:
Component: Internal Services/Service - trac | Version:
Severity: Critical | Resolution: fixed
Keywords: | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
----------------------------------------------+------------------------
Comment (by anarcat):
we just had a problem again where trac was overwhelmed. I noticed an IP
that was hogging ~30 apache threads all on its own, thanks to this magic
command:
{{{
ss -t -n 'dport = 80 or sport = 80 or dport = 443 or sport = 443' | awk
'{print $NF}' | sed 's/:[0-9]*$//' | sort | uniq -c | sort
}}}
That showed a single IP that was taking up most of the threads. I killed
the IP with:
{{{
iptables -I INPUT -s $IPADDRESS -j REJECT
}}}
... and restarted apache (to kill old sockets). Load has returned to
normal and things seem generally happier.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/29672#comment:5>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
