ZCS 3.1 upgrade
ZCS 3.1 upgrade
I've made a copy of opt/zimbra and installed the new version after stopping all services. I received the following ERROR:
Setting defaults...Setting defaults from existing config...Done
Upgrading from 3.0.1_GA_160 to 3.1.0_GA_328
Fri Apr 14 12:19:16 2006: Stopping zimbra services
Fri Apr 14 12:19:18 2006: Checking mysql status
Fri Apr 14 12:19:18 2006: Starting mysql
Fri Apr 14 12:19:18 2006: SELECT value FROM config WHERE name = 'db.version'
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/opt/zimbra/db/mysql.sock' (2)
Error while running
Daniel Bülow (12:35 PM) :
'/opt/zimbra/bin/mysql --user=zimbra --password=pRI1.tH4_GJH6kycTtxVPvqq1D --database=zimbra --batch --skip-column-names'. at /opt/zimbra/libexec/scripts/Migrate.pm line 134.
Setting defaults...Setting defaults from existing config...Done
Upgrading from 3.0.1_GA_160 to 3.1.0_GA_328
Fri Apr 14 12:19:16 2006: Stopping zimbra services
Fri Apr 14 12:19:18 2006: Checking mysql status
Fri Apr 14 12:19:18 2006: Starting mysql
Fri Apr 14 12:19:18 2006: SELECT value FROM config WHERE name = 'db.version'
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/opt/zimbra/db/mysql.sock' (2)
Error while running
Daniel Bülow (12:35 PM) :
'/opt/zimbra/bin/mysql --user=zimbra --password=pRI1.tH4_GJH6kycTtxVPvqq1D --database=zimbra --batch --skip-column-names'. at /opt/zimbra/libexec/scripts/Migrate.pm line 134.
ZCS 3.1 upgrade
I got the exact same error just now. The only difference that I have is that I'm upgrading from 3.0.0 to 3.1.0. I'm using Fedora Core 4:
Upgrading from 3.0.0_GA_156 to 3.1.0_GA_328
Upgrading from 3.0.0_GA_156 to 3.1.0_GA_328
ZCS 3.1 upgrade
I just got:
Upgrading from 3.1.0_GA_279 to 3.1.0_GA_328
Fri Apr 14 09:15:35 2006: Stopping zimbra services
Fri Apr 14 09:15:36 2006: Checking mysql status
Fri Apr 14 09:15:36 2006: Starting mysql
Fri Apr 14 09:15:36 2006: SELECT value FROM config WHERE name = 'db.version'
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/opt/zimbra/db/mysql.sock' (2)
Error while running '/opt/zimbra/bin/mysql --user=zimbra --password=... --database=zimbra --batch --skip-column-names'. at /opt/zimbra/libexec/scripts/Migrate.pm line 134.
With opensuse 10. Where do I go from here?
Upgrading from 3.1.0_GA_279 to 3.1.0_GA_328
Fri Apr 14 09:15:35 2006: Stopping zimbra services
Fri Apr 14 09:15:36 2006: Checking mysql status
Fri Apr 14 09:15:36 2006: Starting mysql
Fri Apr 14 09:15:36 2006: SELECT value FROM config WHERE name = 'db.version'
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/opt/zimbra/db/mysql.sock' (2)
Error while running '/opt/zimbra/bin/mysql --user=zimbra --password=... --database=zimbra --batch --skip-column-names'. at /opt/zimbra/libexec/scripts/Migrate.pm line 134.
With opensuse 10. Where do I go from here?
ZCS 3.1 upgrade
And now I got:
$ sudo ./zmsetup.pl
Password:
Checking java version...1.5 found
Operations logged to /tmp/zmsetup.log.28406
Setting defaults...Setting defaults from existing config...Done
Upgrading from 3.0.1_GA_160 to 3.1.0_GA_328
Fri Apr 14 11:18:59 2006: Stopping zimbra services
Fri Apr 14 11:20:38 2006: Stop failed - exiting
UPGRADE FAILED - exiting
$ sudo ./zmsetup.pl
Password:
Checking java version...1.5 found
Operations logged to /tmp/zmsetup.log.28406
Setting defaults...Setting defaults from existing config...Done
Upgrading from 3.0.1_GA_160 to 3.1.0_GA_328
Fri Apr 14 11:18:59 2006: Stopping zimbra services
Fri Apr 14 11:20:38 2006: Stop failed - exiting
UPGRADE FAILED - exiting
-
- Ambassador
- Posts: 4558
- Joined: Fri Sep 12, 2014 9:52 pm
ZCS 3.1 upgrade
Seems like MySQL is not starting. Can you try to start it manually?
ZCS 3.1 upgrade
check the logs for mysql to see what's up:
/opt/zimbra/log/my*
/opt/zimbra/log/my*
ZCS 3.1 upgrade
Here's the end of my mysqld.log
060414 8:48:13 InnoDB: Shutdown completed; log sequence number 0 6822185
060414 8:48:13 [Note] /opt/zimbra/mysql/bin/mysqld: Shutdown complete
060414 08:48:13 mysqld ended
060414 09:16:12 mysqld started
060414 9:16:14 InnoDB: Started; log sequence number 0 6822185
/opt/zimbra/mysql/bin/mysqld: ready for connections.
Version: '4.1.16-standard-log' socket: '/opt/zimbra/db/mysql.sock' port: 7306 MySQL Community Edition
- Standard (GPL)
And I can see that its currently listening:
root@hail zcs]# netstat -an | grep 7306
tcp 0 0 127.0.0.1:7306 0.0.0.0:* LISTEN
060414 8:48:13 InnoDB: Shutdown completed; log sequence number 0 6822185
060414 8:48:13 [Note] /opt/zimbra/mysql/bin/mysqld: Shutdown complete
060414 08:48:13 mysqld ended
060414 09:16:12 mysqld started
060414 9:16:14 InnoDB: Started; log sequence number 0 6822185
/opt/zimbra/mysql/bin/mysqld: ready for connections.
Version: '4.1.16-standard-log' socket: '/opt/zimbra/db/mysql.sock' port: 7306 MySQL Community Edition
- Standard (GPL)
And I can see that its currently listening:
root@hail zcs]# netstat -an | grep 7306
tcp 0 0 127.0.0.1:7306 0.0.0.0:* LISTEN
-
- Ambassador
- Posts: 4558
- Joined: Fri Sep 12, 2014 9:52 pm
ZCS 3.1 upgrade
Maybe a timing issue and it tried to access MySQL before it came up. You can try to re-run the upgrade.
ZCS 3.1 upgrade
sure... I'm rerunning the install..sh right now. I should mention that I saw this when rerunning it. I'm assuming that this is something that will probably change in future releases:
The system will be modified. Continue? [N] Y
Shutting down zimbra mail
Backing up ldap
/opt/zimbra/conf/slapd.conf: line 66: "attr" is deprecated (and undocumented); use "attrs" instead.
/opt/zimbra/conf/slapd.conf: line 73: "attr" is deprecated (and undocumented); use "attrs" instead.
/opt/zimbra/conf/slapd.conf: line 87: "attr" is deprecated (and undocumented); use "attrs" instead.
bdb_db_open: Warning - No DB_CONFIG file found in directory /opt/zimbra/openldap-data: (2)
Expect poor performance for suffix .
# no data for entry id=01000000
The system will be modified. Continue? [N] Y
Shutting down zimbra mail
Backing up ldap
/opt/zimbra/conf/slapd.conf: line 66: "attr" is deprecated (and undocumented); use "attrs" instead.
/opt/zimbra/conf/slapd.conf: line 73: "attr" is deprecated (and undocumented); use "attrs" instead.
/opt/zimbra/conf/slapd.conf: line 87: "attr" is deprecated (and undocumented); use "attrs" instead.
bdb_db_open: Warning - No DB_CONFIG file found in directory /opt/zimbra/openldap-data: (2)
Expect poor performance for suffix .
# no data for entry id=01000000
-
- Ambassador
- Posts: 4558
- Joined: Fri Sep 12, 2014 9:52 pm
ZCS 3.1 upgrade
[quote user="hootjr29"]sure... I'm rerunning the install..sh right now. I should mention that I saw this when rerunning it. I'm assuming that this is something that will probably change in future releases:
The system will be modified. Continue? [N] Y
Shutting down zimbra mail
Backing up ldap
/opt/zimbra/conf/slapd.conf: line 66: "attr" is deprecated (and undocumented); use "attrs" instead.
/opt/zimbra/conf/slapd.conf: line 73: "attr" is deprecated (and undocumented); use "attrs" instead.
/opt/zimbra/conf/slapd.conf: line 87: "attr" is deprecated (and undocumented); use "attrs" instead.
bdb_db_open: Warning - No DB_CONFIG file found in directory /opt/zimbra/openldap-data: (2)
Expect poor performance for suffix .
# no data for entry id=01000000[/QUOTE]
Please file this as a bug.
The system will be modified. Continue? [N] Y
Shutting down zimbra mail
Backing up ldap
/opt/zimbra/conf/slapd.conf: line 66: "attr" is deprecated (and undocumented); use "attrs" instead.
/opt/zimbra/conf/slapd.conf: line 73: "attr" is deprecated (and undocumented); use "attrs" instead.
/opt/zimbra/conf/slapd.conf: line 87: "attr" is deprecated (and undocumented); use "attrs" instead.
bdb_db_open: Warning - No DB_CONFIG file found in directory /opt/zimbra/openldap-data: (2)
Expect poor performance for suffix .
# no data for entry id=01000000[/QUOTE]
Please file this as a bug.