It's admin day again.

I tried to update the bugtracker one more time, with a new idea from who-knows-where. "Just delete that plugin in the filesystem and re-install it later via the user interface" said the knowledge base article. That should cure some problem we did not have last time I tried. Guess what: After some wasted hours, the bugtracker is once again f-ed up beyond repair, restore the backup.

Completely unrelated, systemd running as process 1 (a.k.a. init) on our fileserver decided to crash, complain loudly on the console how evil the world is, disconnected from /dev/initctl and dbus, and made the entire server refuse to reboot. Yeah, stuffing everything and the kitchen sink into init sounds completely natural and sensible to about one human on earth. What could possibly go wrong? A sane init looks different: Re^14: CPAN failed install.

No, I won't change the installation to get rid of systemd. I don't want to be the only one who knowns how to work with our servers. Running a stock Debian guarantees that at least one coworker can work with the servers, and others may find solutions through Google.

The trick to get the server to reboot even when systemd has wetted its pants is to sync, hope for the best, and run systemctl --force --force reboot. Almost as good as pressing the reset button while the HDD LED still blinks. Well, the fileserver seems to have survived. ext4 is pretty robust. And if something broke unnoticed, I have a good backup.

Alexander

--
Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)

In reply to Re: How not to implement updaters by afoken
in thread How not to implement updaters by afoken

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.