This is how my logs look like:

chat-synapse-1  | 2023-01-30 09:03:24,465 - synapse.handlers.device - 1273 - WARNING - _maybe_retry_device_resync-3501- Failed to handle device list update for @REDACTED.example.com: 403: Forbidden
chat-synapse-1  | 2023-01-30 09:03:24,679 - synapse.http.matrixfederationclient - 709 - WARNING - _maybe_retry_device_resync-3501- {GET-O-60894641} [synapse.solarinet.org] Request failed: GET matrix://REDACTED/_matrix/federation/v1/user/devices/REDACTED: HttpResponseException('302: Found')
chat-synapse-1  | 2023-01-30 09:03:24,679 - synapse.handlers.device - 1273 - WARNING - _maybe_retry_device_resync-3501- Failed to handle device list update for @REDACTED.example.com: 302: Found
chat-synapse-1  | 2023-01-30 09:03:24,690 - synapse.http.matrixfederationclient - 709 - WARNING - _maybe_retry_device_resync-3501- {GET-O-60894644} [matrix.litness.de] Request failed: GET matrix://REDACTED/_matrix/federation/v1/user/devices/REDACTED: HttpResponseException('404: Not Found')
chat-synapse-1  | 2023-01-30 09:03:24,691 - synapse.handlers.device - 1273 - WARNING - _maybe_retry_device_resync-3501- Failed to handle device list update for @REDACTED.example.com: 404: Not Found
chat-synapse-1  | 2023-01-30 09:03:24,705 - synapse.http.matrixfederationclient - 709 - WARNING - _maybe_retry_device_resync-3501- {GET-O-60894691} [matrix.appsforce.org] Request failed: GET matrix://REDACTED/_matrix/federation/v1/user/devices/REDACTED: HttpResponseException('403: Forbidden')
chat-synapse-1  | 2023-01-30 09:03:24,706 - synapse.handlers.device - 1273 - WARNING - _maybe_retry_device_resync-3501- Failed to handle device list update for @REDACTED.example.com: 403: Forbidden
chat-synapse-1  | 2023-01-30 09:03:24,921 - synapse.http.matrixfederationclient - 709 - WARNING - _maybe_retry_device_resync-3501- {GET-O-60894704} [synapse.solarinet.org] Request failed: GET matrix://REDACTED/_matrix/federation/v1/user/devices/REDACTED: HttpResponseException('302: Found')
chat-synapse-1  | 2023-01-30 09:03:24,921 - synapse.handlers.device - 1273 - WARNING - _maybe_retry_device_resync-3501- Failed to handle device list update for @REDACTED.example.com: 302: Found
chat-synapse-1  | 2023-01-30 09:03:24,935 - synapse.http.matrixfederationclient - 709 - WARNING - _maybe_retry_device_resync-3501- {GET-O-60894705} [matrix.appsforce.org] Request failed: GET matrix://REDACTED/_matrix/federation/v1/user/devices/REDACTED: HttpResponseException('403: Forbidden')
chat-synapse-1  | 2023-01-30 09:03:24,936 - synapse.handlers.device - 1273 - WARNING - _maybe_retry_device_resync-3501- Failed to handle device list update for @REDACTED.example.com: 403: Forbidden
chat-synapse-1  | 2023-01-30 09:03:25,040 - synapse.http.matrixfederationclient - 709 - WARNING - _maybe_retry_device_resync-3501- {GET-O-60894731} [akuj.in] Request failed: GET matrix://REDACTED/_matrix/federation/v1/user/devices/REDACTED: HttpResponseException('403: Forbidden')
chat-synapse-1  | 2023-01-30 09:03:25,040 - synapse.handlers.device - 1273 - WARNING - _maybe_retry_device_resync-3501- Failed to handle device list update for @REDACTED.example.com: 403: Forbidden
chat-synapse-1  | 2023-01-30 09:03:25,044 - synapse.http.matrixfederationclient - 709 - WARNING - _maybe_retry_device_resync-3501- {GET-O-60894739} [ring0.de] Request failed: GET matrix://REDACTED/_matrix/federation/v1/user/devices/REDACTED: HttpResponseException('404: Not Found')
chat-synapse-1  | 2023-01-30 09:03:25,045 - synapse.handlers.device - 1273 - WARNING - _maybe_retry_device_resync-3501- Failed to handle device list update for @REDACTED.example.com: 404: Not Found
chat-synapse-1  | 2023-01-30 09:03:25,209 - synapse.http.matrixfederationclient - 709 - WARNING - _maybe_retry_device_resync-3501- {GET-O-60894832} [synapse.glester.com] Request failed: GET matrix://REDACTED/_matrix/federation/v1/user/devices/REDACTED: HttpResponseException('403: Forbidden')

How can I reduce these specific WARNING messages without reducing the log level? They’re so spammy that I a) can’t see anything else going on without extensively grepping and b) it’s filling up my disk to the point that 80GB of logs on the docker partition made my server go boom.

  • poVoq
    link
    fedilink
    21 year ago

    Log rotation? But I don’t see why you would not want to reduce the log level to errors only on a production system.

    • Helix 🧬OP
      link
      fedilink
      11 year ago

      Log rotation?

      Rotation just zips it, doesn’t delete in my case. Trying to avoid setting up a whole rsyslog server for this. I also don’t want to delete logs, I just want the spam to stop. This should be an INFO log level, I think, since it’s not really warranting a WARNING.

      • poVoq
        link
        fedilink
        2
        edit-2
        1 year ago

        Dunno, file a bug report up-stream? But I personally would just switch to error level only. You can always temporarily switch back in case you need to investigate something further.

        Oh and you should really delete old logs after a while (one month or so) as they can include a lot of privacy sensitive metadata.

        • Helix 🧬OP
          link
          fedilink
          11 year ago

          Oh and you should really delete old logs after a while (one month or so) as they can include a lot of privacy sensitive metadata.

          Good point! Sadly there are not a lot of options for logging, e.g. I’d like to disable the logging of IP addresses wherever possible.