Theo,
Yeah, there does still appear to be a major bug in the
razor-agents with regards to full auto-rediscovery when a
discovery server is unreachable. For now, just to ease the pain,
I've put it back up on honor.cloudmark.com (216.52.13.90).
However, if anyone has any problems with the rediscovery mechanism
you should always try to force a manual rediscovery (as Theo has
done) before reporting any problems. This will be fixed shortly.
Thanks for the heads-up, BTW. Happy Holidays.
--jordan
On Wed, Dec 25, 2002 at 01:40:17PM -0500, Theo Van Dinter wrote:
# On Wed, Dec 25, 2002 at 09:34:38AM -0600, Mike Loiterman wrote:
# > Is the razor2 server down? I'm getting a lot of these messages in my maillog:
# > razor2 check skipped: No such file or directory IO::Socket::INET: Interrupted
system call ...propagated at
/usr/local/lib/perl5/site_perl/5.005/Mail/SpamAssassin/Dns.pm line 391.
#
# They seem to be having issues, I get lots of "Operation now in progress",
# along with a bunch of errors from IO::Socket::INET. Since I haven't
# seen anything on the razor-users list, I'm cross-posting there too.
#
# Running razor-check and following the debug lines, it looks like their
# discovery server is down.
#
# Dec 25 13:34:29.060877 check[8963]: [ 5] server discovery overdue by 44457 seconds
# Dec 25 13:34:29.060967 check[8963]: [ 8] already have 1 discovery servers
# Dec 25 13:34:29.061085 check[8963]: [ 8] Checking with Razor Discovery Server
216.52.13.90
# Dec 25 13:34:29.061211 check[8963]: [ 6] No proper port specified, using 2703
# Dec 25 13:34:29.061257 check[8963]: [ 5] Connecting to 216.52.13.90 ...
# Dec 25 13:34:49.063200 check[8963]: [ 3] Unable to connect to 216.52.13.90:2703;
Reason: Operation now in progress.
# Dec 25 13:34:49.063327 check[8963]: [ 5] Razor Discovery Server 216.52.13.90 not
answering
# Dec 25 13:34:49.063578 check[8963]: [ 1] razor-check error: nextserver: Could not
get valid info from Discovery
# Servers
# nextserver: Could not get valid info from Discovery Servers
#
#
# I did a "razor-admin -discover" and that hit 216.52.3.2 instead of 13.90,
# and everything has gone fine after that. I hope all my users don't have
# to do this as well. Anyway, FYI. :)
msg11448/pgp00000.pgp
Description: PGP signature
