Marco Libanori

@Ape-Decendent, please use the following log4j.properties: ``` log4j.rootLogger=DEBUG, CONSOLE log4j.appender.CONSOLE=org.apache.log4j.ConsoleAppender log4j.appender.CONSOLE.Target=System.out log4j.appender.CONSOLE.layout=org.apache.log4j.PatternLayout log4j.appender.CONSOLE.layout.conversionPattern=%d{yyyy-MM-dd HH:mm:ss,SSS} %-5p - %m%n # Logger... #log4j.logger.org.hibernate=WARN #log4j.logger.org.hibernate.SQL=DEBUG, knowage, CONSOLE #log4j.logger.org.hibernate.type=TRACE, knowage, CONSOLE log4j.logger.Spago=DEBUG,CONSOLE log4j.additivity.Spago=false log4j.logger.it.eng=DEBUG,CONSOLE log4j.additivity.it.eng=false...

@Ape-Decendent, could you please see in the console browser, in the network panel, if there are some XHR call in error? Because, now, i don't think it's a DB problem...

@Ape-Decendent, could you also check the id of your image of Knowage? You can use: ``` $ docker image ls REPOSITORY TAG IMAGE ID CREATED SIZE ... knowagelabs/knowage-server-docker 7.1 0909b96f5d94...

Hi Robert, thank you for you report: we have seen the same problem in our test environments and you are working on it. As you can guess, the -SNAPSHOT version...

Hi Robert, if you pull the new 8.0.0-SNAPSHOT I think we have resolved the problem.

Logs from knowager_1 and knowagepython_1 are perfectly normal because of the health checks in [Python's Dockerfile](https://github.com/KnowageLabs/Knowage-Server-Docker/blob/master/Knowage-Python-Docker/Dockerfile#L32) and [R's Dockerfile](https://github.com/KnowageLabs/Knowage-Server-Docker/blob/master/Knowage-R-Docker/Dockerfile#L30). About the UI, you are using a custom hostname different from...

Thank you for all your report. Please remember that the 8.0.0-SNAPSHOT version is a development version and we use it to discover and work on issues. And please remember that...

I would suggest you the last non-SNAPSHOT major tag like 7.4 then: `docker pull knowagelabs/knowage-server-docker:7.4`

Hi, the 8.1.0-SNAPSHOT it's in development stage. I suggest you to use the latest stable version 7.4 or wait for the 8.0 in the next weeks. In the meantime, I...

Hi @chendelin1982, I confirm the issue: we have some problem with the dependencies in our requirements.txt; I think we need to specify some secondary level dependencies.