ISPConfig 3.0.2.2 released

[till]

ISPConfig 3.0.2.2 is available for download. This release fixes some bugs that were found in ISPConfig 3.0.2.1. For a detailed list of changes, please see the changelog section below.


Download
-----------------------------------------------------

The software can be downloaded here:

http://downloads.sourceforge.net/isp...gz?use_mirror=


Changelog
------------------------------------

http://bugtracker.ispconfig.org/inde...&status[]=


Known Issues:
--------------------------------------

Please take a look at the bugtracker:

http://bugtracker.ispconfig.org


BUG Reporting
--------------------------------------

Please report bugs to the ISPConfig bugtracking system:

http://bugtracker.ispconfig.org


Supported Linux Distributions
-----------------------------
- Debian Etch (4.0) - Squeeze (6.0)
- Ubuntu 7.10 - 10.04
- OpenSuSE 11 - 11.2
- CentOS 5.2 - 5.5
- Fedora 9 - 13


Installation
--------------------

The installation instructions for ISPConfig can be found here:

http://www.ispconfig.org/ispconfig-3/documentation/

or in the text files (named INSTALL_*.txt) which are inside the docs folder of the .tar.gz file.


Update
--------------------

To update existing ISPConfig 3 installations, run this command on the shell:

ispconfig_update.sh

select "stable" as update resource. The script will check if an updated version of ISPConfig 3 is available and then download the tar.gz and start the setup script.

Detailed instructions for making a backup before you update can be found here:

http://www.faqforge.com/linux/contro...e-ispconfig-3/

If the ISPConfig version on your server does not have this script yet, follow the manual update instructions below.



Manual update instructions
--------------------------

cd /tmp
wget http://www.ispconfig.org/downloads/ISPConfig-3-stable.tar.gz
tar xvfz ISPConfig-3-stable.tar.gz
cd ispconfig3_install/install
php -q update.php

[Franz]

on multiserver setup, first update "slave" servers?

[till]

Originally Posted by Franz

on multiserver setup, first update "slave" servers?

Yes, slave servers should be updated first.

[Hans]

Thanks a lot for this new version!
The upgrade from 3.0.2.1 to 3.0.2.2 went flawless on our Debian Lenny ISPConfig3 servers.

[Mike007]

CentOS 5.5 update without any problems, but log shows amavis error:

DKIM signature verification disabled, corresponding features not available. If not intentional, consider enabling it by setting: $enable_dkim_verification to 1, or explicitly disable it by setting it to 0 to quench down this warning.

same info after reboot system.

[racamet]

(excuse me for my poor English)

I upgraded from version 3.0.2.1 and I can not send or receive emails.

Webmin shows me the following error:
postfix: fatal: bad string length 0 <1: myhostname =


How can I fix this?

----

solved, had erased the name of the server in /etc/postfix/main.cfg

[guardian]

Originally Posted by Hans

The upgrade from 3.0.2.1 to 3.0.2.2 went flawless on our Debian Lenny ISPConfig3 servers.

Same here.

[rudolfpietersma]

When I try to update on my slave server it sais:

Possible problem with dumping the database. We will stop here. Please check the file existing_db.sqlroot@backup

What can be the reason for this?
Rudolf.

[till]

ISPConfig has a security mechanism that stops the update in case that the dumped sql database is too small to prevent that the update fauls due to problems with the databse dump. But sometimes this routines is wrong, e.g. if you have fery few records on the slave server.

Please check the file existing_db.sql which has been created in the install folder during the ispconfig update if it seems to contain all data records that you would expect on the server, or if it contains nothing or just a error message.

[rudolfpietersma]

I tried to locate the existing_db.sql file but it doesnt exist?