Messaging Gateway

We've recently brought up the Brightmail appliance in a VM (version 7.7.0-17) and have noticed problems with outbound email.  The appliance was working fine for several days but then stopped sending any mail at all.  I received the following message:

filter-hub exited with 1 on xxxxxxxxxxxxxxx exit code: 0x0100

Storing data in /data/scanner/jobs/filter-hub/2008.12.22-13.51.03

Additionally, the following shows up in the scanner logs:

2008-12-22T19:51:56-05:00 (ERROR:2170.3072456384): [12064] The engine was unable to be kicked.

2008-12-22T19:51:56-05:00 (ERROR:4839.3072165568): [7063] kicker: can not open filter-hub pid file 

/data/scanner/jobs/filter-hub/filter-hub.pid: No such file or directory.

We are relatively new in dealing with the Brightmail product, but have used some of the older Symantec SMTP gateways very successfully.  Any help or ideas would be greatly appreciated.

Thanks.

Tom

Hey Tom,

I am probably going to suggest calling in to support to see what is happening. Generally with filter-hub crashes it would be something difficult to troubleshoot over a forum.

What I can gather though is what version of VM are you using? Just to make sure that it's one of the supported versions. Also you could try to clear messages from the queues and make sure that you are not having a crash on a single message. These are supposed to clear on their own after crashing the filter-hub multiple times, but just in case it could help you will want to make sure that nothing stuck in the queue is causing your issues.

I would go through the steps in the document below before calling in.

Title: 'How to collect data for a filter-hub crash on a Symantec Mail Security 8200 or 8300 series Appliance'

Sorry not so helpful so far. :smileysad:

- Tom

Thanks for the information...  We are running the VM on a test VMWare server with the intent on moving to one of our ESX clusters after a short test period.  I've given the VM plenty of disk space and memory, so I don't believe that is contributing to the problem.  The odd thing is that the queues are clear - there are no messages waiting to be delivered.  But if I look at the audit logs, there are a number of messages that show up with "deliver normally" as the action, but they show nothing for "delivered to:" or "delivery time".

Anyway, I will start gathing some information and see about contacting support.

Thanks for your time.

Tom

Depending on the actual version of VM Server that should work. Have you tried ESXi?

There are a couple reasons that we will get a delivered normally but no delivered to tag. Are you using LDAP integration? Because the drop invalid recipients can do this. Also sometimes a compliance policy can do this. Hopefully the debug logging that the earlier document asks for should show a reason.