digitalfondue / lavagna

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

Mysql database creation not completed on fresh install #45

Closed ejouvin closed 7 years ago

ejouvin commented 7 years ago

Hello.

Just pickup the last commited files and do a fresh install. After configuration, I can conect on the application. But I have an error message displayed : "Connection failure. Please reload the page." This message is displayed on Chrome but not IE 11

But in fact, the trace show the following error : org.springframework.jdbc.BadSqlGrammarException: PreparedStatementCallback; bad SQL grammar [SELECT * FROM LA_PROJECT_MAIL_TICKET_CONFIG]; nested exception is com.mysql.jdbc.exceptions.jdbc4.MySQLS yntaxErrorException: Table 'lavagna.LA_PROJECT_MAIL_TICKET_CONFIG' doesn't exist

It seems that some scripts were not executed, from the 17th.

ejouvin commented 7 years ago

I just run all missing script.

It remove error message in logs, so fine.

But the message is still displayed on the page, and only on Chrome

syjer commented 7 years ago

@ejouvin , about the "Connection failure. Please reload the page." error, are you using a reverse proxy (ngnix?)

ejouvin commented 7 years ago

I think I should have create another issue for the error message after connection in fact.

I did test behind an Apache server. I will test with a direct connection on Tomcat. But I fact, the connection is OK, and I just have a message in the bottom left corner and only on Chrome

syjer commented 7 years ago

if it's behind a proxy, it's possible that you need to add additional configurations, as lavagna use websockets.

ejouvin commented 7 years ago

It seems to be that. I've just test to connect directly on tomcat and it works.

I remember to have seems an exampe of configuration in your doc (but I may be wrong...) but do not find it anymore.

ejouvin commented 7 years ago

I think we can close this issue.

The main topic, about the database creation, is solved. The other one is linked to the case #46 , when deployed behind an Apache server + SSL + for sure a problem of websocket configuration in Apache