Hello there,
Suddenly i saw “error establishing database connection” and after examining log files i realised the directory :
/var/lib/docker/volumes/global-db_db_logs/_data
was full with MariaDB logs.
How can i disable logging?
On the previous easy engine v3 i had to comment out “bin_log” on /etc/mysql/my.cnf
How can i do it on V4 ?
Have you tried commenting out log_bin in /var/lib/docker/volumes/global-db_db_conf/_data/conf.d/ee.cnf?
It Worked!
thanks a lot!
hello, my mariadb-bin.000XXX still there. How to purge it
I have same problem here, diskspace is full and the server is down
I have commented log_bin in ee.cnf
but don’t know how to clean the log
Filesystem Size Used Avail Use% Mounted on
udev 479M 0 479M 0% /dev
tmpfs 100M 9.8M 90M 10% /run
/dev/vda1 14G 14G 0 100% /
tmpfs 497M 0 497M 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 497M 0 497M 0% /sys/fs/cgroup
cgmfs 100K 0 100K 0% /run/cgmanager/fs
tmpfs 100M 0 100M 0% /run/user/0
overlay 14G 14G 0 100% /var/lib/docker/overlay2/6147a4aa23009786869454eddc47481cd7fc2a41fd4c3804cda78be824d8f078/merged
overlay 14G 14G 0 100% /var/lib/docker/overlay2/efd432ddd3085306d3e5177a2922487bfb3ab0ebebb6c7302fc4caab20d7bb9e/merged
overlay 14G 14G 0 100% /var/lib/docker/overlay2/33ebb05181a0c5df05c7d7f61c3f80c63ca0b27de30486d40b7f614d26b6c221/merged
overlay 14G 14G 0 100% /var/lib/docker/overlay2/4b3691fd3e2a1d1ec99008ebf603c224599c737b029d4a5906b82ca1a07b3903/merged
overlay 14G 14G 0 100% /var/lib/docker/overlay2/d4990edf80fe512c76aee38f31c3ffce26de675e3439619fbeefb4877f8d51b3/merged
overlay 14G 14G 0 100% /var/lib/docker/overlay2/f2306a90c07c8cd9afc76e6df30282ba199d43140eee41ee027fd9052b4c08e1/merged
overlay 14G 14G 0 100% /var/lib/docker/overlay2/50cfc1b8bda4e26cdb6236b62e6080922722ceabae9c6dd7d6faefac4a140f2c/merged
overlay 14G 14G 0 100% /var/lib/docker/overlay2/4692951d0d348bc748c8648bf950ac685663e9057d05ce028964964fec05cb19/merged
shm 64M 0 64M 0% /var/lib/docker/containers/95d8850e31cd121dd179123ab28a368c9f90131d7185329350f520df75f1b6f8/mounts/shm
shm 64M 0 64M 0% /var/lib/docker/containers/58ece303d210abd2dab9de32a1708d31ea3571594ffa4f15e8a96c784afc1845/mounts/shm
shm 64M 0 64M 0% /var/lib/docker/containers/de2281502e3b7c836a3bbbe5f5b1faea2ed84d3fd7128252bf28a0ece26e0ef3/mounts/shm
shm 64M 0 64M 0% /var/lib/docker/containers/bfc2196e404d035fd0e7e2452ada99772bb00327ed6645d31a01e53608286899/mounts/shm
shm 64M 0 64M 0% /var/lib/docker/containers/51078df1d2db45e2910106b5e36715bcb821947d1cd9bad4b831b90d4673f22c/mounts/shm
shm 64M 0 64M 0% /var/lib/docker/containers/bd0d015d047bf600d48a1a714adbc7717c6b78ce6334bdf4c6a4fddfcb19a534/mounts/shm
shm 64M 0 64M 0% /var/lib/docker/containers/2eaf41470587ac5683226f249f87b834620006fcf2355a546044ec93c43db4ee/mounts/shm
shm 64M 0 64M 0% /var/lib/docker/containers/6f6970ac86c64f2cb82b33530c201a6cfe81a6e5beaa4d50cf1a3236de894caa/mounts/shm
Have you installed W3 Total Cache?
I solve this problem when turn that plugin off.
i uninstall the w3 total cache same problem