digitalfondue / lavagna

Lavagna: issue tracker/project management tool
http://lavagna.io
GNU General Public License v3.0
636 stars 110 forks source link

HTTP ERROR 503 Service Unavailable #149

Closed JamesDandy closed 3 years ago

JamesDandy commented 3 years ago

I'm no SQL or Jetty expert by any means but I think I've done a good job of following the instructions at the link below. I cannot get past the setup phase because it does not appear that the service is running properly. I do get a few errors reported when running the batch file. If I use the Windows service it starts okay but I get the same issue with the 503 error.

the errors I see when launching from the batch file are:

In between those errors everything seems to be reporting fine and finally at the end it just says"... 41 more"

This is the point in the instructions that I cannot get past: https://help.lavagna.io/02-install/02-03-setup.html

syjer commented 3 years ago

Hi @JamesDandy

The main issue seems to be some kind of failure during the setup of the database:

Caused by: org.flywaydb.core.api.FlywayException: Schema lavagna contains a failed migration to version 1 !

At a certain point, it failed to "install" a sql script. What kind of database are you using?

If possible, could you please delete and recreate the database?

JamesDandy commented 3 years ago

Thank you...

I dropped the database, and re-ran the configuration query from the documentation. That gets me an error about a depreciated character set in the Mysql workbench, something about UTF8 vs UTF8MB4: "Please consider using UTF8MB4 with an appropriate collation instead."

Leaving it alone, I went ahead and ran one of the lavagna scripts. In the past, it would fail each time unless I removed the "&characterEncoding=utf-8" part of the datasource.url line: mysql://localhost:3306/lavagna?useUnicode=true&characterEncoding=utf-8

With this line in place as per the instructions, the scripts both will exit immediately so I had been removing this part. This time however, I replaced the ampersand with a semicolon and ran it, and it seems to be working correctly now, but I can't be sure that the semicolon was the correct choice.

syjer commented 3 years ago

which version of mysql are you using?

JamesDandy commented 3 years ago

Version 8.0.23 (MySql Community Server - GPL) running on Win64

JamesDandy commented 3 years ago

Per the suggestion by syjer, a complete drop and recreating the database worked BUT only after changing the ampersand to a semicolon to the datasource.url line in the xml file (and presumably in the .bat or .sh file) allowed the service to load and work properly.