Reduce systemd logging #145

Closed
opened 2022-05-21 16:59:35 +00:00 by a · 4 comments
Owner

This is similar to #144, but for systemd logging, since this uses up a ton of disk I/O. We log stuff too verbosely.

This is similar to #144, but for systemd logging, since this uses up a ton of disk I/O. We log stuff too verbosely.
a added the
enhancement
bug
labels 2022-05-21 16:59:35 +00:00
a self-assigned this 2022-05-21 16:59:35 +00:00
a added this to the (deleted) project 2022-05-21 16:59:35 +00:00
a started working 2022-05-21 16:59:38 +00:00
Author
Owner

We can probably log Synapse at the ERROR level instead of WARNING.

We can probably log Synapse at the ERROR level instead of WARNING.
Author
Owner

slapd also spams the log with a ton of stuff.

slapd also spams the log with a ton of stuff.
Author
Owner

Adding

[Service]
Environment="SLAPD_OPTIONS=-s 0"

to a slapd override file fixes the slapd log spam.

Adding ``` [Service] Environment="SLAPD_OPTIONS=-s 0" ``` to a slapd override file fixes the slapd log spam.
Author
Owner

It looks like PostgreSQL is responsible for most of the disk I/O now. (specifically the Synapse database)

It looks like PostgreSQL is responsible for most of the disk I/O now. (specifically the Synapse database)
a closed this issue 2022-05-21 17:30:39 +00:00
a stopped working 2022-05-21 17:30:39 +00:00
31 minutes 1 second
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Total time spent: 31 minutes 1 second
a
31 minutes 1 second
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: exozyme/exozyme#145
No description provided.