S. Anthony Sequeira wrote:
quote:

>
> Died at
> /usr/lib/perl5/site_perl/5.8.0/Mail/SpamAssassin/Dns.pm line 409.
> Or any clues as to where to look?


The error message gave a filename and line number.  That's a pretty
good hint.  Did you look there?  Since it's a PERL module, you'll
want to locate/download a copy of Dns.pl to see what is happening
on that line number.

[ Post a follow-up to this message ]

On Mon, 26 Jan 2004 06:29:15 -0800, Doug Freyburger penned:
quote:

> /usr/lib/perl5/site_perl/5.8.0/Mail/SpamAssassin/Dns.pm


I already looked, can't figure out why it's failing after a couple of
months running well.

my $objects = $rc->prepare_objects( \@msg )
or die "error in prepare_objects";
409 --> $rc->get_server_info() or die $rc->errprefix("checkit");

which, to me, means it cannot contact the server, which is more or less
what I gathered from the spamd message anyway.

I'm wondering whether it could be ADSL modem/router related, as about the
only thing I recall changing at the time it started was upgrading the
firmware.

Cheers
--
Tony

[ Post a follow-up to this message ]

S. Anthony Sequeira wrote:
quote:

>
>         my $objects = $rc->prepare_objects( \@msg )
>           or die "error in prepare_objects";
> 409 --> $rc->get_server_info() or die $rc->errprefix("checkit");
>
> which, to me, means it cannot contact the server, which is more or less
> what I gathered from the spamd message anyway.


"transport endpoint not connected" message associated with a
get_server_info() call sure does look like server access is blocked.
That isn't certain because the cited line number can be a few off,
which is why you quoted the stuff above it for one semicolon back.
It also could be a failure in the stuff that set the server
information structures that didn't trigger a failure then.
quote:

> I'm wondering whether it could be ADSL modem/router related, as about the
> only thing I recall changing at the time it started was upgrading the
> firmware.


Sounds like it.  Any idea what server information the get_server_info()
call retrieves?  If the firmware blocks a port now, that would be it.

[ Post a follow-up to this message ]

On Tue, 27 Jan 2004 08:38:29 -0800, Doug Freyburger penned:
quote:

> S. Anthony Sequeira wrote: 
>
> "transport endpoint not connected" message associated with a
> get_server_info() call sure does look like server access is blocked. That
> isn't certain because the cited line number can be a few off, which is why
> you quoted the stuff above it for one semicolon back. It also could be a
> failure in the stuff that set the server information structures that
> didn't trigger a failure then.
> 
>
> Sounds like it.  Any idea what server information the get_server_info()
> call retrieves?  If the firmware blocks a port now, that would be it.


I haven't looked at the code in any detail yet.

The thing is, it's an intermittent error.  I would expect a blocked port
to raise this error consistently, or am I indulging in woolly thinking?

There are a couple of things about this firmware release that make me
think it's dodgy.  I was complaining about the modem regularly dropping
and regaining it's DNS connections, evidenced by the logs.  This release
has either cured this or suppressed the message in the logs.

I'm trying to get hold of the previous firmware to see whether it is a
cure.  Life's short and the list of things to do is long.  Enough sob
stories.

Thanks
--
Tony

[ Post a follow-up to this message ]