Tracker logs are too verbose

[josecelano]

Relates to: torrust/torrust-compose#2

I'm setting up a live demo for the Index and Tracker:

• Index: https://index.torrust-demo.com/
• HTTP Tracker: https://tracker.torrust-demo.com/announce
• UDP Tracker: udp://tracker.torrust-demo.com:6969/announce

After running the containers in the smallest Digital Ocean droplet I run out of disk. The instance has 25GB. I found out the problem was the Tracker logs, in a couple of days the log file size is 21GB 😮.

I've truncated the log file manually with these two commands:

Find log file for tracker:

$ sudo : > $(docker inspect --format='{{.LogPath}}' tracker)
-bash: /var/lib/docker/containers/397484cca9572d98524e4f81095bb27f90c349306c39bc517afe5bcb3a6d7f5e/397484cca9572d98524e4f81095bb27f90c349306c39bc517afe5bcb3a6d7f5e-json.log: Permission denied

Truncate the file:

sudo truncate -s 0 /var/lib/docker/containers/397484cca9572d98524e4f81095bb27f90c349306c39bc517afe5bcb3a6d7f5e/397484cca9572d98524e4f81095bb27f90c349306c39bc517afe5bcb3a6d7f5e-json.log

I can change the docker compose file to limit the log size. See https://docs.docker.com/compose/compose-file/compose-file-v3/#logging but we should make the log
less verbose.

Example log:

$ sudo tail /var/lib/docker/containers/397484cca9572d98524e4f81095bb27f90c349306c39bc517afe5bcb3a6d7f5e/397484cca9572d98524e4f81095bb27f90c349306c39bc517afe5bcb3a6d7f5e-json.log
{"log":"2023-12-14T11:20:55.273246832+00:00 [torrust_tracker::servers::udp::server][INFO] 16 bytes sent\r\n","stream":"stdout","time":"2023-12-14T11:20:55.273453315Z"}
{"log":"2023-12-14T11:20:55.294252436+00:00 [torrust_tracker::servers::udp::server][INFO] Received 16 bytes\r\n","stream":"stdout","time":"2023-12-14T11:20:55.29467371Z"}
{"log":"2023-12-14T11:20:55.294813382+00:00 [torrust_tracker::servers::udp::server][INFO] Sending 16 bytes ...\r\n","stream":"stdout","time":"2023-12-14T11:20:55.294968478Z"}
{"log":"2023-12-14T11:20:55.295131363+00:00 [torrust_tracker::servers::udp::server][INFO] 16 bytes sent\r\n","stream":"stdout","time":"2023-12-14T11:20:55.295311499Z"}
{"log":"2023-12-14T11:20:55.296958051+00:00 [torrust_tracker::servers::udp::server][INFO] Received 100 bytes\r\n","stream":"stdout","time":"2023-12-14T11:20:55.29726668Z"}
{"log":"2023-12-14T11:20:55.297364970+00:00 [torrust_tracker::servers::udp::server][INFO] Sending 43 bytes ...\r\n","stream":"stdout","time":"2023-12-14T11:20:55.29770331Z"}
{"log":"2023-12-14T11:20:55.297629194+00:00 [torrust_tracker::servers::udp::server][INFO] 43 bytes sent\r\n","stream":"stdout","time":"2023-12-14T11:20:55.297944733Z"}
{"log":"2023-12-14T11:20:55.327171107+00:00 [torrust_tracker::servers::udp::server][INFO] Received 16 bytes\r\n","stream":"stdout","time":"2023-12-14T11:20:55.327617363Z"}
{"log":"2023-12-14T11:20:55.327258346+00:00 [torrust_tracker::servers::udp::server][INFO] Sending 16 bytes ...\r\n","stream":"stdout","time":"2023-12-14T11:20:55.327676931Z"}
{"log":"2023-12-14T11:20:55.327333151+00:00 [torrust_tracker::servers::udp::server][INFO] 16 bytes sent\r\n","stream":"stdout","time":"2023-12-14T11:20:55.327887467Z"}

Maybe we should only log send and received bytes in debug mode? @WarmBeer @da2ce7.

These are the current stats for the tracker:

{
  "torrents": 53371,
  "seeders": 205,
  "completed": 115188,
  "leechers": 372,
  "tcp4_connections_handled": 26,
  "tcp4_announces_handled": 0,
  "tcp4_scrapes_handled": 26,
  "tcp6_connections_handled": 0,
  "tcp6_announces_handled": 0,
  "tcp6_scrapes_handled": 0,
  "udp4_connections_handled": 21822485,
  "udp4_announces_handled": 12969080,
  "udp4_scrapes_handled": 398379,
  "udp6_connections_handled": 0,
  "udp6_announces_handled": 0,
  "udp6_scrapes_handled": 0
}

[josecelano]

The disk (25GB) was filled in two days:

[josecelano]

The new output:

2023-12-28T11:56:38.137712228+00:00 [UDP][INFO] "ANNOUNCE TxID -1430127368 IH ae6eada4bbeec3250427f926510bd26eff5aa668"
2023-12-28T11:56:38.142941976+00:00 [UDP][INFO] "ANNOUNCE TxID 838258946 IH 8494df82ad42ba5fd8a59b7ea0dbd249b3581c04"
2023-12-28T11:56:38.143280474+00:00 [UDP][INFO] "ANNOUNCE TxID -2117539665 IH b8d209d46e771c74b073cc72eb0b732b9a4919d2"
2023-12-28T11:56:38.143795292+00:00 [UDP][INFO] "ANNOUNCE TxID -1759889240 IH 9fafc0baec918f1eed7cd0dd152b1f7d5c5bfb07"
2023-12-28T11:56:38.144110792+00:00 [UDP][INFO] "ANNOUNCE TxID 2045533876 IH fd525c936658c462502edbed8f658d396790381a"
2023-12-28T11:56:38.152624443+00:00 [UDP][INFO] "ANNOUNCE TxID -312192600 IH 1e83e692dd773af09e7ccf5995498f8e60afe0e1"