History | Log In     View a printable version of the current page.  
   HOME       BROWSE PROJECT       FIND ISSUES   
    QUICK SEARCH:  
Issue Details (XML | Word | Printable)

Key: CIB-2276
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: 3 3
Assignee: Unassigned
Reporter: jkwong
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Pulse

Upgrade from 2.0.48 to 2.1.13 failed

Created: 12/Jan/10 09:26 PM   Updated: 19/Jan/10 05:16 PM
Component/s: Upgrade
Affects Version/s: 2.1.13
Fix Version/s: 2.1.14

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown
File Attachments: 1. Text File wrapper-01-09-2010.log (16 kb)
Environment:
CentOS release 5.3 x86_64
mysql-server-5.0.45-7.el5
jdk 1.6.0_15
mysql-connector-java-5.1.8-bin.jar


 Description  « Hide
Our company is trying to test version 2.1.13 to see if it'll solve our performance problems with Pulse due to large number of projects in our Pulse instance. The upgrade to 2.1.13 failed almost half way through to process with this error message in wrapper.log:

INFO | jvm 1 | 2010/01/09 15:12:43 | Jan 9, 2010 3:12:43 PM com.zutubi.pulse.master.util.monitor.JobRunner run
INFO | jvm 1 | 2010/01/09 15:12:43 | WARNING: Task 'Remove Trigger Data Map' is marked as failed. The following errors were recorded:
INFO | jvm 1 | 2010/01/09 15:12:43 | Exception: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'INTERVAL = 3600000, REPEAT_COUNT = -1, START_TIME = '2007-05-09' where ID = 1310' at line 1. Please see the log files for details.
INFO | jvm 1 | 2010/01/09 15:12:43 | com.zutubi.pulse.master.util.monitor.TaskException: Task 'Remove Trigger Data Map' is marked as failed. The following errors were recorded:
INFO | jvm 1 | 2010/01/09 15:12:43 | Exception: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'INTERVAL = 3600000, REPEAT_COUNT = -1, START_TIME = '2007-05-09' where ID = 1310' at line 1. Please see the log files for details.
INFO | jvm 1 | 2010/01/09 15:12:43 | at com.zutubi.pulse.master.util.monitor.JobRunner.run(JobRunner.java:90)
INFO | jvm 1 | 2010/01/09 15:12:43 | at com.zutubi.pulse.master.upgrade.DefaultUpgradeManager.executeUpgrade(DefaultUpgradeManager.java:129)
INFO | jvm 1 | 2010/01/09 15:12:43 | at com.zutubi.pulse.master.xwork.actions.upgrade.ExecuteUpgradeAction.execute(ExecuteUpgradeAction.java:32)
INFO | jvm 1 | 2010/01/09 15:12:43 | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
INFO | jvm 1 | 2010/01/09 15:12:43 | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
INFO | jvm 1 | 2010/01/09 15:12:43 | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
INFO | jvm 1 | 2010/01/09 15:12:43 | at java.lang.reflect.Method.invoke(Method.java:597)
INFO | jvm 1 | 2010/01/09 15:12:43 | at com.opensymphony.xwork.DefaultActionInvocation.invokeAction(DefaultActionInvocation.java:358)
INFO | jvm 1 | 2010/01/09 15:12:43 | at com.opensymphony.xwork.DefaultActionInvocation.invokeActionOnly(DefaultActionInvocation.java:218)
INFO | jvm 1 | 2010/01/09 15:12:43 | at com.opensymphony.webwork.interceptor.BackgroundProcess$1.run(BackgroundProcess.java:35)
INFO | jvm 1 | 2010/01/09 15:12:43 | at java.lang.Thread.run(Thread.java:619)


 All   Comments   Work Log   Change History      Sort Order:
[ Permlink | « Hide ]
Daniel Ostermeier - 13/Jan/10 12:03 AM
Hi,

The problem is in an upgrade task that attempts to interact with the LOCAL_TRIGGER table but that upgrade task is using the wrong schema.

Since you are just testing the performance updates, it is safe enough to skip the upgrade task that has failed. You can do so by:

#> update your PULSE_DATA/pulse.config.properties files build.number field to 201004003. It should be 201004002 when you open the file.

This will skip that task and continue the upgrade.

I am fixing this properly now so that when you do your final upgrade from 2.0.x to 2.1.x you will not encounter this problem again.

[ Permlink | « Hide ]
Daniel Ostermeier - 13/Jan/10 12:44 AM
fixed pending review

[ Permlink | « Hide ]
jkwong - 13/Jan/10 01:39 AM
Thanks for the fast feedback! Upgrade is now continuing... :)

[ Permlink | « Hide ]
jkwong - 19/Jan/10 12:15 PM
Update:

I've upgraded from 2.0.48 to 2.1.14 successfully on a development box, but it took

3 days 12 hours 6 mins 58 secs

:)

[ Permlink | « Hide ]
jason - 19/Jan/10 12:54 PM
Hi,

Thanks for letting us know, but obviously we'd like the upgrade to be faster than that! Did you notice by any chance which task(s) took so long?

[ Permlink | « Hide ]
jkwong - 19/Jan/10 01:12 PM
Are the times spent in each action recorded somewhere in the Pulse logs? Perhaps in wrapper.log? I didn't take notes on the times I saw on the web front end since I ran the upgrade over the weekend.

[ Permlink | « Hide ]
Daniel Ostermeier - 19/Jan/10 05:16 PM
The times taken are not recorded in the logs as yet, but we can add this to the next release. We already have an open issue to do something similar (CIB-2258) so will bring that forward.


Powered by Atlassian JIRA the Professional Issue Tracker. (Standard Edition, Version: 3.10.1-#261) - Bug/feature request - Contact Administrators