Knowledge Base >> Ignite Will Not Start

Ignite Will Not Start - Confio Article 1518

Confio Article: 1518 Published: Oct 23 2008 2:59 AM
Version: >=4.1 Topic(s): Install and Setup
Product(s): Ignite
Database(s): All

Ignite Will Not Start

 

If Ignite will not start (no Ignite web pages can be viewed), try the following steps.  To learn how to start Ignite, view the readme.txt file located in the top directory holding the Ignite files.

Note that this is a different situation than when a monitored database cannot be monitored.  If you are experiencing monitoring problems, click the 'Logs' link on the Ignite web page for more information.

If, after reading below, it isn't clear what the problem is, zip all the files in the logs directory (<Ignite Home>/iwc/tomcat/logs) and send them to support@confio.com.

 

Troubleshooting Steps

 

1. Check the logs located in <Ignite Home Directory>/iwc/tomcat/logs/

 

2. If the logs suggest that a port is already in use, change the Ignite settings to an available port.  Instructions are in knowledge base article support.confio.com/kb/1560.

 

3. If the logs suggest that not enough memory can be allocated, then install PI on another machine.

 

4. The error logs don't show errors but I cannot access Ignite from a browser:

  • Make sure you do not have a firewall that may prevent Ignite from listening on the ports that are specified in <Ignite Home>\tomcat\conf\server.xml. Also, make sure the client machine can ping the server running Ignite.

 

5. On Windows, I'm getting "[764  prunsrv.c] [error] Failed creating java" errors when I try to start up the "Ignite" Service:

  • Download JVM 1.5 from http://java.sun.com/ EVEN if you already have it installed.  Apparently, the registry entries can be messed up and installing or reinstalling this fixes the problem.

 

6. On Windows, when starting the Ignite Server, I get "'cscript' is not recognized as an internal or external command":

  • Make sure "c:\windows\system32" is in your path (Windows Script Host 5.6 or above is required).
  • If the startup.bat script fails, manually create a file called java_loc.txt and place it in the <Ignite Home>\iwc\tomcat\ignite_config directory. The file should contain one line with the full path to a java executable.  For example:
C:\Program Files\Java\j2re1.5.2_03\bin\java.exe

 

 

Tags: window ignite log troubleshooting not start startup starting crash unavailable browser memory Tomcat port cscript