Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 22 Next »

This document relates to Charon Log Monitor version 1.0 dated 02-May-2022.

(info) To get the download link, please contact us.

Table of contents

Introduction

The Charon Log Monitor is a utility that monitors the Charon emulator session log files and that sends alerts in case a warning or error message is detected. It can also send alerts for informational messages when the emulator is started or properly stopped, when a CPU BUGCHECK or a CPU Halted message is detected or even if someone connects or disconnects from the emulator console.

It can also send alerts in case of Charon emulator service state change or if the emulator log file is greater than a specified value.

Alerts can either be an entry added in the Windows Application Events log file, an email or a .BAT or .PS1 custom script. A mechanism can be set in place to stop sending alerts in case too many alerts are sent during a specified interval.

Prerequisites

*: If you installed PowerShell 7, please ensure PowerShell 5.1 is installed (not 4.0)

(lightbulb) The utility has been tested on Windows 10, 11, Server 2012 R2, Server 2016, Server 2019 and Server 2022 with Charon-AXP/VAX/PDP.

(info) If it is installed on Windows 7 or Windows Server 2008 R2, storing the email account password will not work, use custom script in this case.

Usage

Once installed, by default in "C:\Program Files\CHARON\Charon Log Monitor", a Charon Log Monitor shortcut is placed on the desktop and in the Windows start menu.

1 - Open the Charon Log Monitor interface


2 - Install the service


3 - Define the settings from the settings tab: what you want to monitor and if you want Windows Application Events to be generated and/or a customer .PS1 or .BAT script to be executed + several other options you can activate

(lightbulb) If a .BAT or .PS1 script needs to be executed, a button will appear to edit the script. If the script does not exist, a skeleton one will be created. This script is located in the Charon Log Monitor installation folder.


4 - If needed, you can use the Email settings tab to specify who you want to send emails to + from who. If the sender account needs a password, you'll need to click the "Save" button (does not work with PowerShell 4.0, 5.1 only). It is recommended to use the "Test email alert" button to ensure emails are correctly sent. If the test email is not received, please check the service log from the "Service log" tab.

(question) The password is encrypted and saved in the registry. It is valid for the local machine only.

(lightbulb) If the email mode is HTML, the email footer can contain HTML tags


5 - Go to the Virtual Machines tab, select one virtual machine: mouse hovering displays several information:

(lightbulb) Virtual machines must exist and be created using the Charon Virtual Machine Manager utility.


Right click on one of them to either enable/disable log monitoring or start/stop the emulator, show the console, edit the .cfg file (if notepad++ is installed, it will use it otherwise it's notepad), open the log file, explore the home directory, etc..

Notes:

  • Double clicking on a virtual machine name opens the latest log file
  • Double clicking on the "Notes" box for a virtual machine opens the "Edit notes" option
  • A circle icon in the details box means the log file is using the log rotation mechanism (highly recommended). Mouse hovering on this icon shows the max file size and rotation period if defined.
  • Other warning icons can be displayed if:
    • The log counters are enabled or
    • The log file size is greater than the limit specified or
    • The log method is set to overwrite (not recommended) or
    • The configuration file has been updated after the emulator was started (an emulator restart is required for the changes to be taken into account)
  • If alerts have been suspended, either manually or due to the limit reached, resuming sending alerts must be done manually

Example:


HTML email example

(lightbulb) To remove the "Notes" part in the email body, uncheck the related option from the "Email settings" tab.


Windows Application Events example

PS C:\Users\Administrator> Get-EventLog -LogName Application -Source CharonLogMonSVC -Newest 15

   Index Time         EntryType   Source            InstanceID Message
   ----- ----         ---------   ------            ---------- -------
    8330 May 03 09:57 Error       CharonLogmonSVC           12 pluto: state is Stopped.
    8329 May 03 09:57 Error       CharonLogmonSVC          586 pluto: Logging stopped.
    8327 May 03 09:54 Information CharonLogmonSVC         1050 pluto: OPA0: disconnected
    8326 May 03 09:53 Warning     CharonLogmonSVC           14 pluto: configuration file has been updated after service was started on 03-May-2022 09:52:04
    8325 May 03 09:52 Warning     CharonLogmonSVC         1049 pluto: OPA0: connected
    8324 May 03 09:52 Error       CharonLogmonSVC          445 pluto: 20220503:095207:ERROR:2:000001BD:scsi_tape.( 810): (3) The system cannot find the path specified. : PKA_5_0: Fai...
    8323 May 03 09:52 Error       CharonLogmonSVC          445 pluto: 20220503:095207:ERROR:2:000001BD:scsi_cdrom( 789): (3) The system cannot find the path specified. : PKA_4_2: Fai...
    8322 May 03 09:52 Error       CharonLogmonSVC          445 pluto: 20220503:095207:ERROR:2:000001BD:scsi_cdrom( 789): (3) The system cannot find the path specified. : PKA_4_1: Fai...
    8321 May 03 09:52 Error       CharonLogmonSVC          445 pluto: 20220503:095207:ERROR:2:000001BD:scsi_cdrom( 789): (3) The system cannot find the path specified. : PKA_4_0: Fai...
    8320 May 03 09:52 Information CharonLogmonSVC          589 pluto: Using license 7003444...
    8319 May 03 09:52 Warning     CharonLogmonSVC          589 pluto: 20220503:095204:WARN :1:0000024D:licenseman(1993): Failed to log in to the Sentinel HASP key: "879642840".
    8318 May 03 09:52 Error       CharonLogmonSVC          589 pluto: 20220503:095204:ERROR:2:0000024D:licenseman(2003): HASP runtime (50): Unable to locate any Feature matching scope.
    8317 May 03 09:52 Information CharonLogmonSVC          585 pluto: Logging started.
    8316 May 03 09:52 Information CharonLogmonSVC           10 pluto: state is Running.
    8315 May 03 09:52 Warning     CharonLogmonSVC           11 pluto: state is StartPending.

Tips

  • Right clicking anywhere but the virtual machine list box will display About and Release Notes
  • Mouse hovering on virtual machines names, buttons and icons displays additional information and help
  • It is also possible to export and import general and email settings for ease of deployment ((info) the email account password will not be exported)



  • No labels