Rant! 100GB Log file in Nextcloud.
-
Just basic checks I prefer to ensure, not leave to distribution good faith. If all is set, good to go. Otherwise, fix and move on.
Specially with self hosted stuff that is a bit more custom than the usual.
-
I stopped using Nextcloud a couple of years ago after it corrupted my encrypted storage. But I'm giving it a try again because of political emergency. But we sure need a long term replacement. Written in Rust or some other sane language.
-
The fact (IMHO) is that the logs shouldn't be there, in a persistent volume.
-
The price rboem is that the log file is inside the container in the www folder
-
Be too, and I went back to the standalone community container
-
for some helpful config, the below is the logging config I have and logs have never been an issue.
You can even add
'logfile' => '/some/location/nextcloud.log',to get the logs in a different place'logtimezone' => 'UTC', 'logdateformat' => 'Y-m-d H:i:s', 'loglevel' => 2, 'log_rotate_size' => 52428800, -
Wow, thanks for the heads up! I use Nextcloud AIO and backups take VERY long. I need to check about those logs!
Don't know if I'm just lucky or what, but it's been working really well for me and takes good care of itself for the most part. I'm a little shocked seeing so many complaints in this thread because elsewhere on the Internet that's the go-to method.
-
Good point!
-
Good suggestion, although I do feel it always comes back to this “many ways to do kind of the same thing” that surrounds the Linux ecosystem. Docker, podman, … some claim it’s better, I hear others say it’s not 100% compatible all the time. My point being more fragmentation.
-
Logration is the abc of the developer.
Why should I need 3rd party tools to fix the work of the developer?? -
At worst it saves in the config folder/volume where persistent stuff should be.
-
100 ways to configure a static ip.
Why does it need that? At least one per distro controlled by the distro-maintainers. -
Well that's not jellyfins faults but rather watchtower...
-
Yes! When I read that I need a second instance for cron I was like "wtf?" I know NC are not the only ones doing that but still
-
Yes. And then I read press announcements like this https://nextcloud.com/blog/press_releases/nextcloud-procolix-partner-netherlands/
-
It can be fidgety, especially if you stray from the main instructions, generally I do think it's okay, but also updates break it a bit every now and again.
-
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.
-
Nc is great, it really is amazing that it is foss.
Sure it isn't the slickest or fastest, and it does need more maintenance than most foss services, but it is also more complex and has so many great features.I really recommend nc, 99% of the time it just works for me. It just seems that their docker was done pretty poorly imo, but still it just works most of the time.
-
Look, defaults are a thing and if your defaults suck then you've made a mistake and if your default is to save a 100GB of log file in one file then something is wrong. The default in Dockers should just be not to save any log files on the persistent volumes.
-
Probably, but still, if they are, just rotate them.
