How-to Updating ISPConfig in a Multiserver System

[vaio1]

Hi guys,

how have I to update ISPConfig to the newer version using the shell command in a multiserver configuration?

Thanks

[till]

I would update the master server first by running the ispconfig_update.sh command as root user on the shell. Select "stable" as update source and when the installer asks you to reconfigure permissions in the master database, choose yes.

For the slaves, use also the ispconfig_update.sh command as root on the shell, choose stable as update source. For the slaves you dont have to reconfigure the permissions in the master database as all permissions for all slaves ahd already been updated while you updated the master.

Before you do the update, you should make a backup of ispconfig and the /etc/ directory as described here:

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

[vaio1]

The Main Server has been updated correctly.
Then this is the result after db server update:

--------------------------------------------------------------------------------
 _____ ___________   _____              __ _         ____
|_   _/  ___| ___ \ /  __ \            / _(_)       /__  \
  | | \ `--.| |_/ / | /  \/ ___  _ __ | |_ _  __ _    _/ /
  | |  `--. \  __/  | |    / _ \| '_ \|  _| |/ _` |  |_ |
 _| |_/\__/ / |     | \__/\ (_) | | | | | | | (_| | ___\ \
 \___/\____/\_|      \____/\___/|_| |_|_| |_|\__, | \____/
                                              __/ |
                                             |___/ 
--------------------------------------------------------------------------------


>> Update  

Operating System: Debian 6.0 (Squeeze/Sid) or compatible

This application will update ISPConfig 3 on your server.
MySQL master server hostname [webserver.mydomain.com]: 

MySQL master server root username [root]: 

MySQL master server root password []: xxxxxxxxxx

MySQL master server database name [dbispconfig]: 

Checking ISPConfig database .. OK
Starting incremental database update.
ERROR 1060 (42S21) at line 1: Duplicate column name 'company_id'
Loading SQL patch file: /tmp/ispconfig3_install/install/sql/incremental/upd_0005.sql
Loading SQL patch file: /tmp/ispconfig3_install/install/sql/incremental/upd_0006.sql
ERROR 1060 (42S21) at line 1: Duplicate column name 'limit_mailmailinglist'
ERROR 1060 (42S21) at line 2: Duplicate column name 'limit_mailmailinglist'
ERROR 1051 (42S02) at line 19: Unknown table 'mail_mailman_domain'
Loading SQL patch file: /tmp/ispconfig3_install/install/sql/incremental/upd_0007.sql
ERROR 1060 (42S21) at line 2: Duplicate column name 'id_rsa'
ERROR 1060 (42S21) at line 3: Duplicate column name 'ssh_rsa'
ERROR 1060 (42S21) at line 4: Duplicate column name 'ssh_rsa'
Loading SQL patch file: /tmp/ispconfig3_install/install/sql/incremental/upd_0008.sql
ERROR 1060 (42S21) at line 64: Duplicate column name 'proxy_server'
ERROR 1060 (42S21) at line 65: Duplicate column name 'firewall_server'
ERROR 1060 (42S21) at line 66: Duplicate column name 'nginx_directives'
Loading SQL patch file: /tmp/ispconfig3_install/install/sql/incremental/upd_0009.sql
ERROR 1060 (42S21) at line 2: Duplicate column name 'login'
Loading SQL patch file: /tmp/ispconfig3_install/install/sql/incremental/upd_0010.sql
Loading SQL patch file: /tmp/ispconfig3_install/install/sql/incremental/upd_0011.sql
ERROR 1062 (23000) at line 49: Duplicate entry '1' for key 'PRIMARY'
ERROR 1062 (23000) at line 109: Duplicate entry '1' for key 'PRIMARY'
Loading SQL patch file: /tmp/ispconfig3_install/install/sql/incremental/upd_0012.sql
Loading SQL patch file: /tmp/ispconfig3_install/install/sql/incremental/upd_0013.sql
ERROR 1060 (42S21) at line 2: Duplicate column name 'source_read_all'
Loading SQL patch file: /tmp/ispconfig3_install/install/sql/incremental/upd_0014.sql
ERROR 1060 (42S21) at line 2: Duplicate column name 'limit_openvz_vm'
Loading SQL patch file: /tmp/ispconfig3_install/install/sql/incremental/upd_0015.sql
ERROR 1060 (42S21) at line 1: Duplicate column name 'ip_type'
ERROR 1060 (42S21) at line 2: Duplicate column name 'virtualhost_port'
ERROR 1060 (42S21) at line 3: Duplicate column name 'client_id'
ERROR 1060 (42S21) at line 4: Duplicate column name 'disablesieve'
ERROR 1060 (42S21) at line 5: Duplicate column name 'disablelda'
Loading SQL patch file: /tmp/ispconfig3_install/install/sql/incremental/upd_0016.sql
ERROR 1060 (42S21) at line 1: Duplicate column name 'limit_openvz_vm'
Loading SQL patch file: /tmp/ispconfig3_install/install/sql/incremental/upd_0017.sql
ERROR 1060 (42S21) at line 1: Duplicate column name 'web_php_options'
ERROR 1060 (42S21) at line 2: Duplicate column name 'ssh_chroot'
Loading SQL patch file: /tmp/ispconfig3_install/install/sql/incremental/upd_0018.sql
ERROR 1051 (42S02) at line 55: Unknown table 'mail_greylist'
Loading SQL patch file: /tmp/ispconfig3_install/install/sql/incremental/upd_0019.sql
ERROR 1060 (42S21) at line 1: Duplicate column name 'seo_redirect'
ERROR 1060 (42S21) at line 2: Duplicate column name 'server_id'
Loading SQL patch file: /tmp/ispconfig3_install/install/sql/incremental/upd_0020.sql
ERROR 1060 (42S21) at line 1: Duplicate column name 'php_fpm_use_socket'
Loading SQL patch file: /tmp/ispconfig3_install/install/sql/incremental/upd_0021.sql
ERROR 1060 (42S21) at line 1: Duplicate column name 'ipv6_address'
Loading SQL patch file: /tmp/ispconfig3_install/install/sql/incremental/upd_0022.sql
Loading SQL patch file: /tmp/ispconfig3_install/install/sql/incremental/upd_0023.sql
ERROR 1060 (42S21) at line 1: Duplicate column name 'python'
Loading SQL patch file: /tmp/ispconfig3_install/install/sql/incremental/upd_0024.sql
ERROR 1060 (42S21) at line 1: Duplicate column name 'pm_max_children'
Loading SQL patch file: /tmp/ispconfig3_install/install/sql/incremental/upd_0025.sql
Loading SQL patch file: /tmp/ispconfig3_install/install/sql/incremental/upd_0026.sql

[till]

Seems as if the database scheme on your db server was already newer then the scheme number that was stored in the server record of the master database for this slave was. Thats not a problem as the errors mean just that the table was already up to date, so this cause no harm. Maybe you restored one of the databases of the master or db server from a backup soe time ago or the databse scheme number was changed otherwise?

[vaio1]

I was scared!
I have not restore nothing, I have just update the system for the first time today, after your first post here. Can I continue to update the mail server?

thanks Till

[till]

If you did not receive any other errors after the ones that you posted, then the update was successfull.

Can I continue to update the mail server?

Yes.

[vaio1]

Hi again Till,

I get this error in the ISPConfig Mailserver Log:

Replication failed. Error: (mail_user) in MySQL server: (localhost) Unknown column 'autoresponder_subject' in 'field list'

What have I to do?

[till]

Seems as if you installed a svn development version on your master server and not a stable ispconfig version. The database field autoresponder_subject does not exist in iSPConfig 3.0.4.1, it exists only in svn trunk.

To fix that, you could either upgrade to svn trunk on the mailserver too, which I dont recommend fro production systems. As you cant downgrade the master, the best solution to fix this might be that you add a field named "autoresponder_subject" as varchar 255 in the table "mail_user" in the ispconfig database of the mail server with phpmyadmin.

[vaio1]

Hi Till,

I have not installed the SVN version I'm sure. I have installed the stable release not the svn.

The Master and Mail Server DB Version is 3.0.3.2

Connection id:    1013
Current database: dbispconfig

mysql> SELECT * FROM `sys_config`;
+-----------+-------+------------+---------+
| config_id | group | name       | value   |
+-----------+-------+------------+---------+
|         1 | db    | db_version | 3.0.3.2 |
+-----------+-------+------------+---------+
1 row in set (0.00 sec)

[till]

The field autoresponder_subject exists only in svn, it does not exist in 3.0.4.1. I just verified this by a fulltext search in the code, so ther is no doubt about that. So you have either the svn version installed or you added the field autoresponder_subject manually in your master database. The update or that you added this field can happend some time ago and not today.