The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

spamassasin problem or not?

Discussion in 'General Discussion' started by PPNSteve, Sep 5, 2010.

  1. PPNSteve

    PPNSteve Well-Known Member

    Joined:
    Mar 13, 2003
    Messages:
    393
    Likes Received:
    1
    Trophy Points:
    18
    Location:
    Somewhere in Ilex Forest
    cPanel Access Level:
    Root Administrator
    Twitter:
    for the last week or so upcp logs have reported:
    Code:
    Updating SpamAssassin rules...Running sa-update (/usr/bin/sa-update).....[12709] dbg: logger: adding facilities: all
    [12709] dbg: logger: logging level is DBG
    [12709] dbg: generic: SpamAssassin version 3.2.4
    [12709] dbg: config: score set 0 chosen.
    [12709] dbg: dns: is Net::DNS::Resolver available? yes
    [12709] dbg: dns: Net::DNS version: 0.66
    [12709] dbg: generic: sa-update version svn607589
    [12709] dbg: generic: using update directory: /var/lib/spamassassin/3.002004
    [12709] dbg: diag: perl platform: 5.008008 linux
    [12709] dbg: diag: module installed: Digest::SHA1, version 2.13
    [12709] dbg: diag: module installed: HTML::Parser, version 3.67
    [12709] dbg: diag: module installed: Net::DNS, version 0.66
    [12709] dbg: diag: module installed: MIME::Base64, version 3.09
    [12709] dbg: diag: module installed: DB_File, version 1.814
    [12709] dbg: diag: module installed: Net::SMTP, version 2.31
    [12709] dbg: diag: module installed: Mail::SPF, version 2.007_001
    [12709] dbg: diag: module installed: Mail::SPF::Query, version 1.999001
    [12709] dbg: diag: module installed: IP::Country::Fast, version 604.001
    [12709] dbg: diag: module not installed: Razor2::Client::Agent ('require' failed)
    [12709] dbg: diag: module not installed: Net::Ident ('require' failed)
    [12709] dbg: diag: module installed: IO::Socket::INET6, version 2.51
    [12709] dbg: diag: module installed: IO::Socket::SSL, version 1.33
    [12709] dbg: diag: module installed: Compress::Zlib, version 2.03
    [12709] dbg: diag: module installed: Time::HiRes, version 1.9721
    [12709] dbg: diag: module installed: Mail::DomainKeys, version 1.0
    [12709] dbg: diag: module installed: Mail::DKIM, version 0.38
    [12709] dbg: diag: module installed: DBI, version 1.613
    [12709] dbg: diag: module installed: Getopt::Long, version 2.38
    [12709] dbg: diag: module installed: LWP::UserAgent, version 5.835
    [12709] dbg: diag: module installed: HTTP::Date, version 5.831
    [12709] dbg: diag: module installed: Archive::Tar, version 1.68
    [12709] dbg: diag: module installed: IO::Zlib, version 1.10
    [12709] dbg: diag: module installed: Encode::Detect, version 1.01
    [12709] dbg: gpg: Searching for 'gpg'
    [12709] dbg: util: current PATH is: /usr/bin:/bin:/sbin:/usr/sbin:/usr/bin:/bin:/usr/local/bin
    [12709] dbg: util: executable for gpg was found at /usr/bin/gpg
    [12709] dbg: gpg: found /usr/bin/gpg
    [12709] dbg: gpg: release trusted key id list: 5E541DC959CB8BAC7C78DFDC4056A61A5244EC45 26C900A46DD40CD5AD24F6D7DEE01987265FA05B 0C2B1D7175B852C64B3CDC716C55397824F434CE
    [12709] dbg: channel: attempting channel updates.spamassassin.org
    [12709] dbg: channel: update directory /var/lib/spamassassin/3.002004/updates_spamassassin_org
    [12709] dbg: channel: channel cf file /var/lib/spamassassin/3.002004/updates_spamassassin_org.cf
    [12709] dbg: channel: channel pre file /var/lib/spamassassin/3.002004/updates_spamassassin_org.pre
    [12709] dbg: channel: metadata version = 895075
    [12709] dbg: dns: 4.2.3.updates.spamassassin.org => 895075, parsed as 895075
    [12709] dbg: channel: current version is 895075, new version is 895075, skipping channel
    [12709] dbg: diag: updates complete, exiting with code 1
    Done
    ...Done
    Is there a problem here? if so what and how to fix it?
    if not, why is it doing this on every update run now?
     
  2. cPanelDon

    cPanelDon cPanel Quality Assurance Analyst
    Staff Member

    Joined:
    Nov 5, 2008
    Messages:
    2,557
    Likes Received:
    7
    Trophy Points:
    38
    Location:
    Houston, Texas, U.S.A.
    cPanel Access Level:
    DataCenter Provider
    Twitter:
    The output appears normal; the log detail includes verbose information while updating the SpamAssassin rules.

    Have you enabled SpamAssassin Rules Updates in the Update Preferences setup using WebHost Manager (WHM)?
    WHM: Main >> Server Configuration >> Update Preferences (Update Config)
    • SpamAssassin® Rules Updates
      • Automatic
      • Manual Updates Only
      • Never Update
     
  3. PPNSteve

    PPNSteve Well-Known Member

    Joined:
    Mar 13, 2003
    Messages:
    393
    Likes Received:
    1
    Trophy Points:
    18
    Location:
    Somewhere in Ilex Forest
    cPanel Access Level:
    Root Administrator
    Twitter:
    Yes, its set to automatic.

    I only mention / post this as this is new behavior in the log reports.. started about a week, week and a half ago.. never showed all that verbose info before.

    It seems to be "current" yet runs through all the list each daily update cycle.

    WHM 11.26.8
    REDHAT Enterprise 5.5 i686 standard
     
  4. cPanelDon

    cPanelDon cPanel Quality Assurance Analyst
    Staff Member

    Joined:
    Nov 5, 2008
    Messages:
    2,557
    Likes Received:
    7
    Trophy Points:
    38
    Location:
    Houston, Texas, U.S.A.
    cPanel Access Level:
    DataCenter Provider
    Twitter:
    In cPanel 11.26 you may find that the cPanel update (upcp) process calls upon the following script:
    Code:
    # /scripts/sa-update_wrapper
    The same level of verbose (debug) output should also appear when directly executing "sa-update" with the "-D" CLI switch:
    Code:
    # /usr/local/bin/sa-update -D
     
  5. sebby

    sebby Well-Known Member

    Joined:
    Jun 15, 2004
    Messages:
    70
    Likes Received:
    0
    Trophy Points:
    6
    Hello all-

    Is there anyway to tone down the SpamAssassin rules update verbose level that is embdeded in daily upcp email notifications?

    Thanks
     
  6. cPanelDon

    cPanelDon cPanel Quality Assurance Analyst
    Staff Member

    Joined:
    Nov 5, 2008
    Messages:
    2,557
    Likes Received:
    7
    Trophy Points:
    38
    Location:
    Houston, Texas, U.S.A.
    cPanel Access Level:
    DataCenter Provider
    Twitter:
    The level of detail in the cPanel update log output is inherently verbose. Is there a specific reason why you want to limit or reduce only the output from updating SpamAssassin rules (versus all other information logged during a cPanel update)?

    The script used is "/scripts/sa-update_wrapper" -- this could be modified to not pass the CLI switch "-D" to sa-update in order to reduce the level of detail. It is possible to automate patching the file using a custom "postupcp" script located at "/scripts/postupcp" which may be created as or consist of a simple shell script that executes specific commands to modify another file or apply a custom patch as needed.
     
    #6 cPanelDon, Dec 22, 2010
    Last edited: Dec 22, 2010
  7. sebby

    sebby Well-Known Member

    Joined:
    Jun 15, 2004
    Messages:
    70
    Likes Received:
    0
    Trophy Points:
    6
    SpamAssassin daily rules updates, which I assume is cycling normally (last line is: dbg: diag: updates complete, exiting with code 0) , is taking 920 of the 1200 lines of the daily upcp notification report... If no error is reported during the update, I would be satisfied with:
    Code:
    Updating SpamAssassin rules...  Done!
     
  8. yayyo

    yayyo Well-Known Member

    Joined:
    Jul 10, 2004
    Messages:
    61
    Likes Received:
    0
    Trophy Points:
    6
    Location:
    London, UK
    cPanel Access Level:
    Root Administrator
    I totally agree. One of my daily tasks is to visually review our server upcp log for errors. What I would prefer is an "exception report" i.e. either tell me that it's "4am and all is well" ;) or just list details for problems/errors. 920 lines telling me the spamassassin update worked is just plain "overkill".

    In the meantime, cPanel removing the -D would be appreciated to revert back to previous behaviour.

    Don, do we need to raise a feature request for this? or could you accept that it is a "bug"?
     
  9. MindStar

    MindStar Member

    Joined:
    Mar 29, 2007
    Messages:
    19
    Likes Received:
    0
    Trophy Points:
    1
    Location:
    UK
    Gentlemen,

    could you please apply whatever fix you applied the last time that this happened; the cPanel daily update report have been bloated with SpamAssassin Debug reporting for the past couple of weeks.

    Personally I would classify this as a security risk as the (IMNSHO) noise from SpamAssassin debug logging is obscuring the rest of the cPanel daily update reporting by the sheer volume of text that is adding to the report.

    Consider this, how much attention do you pay to a short, succinct post on a forum rather than a long rambling brain-dump? Is the same not true of daily update logs? Better to draw attention to something important rather than condition people to ignore a "worthless stream of noise".

    Thanks,

    Marc
     
  10. cPanelTristan

    cPanelTristan Quality Assurance Analyst
    Staff Member

    Joined:
    Oct 2, 2010
    Messages:
    7,623
    Likes Received:
    21
    Trophy Points:
    38
    Location:
    somewhere over the rainbow
    cPanel Access Level:
    Root Administrator
    If you would like to reduce the amount of details provided for SpamAssassin in the update log of cPanel upcp, please post a feature request:

    Feature Requests for cPanel/WHM

    Otherwise, I would be happy to move your post to that forum for consideration of this request.
     
Loading...

Share This Page