Strange as I can see all the output on my web browser. Anyway ... Thanks for the rapid response, but I managed to figure it out. I added some extra tracing to the syncdb.py file to print out the actual SQL statements. I then copied and pasted these into a mysql session and got the same error, so the problem was with MySQL. It turns out that when I removed the original mysql-server package, the data-files for the baruwa database were kept, so I removed the package once more, then removed all the mysql data files from /var/lib/mysql and reinstalled the mysql-server package.
"baruwa-admin syncdb --noinput" now worked but the migrate produced lots of errors about tables already existing. I wasn't too sure whether this was expected or not, but I decided to press on regardless. To my surprise, it looked like it was working (after re-editing the apache stuff) Apart from a few changes to the baruwa.conf file to comment out the signature stuff (to match the working installation I was using as reference). So I am happily running v1.1.1 and am v impressed so far. Unless there are pressing reasons, I will not upgrade to 1.1.2, although I could always build a new VMware image and build a new MailScanner setup side by side, only swapping over when I am happy things are working Thanks for reading and replying -- View this message in context: http://baruwa-users-list.963389.n3.nabble.com/Corrupted-install-v1-1-1-cannot-syncdb-tp4025247p4025249.html Sent from the Baruwa users list mailing list archive at Nabble.com. _______________________________________________ Keep Baruwa FREE - http://pledgie.com/campaigns/12056
