Selfhosted

60451 readers

928 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

Rant! 100GB Log file in Nextcloud. (lemmy.world)

submitted 1 year ago by MTK@lemmy.world 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

[–] catloaf@lemm.ee 35 points 1 year 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.

[–] sugar_in_your_tea@sh.itjust.works 5 points 1 year 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.

[–] RubberElectrons@lemmy.world 2 points 1 year ago

Ideally yes, but I've had to do this regularly for many services developed both in-house and out of house.

Solve problems, and maybe share your work if you like, I think we all appreciate it.

[–] Shimitar@downonthestreet.eu 0 points 1 year ago (1 children)

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.

[–] peregus@lemmy.world 5 points 1 year ago (1 children)

The fact (IMHO) is that the logs shouldn't be there, in a persistent volume.

[–] Shimitar@downonthestreet.eu -1 points 1 year ago

Probably, but still, if they are, just rotate them.