nextcloud / nextcloud/documentation
nextcloud.log fails "check for expected files" while update
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 628
- Forks
- 2.5k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 135
Description
Thanks for helping improve our documentation!
- There is always room for improvement!
- All contributions (changes and change ideas) - from the largest to the tiniest - help make Nextcloud better and easier to use!
In the documentation the example config for file based logging is
"log_type" => "file",
"logfile" => "nextcloud.log",
"loglevel" => 3,
"logdateformat" => "F d, Y H:i:s",
The last update from Nextcloud 31.05 to 31.06 apparently doesnt't expect the log file in /var/www/nextcloud/, so it fails the first check.
Changing the file path to:
"logfile" => "data/nextcloud.log",
resolved the issue for me.
Notes
- Please be patient: this is a large open source project that is overseen by a mixture of volunteers and non-volunteers which are all ultimately busy.
- If your suggestion is a troubleshooting scenario or one you're not 100% certain about, please post for feedback on the Nextcloud Help Forum first.
- Then return here to bring back your experience to help improve the documentation for clarity, etc. (and link back to the forum discussion in your report!)
Protip: If you want to help move things along (or just help out in other ways too) here are some suggestions:
- Look for areas where you can assist - even seemingly unrelated areas - because doing so frees up resources for your favorite topics and ideas.
- Submit a proposed change - that attempts to addresses your issue - as a pull request.
- Participate in a discussion on some other unresolved submitted idea ("issues") to help move it along.
- Post a comment or review on someone else's proposed change ("pull request") to help move it along.
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
Start with the linked logging configuration documentation and its file-based logging example. Verify whether the reported update check requires the log path under data/nextcloud.log, then update the example if confirmed; done means the documented configuration matches the current update behavior.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100