Versions Compared

Old Version 8

changes.mady.by.user Bruno Miretti

Saved on

compared with

New Version Current

changes.mady.by.user Bruno Miretti

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

It runs in the background (as a program or as a service) and periodically scans a specified LOG file. It detects the following messages and executes the associated scripts (created manually):

Error codeDescriptionScript executed
00000424Detected removal of a license.nolicense.bat
0000040BLicense has changed. License detected and online.license_changed.bat

...


Note

The user action file will not invoke interactive applications as it may run in an environment where interactive services do not work, for example: when “Log Monitor & Dispatcher” is installed as a service.

Starting in background mode

In order to start the Log Monitor & Dispatcher as a background application:

  1. Open "cmd.exe" from the "Start" menu.

  2. Change current directory to the folder (presumably) containing the LOG file.
    Start the Log Monitor & Dispatcher using the following command line as an example (for Windows x64; for Windows x86 use the following path: "C:\Program Files\CHARON\Utilities_X.X.XXXXX\x86"):

    For single log file:


    Div
    classsmall

    ...> "C:\Program Files\CHARON\Build_XXX\x86\logmond" my_charon.log 


    .
    For rotating log file: 


    Div
    classsmall

    ...> "C:\Program Files\CHARON\Build_XXX\x86\logmond" -l <log-directory> -p <log-prefix>


    .
    where:

    • <log-directory> is the directory where the rotating log files are stored
    • <log-prefix> is the same as the "configuration_name" value in corresponding CHARON configuration file (or "hw_model", if "configuration_name" is not specified).

Example:

...> "C:\Program Files\CHARON\Build_XXX\x86\logmond" -l "C:\My CHARON logs" -p "MY_VAX"

To stop the Log Monitor & Dispatcher application, open the Task Manager, find the “logmond.exe” process and terminate it.

Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc

Installing as a service

In order to install the Log Monitor & Dispatcher as a background application:

  1. Open "cmd.exe" from the "Start" menu in "Run as Administrator" mode.

  2. Install Log Monitor & Dispatcher service using the following command line as an example:

    ...> "C:\Program Files\CHARON\Build_XXX\x86\logmond" -r
    ...> "C:\Program Files\CHARON\Build_XXX\x86\logmond" -i


As result the "logmond" service has "Manual" service start type. Use Windows service management tools to change this mode to "Automatic" if it is required.

Note
  • There will have one logmond father process that will scan the virtual machines services and one logmond process per log monitored.
  • The EmulatorLogMonitor service running the logmond processes will discover already installed CHARON virtual machines services. If a new virtual machine service is added, it's log file will be automatically discovered and monitored.
  • The "nolicense.bat" and "license_changed.bat" files have to be placed in the virtual machine "Home directory". This directory corresponds to the configuration file folder when the service is installed, however it will not change if the configuration file is relocated and the service is updated. To find this "Home directory", open the "CHARON Service Manager" utility, right click on the corresponding service and select "View configuration"
Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc

Starting the Log Monitor and Dispatcher service

In order to start the Log Monitor & Dispatcher as a background application:

  1. Open "cmd.exe" from the "Start" menu in "Run as Administrator" mode.

  2. Start the Log Monitor & Dispatcher service using the following command line as an example:

    ...> "C:\Program Files\CHARON\Build_XXX\x86\logmond" -u


It is also possible to use Windows service management tools to start up the service.

As soon as "logmond" service is installed this way, and started, it monitors all CHARON instances (provided that these are installed as services).

It does NOT monitor emulator instances started from Launcher or manually from command line prompt. But these cases can still be monitored with "logmond" invoked from command line prompt with name of the log file as an argument (see above).

Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc

Div
classpagebreak


Stopping the Log Monitor and Dispatcher service

In order to stop the Log Monitor & Dispatcher as a background application:

  1. Open "cmd.exe" from the "Start" menu in "Run as Administrator" mode.

  2. Stop the Log Monitor & Dispatcher service using the following command line as an example

    ...> "C:\Program Files\CHARON\Build_XXX\x86\logmond" -d


It is also possible to use Windows service management tools to stop the service.

Include PageKBCOMMON:DOC-GoToTocKBCOMMON:DOC-GoToToc

Uninstalling the Log Monitor and Dispatcher service

In order to uninstall the Log Monitor & Dispatcher as a background application:

  1. Open "cmd.exe" from the "Start" menu in "Run as Administrator" mode.

  2. Uninstall the Log Monitor & Dispatcher service using the following command line as an example

    ...> "C:\Program Files\CHARON\Build_XXX\x86\logmond" -r


Log Monitor and Dispatcher best practice

Refer to this article in the Appendixes for proper configuration of the "nolicense.bat" file to establish needed actions on the dongle removal.

Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc