You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Sparecreative <zo...@sparecreative.com> on 2007/08/08 03:01:15 UTC

Unable to SPamAssassin 3.2.2 started

I've just installed SA 3.2.2 and the installation went fine with no errors.
Then when I tried to invoke it via a rule in Communigate Pro it fails. I
checked the logs and this is what I see:

Aug  8 00:22:54 SpareServer spamc[12563]: connect to spamd on 127.0.0.1
failed, retrying (#1 of 3): Connection refused
Aug  8 00:22:55 SpareServer spamc[12563]: connect to spamd on 127.0.0.1
failed, retrying (#2 of 3): Connection refused
Aug  8 00:22:56 SpareServer spamc[12563]: connect to spamd on 127.0.0.1
failed, retrying (#3 of 3): Connection refused
Aug  8 00:22:57 SpareServer spamc[12563]: connection attempt to spamd
aborted after 3 retries
Aug  8 00:25:04 SpareServer spamc[12668]: connect to spamd on
255.255.255.255 failed, broadcast addr
Aug  8 00:25:04 SpareServer spamc[12668]: connect to spamd on
255.255.255.255 failed, retrying (#1 of 3): Unknown error: 0
Aug  8 00:25:05 SpareServer spamc[12668]: connect to spamd on
255.255.255.255 failed, broadcast addr
Aug  8 00:25:05 SpareServer spamc[12668]: connect to spamd on
255.255.255.255 failed, retrying (#2 of 3): Invalid argument
Aug  8 00:25:06 SpareServer spamc[12668]: connect to spamd on
255.255.255.255 failed, broadcast addr
Aug  8 00:25:06 SpareServer spamc[12668]: connect to spamd on
255.255.255.255 failed, retrying (#3 of 3): Invalid argument


Any pointers would really be appreciated.

Zoran
-- 
View this message in context: http://www.nabble.com/Unable-to-SPamAssassin-3.2.2-started-tf4233729.html#a12045373
Sent from the SpamAssassin - Users mailing list archive at Nabble.com.


Re: Unable to SPamAssassin 3.2.2 started

Posted by Matt Kettler <mk...@verizon.net>.
Sparecreative wrote:
> I've just installed SA 3.2.2 and the installation went fine with no errors.
> Then when I tried to invoke it via a rule in Communigate Pro it fails. I
> checked the logs and this is what I see:
>
> Aug  8 00:22:54 SpareServer spamc[12563]: connect to spamd on 127.0.0.1
> failed, retrying (#1 of 3): Connection refused
> Aug  8 00:22:55 SpareServer spamc[12563]: connect to spamd on 127.0.0.1
> failed, retrying (#2 of 3): Connection refused
> Aug  8 00:22:56 SpareServer spamc[12563]: connect to spamd on 127.0.0.1
> failed, retrying (#3 of 3): Connection refused
> Aug  8 00:22:57 SpareServer spamc[12563]: connection attempt to spamd
> aborted after 3 retries
> Aug  8 00:25:04 SpareServer spamc[12668]: connect to spamd on
> 255.255.255.255 failed, broadcast addr
> Aug  8 00:25:04 SpareServer spamc[12668]: connect to spamd on
> 255.255.255.255 failed, retrying (#1 of 3): Unknown error: 0
> Aug  8 00:25:05 SpareServer spamc[12668]: connect to spamd on
> 255.255.255.255 failed, broadcast addr
> Aug  8 00:25:05 SpareServer spamc[12668]: connect to spamd on
> 255.255.255.255 failed, retrying (#2 of 3): Invalid argument
> Aug  8 00:25:06 SpareServer spamc[12668]: connect to spamd on
> 255.255.255.255 failed, broadcast addr
> Aug  8 00:25:06 SpareServer spamc[12668]: connect to spamd on
> 255.255.255.255 failed, retrying (#3 of 3): Invalid argument
>
>
> Any pointers would really be appreciated.
>   
Is spamd actually running?  You can't invoke spamc without a spamd to do
the work...



Re: Unable to SPamAssassin 3.2.2 started

Posted by "McDonald, Dan" <Da...@austinenergy.com>.
On Tue, 2007-08-07 at 18:01 -0700, Sparecreative wrote:
> I've just installed SA 3.2.2 and the installation went fine with no errors.
> Then when I tried to invoke it via a rule in Communigate Pro it fails. I
> checked the logs and this is what I see:
> 
> Aug  8 00:22:54 SpareServer spamc[12563]: connect to spamd on 127.0.0.1
> failed, retrying (#1 of 3): Connection refused

> 
> 
> Any pointers would really be appreciated.
> 

http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5574


> Zoran
-- 
Daniel J McDonald, CCIE # 2495, CISSP # 78281, CNX
Austin Energy
http://www.austinenergy.com

Re: Unable to SPamAssassin 3.2.2 started

Posted by Duane Hill <d....@yournetplus.com>.
On Tue, 7 Aug 2007 at 20:05 -0700, zoran@sparecreative.com confabulated:

>
> Thanks for that. Spamd hadn't started. There was an error in the local.cf
> file. It looks liek some of the other software I installed modified it.
>
> Thanks for the pointers - it should've been the first place I looked.
>
> Anybody have any experience with Communigate Pro and CGPSA. I'm now having
> trouble get them to communicate.

CGPSA interfaces directly with SA through its API. It does not use spamc. 
Perhaps you should consult with the CGPSA list for assistance. I use to 
use it. However, due to circumstances, I had to create something from 
scratch to interface directly with SA.

The list subscription for CGPSA can be found on:

   http://www.tffenterprises.com/cgpsa/

-------
   _|_
  (_| |

Re: Unable to SPamAssassin 3.2.2 started

Posted by Sparecreative <zo...@sparecreative.com>.
Thanks for that. Spamd hadn't started. There was an error in the local.cf
file. It looks liek some of the other software I installed modified it.

Thanks for the pointers - it should've been the first place I looked.

Anybody have any experience with Communigate Pro and CGPSA. I'm now having
trouble get them to communicate.

Z.
-- 
View this message in context: http://www.nabble.com/Unable-to-SPamAssassin-3.2.2-started-tf4233729.html#a12046366
Sent from the SpamAssassin - Users mailing list archive at Nabble.com.


Re: Unable to SPamAssassin 3.2.2 started

Posted by Jari Fredriksson <ja...@iki.fi>.
Are you sure there is spamd process running on the same host calling this? Looks that there is not.


> I've just installed SA 3.2.2 and the installation went
> fine with no errors. Then when I tried to invoke it via a
> rule in Communigate Pro it fails. I checked the logs and
> this is what I see: 
> 
> Aug  8 00:22:54 SpareServer spamc[12563]: connect to
> spamd on 127.0.0.1 failed, retrying (#1 of 3): Connection
> refused 
> Aug  8 00:22:55 SpareServer spamc[12563]: connect to
> spamd on 127.0.0.1 failed, retrying (#2 of 3): Connection
> refused 
> Aug  8 00:22:56 SpareServer spamc[12563]: connect to
> spamd on 127.0.0.1 failed, retrying (#3 of 3): Connection
> refused 
> Aug  8 00:22:57 SpareServer spamc[12563]: connection
> attempt to spamd aborted after 3 retries
> Aug  8 00:25:04 SpareServer spamc[12668]: connect to
> spamd on 255.255.255.255 failed, broadcast addr
> Aug  8 00:25:04 SpareServer spamc[12668]: connect to
> spamd on 255.255.255.255 failed, retrying (#1 of 3):
> Unknown error: 0 
> Aug  8 00:25:05 SpareServer spamc[12668]: connect to
> spamd on 255.255.255.255 failed, broadcast addr
> Aug  8 00:25:05 SpareServer spamc[12668]: connect to
> spamd on 255.255.255.255 failed, retrying (#2 of 3):
> Invalid argument 
> Aug  8 00:25:06 SpareServer spamc[12668]: connect to
> spamd on 255.255.255.255 failed, broadcast addr
> Aug  8 00:25:06 SpareServer spamc[12668]: connect to
> spamd on 255.255.255.255 failed, retrying (#3 of 3):
> Invalid argument 
> 
> 
> Any pointers would really be appreciated.
> 
> Zoran