загадка glibc - как отменить частичное обновление?

Я использую googlecl для уведомлений Nagios. Я добавляю, что "событие" к моему календарю с в HH:MM/пополудни с HH и набором MM к +2 минутам с текущего времени, и получите SMS с коротким описанием события за 1 минуту, прежде чем "событие" начнется.

Может быть это, возможно настроить, Вы посылаете checing демону по электронной почте для выполнения сценария, если фильтрованная почта находится в indox.

0
задан 21 January 2014 в 20:45
1 ответ

OK, I think we know what happened. A couple of months ago, when reviewing the daily logwatch report, I saw that someone had started to run a dist-upgrade. I asked them about it, and they said they thought they were on their local linux machine, not my server, and ^C'd as soon as they realized something was wrong.

All appeared to be well, so I didn't think more of it... until a different coworker was installing memcached, and for some perhaps-related reason was having problems with the install, so he used one of the various force-this-upgrade options, and that's when all hell broke loose.

Many things were broken: apt/aptitude, anything complicated, even man. But dpkg worked! And if you look, there are archives of every standard library at every point release / update to the system. With careful iterations of downloading a package, install / force reversion to that version, recheck dependencies, download again, we were able to knit the system back together to exactly the same version of all relevant libraries we had at the time. I think we had to use a "hold" option once to keep a circular dependency from causing trouble. It took several hours, but we got the system back to the original state. Then we did a restart (just to make sure -- it had been 253 days since last reboot), and then a standard upgrade to get to the latest release of Ubuntu 10.04 LTS, and reboot again. Voila - saved.

What a nightmare!

Lessons learned:

  1. treat it more seriously when someone accidentally starts upgrading your system;
  2. be sure to make all machines clearly identifiable when you log in;
  3. be sure to stay on top of the smaller releases, since that we wouldn't have gone to the archives;
  4. thank the crazy people who keep those archives of every library version for every system release!
0
ответ дан 5 December 2019 в 14:27

Теги

Похожие вопросы