Current view: XpoLog V6. Available: XpoLog V5 and XpoLog V7 (Latest)

Skip to end of metadata
Go to start of metadata


XpoLog services in not starting or starting and terminated immediately


Due to different reasons, it may be that some key XML configuration files were damaged which may cause such a problem. Review steps below for more information.

Root Cause Options:
  1. Service Level
    Make sure that there is no XpoLog service running in the background, if there is terminate all XpoLog related process and then try to run the service again.
  2. Application Server Level
    Go to XPOLOG_INSTALLATION/ServletContainer/conf/ and ensure the file tomcat-users.xml is not empty. Go to XPOLOG_INSTALLATION/ServletContainer/conf/Catalina/localhost/ and ensure the file logeye.xml is not empty.
    If any of these files are empty it mean the application server which is used to run XpoLog cannot start - contact with this diagnosis for further steps.
  3. Application Level
    Go to XPOLOG _INSTALLATION/conf/general/ and ensure the file Xpolog.xml is not empty. If it is empty, retrieve a valid Xpolog.xml file from the backup directory XPOLOG_EXTERNAL_CONF/temp/backup/LATEST_BACKUP_FILE/conf/general/
    replace the empty file and restart XpoLog.
  4. Infrastructure Level
    1. Storage
      Ensure that both XPOLOG _INSTALLATION and XPOLOG_EXTERNAL_CONF directories are not out of space. If so, allocate more space or advise XpoLog Support regarding other options to clear space.
    2. Users Permissions (commonly seen on UNIX based deployments)
      It may occur that there are permissions gaps between the user that ran or currently tries to run XpoLog and the user the that owns the directories and files in XPOLOG _INSTALLATION and/or XPOLOG_EXTERNAL_CONF directories.
      If that is the case, first stop XpoLog, then run the command 'chown -R XPOLOG_USER:XPOLOG_GROUP /XPOLOG_INSTALLATION', then run the command 'chown -R XPOLOG_USER:XPOLOG_GROUP /XPOLOG_EXTERNAL_CONF' and only then start XpoLog using the XPOLOG_USER
    3. Ports
      Ensure that XpoLog required ports are not occupied which blocks the execution of the XpoLog service. Most common port on a standalone installation of XpoLog is its shutdown port 8095. Additional ports can be reviewed in the System Requirements section.
      It is possible to modify ports in case default ports are already occupied and cannot be available at XPOLOG_INSTALLATION/ServletContainer/conf/server.xml.



XPOLOG _INSTALLATIONThe absolute path of the XpoLog installation directory

XPOLOG_EXTERNAL_CONFThe absolute path of the XpoLog configuration directory. To determine this path go to XpoLog Manager > Settings > General and check the configured path of XpoLog Configuration Directory, if it is empty then consider this parameter to be identical to XPOLOG_INSTALLATION (see value above)

XPOLOG_USER:XPOLOG_GROUP = The user and group which should be used to run XpoLog and have the required permissions on all folders and files in _INSTALLATION and XPOLOG_EXTERNAL_CONF