You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by bu...@bugzilla.spamassassin.org on 2016/11/22 01:05:30 UTC

[Bug 7373] New: Weird startup behaviour on Ubuntu

https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7373

            Bug ID: 7373
           Summary: Weird startup behaviour on Ubuntu
           Product: Spamassassin
           Version: 3.4.1
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: spamc/spamd
          Assignee: dev@spamassassin.apache.org
          Reporter: michael.heuberger@binarykitchen.com
  Target Milestone: Undefined

Hello there

I'm running Spamassassin here on Ubuntu 16.10 together with Monit (and Postfix
of course). Each time server restarts, Monit says first that the spamd process
is not running (no PID) but in three minutes it says it's running.

There is the /etc/init.d/spamassassin file that boots Spamassassin on start.
But somehow it does not seem to get executed asap but 3 mins later. No idea
why.

The PID under /var/run/spamassassin.pid is owned by root and is monitored under
Monit with these configs:

# (hidden) @ (hidden) in /etc/monit/conf.d [14:00:04] C:1
$ cat spamassassin
check process spamd with pidfile /var/run/spamassassin.pid
   group mail
   start program = "/etc/init.d/spamassassin start" with timeout 180 seconds
   stop  program = "/etc/init.d/spamassassin stop"
   if 5 restarts within 5 cycles then timeout
   if cpu usage > 79% for 5 cycles then alert
   if mem usage > 79% for 5 cycles then alert
   depends on spamd_bin
   depends on spamd_rc

check file spamd_rc with path /etc/init.d/spamassassin
   group mail
   if failed checksum then unmonitor
   if failed permission 755 then unmonitor
   if failed uid root then unmonitor
   if failed gid root then unmonitor

check file spamd_bin with path /usr/sbin/spamd
   group mail
   if failed checksum then unmonitor
   if failed permission 755 then unmonitor
   if failed uid root then unmonitor
   if failed gid root then unmonitor

Not sure what the problem is here. Could be one of these:
- a bug in /etc/init.d/spamassassin?
- a bad config in the above monit config
- something in postfix or another lib blocking spamassassin

No idea how to investigate. And there is no spamassassin log showing how it
starts up.

Any clues welcome

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 7373] Weird startup behaviour on Ubuntu

Posted by bu...@bugzilla.spamassassin.org.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7373

AXB <ax...@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |INVALID

--- Comment #1 from AXB <ax...@gmail.com> ---
Bugzilla is not a support "forum" - please move this to the SA user's list

-- 
You are receiving this mail because:
You are the assignee for the bug.