Production log file size

Using Ghost
1

The production log file has reached a size of almost 5gb, is this normal or is there something wrong?

Older production log files are considerably smaller.

Such a large file is difficult to manage

Cattura

1 Like
2

Have you verified that your log file rotation is set up correctly and working? What date range does the log cover?

Large log files would be considered normal if rotation is not configured/running.

3

this is the date in the first line of the file time":"2020-06-03T00:00:15.288Z

I have not changed anything in the server, definitely not from this date on, theoretically everything should be configured the same way as when I started, I have not changed much in the server except something in terms of firewall and security

I’m not sure if I should check the logorate tool, but the content looks correct:

# see "man logrotate" for details
# rotate log files weekly
weekly

# use the syslog group by default, since this is the owning group
# of /var/log/syslog.
su root syslog

# keep 4 weeks worth of backlogs
rotate 4

# create new (empty) log files after rotating old ones
create

# uncomment this if you want your log files compressed
#compress

# packages drop log rotation information into this directory
include /etc/logrotate.d

# no packages own wtmp, or btmp -- we'll rotate them here
/var/log/wtmp {
    missingok
    monthly
    create 0664 root utmp
    rotate 1
}

/var/log/btmp {
    missingok
    monthly
    create 0660 root utmp
    rotate 1
}

# system-specific logs may be configured here
4

You don’t have anything in the shared part of your log rotate config for your Ghost logs. Did you set up log rotation previously?

5

Actually it’s the first time I open this file, I’ve never changed anything, the weird thing is that looking at the previous log files everything worked normally.

I repeat that I have never changed any configuration at the server level, so I don’t know how to explain it. Other than updating what Ghost requested, I haven’t changed anything on the server for at least 1 year.

Should I add something to this logorate config file?

6

any idea how to fix it ?

i installed ghost on a freshly formatted server, this is the contents of logorate.conf:

GNU nano 4.8                                                                        
# see "man logrotate" for details
# rotate log files weekly
weekly

# use the adm group by default, since this is the owning group
# of /var/log/syslog.
su root adm

# keep 4 weeks worth of backlogs
rotate 4

# create new (empty) log files after rotating old ones
create

# use date as a suffix of the rotated file
#dateext

# uncomment this if you want your log files compressed
#compress

# packages drop log rotation information into this directory
include /etc/logrotate.d

# system-specific logs may be also be configured here.
7

You need to add config for any log files that you care about rotating. This isn’t Ghost-specific so any docs or tutorials for logrotate will help, eg:

8

Thanks for the clarification, considering that initially the log management system worked correctly I assumed that I had created some problems with the normal configuration of Ghost.

So by default, on a clean system with Ubuntu 18.04 and 20.04, the log file keeps growing as it is happening to me without being automatically split into different zipped files.