|
Main /
ConnectionAlarmJust to review what happened this morning and how it was fixed... The switch serving both Spectrum network management servers, apple and peach, quit. Spectrum isn't too happy about losing all contact to everything. When the switch came back, OneClick [Spectrum's modern client] showed a landscape alarm for peach. Assuming peach had a problem (in retrospect, I'm not so sure), we restarted processd (the all-things-Spectrum controller, and Spectrum processes PPID). Still landscape alarm. Since a OneKick is so often effective, we tried that. Then peach vanished from OneClick. I launched SpectroGraph, the EOL ancient funky Motif-based Spectrum client before OneClick, and it saw the same thing. When 1C and SG agree, there's no need for OneKick. I used Notice the hope@apple$ netstat -na | grep 152.2.145.20 152.2.145.17.48879 152.2.145.20.50025 49640 0 49640 0 ESTABLISHED 152.2.145.17.56063 152.2.145.20.50116 49640 0 49640 0 TIME_WAIT That connection isn't there on peach. (In fact, that turns out to be the problem.) hope@peach$ netstat -na | grep 152.2.145.17 152.2.145.20.50025 152.2.145.17.48879 49640 0 49640 0 ESTABLISHED And unless hope@peach$ cat /opt/spectrum/NS/NSAGENT.OUT Failure to connect to Location Service at host: peach.net.unc.edu, port #: 56063. NSAgent is now ready on port 0xf00d... hope@apple$ netstat -na | grep 152.2.145.20 152.2.145.17.48879 152.2.145.20.50025 49640 0 49640 0 ESTABLISHED 152.2.145.17.56063 152.2.145.20.50129 49640 0 49640 0 ESTABLISHED Rebooting apple would have fixed it with overkill. Likewise, stopping It's quite possible that peach and OneClick didn't need attention. - Joni Sent from my iPod |