knowage with Docker Menu disabled

[MakremHammali]

after runnig knowage in docker i can't get the menu where data provider and profile management ..
any help please

[Ape-Decendent]

Hello, I have deployed also in docker swarm and server settings are not visible and further configuration cannot be done. Appreciate some help here.

[kerny3d]

Dear all,

which version of Knowage do you deploy? Could you attach to this issue your Docker log? Which user have you used to login on Knowage?

[Ape-Decendent]

@kerny3d we followed the instructions from https://github.com/KnowageLabs/Knowage-Server-Docker and below is the docker file we have. We are running in Swarm.

version: "3.5"

services:
knowage:
image: knowagelabs/knowage-server-docker:7.1
depends_on:
- knowagedb
ports:
- "8082:8080"
environment:
- DB_USER=iudx
- DB_PASS=iudx
- DB_DB=iudx
- DB_HOST=knowagedb
- DB_PORT=3306
- HMAC_KEY=iudx
- PUBLIC_ADDRESS=localhost
networks:
front:
aliases:
- knowage.docker
knowage:
mongo:
orion:
deploy:
replicas: 1
restart_policy:
condition: any

knowagedb:
image: mysql:5.7
environment:
- MYSQL_USER=iudx
- MYSQL_PASSWORD=iudx
- MYSQL_DATABASE=iudx
- MYSQL_ROOT_PASSWORD=iudx
networks:
- knowage
volumes:
- /opt/knowage-mysql:/var/lib/mysql
deploy:
replicas: 1
restart_policy:
condition: any

################################################################################

Networks

################################################################################
networks:

knowage:
    driver: overlay
    ipam:
        config:
            - subnet: 172.60.0.0/16
front:
    driver: overlay
    ipam:
        config:
            - subnet: 172.40.0.0/16
mongo:
    driver: overlay
    ipam:
        config:
            - subnet: 172.47.0.0/16
orion:
    driver: overlay
    ipam:
        config:
            - subnet: 172.41.0.0/16 

[kerny3d]

Dear @Ape-Decendent,

i've tried your YAML file on my local machine on Docker version 19.03.5, build 633a0ea838 and it works correctly.

Could you please get the logs from both MySql and Tomcat and upload them here?

Marco

[Ape-Decendent]

@kerny3d We are running this in Docker Swarm. I will try to pull some logs. I greatly appreciate your help.

[Ape-Decendent]

@Ape-Decendent @davide-zerbetto attaching the logs
knowage_docker_logs.txt
knowage_mysql_docker_logs.txt

[kerny3d]

@Ape-Decendent, quick question: which protocol are you using? HTTP or HTTPS?

[Ape-Decendent]

@kerny3d http

[kerny3d]

@Ape-Decendent, we are not able to replicate your case. On both docker-compose and swarm i see for biadmin:

And for biuser:

Could i ask you to start Knowage with the following docker-compose YAML file?

version: "3.5"

services:
  knowage:
    image: knowagelabs/knowage-server-docker:7.1
    depends_on:
      - knowagedb
    ports:
      - "8080:8080"
    volumes:
      - "./log4j.properties:/home/knowage/apache-tomcat-8.5.37/webapps/knowage/WEB-INF/classes/log4j.properties"
    environment:
      - DB_USER=iudx
      - DB_PASS=iudx
      - DB_DB=iudx
      - DB_HOST=knowagedb
      - DB_PORT=3306
      - HMAC_KEY=iudx
      - PUBLIC_ADDRESS=localhost
    networks:
      knowage:

  knowagedb:
    image: mysql:5.7
    environment:
      - MYSQL_USER=iudx
      - MYSQL_PASSWORD=iudx
      - MYSQL_DATABASE=iudx
      - MYSQL_ROOT_PASSWORD=iudx
    networks:
      - knowage
    volumes:
      - /opt/knowage-mysql:/var/lib/mysql

networks:
  knowage:
      driver: overlay
      ipam:
          config:
              - subnet: 172.60.0.0/16

