The most recent version of this page is a draft.DiffThis version (2014/02/11 14:48) is a draft.
Approvals: 0/1

This is an old revision of the document!

Every services that composed LTU engine can be start stop or restart with the ltud commande.

Logged in as root: /etc/init.d/ltud [option]
options: start, stop, status all, restart

Monitor logs

Logs of the product are order by dangerousity state:

  • INFO : Regular logging information.
  • WARRNING : Potential issue, with no repercution on the product.
  • ERROR : Error in the product this could affect the product.
  • CRITICAL : Something is wrong, contact

When monitoring log, you can filter them according to this various levels.

How to forward logs to syslog

  • Edit your spec file located here: /opt/ltutengine/config/ltuengine.spec
  • Update and add these lines:
    "SYSLOG_LOG_FORMAT_PREFIX": "saas-standalone",
    "SYSLOG_LOG_FORMAT": "%(SYSLOG_LOG_FORMAT_PREFIX)s[%%(threadName)s] %%(levelname)s [%%(name)s::%%(funcName)s] %%(message)s",
    "ENABLE_SYSLOG": "True",

  • Then run this command to reload your configuration:
su - ltu
ltusaas-generate-config-files -i /opt/ltutengine/config/ltuengine.spec -m all -o /opt/ltu/env/run/cache/config
ltud restart all

All PID files can be found on /run/