Logrotate and seafevents.log

Seafile Server
1

Is there any secret if it comes to log rotation for seafevents.log on a recent Pro server?

It seems to be the only log file, which is not jumping to the new log:

-rw-rw-r-- 1 seafile seafile 0 Aug 6 06:25 seafevents.log
-rw-rw-r-- 1 seafile seafile 160635 Aug 7 09:38 seafevents.log.1
-rw-rw-r-- 1 seafile seafile 0 Aug 4 06:25 seafevents.log.2019-07-30

Here’s the part from the logrotate config. Obviously, a new log file is created but Seafile keeps writing to the old one.

/home/seafile/logs/seafevents.log
{
daily
missingok
rotate 24
compress
delaycompress
notifempty
sharedscripts
}

Thanks!

2

push

I still don’t get seafevent.log and seahub.log properly rotated. So what should I do here?
index.log is a new one introduced with 7.1.x?

-rw-rw-r--  1 seafile seafile     100 Apr  7 07:19 ccnet.log
-rw-rw-r--  1 seafile seafile    1350 Apr  7 06:04 ccnet.log.1
-rw-rw-r--  1 seafile seafile     156 Apr  6 06:04 ccnet.log.2.gz
-rw-rw-r--  1 seafile seafile     161 Apr  5 06:04 ccnet.log.3.gz
-rw-rw-r--  1 seafile seafile     204 Apr  4 06:04 ccnet.log.4.gz
-rw-rw-r--  1 seafile seafile     162 Apr  3 06:04 ccnet.log.5.gz
-rw-rw-r--  1 seafile seafile     460 Apr  2 06:04 ccnet.log.6.gz
-rw-rw-r--  1 seafile seafile       0 Apr  2 06:25 controller.log
-rw-rw-r--  1 seafile seafile    4842 Apr  1 23:04 controller.log.1
-rw-rw-r--  1 seafile seafile       0 Apr  1 22:33 elasticsearch_deprecation.log
-rw-rw-r--  1 seafile seafile       0 Apr  1 22:33 elasticsearch_index_indexing_slowlog.log
-rw-rw-r--  1 seafile seafile       0 Apr  1 22:33 elasticsearch_index_search_slowlog.log
-rw-rw-r--  1 seafile seafile    8590 Apr  1 23:04 elasticsearch.log
-rw-rw-r--  1 seafile seafile  666675 Apr  7 07:48 file_updates_sender.log
-rw-rw-r--  1 seafile seafile 1077300 Apr  5 06:24 file_updates_sender.log.1
-rw-rw-r--  1 seafile seafile  149882 Apr  7 06:34 index.log
-rw-rw-r--  1 seafile seafile    5783 Apr  3 15:38 seafdav.log
-rw-rw-r--  1 seafile seafile       0 Apr  7 06:25 seafevents.log
-rw-rw-r--  1 seafile seafile    7789 Apr  7 07:44 seafevents.log.1
-rw-rw-r--  1 seafile seafile       0 Apr  2 06:25 seafevents.log.2020-03-31
-rw-rw-r--  1 seafile seafile   15914 Apr  6 23:04 seafevents.log.2.gz
-rw-rw-r--  1 seafile seafile      75 Apr  7 07:04 seafile.log
-rw-rw-r--  1 seafile seafile    1800 Apr  7 06:04 seafile.log.1
-rw-rw-r--  1 seafile seafile     187 Apr  6 06:04 seafile.log.2.gz
-rw-rw-r--  1 seafile seafile     187 Apr  5 06:04 seafile.log.3.gz
-rw-rw-r--  1 seafile seafile     256 Apr  4 06:04 seafile.log.4.gz
-rw-rw-r--  1 seafile seafile     255 Apr  3 06:04 seafile.log.5.gz
-rw-rw-r--  1 seafile seafile     530 Apr  2 06:04 seafile.log.6.gz
-rw-rw-r--  1 seafile seafile    2053 Apr  7 05:04 seahub_email_sender.log
-rw-rw-r--  1 seafile seafile    3329 Apr  5 05:04 seahub_email_sender.log.1
-rw-r--r--  1 seafile seafile       0 Apr  5 06:25 seahub.log
-rw-r--r--  1 seafile seafile  472226 Apr  6 22:56 seahub.log.1
3

@daniel.pan Did you have a look into this problem?

4

seafevents.log will logrotate automatically. You don’t need to config it manually.

5

But obviously it writes to the wrong file, doesn’t it?

seafile@cloud:~/logs$ ll seafevents.log*
-rw-rw-r-- 1 seafile seafile     0 Apr 21 06:25 seafevents.log
-rw-rw-r-- 1 seafile seafile 35291 Apr 22 09:30 seafevents.log.1
-rw-rw-r-- 1 seafile seafile 20419 Apr 20 23:30 seafevents.log.2.gz

Should I delete that part from my logrotate config?