0 votes
1 view

i cant connect to knowage CE (http://localhost:8080/knowage) and the tomcat log look like this:
        Caused by: java.sql.SQLNonTransientConnectionException: Socket fail to connect to host:localhost, port:3303. Connection refused: connect
                at org.mariadb.jdbc.internal.util.exceptions.ExceptionFactory.createException(ExceptionFactory.java:73)
                at org.mariadb.jdbc.internal.util.exceptions.ExceptionFactory.create(ExceptionFactory.java:183)
                at org.mariadb.jdbc.internal.protocol.AbstractConnectProtocol.createSocket(AbstractConnectProtocol.java:255)
                at org.mariadb.jdbc.internal.protocol.AbstractConnectProtocol.createConnection(AbstractConnectProtocol.java:519)
                at org.mariadb.jdbc.internal.protocol.AbstractConnectProtocol.connectWithoutProxy(AbstractConnectProtocol.java:1387)
                ... 36 more
        Caused by: java.net.ConnectException: Connection refused: connect
                at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method)
                at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:85)
                at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
                at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
                at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
                at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172)
                at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
                at java.net.Socket.connect(Socket.java:589)
                at org.mariadb.jdbc.internal.protocol.AbstractConnectProtocol.createSocket(AbstractConnectProtocol.java:250)
                ... 38 more
03-Nov-2021 09:00:48.468 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Catalina]
03-Nov-2021 09:00:48.469 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet engine: [Apache Tomcat/9.0.50]
03-Nov-2021 09:00:48.613 INFO [Catalina-utility-2] org.apache.catalina.startup.HostConfig.deployWAR Deploying web application archive [D:\Knowage\Knowage-Server-CE\webapps\knowage-api.war]
03-Nov-2021 09:01:00.232 INFO [Catalina-utility-3] org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.

2021-11-03 09:01:14.833  INFO 8376 --- [alina-utility-2] i.e.k.knowageapi.ServletInitializer      : Starting ServletInitializer using Java 1.8.0_111 on LAPTOP-9VKMB29M with PID 8376 (D:\Knowage\Knowage-Server-CE\webapps\knowage-api\WEB-INF\classes started by ACER in D:\Knowage\Knowage-Server-CE\bin)
2021-11-03 09:01:14.848  INFO 8376 --- [alina-utility-2] i.e.k.knowageapi.ServletInitializer      : The following profiles are active: production
2021-11-03 09:01:18.942  INFO 8376 --- [alina-utility-2] j.r.s.ResteasyEmbeddedServletInitializer : Finding JAX-RS Application classes
2021-11-03 09:01:18.953  INFO 8376 --- [alina-utility-2] j.r.s.ResteasyEmbeddedServletInitializer : Property resteasy.jaxrs.app.registration has not been set, JAX-RS Application classes registration is being set to AUTO
2021-11-03 09:01:18.963  INFO 8376 --- [alina-utility-2] j.r.s.ResteasyEmbeddedServletInitializer : Searching for JAX-RS Application Spring beans
2021-11-03 09:01:18.965  INFO 8376 --- [alina-utility-2] j.r.s.ResteasyEmbeddedServletInitializer : No JAX-RS Application Spring beans found
2021-11-03 09:01:18.966  INFO 8376 --- [alina-utility-2] j.r.s.ResteasyEmbeddedServletInitializer : No JAX-RS Application set via property resteasy.jaxrs.app.classes
2021-11-03 09:01:18.972  INFO 8376 --- [alina-utility-2] o.j.r.s.JaxrsApplicationScanner          : Scanning classpath to find JAX-RS Application classes
2021-11-03 09:01:19.102  INFO 8376 --- [alina-utility-2] j.r.s.ResteasyEmbeddedServletInitializer : JAX-RS Application class found: it.eng.knowage.knowageapi.RestApplication
2021-11-03 09:01:19.464  INFO 8376 --- [alina-utility-2] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.ws.config.annotation.DelegatingWsConfiguration' of type [org.springframework.ws.config.annotation.DelegatingWsConfiguration$$EnhancerBySpringCGLIB$$8dd5d4a8] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2021-11-03 09:01:19.620  INFO 8376 --- [alina-utility-2] .w.s.a.s.AnnotationActionEndpointMapping : Supporting [WS-Addressing August 2004, WS-Addressing 1.0]
2021-11-03 09:01:19.939  INFO 8376 --- [alina-utility-2] w.s.c.ServletWebServerApplicationContext : Root WebApplicationContext: initialization completed in 4932 ms
2021-11-03 09:01:20.583  INFO 8376 --- [alina-utility-2] o.s.boot.web.servlet.RegistrationBean    : Servlet it.eng.knowage.knowageapi.RestApplication was not registered (possibly already registered?)
2021-11-03 09:01:31.882  INFO 8376 --- [alina-utility-2] o.s.o.jpa.LocalEntityManagerFactoryBean  : Initialized JPA EntityManagerFactory for persistence unit 'knowage-gallery'
2021-11-03 09:01:32.682  INFO 8376 --- [alina-utility-2] o.s.o.jpa.LocalEntityManagerFactoryBean  : Initialized JPA EntityManagerFactory for persistence unit 'knowage-functioncatalog'
2021-11-03 09:01:33.433  INFO 8376 --- [alina-utility-2] o.s.o.jpa.LocalEntityManagerFactoryBean  : Initialized JPA EntityManagerFactory for persistence unit 'knowage-config'
2021-11-03 09:01:34.972  INFO 8376 --- [alina-utility-2] o.s.s.concurrent.ThreadPoolTaskExecutor  : Initializing ExecutorService 'applicationTaskExecutor'
2021-11-03 09:01:36.046  INFO 8376 --- [alina-utility-2] i.e.k.knowageapi.ServletInitializer      : Started ServletInitializer in 22.851 seconds (JVM running for 61.404)
2021-11-03 09:01:36.631  INFO 8376 --- [alina-utility-2] org.jboss.resteasy.resteasy_jaxrs.i18n   : RESTEASY002225: Deploying javax.ws.rs.core.Application: class it.eng.knowage.knowageapi.RestApplication
03-Nov-2021 09:01:36.663 INFO [Catalina-utility-2] org.apache.catalina.startup.HostConfig.deployWAR Deployment of web application archive [D:\Knowage\Knowage-Server-CE\webapps\knowage-api.war] has finished in [48,050] ms
03-Nov-2021 09:01:36.668 INFO [Catalina-utility-3] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory [D:\Knowage\Knowage-Server-CE\webapps\.install4j]

