Results 1 to 10 of 10
  1. #1
    Master Untangler scot1967's Avatar
    Join Date
    Jan 2008
    Posts
    293

    Default Spam blocker stopped working 10 am today

    The Untangle Spam blocker is not working. Everything comes through with a spam score of 0. It happended at about 10 am this morning. No setting changes were made. Running ver 5.0.3

    Help?

  2. #2
    Master Untangler ronnikat's Avatar
    Join Date
    Apr 2007
    Location
    Bay California
    Posts
    268

    Default

    Quote Originally Posted by scot1967 View Post
    The Untangle Spam blocker is not working. Everything comes through with a spam score of 0. It happended at about 10 am this morning. No setting changes were made. Running ver 5.0.3

    Help?
    Unfortunately that is very common problem where in 5.0x Spam Blocker stops - hence why in 5.1 and above we have added robust babysitters to monitor and restart if it stops responding. Rebooting the machine will make it work again.

  3. #3
    Master Untangler scot1967's Avatar
    Join Date
    Jan 2008
    Posts
    293

    Default Errors I found...

    Seems to have been working untill 10:06:26 am. See error below. I am going to restart the box. Stopping and starting the Spam module had no effect.

    Syslog:

    May 30 10:03:57 untangle spamd[2984]: spamd: server successfully spawned child process, pid 27550
    May 30 10:03:57 untangle spamd[2984]: prefork: child states: BKBI
    May 30 10:04:02 untangle spamd[4041]: spamd: clean message (-1.4/5.0) for spamc:10001 in 5.4 seconds, 15801 bytes.
    May 30 10:04:02 untangle spamd[4041]: spamd: result: . -1 - AWL,BAYES_00,HTML_50_60,HTML_MESSAGE,NO_REAL_NAME scantime=5.4,size=15801,user=spamc,uid=10001,required_score=5.0,rhost=localhost,raddr=127.0.0.1,rport=7402,mid=<E5766CBAF69DD3118F2A0090271B76A60185F535@mail.midweststerilization.com>,bayes=5.55111512312578e-17,autolearn=no
    May 30 10:04:02 untangle spamd[2984]: prefork: child states: BKII
    May 30 10:04:02 untangle spamd[2984]: spamd: handled cleanup of child pid 27550 due to SIGCHLD
    May 30 10:04:02 untangle spamd[2984]: prefork: child states: BKI
    May 30 10:04:24 untangle spamd[4041]: spamd: connection from localhost [127.0.0.1] at port 3105
    May 30 10:04:24 untangle spamd[4041]: spamd: setuid to spamc succeeded
    May 30 10:04:24 untangle spamd[4041]: spamd: checking message <910.48063608320@wwa.midwiferysd.info> for spamc:10001
    May 30 10:04:30 untangle spamd[4041]: spamd: clean message (2.2/5.0) for spamc:10001 in 5.5 seconds, 4871 bytes.
    May 30 10:04:30 untangle spamd[4041]: spamd: result: . 2 - BAYES_00,HTML_90_100,HTML_MESSAGE,URIBL_BLACK,URIBL_SBL scantime=5.5,size=4871,user=spamc,uid=10001,required_score=5.0,rhost=localhost,raddr=127.0.0.1,rport=3105,mid=<910.48063608320@wwa.midwiferysd.info>,bayes=1.45161799247617e-09,autolearn=no
    May 30 10:04:30 untangle spamd[2984]: prefork: child states: BKI
    May 30 10:04:30 untangle spamd[4041]: spamd: connection from localhost [127.0.0.1] at port 4568
    May 30 10:04:30 untangle spamd[4041]: spamd: bad protocol: header error: junk at /usr/sbin/spamd line 1671, <GEN16284> line 1.
    May 30 10:04:30 untangle spamd[2984]: prefork: child states: BKI
    May 30 10:05:08 untangle spamd[4041]: spamd: connection from localhost [127.0.0.1] at port 5642
    May 30 10:05:08 untangle spamd[4041]: spamd: setuid to spamc succeeded
    May 30 10:05:08 untangle spamd[4041]: spamd: checking message <969138557.71131548792383@wegmann.de> for spamc:10001
    May 30 10:06:27 untangle spamd[2984]: spamd: server killed by SIGTERM, shutting down
    May 30 10:08:35 untangle spamd[28514]: spamd: could not create INET socket on 127.0.0.1:783: Address already in useMay 30 10:10:24 untangle spamd[1038]: prefork: sysread(9) failed after 300 secs at /usr/share/perl5/Mail/SpamAssassin/SpamdForkScaling.pm line 561.
    May 30 10:10:42 untangle spamd[28966]: spamd: could not create INET socket on 127.0.0.1:783: Address already in use
    May 30 10:12:49 untangle spamd[29383]: spamd: could not create INET socket on 127.0.0.1:783: Address already in use
    May 30 10:14:56 untangle spamd[29817]: spamd: could not create INET socket on 127.0.0.1:783: Address already in use
    May 30 10:16:53 untangle spamd[30209]: spamd: could not create INET socket on 127.0.0.1:783: Address already in use

  4. #4
    Master Untangler ronnikat's Avatar
    Join Date
    Apr 2007
    Location
    Bay California
    Posts
    268

    Default

    Let me know if it recovers after rebooting the box.

  5. #5
    Master Untangler scot1967's Avatar
    Join Date
    Jan 2008
    Posts
    293

    Default The reboot fix it.

    Thanks!

  6. #6
    Newbie
    Join Date
    Jan 2008
    Posts
    9

    Default

    Hi

    I have the same issue, the spam block stop working since 06/03, only mark mails and quarantine does not work.

    I have rebooted the server and not fix the problem.

    roberto

  7. #7
    Untangle Ninja juank's Avatar
    Join Date
    Aug 2007
    Location
    Athens
    Posts
    1,413

    Default

    Roberto, what version of UT are you running ?
    --------------------------------
    Juan Machado
    --------------------------------

  8. #8
    Newbie
    Join Date
    Jan 2008
    Posts
    9

    Default

    Hi

    I'm running UT Build: 5.2.1~svn20080515r16294release5.2-1sarge and Java: 1.6.0_03

    roberto

  9. #9
    Master Untangler JEllingson's Avatar
    Join Date
    Jan 2008
    Location
    Warner Robins, GA
    Posts
    342

    Default

    This problem happens when SpamAssassin gets sent the TERM signal, but isn't given enough time to clean itself up. So, what happens is that the new instance of SpamAssassin can't use the port 783 and in turn complains and bails out.

    What really needs to happen is a check of the mail.log for the phrase "spamd: could not create INET socket" after a 5 second pause when launching SpamAssassin. If it is found (you can grep the time to make sure you don't end in a loop... or miss the error if something else is added to the log in between), then retry starting SpamAssassin... repeat until successful.

    In the meantime, if this is a real problem for you, then edit your /etc/init.d/spamassassin script file to launch spamassassin TWICE (with a 5-15 second sleep in between). That should improve the chances of a successful launch without too much work.

    I may add some cool scripting code to check for these things to my server and pass them onto Untangle for inclusion in a future release... but lately, I've been swamped at work.

    - Jason

  10. #10
    Newbie
    Join Date
    Mar 2008
    Posts
    7

    Default

    I have the same problem with 5.2 also start from this week.
    Fixed after kill spamd and start /etc/init.d/spamassassin again.

Posting Permissions

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

SEO by vBSEO 3.6.0 PL2