Crumb
c/lemmy_support · by pineapple@lemmy.pineapplemachine.com · 3y

Lemmy's server log is extremely noisy, seemingly logging every single ActivityPub network request and its complete payload. How can I change this?

My log (accessed via docker-compose logs -f lemmy has gotten very noisy since my instance has been federating with several others. It makes it harder to troubleshoot odd behavior and I'm concerned that it's going to quickly fill up my server's disk with logs. What can I do to improve this?

9 points · 7 comments · view on lemmy.world

7 Comments

poVoq@slrpnk.net · 4 pts · 3y

Funny... I was just getting annoyed by the same.

I think the culprit is the RUST_LOG env variable where by default everything is set to "info" or "debug". I had it on "info", but that was still very verbose. I am currently trying it with all "warn".

Edit: the pictrs log is also overly verbose by default it seems.

ptz@lemmy.ptznetwork.org · 3 pts · 3y

I just used the Docker logging options to cap the stdout/stderr log to a reasonable size. Just add logging options to each chatty service and change 25m to whatever makes sense for your environment.

docker-compose.yml:

services:
  ....
  lemmy:
    ...
     logging:                                                                                                                                                                                 
        options:                                                                                                                                                                               
          max-size: 25m
  pictrs:
    ...
       logging:                                                                                                                                                                                 
        options:                                                                                                                                                                               
          max-size: 25m