Where the file log4j.properties is:

log4j.rootLogger=ERROR, 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.Spago=ERROR,CONSOLE
log4j.additivity.Spago=false

log4j.logger.it.eng=ERROR,CONSOLE
log4j.additivity.it.eng=false

log4j.logger.it.eng.spagobi.commons.utilities.messages=ERROR, CONSOLE
log4j.logger.it.eng.spagobi.commons.utilities.urls.WebUrlBuilder=ERROR, CONSOLE

log4j.logger.org.quartz=ERROR, CONSOLE
log4j.logger.org.hibernate=ERROR, CONSOLE
log4j.logger.org.jbpm=ERROR, CONSOLE
log4j.logger.com.hazelcast=ERROR, CONSOLE

log4j.logger.audit=INFO, CONSOLE
log4j.additivity.audit=false

log4j.logger.dataset.audit=ERROR, CONSOLE
log4j.additivity.dataset.audit=false

log4j.logger.it.eng.spagobi.tools.dataset.common.dataproxy.JDBCDataProxy=INFO, CONSOLE
log4j.additivity.it.eng.spagobi.tools.dataset.common.dataproxy.JDBCDataProxy=false
log4j.logger.it.eng.spagobi.tools.dataset.common.dataproxy.JDBCRedShiftDataProxy=INFO, CONSOLE
log4j.additivity.it.eng.spagobi.tools.dataset.common.dataproxy.JDBCRedShiftDataProxy=false

log4j.logger.it.eng.knowage.tools.servermanager=ERROR, CONSOLE
log4j.additivity.it.eng=false

Could you replicate your case again and extract the logs from your environment? We hope we can find the problem this time.

[kerny3d]

@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

log4j.logger.it.eng.spagobi.commons.utilities.messages=DEBUG, CONSOLE
log4j.logger.it.eng.spagobi.commons.utilities.urls.WebUrlBuilder=DEBUG, CONSOLE

log4j.logger.org.quartz=DEBUG, CONSOLE
log4j.logger.org.hibernate=DEBUG, CONSOLE
log4j.logger.org.jbpm=DEBUG, CONSOLE
log4j.logger.com.hazelcast=DEBUG, CONSOLE

#log4j.logger.com.hazelcast.cluster=debug
#log4j.logger.com.hazelcast.partition=debug
#log4j.logger.com.hazelcast.partition.InternalPartitionService=debug
#log4j.logger.com.hazelcast.nio=debug
#log4j.logger.com.hazelcast.hibernate=debug

log4j.logger.audit=INFO, CONSOLE
log4j.additivity.audit=false

log4j.logger.dataset.audit=DEBUG, CONSOLE
log4j.additivity.dataset.audit=false

log4j.logger.it.eng.spagobi.tools.dataset.common.dataproxy.JDBCDataProxy=DEBUG, CONSOLE
log4j.additivity.it.eng.spagobi.tools.dataset.common.dataproxy.JDBCDataProxy=false
log4j.logger.it.eng.spagobi.tools.dataset.common.dataproxy.JDBCRedShiftDataProxy=DEBUG, CONSOLE
log4j.additivity.it.eng.spagobi.tools.dataset.common.dataproxy.JDBCRedShiftDataProxy=false

log4j.logger.it.eng.knowage.tools.servermanager=DEBUG, CONSOLE
log4j.additivity.it.eng=false

I'm sorry for the error.

[Ape-Decendent]

@kerny3d here it goes

knowage-Container.txt
Knowagedb-container.txt

[kerny3d]

@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 or something like that. I think it's the 8082 port the real problem. In the meantime i will try your precise case because the first time i've updated you YAML because my 8082 was already used.

[kerny3d]

@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        3 months ago        2.25GB
...

[Ape-Decendent]

@kerny3d sorry for the late reply. I needed to focus on some other things.

I realized from docker logs that Tomcat is not happy with unsecured site. So I have put behind the reverse proxy with a sub-domain https://knowage.onion.fiware.city/knowage and seems to work

I am now configuring it.