404 error after installing knowage and access the main page.

Question

Hello guys,

After install the environment to run Knowage in Ubuntu 20.04 and with all services up the following message appears when acessing the main page at  http://localhost:8080/knowage:

HTTP Status 404 – Not Found

---

Type Status Report

Message /knowage/jsp/spago/jspError.jsp

Description The origin server did not find a current representation for the target resource or is not willing to disclose that one exists.

---

Can somebody help me?

Knowage 7.2.0

Ubuntu 20.04

Mysql 8.0.21

Java 1.8.0_261

Comments

Unfortunately I am getting the same error. Please can someone help?

---

Hi joelson.paulo,

Do you have errors in you log files?

Best regards,

Andrijana

---

these are the first lines in knowage.log:

[localhost-startStop-4] 15 set 2020 13:58:47,168 ERROR it.eng.spagobi.tools.scheduler.init.QuartzInitializer.determineDelegateClass:139 - Error determining Hibernate's dialect
javax.naming.NamingException: Unexpected exception resolving reference [Root exception is com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: Could not create connection to database server.]
    at org.apache.naming.NamingContext.lookup(NamingContext.java:856)
    at org.apache.naming.NamingContext.lookup(NamingContext.java:159)
    at org.apache.naming.NamingContext.lookup(NamingContext.java:827)
    at org.apache.naming.NamingContext.lookup(NamingContext.java:173)
    at org.apache.naming.factory.ResourceLinkFactory.getObjectInstance(ResourceLinkFactory.java:152)
    at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:321)
    at org.apache.naming.NamingContext.lookup(NamingContext.java:839)
    at org.apache.naming.NamingContext.lookup(NamingContext.java:159)
    at org.apache.naming.NamingContext.lookup(NamingContext.java:827)
    at org.apache.naming.NamingContext.lookup(NamingContext.java:159)
    at org.apache.naming.NamingContext.lookup(NamingContext.java:827)
    at org.apache.naming.NamingContext.lookup(NamingContext.java:159)
    at org.apache.naming.NamingContext.lookup(NamingContext.java:827)
    at org.apache.naming.NamingContext.lookup(NamingContext.java:173)
    at org.apache.naming.SelectorContext.lookup(SelectorContext.java:163)
    at javax.naming.InitialContext.lookup(InitialContext.java:417)
    at it.eng.spagobi.tools.scheduler.init.QuartzInitializer.determineDelegateClass(QuartzInitializer.java:119)
    at it.eng.spagobi.tools.scheduler.init.QuartzInitializer.init(QuartzInitializer.java:92)
    at it.eng.spago.init.InitializerManager.init(InitializerManager.java:79)
    at it.eng.spago.configuration.ConfigServlet.init(ConfigServlet.java:115)
    at org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1132)
    at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1079)
    at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:973)
    at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4885)
    at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5199)
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
    at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:743)
    at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:719)
    at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:714)
    at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1125)
    at org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1859)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    at java.lang.Thread.run(Thread.java:748)
Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: Could not create connection to database server.

.

.

.

I think some problem with MySql version... I will try to proced the downgrade from 8.0.2 to 5.7.31, after i'll  post here the result.

Others ideais i'm greatful

---

Dear

Knowage 7.2 is certified on MySQL 8, we are using this versione in a lot of projects.

I think the issue could be related to the JDBC driver version or the URL:

Try to put the serverTimezone option:

jdbc:mysql://< address > :3306/<database>?serverTimezone=UTC

let me know

Angelo

---

Sorry. I'm newbie. where should i set this serverTimezone option? and wich <database> option to use?

Answer 1

Copy the mysql-connector-java-8.0.22.jar in /Knowage-Server-CE/lib folder if it is not. it worked for me as by default there was mysql-connector-java-5.1.33-bin.jar

Comments

That's it. Thanks @viping Knowage is running Ok now.

I downloaded the mysql java connecter from here:

https://jar-download.com/artifacts/mysql/mysql-connector-java

Answer 2

I have the same configuration and the same problem with mysql server. Looks like there is something wrong with the mysql settings:

martin@Acer:~/Knowage/Knowage-Server-CE/bin$ ./knowage_startup.sh
Waiting for MariaDB...
./knowage_startup.sh: 62: ./../../MariaDB/bin/mysqld_safe: not found
Starting Knowage...

I have only installed mysql, MariaDB is not on my system.