Log names in /home/*/access-logs/* witch extention .log

[Widmo]

In /home/user/access-logs i have logs.

root@vi [/home/user/access-logs]# ls -l
-rw-r----- 1 root user 0 Jan 20 14:01 index.user.anonimandia.pl
-rw-r----- 1 root user 0 Jan 20 14:01 ns6.user.anonimandia.biz
-rw-r----- 1 root user 0 Jan 20 14:01 plix2.user.anonimandia.org
-rw-r----- 1 root user 0 Jan 20 14:01 user-pl.user.anonimandia.com.pl
-rw-r----- 1 root user 0 Jan 20 14:01 user.anonimandia.eu

Then i need to rotate them.

So create:

root@vi [/home/user/access-logs]# cat /etc/logrotate.d/logs-user
/home/user/access-logs/* {
create
missingok
rotate 4
compress
weekly
}

and then i have horrible loop looking like tree .
every log.gz is compressed many, many time:

access-logs/user/3ff.pl.3
access-logs/user/3ff.user.anonimandia.pl
access-logs/user/3ff.user.anonimandia.pl.1.gz
access-logs/user/3ff.user.anonimandia.pl.1.gz.1.gz
access-logs/user/3ff.user.anonimandia.pl.1.gz.1.gz.1.gz
access-logs/user/3ff.user.anonimandia.pl.1.gz.1.gz.1.gz.1.gz
access-logs/user/3ff.user.anonimandia.pl.1.gz.1.gz.1.gz.1.gz.1.gz
access-logs/user/3ff.user.anonimandia.pl.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz
access-logs/user/3ff.user.anonimandia.pl.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz
access-logs/user/3ff.user.anonimandia.pl.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz
access-logs/user/3ff.user.anonimandia.pl.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz
access-logs/user/3ff.user.anonimandia.pl.1.gz.2.gz
access-logs/user/3ff.user.anonimandia.pl.2.gz
access-logs/user/3ff.user.anonimandia.pl.3.1
access-logs/user/bgt.user.biz
access-logs/user/bgt.user.biz.1.gz
access-logs/user/bgt.user.biz.1.gz.1.gz
access-logs/user/bgt.user.biz.1.gz.1.gz.1.gz
access-logs/user/bgt.user.biz.1.gz.1.gz.1.gz.1.gz
access-logs/user/bgt.user.biz.1.gz.1.gz.1.gz.1.gz.1.gz
access-logs/user/bgt.user.biz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz
access-logs/user/bgt.user.biz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz
access-logs/user/bgt.user.biz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz
access-logs/user/bgt.user.biz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz
access-logs/user/bgt.user.biz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz
access-logs/user/bgt.user.biz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz

Most of them are empty.

It happend, becouse

/etc/logrotate.d/logs-user

contain:

/home/user/access-logs/*

but should be:

/home/user/access-logs/*.log ( or exclude .gz )

It can't be changed manually, or from template becouse stats is generating from hardcoded names.

It would be perfect - if the name of logs have uniqe postfix.

[Infopro]

In WHM > Service Configuration > cPanel Log Rotation Configuration, is where you would enable Log Rotation for access_logs.

Files from /usr/local/cpanel/logs selected below will be rotated based upon their size. The rotated files will be compressed and stored in /usr/local/cpanel/logs/archive/. The files are named to include the month in which they are rotated. Consequently, the file names do not relate in any way to the content of the file being rotated. Files are only rotated when they grow larger than the WHM >> Tweak Settings >> Log Rotation Size Threshold or the default of 300MB. The archived log files are left in place indefinitely. Files not chosen here will not ever be rotated by cPanel software.

[cPanelBrianO]

Be aware that /home/$user/access-logs is a symlink to /usr/local/apache/domlogs/$user/

Accordingly, these logs are already automatically maintained by cpanellogd and rotated along with Web Statistics generation. If you are independently rotating these (like you're attempting to do) you stand to lose web stats information and cause other unexpected problems. This would be because you would be prematurely rotating logs outside of cPanel's expectations. Accordingly, I cannot recommend that you proceed with your current actions.

As advised by Infopro, please utilize cPanel & WHM provided log rotation mechanisms to rotate these as desired.

Just like Infopro has posted:

WHM -> Tweak Settings
Log rotation size threshold

and the other various log configurations under that "Stats and Logs" tab. Those would be what you're looking for.

Again, I cannot recommend pursuing the actions you're looking at since you would effectively be introducing two independent log rotation mechanisms and result in expected behavior, lost statistics, etc.

[Widmo]

True, and I know this options, but it is always last 300 MB.

But i thing better idea is store last X month / weeks / days.

Thank You for help

[cPanelBrianO]

If you're looking to archive logs, then that's an entirely different concept from the rotate option in Tweak Settings.

Please see: Raw Access Logs

Per that documentation, you can check the box:
Archive logs in your home directory at the end of each stats run

and archive domain logs for an account at /home/$user/logs/ after each statistics run. They will be in month-by-month archives stored as:

/home/$user/logs/$domain-Month-Year.gz

example:
/home/brian/logs/mysite.com-Jan-2012.gz

Note that the interval at which these log archives are updated is the same interval that you have set in "WHM -> Statistics Software Configuration" for Log Processing Frequency.

[Widmo]

Thank You