Environment Knowage 8_0_1 CE
asked Nov 3, 2021 in Installation by yasifaana (220 points) | 1 view
Hi,

could you list the step you took to make the installation? Are you using the embedded database or are you using an already installed one? Is it a MariaDB or a MySQL?

Thank you
Hi,

I'm using embedded MariaDB database

I followed the installation steps from the knowage youtube channel. and before i did the install i added JAVA_HOME to the computer settings and to the path to point to the existing java 16. I've tried changing to java version 1.8 but still can't.
does the installation have to be done as administrator? I mean "run as administrator"? because I installed it directly, not as administrator. is it because of that?
Hi,

"run as administrator" would help if you install Knowage in a directory where administrative privileges are needed: in our test environment we often use "C:\Knowage" and yes, we use "run as administrator".

From the log the problem is very simple: the embedded DB didn't start as expected. I don't think the DB is corrupted: as you say I think it's more related to the administrative privileges.

Could you do an installation with "run as administrator"?

I already uninstall it and then re-install using 'run as administrator', but its still the same.

and when I re-install the knowage, suddenly a dialog box appears. the dialog box looks like this:

I click 'retry' and then the installation is complete. Is it because of that?

Hi,

we also see that dialog on slow machines sometimes but clicking Retry it should end the installation successfully: the common problem is that the DB is not started yet.
Hi, im sorry for late reply.

this is how my MariaDB command looks like:

D:\knowage\MariaDB\bin>mysqld --defaults-file=knowage.ini --console
2021-11-19 19:57:17 0 [Note] mysqld (mysqld 10.3.30-MariaDB-log) starting as process 20728 ...
2021-11-19 19:57:17 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2021-11-19 19:57:17 0 [Note] InnoDB: Uses event mutexes
2021-11-19 19:57:17 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2021-11-19 19:57:17 0 [Note] InnoDB: Number of pools: 1
2021-11-19 19:57:17 0 [Note] InnoDB: Using SSE2 crc32 instructions
2021-11-19 19:57:17 0 [Note] InnoDB: Initializing buffer pool, total size = 2G, instances = 8, chunk size = 128M
2021-11-19 19:57:17 0 [Note] InnoDB: Completed initialization of buffer pool
2021-11-19 19:57:20 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2021-11-19 19:57:20 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2021-11-19 19:57:20 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2021-11-19 19:57:20 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\knowage_ce\hibernate_sequences.ibd' OS error: 203
2021-11-19 19:57:20 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2021-11-19 19:57:20 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/
2021-11-19 19:57:20 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``knowage_ce`.`hibernate_sequences``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue.
2021-11-19 19:57:20 0 [Warning] InnoDB: Ignoring tablespace for `knowage_ce`.`hibernate_sequences` because it could not be opened.
2021-11-19 19:57:20 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2021-11-19 19:57:20 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2021-11-19 19:57:20 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2021-11-19 19:57:20 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\knowage_ce\qrtz_blob_triggers.ibd' OS error: 203
2021-11-19 19:57:20 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2021-11-19 19:57:20 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/
2021-11-19 19:57:20 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``knowage_ce`.`qrtz_blob_triggers``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue.
2021-11-19 19:57:20 0 [Warning] InnoDB: Ignoring tablespace for `knowage_ce`.`qrtz_blob_triggers` because it could not be opened.



2021-11-19 19:57:27 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2021-11-19 19:57:27 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2021-11-19 19:57:27 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2021-11-19 19:57:27 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\knowage_ce\sbi_widget_gallery.ibd' OS error: 203
2021-11-19 19:57:27 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2021-11-19 19:57:28 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/
2021-11-19 19:57:28 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``knowage_ce`.`sbi_widget_gallery``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue.
2021-11-19 19:57:28 0 [Warning] InnoDB: Ignoring tablespace for `knowage_ce`.`sbi_widget_gallery` because it could not be opened.
2021-11-19 19:57:28 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2021-11-19 19:57:28 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2021-11-19 19:57:28 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2021-11-19 19:57:28 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\knowage_ce\sbi_widget_gallery_tags.ibd' OS error: 203
2021-11-19 19:57:28 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2021-11-19 19:57:28 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/
2021-11-19 19:57:28 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``knowage_ce`.`sbi_widget_gallery_tags``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue.
2021-11-19 19:57:28 0 [Warning] InnoDB: Ignoring tablespace for `knowage_ce`.`sbi_widget_gallery_tags` because it could not be opened.
2021-11-19 19:57:28 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2021-11-19 19:57:28 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2021-11-19 19:57:28 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2021-11-19 19:57:28 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\knowage_ce\sbi_ws_event.ibd' OS error: 203
2021-11-19 19:57:28 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2021-11-19 19:57:28 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/
2021-11-19 19:57:28 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``knowage_ce`.`sbi_ws_event``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue.
2021-11-19 19:57:28 0 [Warning] InnoDB: Ignoring tablespace for `knowage_ce`.`sbi_ws_event` because it could not be opened.
[Note] InnoDB: 128 out of 128 rollback segments are active.
[Note] InnoDB: Creating shared tablespace for temporary tables
[Note] InnoDB: Setting file '.\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
[Note] InnoDB: File '.\ibtmp1' size is now 12 MB.
[Note] InnoDB: Waiting for purge to start
[Note] InnoDB: 10.3.30 started; log sequence number 892453989; transaction id 991791
[Note] InnoDB: Loading buffer pool(s) from D:\knowage\MariaDB\data\ib_buffer_pool
[Note] Plugin 'FEEDBACK' is disabled.
[Note] Server socket created on IP: '::'.
[Note] Reading of all Master_info entries succeeded
[Note] Added new Master_info '' to hash table
[Note] mysqld: ready for connections.
Version: '10.3.30-MariaDB-log'  socket: ''  port: 3303  mariadb.org binary distribution
 [Note] InnoDB: Buffer pool(s) load completed at 211119 19:57:35

it's say that load completed? its already started or not?

Please log in or register to answer this question.

1,553 questions
1,017 answers
2,037 comments
2,567 users