Tally doesn't log into system.log

[Aar]

Just to be on the safe side?
I have installed the latest stable Direct Admin version. Could it be correct that the DA tally is no longer working properly, or is being logged?

I noticed that the system.log is empty:

grep -F "Tally All Complete" /var/log/directadmin/system.log

In DirectAdmin itself, I also see an empty file under Log Viewer -> /var/log/directadmin/system.log.

That can't be right, can it? It should show something like this, shouldn't it?

2026:10:25-00:10:05: Tally User admin Start
2026:10:25-00:10:10: Tally User admin Complete
2026:10:25-00:10:10: Tally All Complete
2026:10:25-00:10:50: httpd reloaded

What I know so far:

- The cron job is present and schedules the tally for 00:10.
- restart_apache_after_tally=1 is set.
- According to the journal, Apache was reloaded at 00:18:37.
- system.log is empty and therefore contains no tally registration.

I've tried this:, the files are empty

[root@server admin]# ls -lah --full-time /var/log/directadmin/system.log /var/log/directadmin/errortaskq.log

-rw-r--r-- 1 diradmin diradmin 0 2026-10-25 03:14:02.434106564 +0100 /var/log/directadmin/errortaskq.log
-rw-r--r-- 1 diradmin diradmin 0 2026-10-25 03:14:02.434106564 +0100 /var/log/directadmin/system.log

But the file is empty?
How come?

I'm a step closer.....
The tally of last night has been been rotated to /var/log/directadmin/system.log-20261025? But why?

[root@web01 admin]# grep -iE 'system\.log|error\.log|errortaskq\.log|security\.log|login\.log' /var/lib/logrotate/logrotate.status
"/var/log/directadmin/error.log" 2026-10-25-3:14:2
"/var/log/directadmin/errortaskq.log" 2026-10-25-3:14:2
"/var/log/directadmin/security.log" 2026-10-25-3:14:2
"/var/log/directadmin/login.log" 2026-10-25-3:14:2
"/var/log/directadmin/system.log" 2026-10-25-3:14:2

The behaviour looks not right? Or is the daylight saving time the cause?

 

[Aar]

The log is now being working correctly, without anything having been changed in the sourcecode:
After adding a subdomain and a mail-setting, i can be relieved.

2026:10:25-13:20:57: named reloaded
2026:10:25-13:41:58: named reloaded
2026:10:25-13:41:59: httpd reloaded
2026:10:25-13:41:59: php-fpm74 reloaded
2026:10:25-13:41:59: php-fpm84 reloaded

But it is strange that the log from last night was already rotated that night?
How is this possible? Am I seeing things, or is this behavior normal?

 

[Aar]

A new day, a new check...

And the rotate seems to be working perfectly now.
I can now see the logs from last night in system.log.

It is strange that they were rotated yesterday night already. Could it have something to do with the switch to winter time after all?

Perhaps someone can tell me if this theory could be correct on a standard Direct Admin machine?
And maybe i have found a small, small bug.

 

[Ohm J]

maybe it's timezone incorrect. Midnight will depending on the timezone, not force strict to UTC by application/cron itself