>> then decided to rollback the >> BerkeleyDB to previous version > Upgrading the BerkleyDB engine version from version 4 to 5 > needs a conversion of all BDB databases - follow the oracle > roadmap or - export the db's, delete all BDB files and import the > DB's. ASSP will delete and recreate the BDB-ENV's (/tmpDB) > if a engine version is changed, but not the database files.
As I wrote, I wiped "tmpDB", "optRE" and "pb" ... sure, the spamdb and the other ones sitting inside the ASSP folder (aside from the graylist and ldaplist which I deleted) were left unchanged; I wonder if the remaining DBs (spamdb...) may be the cause of such an issue but, for sure, it would be a good idea having a ".pl" module to help migrating all the "bdb" files to the BDBv5 :) >> it will start listening and *accepting* > > This is not true! SMTP-connection will be accepted only by the > SMTP-Workers. The first transfer of a connection from Ok... pick a (quite busy) copy of ASSP on windows, stop it, fire up "process explorer" then start ASSP from cmd line (so that you'll have console logging), double click on the "perl" process and look at the TCP/IP panel :-) ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ Assp-test mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-test
