View Source

Yet again, this is abbreviated. One reason is that our software tools are broken:

I can't get to nagios through ops-perdigao.dyndns.org. I thought Gary's last message said it should work. Presumably, I could vpn in to ustar and run nagios locally, but I haven't tried this. Running from within the ops center on the .100 subnet serving from 192.168.1.10 works.
eddy's WiFi stopped working yesterday. It connects, but ping drops 50–80% of packets on all 3 wifi networks. cockpit can't connect. Since this is the only machine (other than ustar on the balcony) that can run cockpit, we no longer have cockpit. My workaround plan is to run an ethernet cable from the balcony down to the ops center main floor to connect eddy back to the net.

Started the morning with a drive to v07, that I had recalled didn't come up yesterday. Found that v07b is fine, but the power front panel on v07b squeals when I connect v07t power through the AUX connector. I suspect something is quite wrong with v07t. (I also recall that it was in our plan to ground v07t, but I don't think we did it.) Since Andy took the day off, I couldn't climb to check this out. v07b is running fine and archiving to its USB stick.

Then got a call from José Carlos that Generg was working on the power on the sw ridge. With their work, replacing 2 12V power supplies, and resetting one differential protection, the entire ridge is now up. (The Generg crew may have reset more differential protection circuits.) The Generg crew at first thought that some of the problem was that we had connected the ground wire to our power supplies to neutral, so they cut the ground wire off. However, when they started to demonstrate the problem to me, they couldn't replicate it (Murphy's Law). Thus, I think some of the ground wires are now connected and others aren't. At tnw03, I found that +24VDC from the DC-DC converter wasn't on and replaced it, however the new one didn't start immediately, yet eventually did while I was "poking around". Not sure yet what action worked.