Blockscout: Log eating space

[bellaj]

I have deployed blockscout on azure with a Poa network. I have faced few issues, but I've managed to get the explorer working but I am getting still a repetitive error in the log :

therefore the log file's size is quickly becoming huge (X Gigbytes).
Am wondering how can i redirect the log or disable it?

[ayrat555]

@bellaj which version of parity are you using?

[vbaranov]

@bellaj also, logs rotation is configured for production environment:
https://github.com/poanetwork/blockscout/blob/81179f9459fc6a80944d8490a331c9160d85ecdd/apps/explorer/config/prod.exs#L16

[bellaj]

@bellaj which version of parity are you using?
@ayrat555
I am using :

Parity v1.10.6-stable-bc0d134-20180605

[bellaj]

Thanks @vbaranov
would you please explain what are max_bytes and keep parameters?
I presume it's max size (Gb) and how many days to keep the log, right?

One more thing, the file who is growing quickly is error.log not explorer.log

[ayrat555]

there is an issue https://github.com/paritytech/parity-ethereum/issues/8725 that was fixed in v2.0.0. I believe it's causing your issue

[vbaranov]

@bellaj

I presume it's max size (Gb) and how many days to keep the log, right?

No, this is the size of each file in bytes and the maximum number of files to keep.

Logs rotation was introduced here https://github.com/poanetwork/blockscout/pull/958

Editing the logger backends to do file rotation every 50mb and keep
the last 19 log files per logger backend. 50mb * 20 = ~1gb