To give a brief history<br>Running kolab 2.2.4. and it has been fine for a long time.<br>It's running under xen. Using debian lenny.<br>Xen is running on raid1 drives..<br>A day ago the power company did some work. Power was out a while but suspect there may been more happening :-(<br>
The only issue remaining that I know of it this issue.<br><br>I had a lot to fix but will stick to related parts.<br>Air conditioner died and room was 88 F. Fixed...<br>One of the disks died. Replaced it.<br>Did a fsck on all the partitions and saw no problems.<br>
There is a ups but suspect it did not shutdown properly.<br><br>I get errors like this in postfix log for each incoming mail:<br>Jun 05 19:53:10 <a href="http://mail.advocap.org">mail.advocap.org</a> <info> postfix/error[20404]: 6D19521A6AB: to=<<a href="mailto:mikeb@advocap.org">mikeb@advocap.org</a>>, relay=none, delay=16906, delays=16906/0.36/0/0.23, dsn=4.4.1, status=deferred (delivery temporarily suspended: connect to 127.0.0.1[127.0.0.1]: Connection refused)<br>
<br>My top suspect is that amavisd is not working.<br><br>When I look in rc.amavisd it looks like there should be a processes amavisd and amavis-milter but I see neither one.<br>There are not new entries in /kolab/var/amavisd since it died.<br>
<br>starting amavisd gives no errors.<br><br>It's partitioned like this:<br>df -h<br>Filesystem Size Used Avail Use% Mounted on<br>/dev/xvda2 4.0G 1.3G 2.5G 35% /<br>tmpfs 1.3G 0 1.3G 0% /lib/init/rw<br>
udev 10M 460K 9.6M 5% /dev<br>tmpfs 1.3G 4.0K 1.3G 1% /dev/shm<br>/dev/xvda3 508M 4.7M 503M 1% /tmp<br>/dev/xvda4 2.0G 858M 1.2G 43% /kolab<br>/dev/xvda5 4.0G 2.1G 2.0G 52% /kolab/var<br>
/dev/xvda6 50G 29G 22G 57% /kolab/var/imapd/spool<br><br>I do have backups.<br>I'm thinking of doing a fresh install on a vm to see how it's supposed to run.<br><br>Any suggestions?<br><br>John<br>
<br><br><br><br><br>