There seems to be 4 user cron log files rotated in folder private every night, where three of them are empty: How is this managed?
You do not bother to mention what operating system is involved. What directory exactly? So hard to say. My guess is it is logrotate that makes those gzipped logfiles, read man logrotate It should make only one copy per day, so it is indeed strange to have 4. Perhaps logrotate is somehow started four times, when it should only run once.
Well, I did bother. The signature says Debian. The text said "folder private". This is logrotate of the users cron files, that resides in their private directory. I don't believe they are managed by logrotate, but have not checked that. This user has 4 cron jobs, I supspect there could be a bug.
No, I can't see they are managed by logrotate, as I originally did not believe as well, hence I asked here.
The only thing I found so far, this sql statement Code: $sql = "SELECT domain_id, domain, type, document_root, web_folder, parent_domain_id, log_retention FROM web_domain WHERE (type = 'vhost' or type = 'vhostsubdomain ' or type = 'vhostalias') AND server_id = ?"; will return the same document_root several times if there are vhostaliases and/or vhostsubdomains, and hence rotation of Code: $cron_logfiles = array('cron.log', 'cron_error.log', 'cron_wget.log'); foreach($cron_logfiles as $cron_logfile) { $cron_logfile = $rec['document_root'].'/private/' . $cron_logfile; // rename older files (move up by one) . . will be done several times. However, this is not the case for me, my example does only have one vhost, nothing else, hence it does not explain the multiple log rotations for me. Guess I will have to put in some debug code and see what happens during the nights.
Hm, it turned out this is the bug that causes multiple log rotations for me. My domain did have three "vhostsubdomain" on top of the "vhost", that is four and hence the cron files have been rotated four times. Thanks for your time and attention
Ah, yes. You are right. Please open a bug report (with the template Bug report) on https://git.ispconfig.org/ispconfig/ispconfig3/-/issues