59
Rant! 100GB Log file in Nextcloud. (lemmy.world)
submitted 2 years ago by to c/selfhosted@lemmy.world
76 comments fedilink hide all child comments
 

I set it to debug at somepoint and forgot maybe? Idk, but why the heck does the default config of the official Docker is to keep all logs, forever, in a single file woth no rotation?

Feels like 101 of log files. Anyway, this explains why my storage recipt grew slowly but unexpectedly.

you are viewing a single comment's thread
view the rest of the comments
[–] 25 points 2 years ago (2 children)

You should always setup logrotate. Yes the good old Linux logrotate...

  • permalink
  • fedilink
  • source
  • hideshow 4 child comments
    •
  • [–] 35 points 2 years ago (3 children)

    We should each not have to configure log rotation for every individual service. That would require identify what and how it logs data in the first place, then implementing a logrotate config. Services should include a reasonable default in logrotate.d as part of their install package.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] 5 points 2 years ago

    Docker services should let docker handle it, and the user could then manage it through Docker or forward to some other logging service (syslog, systemd, etc). Processes in containers shouldn't touch rotation or anything, just log levels and maybe which types of logs go to stdout vs stderr.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 0 points 2 years ago (1 child)

    Agreed, but going container route those nice basic practices are dead.

    And also, being mextcloud a php service, of can't by definition ship with a logrotate config too, because its never packaged by your repo.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 28 points 2 years ago (1 child)

    I don't disagree that logrotate is a sensible answer here, but making that the responsibility of the user is silly.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [+] -10 points 2 years ago (4 children)

    Are you crazy? I understand that we are used to dumbed down stuff, but come on...

    Rotating logs is in the ABC of any sysadmin, even before backups.

    First, secure your ssh logins, then secure your logs, then your fail2ban then your backups...

    To me, that's in the basic stuff you must always ensure.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 8 child comments
    •
  • [–] [S] 5 points 2 years ago (2 children)

    This is a docker! If your docker is marketed as ready to go and all-in-one, it should have basic things like that.

    If I were running this as a full system with a user base then of course I would go over everything and make sure it all makes sebse for my needs. But since my needs were just a running nc instance, it would make sense to run a simple docker with mostly default config. If your docker by default has terrible config, then you are missing the point a bit.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] -5 points 2 years ago (2 children)

    Dockers images are often incoherent and just different from one a other so much that you should never give something as expected and doublecheck the basics.

    Docker was never meant do deploy services, and I shows.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 4 points 2 years ago (1 child)

    Logration is the abc of the developer.
    Why should I need 3rd party tools to fix the work of the developer??

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 2 years ago (2 children)

    Why is that? Really? The Dev should replace a system function? And implement over and over again the same errors when logrotate exist?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 3 points 2 years ago (1 child)

    Yes, that’s exactly what we’re arguing here. The developer also should replace autotools/cmake, git, … Don’t be daft! Packaging sane defaults for logrotate is now replacing a system function?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •