Not receiving or sending email

[carnold]

I just installed zimbra beta 2 OSS on SLES10 and now no email is being received or sent (from an email client or the webui). I am able to login as a user and as the admin using the webui. Is this something with beta2 or something not set right?
Beta1 was working before i moved /opt to a new array and installed beta2.

[mmorse]

that's um...not very descriptive...could we get some error logs?

[carnold]

Looking at the logs in /opt/zimbra/log and /var/log/zimbra does not show anything. In fact, /var/log/zimbra is blank. what logs should i be looking at? Actually, the messages show they are being delivered just are not visible in the inbox. Check out the message from jchurchill titled "messages delivered but not visible in inbox". Here are the delivery logs:
Jul 31 21:21:41 mail postfix/smtp[27262]: 45773A842: to=, relay=127.0.0.1[127.0.0.1], delay=7, status=deferred (host 127.0.0.1[127.0.0.1] said: 451 4.5.0 Error in processing, id=27283-03, virus_scan FAILED: virus_scan: ALL VIRUS SCANNERS FAILED: ClamAV-clamd av-scanner FAILED: Too many retries to talk to 127.0.0.1:3310 (Can't connect to INET socket 127.0.0.1:3310: Connection refused) at (eval 69) line 269. (in reply to end of DATA command))
Jul 31 21:22:04 mail zmmailboxdmgr[27799]: status requested
Jul 31 21:22:04 mail zmmailboxdmgr[27799]: status OK
Jul 31 21:22:04 mail postfix/smtpd[27613]: disconnect from nf-out-0910.google.com[64.233.182.190]
Jul 31 21:22:22 mail postfix/smtpd[27613]: connect from ug-out-1314.google.com[66.249.92.175]
Jul 31 21:22:22 mail postfix/smtpd[27613]: D53BCA851: client=ug-out-1314.google.com[66.249.92.175]
Jul 31 21:22:23 mail postfix/cleanup[27634]: D53BCA851: message-id=
Jul 31 21:22:23 mail postfix/qmgr[27252]: D53BCA851: from=, size=1963, nrcpt=1 (queue active)
Jul 31 21:22:30 mail postfix/smtp[27264]: D53BCA851: to=, relay=127.0.0.1[127.0.0.1], delay=8, status=deferred (host 127.0.0.1[127.0.0.1] said: 451 4.5.0 Error in processing, id=27284-02, virus_scan FAILED: virus_scan: ALL VIRUS SCANNERS FAILED: ClamAV-clamd av-scanner FAILED: Too many retries to talk to 127.0.0.1:3310 (Can't connect to INET socket 127.0.0.1:3310: Connection refused) at (eval 69) line 269. (in reply to end of DATA command))
Jul 31 21:22:35 mail postfix/smtpd[27842]: connect from hostname here[xx.xx.xx.xx]
Jul 31 21:22:35 mail postfix/smtpd[27842]: setting up TLS connection from hostname here[xx.xx.xx.xx]
Jul 31 21:22:35 mail postfix/smtpd[27842]: TLS connection established from hostname here[xx.xx.xx.xx]: TLSv1 with cipher

[phoenix]

Originally Posted by carnold

Beta1 was working before i moved /opt to a new array and installed beta2.

How did you perform this little trick? Did you reset the permissions on the files after you moved them?

[phoenix]

I noticed in another thread you mention that the new location for /opt is on resierfs, is that correct? We do not recommend using reiserfs for the Zimbra file system, I would recommend that you change it as soon as you can.

[carnold]

Why would i change it from reiserfs? What are any pro's for changing it. It worked fine in beta1. Why is it not reccommended to have zimbra on reiserfs?

[phoenix]

Originally Posted by carnold

Why would i change it from reiserfs? What are any pro's for changing it. It worked fine in beta1. Why is it not reccommended to have zimbra on reiserfs?

It's not suitable for an enterprise file system (IIRC, there's some comments in the forums). I have seen corruption problems with it in some circumstances (usually power-failure) - we recommend ext3. If you continue using reiserfs, just make sure you backup fully and often.

[carnold]

Wel,, back to the original problem: mails seem to be moving both ways now I don't know why it took like 2 hrs but they seem to work now.
On the reiserfs front: what would it take to move from reiserfs to ext3? I really don't want to have to start over and neither do the users

[phoenix]

The most simple method is to backup your /opt/zimbra directory, wipe out your current filesystem and replace it with ext3, install a new copy (the same release in the new /opt directory ) of Zimbra, restore the /opt/zimbra directory over the recently installed one and reinstall zimbra again. Slightly long winded but it works fine.

Use the following rsync command to copy and restore and keep the corret file permissions:

# rsync backup
rsync -avrlHKpogDt /opt/zimbra/ /data/backup/zimbra

# rsync restore
rsync -avrlHKpogDt /data/backup/zimbra /opt/zimbra

obviously file location for your bacup is your preference.

[carnold]

I really don't want to do this but.........1 thing that would sway me is, if i do this (change the filesystem) will we see a "performance" increase?