6 ms·

The problem here was that the box went down by accident due to this bug.

• nodata 12y ago
  Really? How?
  • masklinn 12y ago
    Because the bug kills pid1 which took down production boxes: > I should point out that this is not theoretical. I went through all of the above because some real machines hit this for some reason. I don't have access to them, so I had to work backwards from just the message logged by init. > […] > Let me say this again: this happens in the wild. The "touch * * *..." repro looks contrived, because, well, that's the whole point of a repro.
    • nodata 12y ago
      No, how did you accidentally write to /etc/init.d?
      • masklinn 12y ago
        > No, how did you accidentally write to /etc/init.d? Let me quote again, with a finer slicing: > I went through all of the above because some real machines hit this for some reason. I don't have access to them
        • nodata 12y ago
          So you don't know? Gotcha.
          • chris_wot 12y ago
            That's the point.
          • raverbashing 12y ago
            And you apparently never managed anything in production. Have you ever heard of "reproducing a problem"?
            • nodata 12y ago
              I've never seen anything write to /etc/init.d in production (or anywhere actually), which is why I asked for the root cause.
              • raverbashing 12y ago
                From the article Upstart is watching /etc so the example might have used /etc/init.d just to illustrate it But yes, it is really strange. This usually means some weird proprietary tools
                • Ded7xSEoPKYNsDd 12y ago
                  I'm a bit out of the loop on this stuff, but isn't this kind of thing (bulk-rewriting stuff in /etc) exactly what configuration management systems do in their normal operation?
                  • Sanddancer 12y ago
                    I don't have a chef/puppet/etc system handy at the moment, but could this possibly be the result of someone setting a file immutable, with the chef recipe dealing with that bit of the filesystem changing, causing chef to repeatedly trying to apply a changeset?
              • kordless 12y ago
                The author indicates the watcher also follows /etc, so any files written there could cause this as well.
              • gpvos 12y ago
                Without, all the time, bothering to read the article, and asking here something that no-one here could know, because it's not in the article. If you really wanted to know, you could have mailed the author. Boy, do you deserve these downvotes.
  • jandrese 12y ago
    Maybe someone untarred a ton of config files into /etc and hit this limit?