• library_napper@monyet.cc
    link
    fedilink
    arrow-up
    4
    arrow-down
    10
    ·
    1 year ago

    Aaaand your server just crashed because of a spammy log. You lost the company $222 million overnight, the database is corrupt, and every 9 minutes the company looses another $1 million.

    Good job.

    • chayleaf@lemmy.ml
      link
      fedilink
      arrow-up
      6
      arrow-down
      1
      ·
      1 year ago

      systemd resets the logs when they get bit, this isn’t the 2000s anymore. But if you want to limit the size of /var/log, any modern filesystem has disk quotas per-directory

      • I found out the hard way that this isn’t always true. The vacuum task runs occasionally, but if the logs get spammed hard enough (i.e. faulty hardware) you can get 50GB of log files.

        That said, this problem can be prevented using a little extra configuration. I just didn’t expect this to be a problem on a vanilla Ubuntu install, lol.

    • If the server is that important, monitoring should’ve woken up the emergency response team long before the database crashed.

      It’s annoying to see Linux still doesn’t have usable disk quotas the way Windows 2000 had them, but the same is true for ACLs and many other things other operating systems have implemented decades before. I suppose you could repartition your disk to compensate for the lack of quote support by default, but there are better options.