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.

Spamassassin Configure error

Discussion in 'General Discussion' started by NightStorm, Jun 4, 2006.

  1. NightStorm

    NightStorm Well-Known Member

    Joined:
    Jul 28, 2003
    Messages:
    286
    Likes Received:
    4
    Trophy Points:
    168
    cPanel Access Level:
    Root Administrator
    Twitter:
    Clicking on the "Configure Spamassassin" button from within CPanel, I receive the following error:
    An output of the error log shows:
    I am running the latest perl, I have checked that the modules are up to date with /usr/local/cpanel/bin/checkperlmodules, and have also run /scripts/perlinstaller --force List::Util, on the longshot that it was a problem (it came up in the search).
    WHM 10.8.0 cPanel 10.8.2-E135
    RedHat Enterprise 3 i686 - WHM X v3.1.0
    Any ideas?
     
    #1 NightStorm, Jun 4, 2006
  2. OCX

    OCX Well-Known Member

    Joined:
    Sep 20, 2003
    Messages:
    232
    Likes Received:
    0
    Trophy Points:
    166
    Code:
    run /scripts/perlinstaller --force Bundle::DBD::mysql


then run
/usr/local/cpanel/bin/checkperlmodules


    OCX
     
    #2 OCX, Jun 4, 2006
  3. NightStorm

    NightStorm Well-Known Member

    Joined:
    Jul 28, 2003
    Messages:
    286
    Likes Received:
    4
    Trophy Points:
    168
    cPanel Access Level:
    Root Administrator
    Twitter:
    Done both, error still happens, and the error_log has not changed (same results).
     
    #3 NightStorm, Jun 4, 2006
  4. OCX

    OCX Well-Known Member

    Joined:
    Sep 20, 2003
    Messages:
    232
    Likes Received:
    0
    Trophy Points:
    166
    #4 OCX, Jun 4, 2006
  5. NightStorm

    NightStorm Well-Known Member

    Joined:
    Jul 28, 2003
    Messages:
    286
    Likes Received:
    4
    Trophy Points:
    168
    cPanel Access Level:
    Root Administrator
    Twitter:
    Already done that once (hence the perl -v output) but I'll try it again and see what happens...
     
    #5 NightStorm, Jun 4, 2006
  6. chirpy

    chirpy Well-Known Member

    Joined:
    Jun 15, 2002
    Messages:
    13,472
    Likes Received:
    20
    Trophy Points:
    463
    Location:
    Go on, have a guess
    This can sometimes happen if /usr/local/bin/perl isn't a simple symlink to /usr/bin/perl
     
    #6 chirpy, Jun 5, 2006
  7. chirpy

    chirpy Well-Known Member

    Joined:
    Jun 15, 2002
    Messages:
    13,472
    Likes Received:
    20
    Trophy Points:
    463
    Location:
    Go on, have a guess
    No, that won't fix it.

    Try running:

    /usr/local/bin/perl -v

    /usr/bin/perl -v

    Do you get the same results?
     
    #7 chirpy, Jun 5, 2006
  8. NightStorm

    NightStorm Well-Known Member

    Joined:
    Jul 28, 2003
    Messages:
    286
    Likes Received:
    4
    Trophy Points:
    168
    cPanel Access Level:
    Root Administrator
    Twitter:
    So you think that executing:
    ln -s /usr/bin/perl /usr/local/bin/perl
    might fix it?

    *edit* Nope... that isn't it either.
    ln: `/usr/local/bin/perl': File exists
    lrwxrwxrwx 1 root root 13 Sep 2 2005 /usr/local/bin/perl -> /usr/bin/perl*

    This really has me stumped. I opened a ticket with CPanel yesterday, but as yet, have not received a reply. I'm guessing a Sunday was a bad time to discover this problem.
     
    #8 NightStorm, Jun 5, 2006
    Last edited: Jun 5, 2006
  9. NightStorm

    NightStorm Well-Known Member

    Joined:
    Jul 28, 2003
    Messages:
    286
    Likes Received:
    4
    Trophy Points:
    168
    cPanel Access Level:
    Root Administrator
    Twitter:
    I swear... this is just a good week...
     
    #9 NightStorm, Jun 5, 2006
  10. NightStorm

    NightStorm Well-Known Member

    Joined:
    Jul 28, 2003
    Messages:
    286
    Likes Received:
    4
    Trophy Points:
    168
    cPanel Access Level:
    Root Administrator
    Twitter:
    Done some experimenting. This is a bug in the EDGE build, as the error goes away and the page works when using CURRENT, but returns with EDGE.
    Guess I'll go update my ticket.
     
    #10 NightStorm, Jun 5, 2006
    Last edited: Jun 5, 2006
  11. cinusik

    cinusik Active Member

    Joined:
    Jul 31, 2003
    Messages:
    36
    Likes Received:
    1
    Trophy Points:
    158
    cPanel Access Level:
    Root Administrator
    NightStorm, I have the same issue on EDGE too. If you'll have any resolution for thisone, please post it here. Thanks in advance.
     
    #11 cinusik, Jun 6, 2006
  12. NightStorm

    NightStorm Well-Known Member

    Joined:
    Jul 28, 2003
    Messages:
    286
    Likes Received:
    4
    Trophy Points:
    168
    cPanel Access Level:
    Root Administrator
    Twitter:
    http://bugzilla.cpanel.net/show_bug.cgi?id=4264

    Reported the bug. Feel free to vote for it and add any additional information you can think of that could help the staff to fix the problem.
    For the time being, I suggest a downgrade to the latest CURRENT. It's not experiencing the same problems, and the latest EDGE (released last night) does not yet fix the problem.
     
    #12 NightStorm, Jun 6, 2006
  13. jackal

    jackal Well-Known Member
    PartnerNOC

    Joined:
    Feb 23, 2002
    Messages:
    708
    Likes Received:
    0
    Trophy Points:
    316
    Voted on your ticket same issue here also issue with perl relating to cachelanguages
     
    #13 jackal, Jun 12, 2006
  14. NightStorm

    NightStorm Well-Known Member

    Joined:
    Jul 28, 2003
    Messages:
    286
    Likes Received:
    4
    Trophy Points:
    168
    cPanel Access Level:
    Root Administrator
    Twitter:
    Just an update. While the changelog shows SFA, this bug has been fixed in the latest EDGE update (released last night).
     
    #14 NightStorm, Jun 13, 2006
  15. cinusik

    cinusik Active Member

    Joined:
    Jul 31, 2003
    Messages:
    36
    Likes Received:
    1
    Trophy Points:
    158
    cPanel Access Level:
    Root Administrator
    EDGE 138 fix this issue, that I can confirm on my 2 servers but E138 breaks domains parking. Can you confirm thisone NightStorm?
    Just try to park any domain on any server and you'll see the error.
     
    #15 cinusik, Jun 14, 2006
  16. rpmws

    rpmws Well-Known Member

    Joined:
    Aug 14, 2001
    Messages:
    1,824
    Likes Received:
    7
    Trophy Points:
    318
    Location:
    back woods of NC, USA
    domain parking / subdomains / add-on domains all screwed up ..or some combination of the above in 138
     
    #16 rpmws, Jun 14, 2006
(You must log in or sign up to post here.)
Loading...
Similar Threads - Spamassassin Configure error
  1. silverbytes

    SpamAssassin Subject in Whitelist question

    silverbytes, Aug 16, 2017 at 7:29 AM, in forum: E-mail Discussions
    Replies:
    1
    Views:
    43
    cPanelMichael
    Aug 16, 2017 at 10:09 AM
  2. siriusb

    SpamAssassin disabled, but going to Junk

    siriusb, Aug 7, 2017, in forum: E-mail Discussions
    Replies:
    5
    Views:
    81
    siriusb
    Aug 10, 2017
  3. silverbytes

    Where are the spamassassin filtered emails?

    silverbytes, Aug 4, 2017, in forum: E-mail Discussions
    Replies:
    3
    Views:
    109
    rpvw
    Aug 5, 2017
  4. Abin C Jose

    Blocking an email with SpamAssassin

    Abin C Jose, Jul 6, 2017, in forum: E-mail Discussions
    Replies:
    1
    Views:
    141
    cPanelMichael
    Jul 6, 2017
  5. keat63

    Create a SpamAssassin Score?

    keat63, Jun 22, 2017, in forum: E-mail Discussions
    Replies:
    2
    Views:
    140
    keat63
    Jun 22, 2017

Share This Page