problem with apache "yesterday" access logs

Discussion in 'ISPConfig 3 Priority Support' started by RubenG, Jan 28, 2021.

  1. RubenG

    RubenG New Member HowtoForge Supporter

    Hello
    I had a ISPconfig server, on version 3.1.14p2 . (Yes I must upgrade it, I'm migrating before the more critical apps to a new 3.2.2 server )
    Http access log for actual day is correct, but cron job fail to copy/create to yesterday , lefting it at 0 bytes and previous logs when gzipped left to 40 bytes.
    I have readed in this forum that in version 3 there are not any yesterday-access.log file, but I have it.
    This occurs in every http site/instance.
    Note that access.log is not linked with the current date 20210128-access.log
    Server is CENTOS 7, with apache. PHP CLI 5.4.16.
    I'm unable to see what is wrong here.
    Today is 28 Jan 2021.
    Code:
    # ls -l /var/www/clients/client4/web126/log
    total 808
    -rw-r--r-- 1 root root     40 ene 18 00:17 20210116-access.log.gz
    -rw-r--r-- 1 root root     40 ene 19 00:17 20210117-access.log.gz
    -rw-r--r-- 1 root root     40 ene 20 00:18 20210118-access.log.gz
    -rw-r--r-- 1 root root     40 ene 21 00:17 20210119-access.log.gz
    -rw-r--r-- 1 root root     40 ene 22 00:18 20210120-access.log.gz
    -rw-r--r-- 1 root root     40 ene 23 00:18 20210121-access.log.gz
    -rw-r--r-- 1 root root     40 ene 24 00:17 20210122-access.log.gz
    -rw-r--r-- 1 root root     40 ene 25 00:17 20210123-access.log.gz
    -rw-r--r-- 1 root root     40 ene 26 00:18 20210124-access.log.gz
    -rw-r--r-- 1 root root     40 ene 27 00:18 20210125-access.log.gz
    -rw-r--r-- 1 root root     40 ene 28 00:17 20210126-access.log.gz
    -rw-r--r-- 1 root root      0 ene 27 00:00 20210127-access.log
    -rw-r--r-- 1 root root 693227 ene 28 21:59 20210128-access.log
    -rw-r--r-- 1 root root      0 ene 28 00:00 access.log
    -rw-r--r-- 1 root root  38273 ene 28 21:42 error.log
    -rw-r--r-- 1 root root   3155 ene 19 00:17 error.log.10.gz
    -rw-r--r-- 1 root root   2729 ene 18 00:17 error.log.11.gz
    -rw-r--r-- 1 root root   3315 ene 28 00:17 error.log.1.gz
    -rw-r--r-- 1 root root   2970 ene 27 00:18 error.log.2.gz
    -rw-r--r-- 1 root root   3683 ene 26 00:18 error.log.3.gz
    -rw-r--r-- 1 root root   2455 ene 25 00:17 error.log.4.gz
    -rw-r--r-- 1 root root   2524 ene 24 00:17 error.log.5.gz
    -rw-r--r-- 1 root root   2962 ene 23 00:18 error.log.6.gz
    -rw-r--r-- 1 root root   3210 ene 22 00:18 error.log.7.gz
    -rw-r--r-- 1 root root   3966 ene 21 00:17 error.log.8.gz
    -rw-r--r-- 1 root root   3351 ene 20 00:18 error.log.9.gz
    lrwxrwxrwx 1 root root     55 ene 28 00:15 yesterday-access.log -> /var/www/clients/client4/web126/log/20210127-access.log
     
    Last edited: Jan 28, 2021
  2. Jesse Norell

    Jesse Norell ISPConfig Developer Staff Member ISPConfig Developer

    Checking a random site on a 3.2.2 server, I do not see this:
    Code:
    -rw-r--r-- 1 root root  44330 Jan 18 00:12 20210116-access.log.gz
    -rw-r--r-- 1 root root  47169 Jan 19 00:12 20210117-access.log.gz
    -rw-r--r-- 1 root root  41518 Jan 20 00:12 20210118-access.log.gz
    -rw-r--r-- 1 root root  55786 Jan 21 00:11 20210119-access.log.gz
    -rw-r--r-- 1 root root  45229 Jan 22 00:11 20210120-access.log.gz
    -rw-r--r-- 1 root root  43870 Jan 23 00:11 20210121-access.log.gz
    -rw-r--r-- 1 root root  48131 Jan 24 00:10 20210122-access.log.gz
    -rw-r--r-- 1 root root  49573 Jan 25 00:10 20210123-access.log.gz
    -rw-r--r-- 1 root root  48385 Jan 26 00:12 20210124-access.log.gz
    -rw-r--r-- 1 root root  52009 Jan 27 00:11 20210125-access.log.gz
    -rw-r--r-- 1 root root  61665 Jan 28 00:11 20210126-access.log.gz
    -rw-r--r-- 1 root root 408642 Jan 27 23:58 20210127-access.log
    -rw-r--r-- 1 root root 388189 Jan 28 14:45 20210128-access.log
    lrwxrwxrwx 1 root root     19 Jan 28 00:05 access.log -> 20210128-access.log
    -rw-r--r-- 1 root root  90484 Jan 28 14:45 error.log
    -rw-r--r-- 1 root root   6648 Jan 19 00:12 error.log.10.gz
    -rw-r--r-- 1 root root   9226 Jan 18 00:12 error.log.11.gz
    -rw-r--r-- 1 root root   9632 Jan 28 00:11 error.log.1.gz
    -rw-r--r-- 1 root root  13783 Jan 27 00:11 error.log.2.gz
    -rw-r--r-- 1 root root  12801 Jan 26 00:12 error.log.3.gz
    -rw-r--r-- 1 root root   7980 Jan 25 00:10 error.log.4.gz
    -rw-r--r-- 1 root root   9056 Jan 24 00:10 error.log.5.gz
    -rw-r--r-- 1 root root   9267 Jan 23 00:11 error.log.6.gz
    -rw-r--r-- 1 root root   8814 Jan 22 00:11 error.log.7.gz
    -rw-r--r-- 1 root root   7469 Jan 21 00:11 error.log.8.gz
    -rw-r--r-- 1 root root  10690 Jan 20 00:12 error.log.9.gz
    lrwxrwxrwx 1 root root     53 Jan 28 00:06 yesterday-access.log -> /var/www/clients/client6/web6/log/20210127-access.log
    
    My guess is upgrading/migrating would fix it. Perhaps you could track down a specific bugfix between your version and current to apply to your server if you can't simply upgrade.
     
  3. till

    till Super Moderator Staff Member ISPConfig Developer

    My guess is that either there is no traffic on that site, as the link is created by vlogger when the log is written, or you must delete that file as it might be that vlogger can't recreate the symlink if there is a file in place with the same name. Regarding gt files, have not seen that yet on any system.
     
  4. RubenG

    RubenG New Member HowtoForge Supporter

    SOLVED.
    A previous sysadmin here had enabled the ngnix log script on crontab, and this is a apache server.:mad:
    Just commented it two days ago and now is running fine.
    #0 0 * * * /usr/local/ispconfig/server/scripts/create_daily_nginx_access_logs.sh &> /dev/null
     
    till likes this.

Share This Page