Error with log files rotation

[EnolMy]

Hello,

I have Pika installed as docker container with default config in log rotation configuration. Today I have an issue because the disk of the host being full because pika logs files.

The configuration I can see in the config file about log rotation is:

# Expire-time of binlog(write2file) files that stored within log-path.
# Any binlog(write2file) files that exceed this expire time will be cleaned up.
# The unit of expire-logs-days is in [days] and the default value is 7(days).
# The [Minimum value] of this parameter is 1(day).
expire-logs-days : 7

# The maximum number of binlog(write2file) files.
# Once the total number of binlog files exceed this value,
# automatic cleaning will start to ensure the maximum number
# of binlog files is equal to expire-logs-nums.
# The [Minimum value] of this parameter is 10.
expire-logs-nums : 10

# write_binlog  [yes | no]
write-binlog : yes

# The size of binlog file, which can not be modified once Pika instance started.
# [NOTICE] Master and slaves must have exactly the same value for the binlog-file-size.
# The [value range] of binlog-file-size is [1K, 2G].
# Supported Units [K|M|G], binlog-file-size default unit is in [bytes] and the default value is 100M.
binlog-file-size : 104857600

I have attached a screenshot about the amount of files ( I have deleted a few days, from may 22 to may 25 because the disk was full)

I have seen the first log file was from may 20th, expire-logs-days : 7 is not working. Before the files deletion, pika had 69 log files, so expire-logs-nums : 10 are not working well too, and the size of the files is 1.8 Gb, so binlog-file-size : 104857600 fails too

We are using pika:3.5.2.0

[lukebakken]

Hello, I think you posted this issue to the wrong repository. pika:3.5.2.0 is not a valid version of the Pika AMQP 0.9.1 client library.

[EnolMy]

Sorry. my bad