Problems Upgrading from 2.1 using MySQL

I am having problems upgrading from a 2.1 production version to the most recent EAP (5725). I had this problem with 5644, but eventually got it right.

The error message in catalina.out is:

org.jdom.input.JDOMParseException: Error on line 6 of document file:/home/dev/.BuildServer/config/Apex/project-config.xml: Element type "vcs-roots" must be declared.

Here is what I've done (this is for a test system on a different box).

- Synced .BuildServer/config from the production system.
- Changed database.properties to point to a different database.
- Wipe the new database. No schema. No rows.
- Move .BuildServer/system out of the way.
- Create a new .BuildServer/system and copy version.data and license.keys to it.
- Start the server.

The contents of the version.dat are:

#Fri Oct 12 15:24:17 PDT 2007
version.com.mysql.jdbc.Driver=124

I've tried with 117 and 127, also. And my original version has a third line:

version=78

No luck in any variation.

--Tim

3 comments

I guess you should bring back your database, take version.dat from your
backup and try again. TeamCity did not run any converters on your
configuration files because it did not find a database and decided that no
conversion is required (this is a known issue).

--
Pavel Sher
Software Developer
JetBrains, Inc.
http://www.jetbrains.com
"Develop with pleasure!"



"Tim McNerney" <intellij@oneofus.org> wrote in message
news:15206278.1192228789250.JavaMail.itn@is.intellij.net...
>I am having problems upgrading from a 2.1 production version to the most
>recent EAP (5725). I had this problem with 5644, but eventually got it
>right.
>

The error message in catalina.out is:

>

org.jdom.input.JDOMParseException: Error on line 6 of document
file:/home/dev/.BuildServer/config/Apex/project-config.xml: Element type
"vcs-roots" must be declared.

>

Here is what I've done (this is for a test system on a different box).

>

- Synced .BuildServer/config from the production system.
- Changed database.properties to point to a different database.
- Wipe the new database. No schema. No rows.
- Move .BuildServer/system out of the way.
- Create a new .BuildServer/system and copy version.data and license.keys
to it.
- Start the server.

>

The contents of the version.dat are:

>

#Fri Oct 12 15:24:17 PDT 2007
version.com.mysql.jdbc.Driver=124

>

I've tried with 117 and 127, also. And my original version has a third
line:

>

version=78

>

No luck in any variation.

>

--Tim



0

That worked.

What I was trying to do as you'd guess is to set up a test system for the EAP so that I could make sure everything was working, but I wanted to start with a clean database with the existing configuration. I guess I could do that by upgrading with a copy of the database and then stopping, deleting the database and restarting, thus keeping the upgraded config files and creating a new database.

--Tim

0

I understand. We have plans to fix such behaviour of our converters in the
future, but probably not in the 3.0 version.

--
Pavel Sher
Software Developer
JetBrains, Inc.
http://www.jetbrains.com
"Develop with pleasure!"



"Tim McNerney" <intellij@oneofus.org> wrote in message
news:32281275.1192465968522.JavaMail.itn@is.intellij.net...

That worked.

>

What I was trying to do as you'd guess is to set up a test system for the
EAP so that I could make sure everything was working, but I wanted to
start with a clean database with the existing configuration. I guess I
could do that by upgrading with a copy of the database and then stopping,
deleting the database and restarting, thus keeping the upgraded config
files and creating a new database.

>

--Tim



0

Please sign in to leave a comment.