zmamavisdctl is not running

[swu]

New install of Zimbra 4.5.6 and basically going ok except I can't get clamav or spamassassin to run, or stay running:

zimbra@es-mail-01:/$ zmcontrol start
Host mail-01
Starting ldap...Done.
Starting logger...Done.
Starting mailbox...Done.
Starting antispam...Done.
Starting antivirus...Done.
Starting snmp...Done.
Starting spell...Done.
Starting mta...Done.

zimbra@es-mail-01:/$ zmcontrol status
Host mail-01
antispam Stopped
zmamavisdctl is not running
antivirus Stopped
zmamavisdctl is not running
zmclamdctl is not running


The two services are enabled in the GUI. I have restarted the server and manually tried to start the two services. Any help would be greatly appreciated.

Thx!

[hlribeiro]

This happened to me too.

[jholder]

Yep, it's a bug:
Bug 17992 - zmclamdctl is not running

It's probably really running, and if you give it some time, it will show up.

[swu]

Thanks for the bug list. I'm starting to test the server and the service still does not show as running and I can't send email out. In the postfix log:

Jul 3 14:59:49 es-mail-01 postfix/qmgr[4746]: BAC72AA007F: from=, size=613, nrcpt=1 (queue active)
Jul 3 14:59:49 es-mail-01 postfix/smtpd[11858]: disconnect from mail-01.emerson-school.org[10.10.10.18]
Jul 3 14:59:49 es-mail-01 postfix/smtp[11863]: connect to 127.0.0.1[127.0.0.1]: Connection refused (port 10024)
Jul 3 14:59:50 es-mail-01 postfix/smtp[11863]: BAC72AA007F: to=, relay=none, delay=1, status=deferred (connect to 127.0.0.1[127.0.0.1]: Connection refused)

It looks like amavisd really *isn't* running so postfix can't talk to the virus scanner (through amavisd) so nothing is going out.

mailman@es-mail-01:/etc$ telnet 127.0.0.1 10024
Trying 127.0.0.1...
telnet: Unable to connect to remote host: Connection refused
mailman@es-mail-01:/etc$

Any ideas on how to get this going? Thx!

[jholder]

What happens if you run
zmamavisdctl start
zmclamdctl start

[swu]

Odd. This is what I get when I su zimbra

zimbra@mail-01:/home/mailman$ zmamavisdctl start
zimbra@mail-01:/home/mailman$ The value of variable $myhostname is "mail-01", but should have been
a fully qualified domain name; perhaps uname(3) did not provide such.
You must explicitly assign a FQDN of this host to variable $myhostname
in amavisd.conf, or fix what uname(3) provides as a host's network name!

In my amavisd.conf file in /opt/conf (when I sudo vi amavisd.conf)

$myhostname = 'mail-01.emerson-school.org'; # must be a fully-qualified domain name!

Pinging mail-01.emerson-school.org [10.10.10.18] with 32 bytes of data:

Reply from 10.10.10.18: bytes=32 time<1ms TTL=63
Reply from 10.10.10.18: bytes=32 time<1ms TTL=63
Reply from 10.10.10.18: bytes=32 time<1ms TTL=63
Reply from 10.10.10.18: bytes=32 time<1ms TTL=63

Thx for any help!

[jholder]

So a couple things:
1) It's not a good idea to use ping for name resolution. It can lie. Use dig.
2) Check your hosts file to ensure it's correct
3) You shouldn't edit the amavisd.conf file. You should be editing the amavisd.conf.in file. The conf file is generated on the fly, which means it gets rewritten.

john

[jholder]

Also, can you update your profile with your version info? That would be great

[swu]

<< You shouldn't edit the amavisd.conf file. You should be editing the amavisd.conf.in file. The conf file is generated on the fly, which means it gets rewritten. >>

Thanks! That was it. The .in file did not have a FQDN, just the hostname. I set it to its FQDN and did a zmamavisdctl start and everything is up and running and my test messages are going out!

I've updated my profile with the version we are running. Thanks again!

[rickvv]

Using Release 4.5.6_GA_1044.FC5_20070706162711 FC5 FOSS edition

After a server restart, all of Zimbra seems to start up OK. Mail goes in and out, and collabration works.
But-
When i su to zimbra, and do a zmcontrol status, zmclamdctl is not running.
I can give it an explicit
zmamavisdctl start
zmclamdctl start, and it goes with no errors....but status still shows
antivirus stopped, and "zmclamdctl is not running".

Where should I look?
thanks
rick

PS-After starting the AV/AS services, then incoming mail gets caught in deferred, failing with 'too many retires', and something about port 3310(?)