nextcloud / nextcloud/cookbook
Log File gets really large when importing
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 641
- Forks
- 113
- Avg merge
- 21h 31m
- Merged PRs (30d)
- 26
Description
Description
I couldn't figure out where all the space was going on my server until I realized that each time I imported a new recipe the log file was filled with the parsing of the recipes. Is there any reason you are logging all the output and can this be turned off? I saw one import go from 0bytes up to 1GB even when I had set my error logs to only output errors instead of warning messages.
Reproduction
Steps to reproduce the behavior:
- Remove your log file
- Add a new recipe to import
- Watch the log file grow
Expected behavior
The log file wouldn't be touched during hte import unless there was issues with the parsing of a page.
Screenshots
If applicable, add screenshots to help explain your problem.
Browser
Chrome
Versions
Nextcloud server version: 18
Cookbook version: Latest
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by tracing the recipe import flow and its logging configuration, then reproduce the import while monitoring the log file. Done means normal recipe parsing no longer produces excessive log output, while genuine parsing issues remain visible.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100