712449 - retire mv-buildproxy01

Status: RESOLVED FIXED

(Infrastructure & Operations :: RelOps: General, task)

Description

[Dustin J. Mitchell [:dustin] (he/him)]

With bug 704329 fixed, it's time to take this host out.

That will start with disabling named and squid on it, to see if anything screams, then deleting the vm (with corresponding inventory, DNS, DHCP, and nagios changes).

Comment 1

[Dustin J. Mitchell [:dustin] (he/him)]

Comment 0 gives the "mean" way to determine whether this is still in use.

The nicer way, which is worth trying, is to run tcpdump for a while on the host to see who, exactly, is still talking to it, then fix those hosts.  For mv-buildproxy01 I don't expect much, but I think we will need to use the "nice" technique for admin1a/b.infra.scl1, so it's worth practicing here.

Comment 2

[Justin Dow [:jabba]]

So, I'm 99% sure squid isn't doing anything on it, since that hasn't worked since we got the new firewalls in the office (seems like almost a year ago?). The only other thing on this box is named, and that is easy to check. Just run "rndc querylog" and it will start logging all DNS queries it receives and this will help identify what is still using it. I did this method when switching dns *to* this box from the older bc-proxy01, which was the first version of this box. Probably turn on query logging and then wait 24-48 hours to see what still uses it, fix those and then turn it off...

Comment 3

[Matthew Larrain[:MaRu]]

Running tcpdump -v >> tcpdump.txt in a screen session till tomorrow to verify what is going on connectionwise with this machine.

Comment 4

[Matthew Larrain[:MaRu]]

stopped bind9 after reviewing the tcpdump file
No complaints, powering off the server now.

Comment 5

[Dustin J. Mitchell [:dustin] (he/him)]

Please delete the VM, too.

Comment 6

[Matthew Larrain[:MaRu]]

VM has been deleted. Closing bug now.