No email in or out - clamav stopped Service Router

[coltect]

Hello,
Firstly, my main problem is resolved thanks to the info in viewtopic.php?t=6673&highlight=5183

and we are now processing email again.

What happened in this case was freshclam updated the virus definitions, but when clamd tried to reload with the new definitions, it decided they were corrupt, and wouldn't start.

So the Service Router could not process any messages.

I renamed all the clamav virus definition files, and ran freshclam manually. This updated the definitions from scratch (I think) and I was able to start the Service router again.

What appears to have happened though is that all (some?) of the email that should have been processed during the period the Service Router wasn't working had been sent to the Corrupt Messages queue.

Is there any way to recover these messages ?

By the way I am a complete novice with Scalix.
using
Scalix server 11.0.2
clamav 0.90.1
Fedora Core 5





Also at the end of the other thread Subir asked the original poster:

Hi mmondok!

Can you start a new forum post, with the informations such as what Scalix version you
use, the ClamAV version installed on the server, OS you use, and result for the commands
below:
Quote:
omstat -a
omstat -s
ps ax | grep clam

Thanks,
Subir


I am connecting to the Scalix server remotely, through another remote connection through another remote connection, and can't get copy paste from there to here.
If this info is important I can get it next time I am in their office.

From the look of the output, its probably useless now as everything is running OK.

Thanks
Col

[coltect]

Found the answer here at viewtopic.php?t=4836&highlight=omresub

Now I noticed that the Corrupt Message queue had exactly 200 messages in it. This seems like too nice a round number to be a coincidence, so I reckon that somewhere there will be a setting limiting this queue to 200.

I'll look around and see what I can find, but if anyone can tell me where to look I'd appreciate it.

Thanks,
Col

[ScalixSupport]

Hi Col!

I am not aware of any settings that define the queue size, the only restriction that I could
see was in SAC, that had an option of setting for No. of Messages. You can find this
in SAC, choose the tab Server Info->from left panel choose the Queue Name, in the display
box find the option No. of Messages.

I am not sure if this is relevant, apart from this I am not aware of a property that restricts the
queue size.

Thanks,
Subir

[coltect]

Thanks Subir,
This option only seems to modify the amount of messages being displayed in SAC, not the actual length of the queue. I think that maybe there really was exactly 200 messages sent to the Corrupt Messages queue.

Back to my original problem, which was clamav update failing causing the service router to stop processing messages.

Is there a way to configure Scalix to use ClamAV and not experience this problem.

Thanks,
Col

[ScalixSupport]

Hey Col!

To resubmit the messages from error queue to the router queue, use omresub, this
should be done by the command:

Code: Select all

omresub -q error

you may or may not use -i (for interactive) option refer man page for details.

As soon as these messages are resubmitted, Service Router would try to send these
messages again. Yes since now ClamAV is integrated with Scalix Server, all these
messages would be scanned before they are sent.

I hope this is what you were looking for.

Is there a way to configure Scalix to use ClamAV and not experience this problem.

Until there is a down time for Service Router, messages get collected in queue, there is
no way to avoid this.

Thanks,
Subir

[coltect]

Thanks again Subir,
omresub -q error did the trick.

and Thanks to the whole Scalix team. Great software, very good documentation and from what I have experienced so far, great support

I'll start a new post re the problem with ClamAV.

Cheers,
Col

[ScalixSupport]

Hey Col!

Its great things are back on track. You are always welcome.

Thanks for the compliments, we really appreciate.

Regards,
Subir