Closed Bug 778831 Opened 8 years ago Closed 8 years ago
Setup tcpdump on socorro staging processors, hbase, and postgres
Tracking bug for Setup tcpdump on socorro staging processors, hbase, and postgres with a rolling window to get some packet captures
Postgres has been stable since we tweaked the connection time out setting. Working on tcpdumps for processors, monitor, and hbase nodes.
Status: NEW → ASSIGNED
tcpdump -Z root -i any -s0 -C 5000000 -W 1000 -w socorro.778831 is now running on supportadm.stage, processor1-2, and hp-node62-69
(In reply to Brandon Burton [:solarce] from comment #2) > tcpdump -Z root -i any -s0 -C 5000000 -W 1000 -w socorro.778831 is now > running on supportadm.stage, processor1-2, and hp-node62-69 ...and filling up disk by a significant extent on socorro-processor2.stage.metrics.phx1. I'm gonna gzip some older logs.
gzip logs older than 3 days (128 files) on socorro-processor1.stage.metrics.phx1 as well as; Before 177G /root/778831/ After 114G /root/778831/ Command ran; cd /root/778831/ find . -atime +3 | xargs gzip
I have stopped all the tcpdumps that were running and deleted all the pcap files to clean things up.
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Component: Server Operations: Web Operations → WebOps: Other
Product: mozilla.org → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.