$ kubectl logs -n observability clickhouse-logs-0 -c

clickhouse -f
Poco::Exception. Code: 1000, e.code() = 0, e.displayText() = Not found: logger.log (version 20.5.3.27 (official build))
dirname: missing operand
Try 'dirname --help' for more information.
Poco::Exception. Code: 1000, e.code() = 0, e.displayText() = Not found: logger.errorlog (version 20.5.3.27 (official build))
dirname: missing operand
Try 'dirname --help' for more information.
Processing configuration file '/etc/clickhouse-server/config.xml'.
Merging configuration file '/etc/clickhouse-server/config.d/docker_related_config.xml'.
Include not found: clickhouse_compression
Logging information to console
2020.09.21 07:00:48.502648 [ 34 ] {} <Information> : Starting ClickHouse 20.5.3.27 with revision 54435, build id: 5820B4CE93C60E3C, PID 34
2020.09.21 07:00:48.504722 [ 34 ] {} <Information> Application: starting up
2020.09.21 07:00:48.509153 [ 34 ] {} <Information> Application: It looks like the process has no CAP_IPC_LOCK capability, binary mlock will be disabled. It could happen due to incorrect ClickHouse package installation. You could resolve the problem manually with 'sudo setcap cap_ipc_lock=+ep /usr/bin/clickhouse'. Note that it will not work on 'nosuid' mounted filesystems.
2020.09.21 07:00:48.509968 [ 34 ] {} <Information> StatusFile: Status file /var/lib/clickhouse/status already exists - unclean restart. Contents:
PID: 34
Started at: 2020-09-21 06:59:28
Revision: 54435
Include not found: networks
2020.09.21 07:00:48.513564 [ 34 ] {} <Information> Application: Setting max_server_memory_usage was set to 27.57 GiB
2020.09.21 07:00:48.513577 [ 34 ] {} <Information> Application: Loading metadata from /var/lib/clickhouse/
2020.09.21 07:00:48.515749 [ 34 ] {} <Information> DatabaseOrdinary (system): Total 7 tables and 0 dictionaries.
2020.09.21 07:00:48.516635 [ 46 ] {} <Information> BackgroundProcessingPool: Create BackgroundProcessingPool with 16 threads
2020.09.21 07:00:48.644432 [ 34 ] {} <Information> DatabaseOrdinary (system): Starting up tables.
2020.09.21 07:00:48.646641 [ 34 ] {} <Information> DatabaseOrdinary (default): Total 0 tables and 0 dictionaries.
2020.09.21 07:00:48.646658 [ 34 ] {} <Information> DatabaseOrdinary (default): Starting up tables.
2020.09.21 07:00:48.651629 [ 34 ] {} <Information> DatabaseOrdinary (logs): Total 19 tables and 0 dictionaries.
2020.09.21 07:00:53.693814 [ 68 ] {} <Information> DatabaseOrdinary (logs): 73.6842105263158%
ClickHouse init process failed.
подскажите пожалуйста почему не может стартануть (обычный рестарт)?

grep -r logger /etc/clickhouse-server поглядите посмотрите что там написано, выглядит как какие то косяки в конфиге такое ощущение что пытались логирование перенастроить или ссылается кто-то в /metadata/*/*.sql на таблицы которые не существуют вообще лучше глянуть в /var/log/clickhouse/clickhouse-server.err.log только PV для /var/log/clickhouse/ сделайте

конфиг не меняли, с ним он и работал, я перенаправляю все в stdout/stderr: <logger> <level>information</level> <console>1</console> </logger> включил debug: 2020.09.21 07:09:41.819732 [ 75 ] {} <Debug> logs.envoy: Loading mutation: mutation_237046.txt entry, commands size: 1 2020.09.21 07:09:41.821255 [ 75 ] {} <Debug> logs.envoy: Loading mutation: mutation_654399.txt entry, commands size: 1 2020.09.21 07:09:41.822902 [ 75 ] {} <Debug> logs.envoy: Loading mutation: mutation_1060891.txt entry, commands size: 1 2020.09.21 07:09:41.824608 [ 75 ] {} <Debug> logs.envoy: Loading mutation: mutation_113951.txt entry, commands size: 1 ClickHouse init process failed. dmitry.vasiliev@production-kubeops-1:~$