The Enhanced Event Logging System

Setting the debug level for eelsd

If you experience difficulties in getting EELS to start, or part of your configuration does not work as expected, you may want to switch on debugging. EELS supports up to four levels of debugging for eelsd(1Meels) as well as up to four levels of debugging for each RTLSP process.

To start EELS in debugging mode, you must shutdown EELS and then restart it manually specifying the debug flags on the command line. Use the following syntax when specifying debug flags for eelsd.

eelsd [-d [-d [-d [-d]]]] [-o "-d [-d [-d [-d]]]"]

The -o option specifies that the following options should be passed directly to any RTLSP processes spawned by eelsd. If you need to specify multiple -d options for RTLSPs, enclose them in double quotes. For example, to start eelsd with a debug level of 3 and a debug level of 2 for RTLSPs, use the following command:

/etc/eels/bin/eelsd -d -d -d -o "-d -d"

NOTE: Under normal circumstances, debug level 1 just for eelsd should provide you all the information you require to track down your problems.

Under normal conditions, when you close down EELS, everything related to EELS should also closedown correctly. However, under certain circumstances, your database may not close down correctly and it will be up to you to correct the situation before starting eelsd in debug mode. Take the following steps to check the consistency of the EELS database and then start eelsd in basic debug mode:

Log in as root
Shutdown the current EELS session

/etc/init.d/eelsrc stop
Restart EELS in basic debug mode

/etc/init.d/eelsrc start -d
Debugging information is written to the EELS log in /etc/eels/logs/eelsd.log.
NOTE: In some versions of EELS you may find that after restarting in a debug mode, the EELS daemon (eelsd) remains in the foreground. In this case you should open a new window and work from there. When you want to stop the session, use eelsrc in your new window.
After you have gathered all the debugging information you require, stop and restart EELS by using the following commands:

/etc/init.d/eelsrc stop
/etc/init.d/eelsrc start

The amount of information written to eelsd.log varies depending on the debug level you select. No matter what level you do select, always keep an eye on the size of the log file as it can grow quite large in a relatively short amount of time.