ElasticSearch log size

[squares-ui]

Locally the box has had issues due to log size of elastic

Accessing WebUI gives a 500

{"error":{"code":500,"status":"Internal Server Error","message":"sqlite create: unable to open database file: no such file or directory"}}
Looking at the disc

# df -h
Filesystem               Size  Used Avail Use% Mounted on
devtmpfs                  12G     0   12G   0% /dev
tmpfs                     12G  340K   12G   1% /dev/shm
tmpfs                     12G  122M   12G   2% /run
tmpfs                     12G     0   12G   0% /sys/fs/cgroup
/dev/mapper/system-root   65G   65G   20K 100% /
/dev/sda2                497M  191M  306M  39% /boot
/dev/mapper/system-nsm   126G   19G  107G  15% /nsm
/dev/mapper/system-tmp   2.0G   33M  2.0G   2% /tmp

Looks like "/" is full

# pwd
/opt/so/log/elasticsearch

# ls -lasht
total 50G
620K -rw-rw-r--.  1 elasticsearch elasticsearch 616K Mar 29 13:07 so2.log
4.0K drwxr-xr-x.  2 elasticsearch socore        4.0K Mar 29 12:58 .
 12G -rw-rw-r--.  1 elasticsearch elasticsearch  12G Mar 28 23:59 so2-2021-03-28.log
 34M -rw-rw-r--.  1 elasticsearch elasticsearch  34M Mar 27 23:59 so2-2021-03-27.log
112M -rw-rw-r--.  1 elasticsearch elasticsearch 112M Mar 26 23:59 so2-2021-03-26.log
 35M -rw-rw-r--.  1 elasticsearch elasticsearch  35M Mar 25 23:59 so2-2021-03-25.log
5.4G -rw-rw-r--.  1 elasticsearch elasticsearch 5.4G Mar 24 23:59 so2-2021-03-24.log
 18G -rw-rw-r--.  1 elasticsearch elasticsearch  18G Mar 23 23:59 so2-2021-03-23.log
 35M -rw-rw-r--.  1 elasticsearch elasticsearch  35M Mar 22 23:59 so2-2021-03-22.log
 33M -rw-rw-r--.  1 elasticsearch elasticsearch  33M Mar 21 23:59 so2-2021-03-21.log
 33M -rw-rw-r--.  1 elasticsearch elasticsearch  33M Mar 20 23:59 so2-2021-03-20.log
 34M -rw-rw-r--.  1 elasticsearch elasticsearch  34M Mar 19 23:59 so2-2021-03-19.log
 33M -rw-rw-r--.  1 elasticsearch elasticsearch  33M Mar 18 23:59 so2-2021-03-18.log
2.1G -rw-rw-r--.  1 elasticsearch elasticsearch 2.1G Mar 17 23:59 so2-2021-03-17.log
1.1G -rw-rw-r--.  1 elasticsearch elasticsearch 1.1G Mar 16 23:59 so2-2021-03-16.log
 24M -rw-rw-r--.  1 elasticsearch elasticsearch  24M Mar 14 17:22 so2-2021-03-14.log
2.8G -rw-rw-r--.  1 elasticsearch elasticsearch 2.8G Mar 13 23:59 so2-2021-03-13.log
7.9G -rw-rw-r--.  1 elasticsearch elasticsearch 7.9G Mar 12 23:59 so2-2021-03-12.log
 35M -rw-rw-r--.  1 elasticsearch elasticsearch  35M Mar 11 23:59 so2-2021-03-11.log
 96M -rw-rw-r--.  1 elasticsearch elasticsearch  96M Mar 10 23:59 so2-2021-03-10.log
239M -rw-rw-r--.  1 elasticsearch elasticsearch 239M Mar  9 23:59 so2-2021-03-09.log
334M -rw-rw-r--.  1 elasticsearch elasticsearch 334M Mar  8 23:59 so2-2021-03-08.log
 29M -rw-rw-r--.  1 elasticsearch elasticsearch  29M Mar  7 23:59 so2-2021-03-07.log

50GB of logs from ElasticSearch (majority was DEPRACTED), I feel that even with a bigger disk on install this would still fill up lol

Can you consider log rotation/compression/clean up please

Many thanks
Andy

[squares-ui]

Looks like unhappy hardware, it created another 50GB log in a few hours, maybe rotation wouldn't help that lol

[root@so2 elasticsearch]# head -n 1 so2.log
[2021-03-29T14:21:36,624][INFO ][org.elasticsearch.node.Node] version[7.10.2], pid[7], build[oss/docker/747e1cc71def077253878a59143c1f785afa92b9/2021-01-13T00:42:12.435326Z], OS[Linux/3.10.0-1160.21.1.el7.x86_64/amd64], JVM[AdoptOpenJDK/OpenJDK 64-Bit Server VM/15.0.1/15.0.1+9]
[root@so2 elasticsearch]# tail -n 1 so2.log
[2021-03-29T20:36:37,086][DEPRECATION][org.elasticsearch.deprecation.script.JodaCompatibleZonedDateTime] The return typ[root@so2 elasticsearch]#
[root@so2 elasticsearch]#
[root@so2 elasticsearch]# ls -lth
total 50G
-rw-rw-r--. 1 elasticsearch elasticsearch 50G Mar 29 21:58 so2.log

Ignore/close/delete