Results 1 to 9 of 9

Thread: [SOLVED] logrotate issue

  1. #1
    Join Date
    Jun 2008
    Location
    Berkeley, CA
    Posts
    1,474
    Rep Power
    9

    Default [SOLVED] logrotate issue

    After upgrade to 6.0.9 I got this message in admin inbox from the cron daemon:

    Code:
    /etc/cron.daily/logrotate:
    
    error: zimbra:5 unknown user 'USER'
    error: found error in /var/log/zimbra.log , skipping
    error: zimbra:17 unknown user 'USER'
    error: found error in /var/log/zimbra-stats.log , skipping
    Looking in /etc/logrotate.d/zimbra I see the file starts with:

    Code:
    /var/log/zimbra.log {
        daily
        missingok
        notifempty
        create 0644 USER GROUP
        postrotate
          killall -HUP syslogd 2> /dev/null || true
          su - zimbra -c "/opt/zimbra/bin/zmswatchctl restart" > /dev/null 2>&1 || true
        endscript
        compress
    }
    
    /var/log/zimbra-stats.log {
        daily
        missingok
        notifempty
        create 0644 USER GROUP
        postrotate
          killall -HUP syslogd 2> /dev/null || true
          su - zimbra -c "/opt/zimbra/bin/zmlogswatchctl restart" > /dev/null 2>&1 || true
        endscript
        rotate 0
    }
    I think there must have been something wrong with the install(er) that caused "USER GROUP" to appear in lines 5 and 17 instead of "zimbra zimbra". Would someone who has a recent pre-6.0.9 install please post the relevant lines of their /etc/logrotate.d/zimbra?

  2. #2
    Join Date
    Jun 2008
    Location
    Berkeley, CA
    Posts
    1,474
    Rep Power
    9

    Default

    Ah, I see uxbox caught this too: Bug 53584 – logrotate issue

    Would like to be certain of the values that should be there before I go back and manually fix the file.

  3. #3
    Join Date
    Sep 2006
    Location
    477 Congress Street | Portland, ME 04101
    Posts
    1,374
    Rep Power
    11

    Default

    Hi Elliot,

    This is from one of the 6.0.8+P3 servers in our hosting farm (yes, we name our servers after wines...)

    We expect to upgrade to 6.0.9 shortly; this bug is easy to fix manually.

    Hope that helps,
    Mark

    Code:
    malbec:~ # cat /etc/logrotate.d/zimbra
    /var/log/zimbra.log {
        daily
        missingok
        notifempty
        create 0644 zimbra zimbra
        postrotate
          killall -HUP syslog-ng 2> /dev/null || true
          su - zimbra -c "/opt/zimbra/bin/zmswatchctl restart" > /dev/null 2>&1 || true
        endscript
        compress
    }
    
    /var/log/zimbra-stats.log {
        daily
        missingok
        notifempty
        create 0644 zimbra zimbra
        postrotate
          killall -HUP syslog-ng 2> /dev/null || true
          su - zimbra -c "/opt/zimbra/bin/zmlogswatchctl restart" > /dev/null 2>&1 || true
        endscript
        rotate 0
    }
    
    /opt/zimbra/log/myslow.log {
        daily
        missingok
        copytruncate
        rotate 30
        notifempty
        create 0644 zimbra zimbra
        compress
    }
    
    /opt/zimbra/log/logger_myslow.log {
        daily
        missingok
        copytruncate
        notifempty
        create 0660 zimbra zimbra
        compress
        size 5000k
        rotate 7
    } 
    
    /opt/zimbra/log/clamd.log {
        daily
        missingok
        copytruncate
        notifempty
        create 0660 zimbra zimbra
        postrotate
         kill -HUP `cat /opt/zimbra/log/clamd.pid 2> /dev/null` 2> /dev/null || true
        endscript
        compress
        size 5000k
        rotate 7
    }
    
    /opt/zimbra/log/freshclam.log {
        daily
        missingok
        copytruncate
        notifempty
        create 0660 zimbra zimbra
        postrotate
         kill -HUP `cat /opt/zimbra/log/freshclam.pid 2> /dev/null` 2> /dev/null || true
        endscript
        compress
        size 5000k
        rotate 7
    }   
    
    /opt/zimbra/log/zmlogswatch.out {
        daily
        missingok
        copytruncate
        notifempty
        create 0740 zimbra zimbra
        postrotate
          su - zimbra -c "/opt/zimbra/bin/zmlogswatchctl restart" > /dev/null 2>&1 || true
        endscript
        rotate 5
        compress
    }
    
    /opt/zimbra/log/zmswatch.out {
        daily
        missingok
        copytruncate
        notifempty
        create 0740 zimbra zimbra
        postrotate
          su - zimbra -c "/opt/zimbra/bin/zmswatchctl restart" > /dev/null 2>&1 || true
        endscript
        rotate 5
        compress
    }
    
    /opt/zimbra/log/zmmtaconfig.log {
        daily
        missingok
        copytruncate
        notifempty
        create 0740 zimbra zimbra
        postrotate
          su - zimbra -c "/opt/zimbra/bin/zmmtaconfigctl restart" > /dev/null 2>&1 || true
        endscript
        rotate 5
        compress
    }
    
    /opt/zimbra/log/nginx.log /opt/zimbra/log/nginx.access.log {
        daily
        sharedscripts
        missingok
        notifempty
        create 0644 zimbra zimbra
        postrotate
          kill -USR1 `cat /opt/zimbra/log/nginx.pid 2> /dev/null` 2> /dev/null || true
        endscript
        rotate 7
        compress
    }
    
    /opt/zimbra/zmstat/zmstat.out {
        daily
        missingok
        copytruncate
        rotate 7
        notifempty
        compress
    }
    malbec:~ #

  4. #4
    Join Date
    Jun 2008
    Location
    Berkeley, CA
    Posts
    1,474
    Rep Power
    9

  5. #5
    Join Date
    Apr 2009
    Posts
    304
    Rep Power
    6

    Default

    I had this error to after upgrading.

    Thanks.

  6. #6
    Join Date
    Oct 2010
    Posts
    373
    Rep Power
    5

    Default

    Thanks Elliot .. fixed it.

  7. #7
    Join Date
    Apr 2007
    Posts
    32
    Rep Power
    8

    Default

    We've been caught by this too - If someone from Zimbra is listening please could you get it fixed in the next release? (It might have been done in 6.0.10 but isn't in the release notes).

    Thanks,
    Rob

  8. #8
    Join Date
    Oct 2010
    Posts
    373
    Rep Power
    5

    Default

    Quote Originally Posted by robh View Post
    We've been caught by this too - If someone from Zimbra is listening please could you get it fixed in the next release? (It might have been done in 6.0.10 but isn't in the release notes).
    Thanks,
    Rob
    Uxbod has filed a bug, see Elliot's comment above. You can vote for it. I believe they'll patch this up in the next release.

    edit : Sorry it seem they've closed the report so it must be fixed in .10. Forgot It's been a while
    Last edited by fyd; 01-13-2011 at 03:50 AM.

  9. #9
    Join Date
    Sep 2006
    Location
    477 Congress Street | Portland, ME 04101
    Posts
    1,374
    Rep Power
    11

    Default

    None of the 6.0.10 upgrades nor fresh installs we have done have exhibited this bug. I'd say, at least for us, on 64-bit CentOS and SLES10/11, the bug is fixed in 6.0.10.

    Hope that helps,
    Mark

Similar Threads

  1. duplicate email issue
    By kollross in forum Administrators
    Replies: 29
    Last Post: 01-31-2010, 06:43 PM
  2. Backup Size - log size issue?
    By sternfan in forum Administrators
    Replies: 1
    Last Post: 01-03-2008, 08:01 AM
  3. Issue with Print Size in Zimbra Web Client
    By soxfan in forum Administrators
    Replies: 0
    Last Post: 05-11-2007, 01:59 PM
  4. dns issue with suse 10.2 and issue with bind
    By zjustin in forum Installation
    Replies: 11
    Last Post: 05-06-2007, 12:18 PM
  5. Intermittent issue (issue# 5852) ?
    By nick20 in forum Installation
    Replies: 1
    Last Post: 02-08-2006, 02:47 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •