5 Setting Up Garoon 3 After Upgrading
5.1 Executing an Update Program
5 Setting Up Garoon 3 After Upgrading
Depending on the version of Garoon before upgrading, some additional configurations may be required.
This chapter assumes the following configuration:
Item Example
Environment CGI directory on the Web server - On Windows : C:¥Inetpub¥scripts - On Linux : /var/www/cgi-bin/cbgrn Installation identifier cbgrn
Server configuration Application server - Server A - Server B
Database server Server C
5.1 Executing an Update Program
You must execute the update program "versionup3.csp" on all servers, if you have upgraded from Garoon 2.5.x to Garoon 3.1.0.
Execute the update program in the following order:
1. Database server 2. Application server
If you access Garoon 3 without executing "versionup3.csp", you will be prompted by a message to execute the program.
Tip
"versionup3.csp" will be deleted when the program is executed successfully.
•
On Windows
1
Stop Web servers on Server A and Server B.2
Start the database engine on Server A and Server B.From the Windows Start menu, select Control Panel > Administrative Tools > Services, and start the following services:
• Database engine: Cybozu_Database_Engine_5_0
3
Stop the scheduling service on Server C.From the Windows Start menu, select Control Panel > Administrative Tools > Services, and stop the following services:
• Scheduling service: Cybozu_Scheduling_Service_cbgrn (*1)
*1: cbgrn may be replaced by your installation identifier.
4
Launch the command prompt and change the current directory.Launch the command prompt on each server, and change the current directory to where "grn.exe" is located.
> cd C:¥Inetpub¥scripts¥cbgrn
5
Execute the update program from the command line.Execute the update program in the following order:
1. Server C
2. Server A and Server B
Execute the following command:
> grn_command.exe -f tmp¥versionup_scripts¥versionup3.csp
After executing the program on each server, you will be prompted to enter the database administrator's password (cbroot).
"Preparing programs and information for installation" on page 9.
6
Start the scheduling service on Server C.From the Windows Start menu, select Control Panel > Administrative Tools > Services, and start the following services:
• Scheduling service: Cybozu_Scheduling_Service_cbgrn (*1)
*1: cbgrn may be replaced by your installation identifier.
7
Stop the database engines on Server A and Server B.From the Windows Start menu, select Control Panel > Administrative Tools > Services, and stop the following services:
• Database engine: Cybozu_Database_Engine_5_0
8
Start Web servers on Server A and Server B.9
Check the command results.Open the log file to check the results.
Example: C:¥Inetpub¥scripts¥cbgrn¥versionup3_###.log - ### indicates a 3 digit number.
"Verifying Logs" on page 52.
On Linux
1
Start Web servers (httpd) on Server A and Server B.Execute the following command:
# /etc/init.d/httpd stop
2
Start the database engine on Server A and Server B.Execute the following command:
5.1 Executing an Update Program
# /etc/rc.d/init.d/cyde_5_0 start
3
Stop the scheduling service on Server C.Execute the following command:
# /etc/rc.d/init.d/cyss_cbgrn stop (*1)
*1: "cbgrn" is an installation identifier.
4
Move the current directory.Move the current directory on each server to where "grn.cgi" is located.
# cd /var/www/cgi-bin/cbgrn
5
Execute "versionup3.csp" from the command line.Execute the update program in the following order:
1. Server C
2. Server A and Server B
Execute the following command:
#./grn_command -f tmp/versionup_scripts/versionup3.csp
After executing the program on each server, you will be prompted to enter the database administrator's password (cbroot).
"Preparing programs and information for installation" on page 9.
6
Start the scheduling service on Server C.Execute the following command:
# /etc/rc.d/init.d/cyss_cbgrn start (*1)
*1: "cbgrn" may be replaced by your installation identifier.
7
Stop the database engines on Server A and Server B.Execute the following command:
# /etc/rc.d/init.d/cyde_5_0 stop
8
Start Web servers on Server A and Server B.Execute the following command:
# /etc/init.d/httpd start
9
Check the command results.Open the log file to check the results.
Example: /var/www/cgi-bin/cbgrn/versionup3_###.log
※"###" indicates a 3 digit number.
"Verifying Logs" on page 52.
Verifying Logs
Open the log files to verify that the update program has been executed successfully.
The log files contain the following information:
Report on the MySQL update
•
Report on the update of Garoon 3 data
•
Report on the update program execution
•
The logs are saved in the following files if Garoon 3 has been installed in the default directories:
OS Report on "versionup3.csp"
execution MySQL errors
Windows C:¥Inetpub¥scripts¥cbgrn¥
versionup3_###.log
C:¥Program
Files¥Cybozu¥mysql-5.0¥data¥
error.log Linux /var/www/cgi-bin/cbgrn/versionup3_###
.log
/usr/local/cybozu/mysql-5.0/data/error.lo g
### indicates a 3 digit number.
5.1 Executing an Update Program
Output of "versionup3_###.log
This example assumes that the log is exported on Windows.
[Tue, 13 Jul 2010 13:01:46 +0900] DB root password corrected!
[Tue, 13 Jul 2010 13:01:46 +0900] start upgrading mysqldb
[Tue, 13 Jul 2010 13:03:28 +0900] execute mysql_upgrade command finished.
[Tue, 13 Jul 2010 13:03:28 +0900] Looking for 'mysql.exe' as: C:¥Program Files¥Cybozu¥mysql-5.0¥bin¥mysql.exe
[Tue, 13 Jul 2010 13:03:28 +0900] Looking for 'mysqlcheck.exe' as:
C:¥Program Files¥Cybozu¥mysql-5.0¥bin¥mysqlcheck.exe
[Tue, 13 Jul 2010 13:03:28 +0900] Running 'mysqlcheck' with connection arguments: "--port=3770" "--host=127.0.0.1"
[Tue, 13 Jul 2010 13:03:28 +0900] Running 'mysqlcheck' with connection arguments: "--port=3770" "--host=127.0.0.1"
[Tue, 13 Jul 2010 13:03:28 +0900] cb_cbgrn._table_info OK
[Tue, 13 Jul 2010 13:03:28 +0900] cb_cbgrn.tab_cb_backupmode OK [. . .]
[Tue, 13 Jul 2010 13:03:30 +0900] end upgrading mysqldb
[Tue, 13 Jul 2010 13:03:33 +0900] 20100713 13:03:30 [INFO] Started updating.
20100713 13:03:30 [INFO] Started grn3.1.0_local_main.
20100713 13:03:30 [INFO] Updated the version number of system attribute.
3.1.0
20100713 13:03:30 [INFO] Successeed to delete table 'tab_grn_message_addressees'
[. . .]
20100713 13:03:33 [INFO] Finished updating.
[Tue, 13 Jul 2010 13:03:40 +0900] 20100713 13:03:34 [INFO] Started updating after installation.
20100713 13:03:34 [INFO] Deleting old time zone data.
[. . .]
20100713 13:03:40 [INFO] Finished updating after installation.
[Tue, 13 Jul 2010 13:03:40 +0900] start removing versionup scripts [Tue, 13 Jul 2010 13:03:40 +0900] end removing versionup scripts
a : Report on the MySQL update
b : Report on the update of Garoon 3 data c : Report on the "versionup3.csp" execution
a
b
c
Depending on your Garoon version, the update program may require the database to be fixed. The following log will be output after fixing the database even if the process is completed successfully:
mysql.help_category
error : Table upgrade required. Please do "REPAIR TABLE `help_category`" or dump/reload to fix it!
[. . .]
Repairing tables
mysql.help_category OK mysql.help_keyword OK mysql.help_topic OK
mysql.proc OK
mysql.time_zone_name OK
a : Status Note
If any status other than "INFO" or "OK" is output, follow the instruction in the message to troubleshoot.
•
For information on the cause of the errors, contact our official partners or your vendor.
Tip
The following errors require no action if the status is "OK":
•
Example of "mysql.general_log" (general query log table):
•
[Tue, 13 Jul 2010 13:03:30 +0900] mysql.general_log
[Tue, 13 Jul 2010 13:03:30 +0900] Error : You can't use locks with log tables.
[Tue, 13 Jul 2010 13:03:30 +0900] status : OK
Example of "mysql.slow_log" (slow query log table):
•
[Tue, 13 Jul 2010 13:03:30 +0900] mysql.slow_log
[Tue, 13 Jul 2010 13:03:30 +0900] Error : You can't use locks with log tables.
[Tue, 13 Jul 2010 13:03:30 +0900] status : OK MySQL errors
Temporary errors may occur while files and data of MySQL are gradually updated. The following error will be output in the "error.log" file even if the process is completed successfully:
Example error messages on Windows:
100713 14:46:05 InnoDB: Started; log sequence number 0 40732198
100713 14:46:06 [ERROR] Column count of mysql.db is wrong. Expected 22, found 20. Created with MySQL 50046, now running 50142. Please use mysql_upgrade to fix this error.
100713 14:46:06 [ERROR] mysql.user has no `Event_priv` column at position 29 100713 14:46:06 [ERROR] Event Scheduler: An error occurred when initializing system tables. Disabling the Event Scheduler.
100512 14:46:06 [Note] C:¥Program Files¥Cybozu¥mysql-5.0¥bin¥mysqld.exe:
ready for connections.
Version: '5.1.42-enterprise-cybozu' socket: '' port: 3770 MySQL Enterprise Server (Commercial) - Cybozu
a : Error messages Note
For information on the cause of the errors, contact our official partners or your vendor.
•
a
a