Hey Ralph and others, thanks for following-up and getting to the bottom
of this.
It is quite clear that razor2's diagnostic messages could and should be
improved: the effort you put into this do show this pretty well. However we
believe that this request belongs to the upstream project, and not
** Tags removed: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819977
Title:
razor2 had unknown error during get_server_info
To manage notifications about this bug go to:
htt
** Tags added: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819977
Title:
razor2 had unknown error during get_server_info
To manage notifications about this bug go to:
https
Hi Christian, DNS resolved the domainname to one of three IP addresses
and the server listening on one of those developed a fault leading to
the client reporting the error, but in an unclear manner. The server
owners were alerted thanks to nyet and fixed their server's problem.
Thus the software d
Hey guys, I highly appreciate that you all got this sorted out.
I tried to follow the updates, but there was a lot going on .
My naive question would be if that was really all resolved on the
backend and no changes to the Ubuntu packages are needed?
--
You received this bug notification because
In case of future similar problems, I think the error logged should
include the IP address used.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819977
Title:
razor2 had unknown error during get_serv
Hi nyet, thanks for letting us know. What mechanism did you use to
contact CloudMark that worked?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819977
Title:
razor2 had unknown error during get_se
I have received a response from cloudmark and they appear to have fixed the
issue.
$ telnet 208.83.139.205 2703
Trying 208.83.139.205...
Connected to 208.83.139.205.
Escape character is '^]'.
sn=D&srl=670&a=l&a=cg
a=g&pm=csl
-csl=?
c302.cloudmark.com
c303.cloudmark.com
c301.cloudmark.com
.
a=g&pm=
Note that proofpoint has no interest in helping anyone that isn't paying
them:
https://proofpointcommunities.force.com/community/PPSupCommunityLogin
> If you do not have access to this system, contact your Proofpoint Sales
> Representative.
>
> If you are having trouble logging in, please contac
I tried to contact cloudmark/proofpoint a week ago. Still no response.
I don't think they care.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819977
Title:
razor2 had unknown error during get_serv
Deb bug is here
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924583
$ telnet 208.83.137.117 2703
Trying 208.83.137.117...
Connected to 208.83.137.117.
Escape character is '^]'.
sn=C&srl=43940&a=l&a=cg
a=g&pm=csl
err=240
a=g&pm=nsl
err=240
$ telnet 208.83.137.118 2703
Trying 208.83.137.118...
On my end it seems like all 3 IPs that discovery.razor.cloudmark.com is
pointing to now show the same error :(
For reference:
$ host discovery.razor.cloudmark.com.
discovery.razor.cloudmark.com has address 208.83.139.205
discovery.razor.cloudmark.com has address 208.83.137.118
discovery.razor.clo
Is hacking hosts file really a good idea? Shouldn't this be fixed within
Razor's package in the next update? If so, where to report directly?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819977
Titl
Great workaround tip thanks @strredwolf.
You can use either 208.83.137.117 or 208.83.137.118, the current problem
is with 208.83.139.205.
To test, set the ip you want to test in /etc/hosts. Example:
208.83.139.205 discovery.razor.cloudmark.com
Then:
# echo "test" | spamassassin -D razor2 2>&1 |
Chiming in here. I've worked around this via a DNS host entry in
/etc/hosts:
208.83.137.117 discovery.razor.cloudmark.com
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819977
Title:
razor2 had u
So you could forward your connections intended to the faulty .205 server
to one of the others to mitigate the issue client-side?
https://superuser.com/a/681707 - forwarding through iptables like this
seems to work for me. I have no idea about further implications of this
workaround, though.
--
Y
Hi nyet, You state this all as fact, but give no references to the
source of the information, nor say why you'd know, e.g. an employee of
Cloudmark. And what you say is incorrect because 'Razor servers' are
not dead, some are still alive.
/etc/cron.d/amavisd-new has
18 */3 * * * amavis ... s
Razor servers are dead. Dev is MIA, with absolutely no indication who to
contact, or if there are backups of the server, or if there is a way to
replicate the server.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
Mar 17 11:34:00.034823 check[8834]: [ 5] Razor Discovery Server
discovery.razor.cloudmark.com had no valid nsl servers
Mar 17 11:34:00.034872 check[8834]: [ 5] Couldn't talk to discovery servers.
Will force a bootstrap...
Mar 17 11:34:00.034919 check[8834]: [ 6] no discovery listfile:
servers.d
A DNS lookup of discovery.razor.cloudmark.com occurs. Here, that gives
three A records: 208.83.137.118, 208.83.139.205, and 208.83.137.117.
When the ..205 is connected, the initial read(2) of 'sn=D...', write(2)
of 'a=g...', triggers a read() of 'err=240\r\n'. connect() to ..117 and
that error do
Seems to be a server error from the remote site.
I tested several times with: echo "test" | spamassassin -D razor2 2>&1 |
less
Sometimes the error occurred, other times not. The only difference was that -
when it worked - it showed:
Mar 15 11:12:48.739649 check[21141]: [ 8] Discovery Server
dis
Mabe it is a kind of racetime condition (concurrency issue)?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819977
Title:
razor2 had unknown error during get_server_info
To manage notifications abo
Whoops.. pyzor.. razor.. keep confusing the two. So, a correction to the
above:
The razor packages on Ubuntu 16.04 LTS and Debian 9.7 are very similar:
2.85-4.2build1 and 2.85-4.2+b2 respectively. So I guess that is not it.
Similarly, spamassassin is 3.4.2-0ubuntu0.16.04.1 on Ubuntu and 3.4.2-1~d
Hi,
not sure if this is really needed as Bram and Googolplex are all over that bug
and know what they are doing.
But a plain install of the components from the archive works, so it must
be some part of the custom post-install configuration that eventually
makes it fail. That seems clear to all of
It's worth mentioning that on the mailinglist at
https://sourceforge.net/p/razor/mailman/razor-users/ it has been
questioned back in 2018 if the project is dead (or development of the
client software, anyway).
Also, when I compare two mail servers under my control:
* On Ubuntu 16.04 LTS where I se
Thanks but still fail. Tried to recreate based on step 1) and says
$ razor-admin -create
nextserver: Bootstrap discovery failed. Giving up.
Still nothing works :(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
Actually, ignore my message. I still have the error.
Strange, could it be that it does not happen 100% of the cases? After
all I also see RAZOR2_CHECK and RAZOR2_CF_RANGE_51_100 scores in spamd
results a couple of times during the day. That implies that it works..
or at least some of the time
I had the same issue on a mail server with Ubuntu 16.04.5 LTS. After reading
previous comment I ran the following command (note that the username, 'mail' in
this case, may be different on your system):
root@mail:~# su -s /bin/bash - mail
mail@mail:~$ razor-admin --discover
That made the "razor2
Test as root: echo "test" | spamassassin -D razor2 2>&1 | less
Result with error:
Mar 14 12:53:56.923 [27516] dbg: razor2: razor2 is available, version 2.84
Mar 14 12:53:58.439 [27516] warn: razor2: razor2 check failed: razor2: razor2
had unknown error during get_server_i
nfo at /usr/share/perl5/
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: spamassassin (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819977
Title:
30 matches
Mail list logo
