I am in the process of testing a fix and will post my results as soon as they are completed.
As I show (and mention above), the first installed failed becuase the zimbra-core rpm had a problem with the internal md5sum being incorrect, most probably caused by the untar of the downloaded tarball rather than the download itself (I downloaded twice and checksums were same for both downloads). The rpm error did not print to screen, it was only when I invoked the rpm command manually did it croak to screen. Printing these errors to terminal needs fixing IMO.
I keep saying and lets re-iterate, the biggest issue here is that I did not backup outside of /opt/zimbra and that is my fault, probably because my dependancy grew on zimbra without even realising it and was too busy in my day job. The dact my dependancy grew on Zimbra as did my family and friends is the fault of Zimbra as it shows how good the product is ;-)
But, the fact it deleted without prompt is the 2nd problem which is big in my opinion and quite simple to invoke. Simply removing the packages of your installation via rpm:
rpm -e zimbra-ldap zimbra-logger zimbra-mta zimbra-snmp zimbra-store zimbra-apache zimbra-spell zimbra-core
and then running install.sh will confuse the installer into thinking it is a new install and then simply delete /opt/zimbra/
I'll post back shortly with my fix results.
David.
Last edited by DGS_David : 10-21-2006 at 11:14 AM.
|