Problems upgrading from 3.0 to 3.0.3

After upgrading, I can't log in - and the login prompt doesn't include the link to reset your password.  To upgrade, I simply shifted the link for youtrack.jar from the old to the new and restarted the service.  I'm running on Linux...  What am I missing?  I have a test instance that was running 3.0.2a and the upgrade there went fine.

10 comments
Comment actions Permalink

Also, swapping the old jar back in "fixes" things.

0
Comment actions Permalink

Looks like it can't find my config / settings.  If instead of just refreshing a page, I go to the root URL, it "logs me in as root" and ask me to do initial setup (license, etc).  I DO have a 50 seat license...

0
Comment actions Permalink

Hello, Jerry.

YouTrack stores its database in the ${user.home}/teamsysdata folder by default. So if you run YouTrack 3.0.3 not under the same user you used to run YouTrack 3.0 you'll face this issue. Of course you can always change the location of the database.

0
Comment actions Permalink

I doubt this is the problem - I'm simply doing the following:

stop the service with:

sudo service youtrack stop

sudo rm youtrack.jar

sudo -u youtrack ln -s youtrack-3.0.3.jar youtrack.jar

sudo service youtrack start

<can't log in>

sudo service youtrack stop

sudo rm youtrack.jar

sudo -u youtrack ln -s youtrack-3.0.jar youtrack.jar

sudo service youtrack start

<works fine again>

I may have the jar names not quite correct above as I'm at home...

0
Comment actions Permalink

Hm. Are you sure that you haven't modify youtrack-3.0.jar database location in the web.xml?

0
Comment actions Permalink

I don't think so but am not positive as I didn't set it up originally.  And my recollection is that the

DB appeared to be in the correct location based on the user home dir as you specified in your earlier post.  I will check

and get back to you.  Thanks for you help / suggestions.

0
Comment actions Permalink

Turns out, yes, the jar was modified.  I can see also database.backup.location was also changed.  Seems it would be better to make this config change via the command  line?  I assume I can also change the backup db location w/ -Ddatabase.backup.location=<path>?

0
Comment actions Permalink

Issue was database.location was hand modified inside the jar.

I instead modified wrapper.conf to include -D parameters for database.location and database.backup.location as this makes it easier for the next person to upgrade...

Thanks!

0
Comment actions Permalink

So as I understand you need to download jar, modify path in web.xml for it to point to the database location if it was modified and this is all there is for a successful update? If so, then too bad, that this process wasn't made automatically in youtrack. Would be great if it was.

0
Comment actions Permalink

If you haven't previously modified the path inside the jar, you don't need to do that.  If you haven't, all you need to do is:

stop the service

replace the jar

start the service

and you're done.  pretty sweet.

0

Please sign in to leave a comment.