![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
All computer repair comes down to this.
You should imagine that, for this post, my LJ icon is a picture of the "Chicken On Yer Head" card from Munchkin. Teh IntarWeb doesn't seem to have an image available, so it'll have to wait until I can scan it.
Situation: absinthe was due for sundry work yesterday--swapping in new mirrored drive, updated kernel, etc. etc. Most of this was accomplished with little hassle, except for that once again the automatic updates tried to plug in Mailman 2.x, which is not compatible with 1.x, which fucks up all our existing lists, heigh ho. We beat that into useable, though unpretty shape, yesterday evening, and the primary worker continued upgrading the jail kernels.
Then, about 11:45pm, I was woken out of sound sleep by a phone call: absinthe was no longer responding on the network and did I know if anyone was still in the office? No one was, as it turned out, so as next person in I would need to hard reboot it when I came in the next morning.
This I did. Still no network. Happy routing table, happy ifconfig, all applications loading happily. Reseated both ends of ethernet cable; turned off ipfilter; still can't reach the gateway. Got word from![[livejournal.com profile]](https://www.dreamwidth.org/img/external/lj-userinfo.gif)
blarglefiend that amoeba had vanished off the planet at about the same time, which sort of indicated some kind of overnight network buggery. I have no access to the routers, so I nobbled Ken when he got in--he saw nothing amiss, but he's not familiar with the co-lo routers so this was nothing like definitive. Rebooted from old kernel: nothing. Rebooted the switch: nothing. Finally, just for thoroughness' sake, I replaced the Ethernet cable entirely, since we had nothing better to try til Ed or Brian got in.
That worked.
Situation: absinthe was due for sundry work yesterday--swapping in new mirrored drive, updated kernel, etc. etc. Most of this was accomplished with little hassle, except for that once again the automatic updates tried to plug in Mailman 2.x, which is not compatible with 1.x, which fucks up all our existing lists, heigh ho. We beat that into useable, though unpretty shape, yesterday evening, and the primary worker continued upgrading the jail kernels.
Then, about 11:45pm, I was woken out of sound sleep by a phone call: absinthe was no longer responding on the network and did I know if anyone was still in the office? No one was, as it turned out, so as next person in I would need to hard reboot it when I came in the next morning.
This I did. Still no network. Happy routing table, happy ifconfig, all applications loading happily. Reseated both ends of ethernet cable; turned off ipfilter; still can't reach the gateway. Got word from
blarglefiend that amoeba had vanished off the planet at about the same time, which sort of indicated some kind of overnight network buggery. I have no access to the routers, so I nobbled Ken when he got in--he saw nothing amiss, but he's not familiar with the co-lo routers so this was nothing like definitive. Rebooted from old kernel: nothing. Rebooted the switch: nothing. Finally, just for thoroughness' sake, I replaced the Ethernet cable entirely, since we had nothing better to try til Ed or Brian got in.That worked.