Welcome to Knowage Q&A, where you can ask questions and receive answers from other members of the community.

Categories

Most popular tags

cockpit dataset error chart datasource installer datasets installation widget parameters business-model olap knowage knowage_7_1 integration login knowage_7_1-ce report-designer cross-navigation analyticaldriver

HTTP Status 404 – Not Found error after the installation - Scheduler has not been started. Use scheduler.start()

0 votes
1 view

Hello Guys!

I have successfully installed Knowage on my Ubuntu 20.04 and Tomcat 9. Configured everything based on the Youtube tutorial and the installation guides. However, I encountered a HTTP Status 404 – Not Found error after the installation.

The log says:

/Knowage-Server-CE/bin#./knowage_startup.sh
Waiting for MariaDB...
./knowage_startup.sh: 62: ./../../MariaDB/bin/mysqld_safe: not found
Starting Knowage...
Using CATALINA_BASE:   /usr/lib/Knowage-Server-CE
Using CATALINA_HOME:   /usr/lib/Knowage-Server-CE
Using CATALINA_TMPDIR: /usr/lib/Knowage-Server-CE/temp
Using JRE_HOME:        /usr
Using CLASSPATH:       /usr/lib/Knowage-Server-CE/bin/bootstrap.jar:/usr/lib/Kno             wage-Server-CE/bin/tomcat-juli.jar
Using CATALINA_OPTS:
Tomcat started.

Here is the additional logs from Catalina:

01-Mar-2022 08:41:30.007 SEVERE [Catalina-utility-2] org.apache.catalina.core.StandardContext.listenerStart Exception sending context initialized event to listener instance of class [it.eng.spagobi.utilities.locks.listeners.HazelcastContextListener]

com.hazelcast.core.HazelcastException: Port [5701] is already in use and auto-increment is disabled. Hazelcast cannot start.

at com.hazelcast.instance.DefaultAddressPicker.getPublicAddressByPortSearch(DefaultAddressPicker.java:139)

at com.hazelcast.instance.DefaultAddressPicker.pickAddress(DefaultAddressPicker.java:74)

at com.hazelcast.instance.Node.<init>(Node.java:157)

at com.hazelcast.instance.HazelcastInstanceImpl.<init>(HazelcastInstanceImpl.java:125)

at com.hazelcast.instance.HazelcastInstanceFactory.constructHazelcastInstance(HazelcastInstanceFactory.java:160)

at com.hazelcast.instance.HazelcastInstanceFactory.newHazelcastInstance(HazelcastInstanceFactory.java:143)

at com.hazelcast.instance.HazelcastInstanceFactory.newHazelcastInstance(HazelcastInstanceFactory.java:111)

at com.hazelcast.core.Hazelcast.newHazelcastInstance(Hazelcast.java:58)

at it.eng.spagobi.utilities.locks.DistributedLockFactory.getHazelcastInstance(DistributedLockFactory.java:61)

at it.eng.spagobi.utilities.locks.DistributedLockFactory.getDistributedMap(DistributedLockFactory.java:49)

at it.eng.spagobi.utilities.locks.listeners.HazelcastContextListener.contextInitialized(HazelcastContextListener.java:28)

at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4768)

at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5230)

at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)

at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:728)

at org.apache.catalina.core.ContainerBase.access$000(ContainerBase.java:129)

at org.apache.catalina.core.ContainerBase$PrivilegedAddChild.run(ContainerBase.java:150)

at org.apache.catalina.core.ContainerBase$PrivilegedAddChild.run(ContainerBase.java:140)

at java.security.AccessController.doPrivileged(Native Method)

at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:698)

at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:696)

at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1185)

at org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1933)

at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)

at java.util.concurrent.FutureTask.run(FutureTask.java:266)

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)

at java.lang.Thread.run(Thread.java:748)

01-Mar-2022 08:42:06.213 INFO [Catalina-utility-4] org.apache.catalina.core.ApplicationContext.log SessionListener: contextDestroyed()

01-Mar-2022 08:42:06.213 INFO [Catalina-utility-4] org.apache.catalina.core.ApplicationContext.log ContextListener: contextDestroyed()

01-Mar-2022 09:34:28.136 INFO [Catalina-utility-2] org.apache.catalina.core.ApplicationContext.log 2 Spring WebApplicationInitializers detected on classpath

01-Mar-2022 09:34:31.676 INFO [Catalina-utility-3] org.apache.catalina.core.ApplicationContext.log 2 Spring WebApplicationInitializers detected on classpath

This may be a simple fix for some. Any workarounds is appreciated. Thanks in advance!

Environment Knowage 8, Ubuntu 20.04, Tomcat 9
in Standard by (310 points)
edited by

Hi Irfan,

can you please attach the full knowage.log file?
Besides that, check that Port [5701] is not already in use.

Bye,
Marco

by (9.3k points)
Hi Marco,

Thank you for your response. The knowage.log is empty, however, catalina.log is not. Since there is a 8000 characters limit, do you have any email that I can send it to?

Regards,

Irfan
by (310 points)

The Q&A is a Community tool, therefore the whole thread should be visible to the community. If you cannot attach the file because of size limit, please use an external link such as codepen or similar tools.

For Direct support please consider our professional services knowage@eng.it.

by (9.3k points)
Hi Marco,

Please refer to this link https://codepen.io/hexobox/pen/RwxxOpv for a complete log. I posted both catalina.log and catalina.out.
by (310 points)
Hi Marco,

It is resolved! The application is now running. There was a slight conflict in the tomcat.

Thank you for your help.

Regards,

Irfan
by (310 points)

2 Answers

0 votes
 
Best answer
This issue has been resolved. The application is now running! Thank you everyone involved particularly Marco @mbalestri..
by (310 points)
selected by
0 votes
Any update on this question? We have a few demos that we would like to do and are stuck as we cannot get Knowage up.
by (200 points)

Dear kaptkanga,

the Q&A forum is powered by the community, short waiting times cannot be guaranteed. Professional support services are provided by KNOWAGE Labs only for Enterprise Edition user.

For more informations on professional support please write to knowage@eng.it.
 

Regards

by (140 points)
Powered by Question2Answer
...