Page 2 of 2 FirstFirst 12
Results 11 to 19 of 19

Thread: spam graph

  1. #11
    phoenix is offline Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,587
    Rep Power
    58

    Default

    What operating system is this? What I suggest you do first is stop Zimbra and kill any runing processes that may be left. When you've done that go to the libexec directory and run (as root) the zmfixperms script the retstart zimbra and try the zmloggerinit again.
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  2. #12
    Join Date
    Mar 2007
    Location
    New England
    Posts
    55
    Rep Power
    8

    Default

    Ubuntu 6.10

    Same problem:


    zimbra@mail:~/libexec$ ./zmloggerinit
    * Creating required directories
    * Creating database in /opt/zimbra/logger/db/data
    * Starting logger_mysql server
    * Loading schema /opt/zimbra/db/loggerdb.sql
    ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/opt/zimbra/logger/db/mysql.sock' (2)
    ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/opt/zimbra/logger/db/mysql.sock' (2)
    * Setting random password for mysql root user in zimbra local config
    * Setting random password for mysql zimbra user in zimbra local config
    * Changing mysql root user password
    /opt/zimbra/logger/mysql/bin/mysqladmin: connect to server at 'localhost' failed
    error: 'Can't connect to local MySQL server through socket '/opt/zimbra/logger/db/mysql.sock' (2)'
    Check that mysqld is running and that the socket: '/opt/zimbra/logger/db/mysql.sock' exists!
    * Changing mysql zimbra user password
    ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/opt/zimbra/logger/db/mysql.sock' (2)
    **** PASSWORD CHANGE FAILED

    Edit: Note: Logger was working until I upgraded to the most recent version.
    Last edited by Cryophallion; 05-03-2007 at 07:44 AM. Reason: background info

  3. #13
    Join Date
    Apr 2007
    Posts
    6
    Rep Power
    8

    Default

    Looks like I jumped the gun too early on the no-data part. This morning came back, check the graphs and they're working fine and dandy!

    I too had that mysql.sock error thingee? but it was because I never killed my mysql process cleanly. Once I did that, I restarted from step 1, remove that db folder, zmloggerinit and presto it worked again for me.

    Thanks anyhow! (this ought to be in the wiki - how to fix non-working graph!)

  4. #14
    Join Date
    Mar 2007
    Location
    New England
    Posts
    55
    Rep Power
    8

    Default

    Does the logger get updated during the install process? I haven't installed the security upgrade yet, but I am wondering if that will reset the logger for me (as the last upgrade is when it stopped working).

    UPDATE: Upgrading to 4.5.5 did the trick. Thanks for your help.
    Last edited by Cryophallion; 05-09-2007 at 09:25 AM. Reason: Fixed

  5. #15
    Join Date
    Jul 2006
    Location
    ireland
    Posts
    388
    Rep Power
    9

    Default

    Quote Originally Posted by scalper View Post
    I have encountered this before..

    My loggerdb went corrupt of somewhat reasons..

    What's the output of zmlogprocess and zmgengraphs commands? any errors in /tmp/logprocess.out and /tmp/logswatch.out

    I have trouble running zmlogprocess.. it claimed my db got errors

    So, if the db is the problem.. you just reinit the db back again..

    % su - zimbra
    % rm -rf logger/db
    % zmloggerinit

    Hope that helps.
    Thanks for the tip,

    I tried this but the spam data is still blank all other tables are ok.
    the zmlogprocess fails to update the amavis logger db table
    lots of FAILED 225901: (07007-10) Blocked SPAM,... messages in /tmp/logprocess.out

  6. #16
    Join Date
    Jul 2006
    Location
    ireland
    Posts
    388
    Rep Power
    9

    Smile UPDATE /opt/zimbra/libexec/zmlogprocess

    updated /opt/zimbra/libexec/zmlogprocess
    processAmavis subroutine wih the following code
    the issue is caused by origIP regex

    Code:
    ###############################################################################
    #UPDATE /opt/zimbra/libexec/zmlogprocess (processAmavis subroutine)
    # to remove FAILED: amavid logger db tables update errors in /tmp/logprogess.out
    #################################################################################
    
    # this is spam with no queued_as
    #e.g. (17580-03) Blocked SPAM, [59.188.231.163] <dwfranzim@franzi.de> -> <john.doe@mail.server.com>, Message-ID: <671718323.59948948578949@franzi.de>, mail_id: kogwtpwxSXDP, Hits: 16.242, 644 ms
    
               elsif ( $msg =~ /\(([^)]+)\) (Passed|Blocked) ([^,]+), (?:LOCAL )?\[([^]]+)\] <([^>]*)> -> (<[^>]+>(?:,<[^>]+>)*),(?: quarantine: [^,]+,)? Message-ID: <([^>]+)>,(?: Resent-Message-ID: <[^>]+>,)? mail_id: \S+, Hits: (\S+), (\d+) ms/)  {
                $pid = $1;
                $disp = $2;
                $reason = $3;
                $fromIP = $4;
                #$origIP = IS UNKNOWN;
                $sender = $5;
                $recips = $6;
                $msgid = $7;
                $hits = $8;
                $ms = $9;
              }
    
    # this is spam with a queued_as
    #e.g.(17580-02) Passed SPAMMY, [84.136.228.166] <alexboguesaid@parlyweb.demon.co.uk> -> <john.doe@mail.server.com>, Message-ID: <000b01c7a39e$641904f0$1402a8c0@p5488e4a6.dip.t-dialin.net>, mail_id: LtRCG1r8djvZ, Hits: 9.636, queued_as: 390A5808C0B8, 368 ms
    
              elsif ( $msg =~ /\(([^)]+)\) (Passed|Blocked) ([^,]+), (?:LOCAL )?\[([^]]+)\] <([^>]*)> -> (<[^>]+>(?:,<[^>]+>)*),(?: quarantine: [^,]+,)? Message-ID: <([^>]+)>,(?: Resent-Message-ID: <[^>]+>,)? mail_id: \S+, Hits: (\S+), queued_as: (\S+), (\d+) ms/)  {
                $pid = $1;
                $disp = $2;
                $reason = $3;
                $fromIP = $4;
                #$origIP = IS UNKNOWN;
                $sender = $5;
                $recips = $6;
                $msgid = $7;
                $hits = $8;
                $queued_as = $9;
                $ms = $10;
              }
    
    # this covers local CLEAN messages with Passed
    #e.g  (05142-10) Passed CLEAN, <john.doe@mail.server.com> -> <jane.doe@mail.server.com>, Message-ID: <1664801169.39531180627w01262.JavaMail.root@mail.server.com>, mail_id: xQKsaZLBiQX8, Hits: -4.399, queued_as: E346B80SC0B8, 606 ms
    
              elsif  ( $msg =~  /\(([^)]+)\) (Passed|Blocked) ([^,]+), <([^>]*)> -> (<[^>]+>(?:,<[^>]+>)*),(?: quarantine: [^,]+,)? Message-ID: <([^>]+)>,(?: Resent-Message-ID: <[^>]+>,)? mail_id: \S+, Hits: (\S+), queued_as: (\S+), (\d+) ms/) {
                $pid = $1;
                $disp = $2;
                $reason = $3;
                $fromIP = $4;
                #$origIP = IS UNKNOWN;
                $sender = $5;
                $recips = $6;
                $msgid = $7;
                $hits = $8;
                $queued_as = $9;
                $ms = $10;
              }
    this has got rig of errors in tmp/logprogess.out hopefully the spam graph will return
    Last edited by padraig; 05-31-2007 at 11:08 AM. Reason: the issue is caused by origIP regex

  7. #17
    Join Date
    Jul 2006
    Location
    ireland
    Posts
    388
    Rep Power
    9

    Default spam graph back

    Excellent my spam GRAPH is back no errors in /tmp/logprocess.out

    NB:: before this fix mysqld was eating CPU aggregating amavis back to the last correct amavis entry!

  8. #18
    Join Date
    Mar 2007
    Location
    New England
    Posts
    55
    Rep Power
    8

    Default Not AGAIN

    So, I updated to 4.5.7 last week. Guess what stopped working again?

    Last time, updating fixed it. So I tried "updating" to 4.5.7 again with my existing 4.5.7 install. Didn't work.

    This seems to break with each new release. Hopefully this won't happen after 5.

  9. #19
    Join Date
    May 2006
    Location
    USA
    Posts
    6,242
    Rep Power
    21

    Default

    If it's just the spam graphs as the title of this thread suggests (and not the entire logger showing as stopped-different bug) it might be Bug 20732 - amavisd update changed log format breaking logger stats

    which has been fixed for :
    4.5.9_GA_1445
    &
    5.0.0_RC2_1603

Similar Threads

  1. Trying to understand Zimbra's anti-spam system
    By TaskMaster in forum Users
    Replies: 11
    Last Post: 01-25-2008, 09:59 AM
  2. av/ spam graph stopped in admin console
    By padraig in forum Administrators
    Replies: 8
    Last Post: 12-04-2007, 06:48 AM
  3. centos 5 zimbra 4.5.6 no statistics
    By rutman286 in forum Installation
    Replies: 9
    Last Post: 08-14-2007, 10:30 AM
  4. Stats don't update
    By Doug_M in forum Administrators
    Replies: 33
    Last Post: 05-05-2007, 09:17 PM
  5. Training spam and ham
    By Justin in forum Developers
    Replies: 2
    Last Post: 10-31-2006, 03:39 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
  •