Skip to content

nixos/nextcloud: Update logreader warning description #372187

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Ma27 merged 2 commits into from
Feb 14, 2025
Merged

nixos/nextcloud: Update logreader warning description #372187

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9683835
nixos/nextcloud: Update logreader warning description
provokateurin Jan 8, 2025
9430768
nixos/nextcloud: reword docs about logs a bit
Ma27 Feb 14, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions nixos/modules/services/web-apps/nextcloud.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -245,18 +245,18 @@ that are managed by Nix. If you want automatic updates it is recommended that yo

## Known warnings {#module-services-nextcloud-known-warnings}

### Failed to get an iterator for log entries: Logreader application only supports "file" log_type {#module-services-nextcloud-warning-logreader}
### Logreader application only supports "file" log_type {#module-services-nextcloud-warning-logreader}

This is because

* our module writes logs into the journal (`journalctl -t Nextcloud`)
* the Logreader application that allows reading logs in the admin panel is enabled
by default and requires logs written to a file.

The logreader application doesn't work, as it was the case before. The only change is that
it complains loudly now. So nothing actionable here by default. Alternatively you can
The logreader application doesn't work, as it was the case before.
So nothing actionable here by default. Alternatively you can

* disable the logreader application to shut up the "error".
* disable the logreader application to shut up the "info".

We can't really do that by default since whether apps are enabled/disabled is part
of the application's state and tracked inside the database.
Expand Down