Any big deal if the make-test coughs up one error?

t/heuristic......FAILED test 7
Failed 1/15 tests, 93.33% okay

Well, I proceeded anyway and it looks like the skd installs okay, but I have a compelte failure in the agents. Make and make test went okay, but make install reults ultimately in:

Digest::SHA1 object version 2.01 does not match bootstrap parameter 2.10 at /usr/lib/perl5/5.8.3/i386-linux-thread-multi/DynaLoader.pm line 249.

I have tried updating Digest::SHA1 three times, but it indicates that it is the latest version.

This is a Fedora Core 2 box.

On a Fedora Core 2 server, the version of Digest::SHA1 was 2.01. I had to manually download and install version 2.10 from here:

http://search.cpan.org/dist/Digest-SHA1/

And the make install for the agent-2,61 worked fine.

I'll guess I'll make this my running commentary on erros I found..

On this step:

razor-admin -d -create -home=/var/spool/mqueue/.razor/

We failed because there was no mqueue directroy. I manually created it, but am unsure about ownership. Should it be mailnull:mail?

razor-admin -register -home=/var/spool/mqueue/.razor/

This failed the first time it ran. WHen I reran it, it worked. Weird.
------------------------------------
This line was not in the razor configuration:

razorhome = /var/spool/mqueue/.razor/

So I simply added it to the bottom.
-----------------------------------
At this this point:

chkconfig --add DCC

Shouldn't we also do

chkconfig DCC on

So that it restarts on reboot?
====================
Line break is bad on the ACL section:

#!!# ACL that is used after the
DATA command
check_message:
require verify = header_sender

DATA should be on top line after the
==========================

I am stopping for now and taking a break, but in reading ahead, I see a potential conflict. You have us edit the middle box in the ACLs to enable filename and mime scanning, and then again you have us edit the same section for the spamassassin actions.

Does it matter where we put it? Above, below or what?

Did you run /scripts/perlinstaller Digest::SHA1 ?
It should update Digest::SHA1 to latest version.



I updated the instruction to make /var/spool/mqueue dir. The owner have to be mailnull:mail.




Because only do chkconfig --add DCC, when I reboot the server, DCC start on reboot. By theory it should but no one reommend it, so I leave it.




The order does matter. I have edited the instruction to avoid confusion.

That was the point of my comment. i tried updateding it via /scripts/perlinstaller three times, but each time it said that it was up to date.

The only way I could get it updated was to download it from the link I posted and compiling manually.

Here's how I fixed the problem:

1) go to

/home/.cpan/build/Digest-SHA1-2.10

and do

make install

2) Wipe the existing razor-agents source directory and do a fresh razor-agents install from the tarball.

With both the SHA1 from the rasor sdk and the perlinstaller version there is a conflict. Razor will work with either version. This uses the perlinstaller version of SHA1 and overwrites the older razor sdk version.

Hope this helps,

pulse

For the record, I just spent an hour on a RH 7.3 server tryint to install Razor, and it turned out to be a MIME::Base64 problem.

Word to the wise.

I have the same problem...

I have cPanel + RVskins in cpanel... and i get the same problem:

t/heuristic......FAILED test 7
Failed 1/15 tests, 93.33% okay

I installed latest SHA1 using perlinstaller, then tried the same downloading it from cpan's website and do a manual install, and I get always the same.

If I ifnore the error and try to install razor-agents-1.67, I get this:

Digest::SHA1 object version 2.01 does not match bootstrap parameter 2.10 at /usr/lib/perl5/5.8.4/i686-linux/DynaLoader.pm line 253.


Any ideas how to fix this on cpanel/RH?

I ran out of ideas... seems, as stated, razor 2.01 & 2.10 can't work together, but i don't know what to do to fix this issue

please help me

Regards
Omar

This is a particularly thorny issue, esp[ on RH less than EL versio 3.

I have had to manually update Digest::MD5 and other packages as well. Best thing to do is closely read the output of the make an d make installs and when you corect something go back and make clean before rerunning the configure.

could get it working... is pretty cool!
bye bye spam

what I think, is that insalling sdk is a pain for conflicts...

Should be better, in the guide, to gorget about sdk and install individual perl modules like stated here:
http://razor.sourceforge.net/docs/install.php



Should cause less conlicts... I added the 3 options for 3) in tutorial .)

now, let's see how it works in the long-run

thanks,
Omar

If anyone is still interested, I found you could fix it with:

/scripts/perlinstaller --force Digest::SHA1

Thanks this fixed the issue.