Charon-PAR Linux Toolkit - Release notes for Kit 1.4.6

Charon-PAR Linux Toolkit - Release notes for Kit 1.4.6

Version: 1 - Published: Mar 3, 2022 

Linux Toolkit description

The crontab file is no more /var/spool/cron/root but /etc/cron.d/charon so in case of upgrade, this requires the lines related to Charon in the /var/spool/cron/root file to be deleted and the menu option '13 - Manage recurring jobs' to be executed

History

March, 3rd 2022 - kit version 1.4.6

Problems fixed by this patch

  • Deleted software licenses are no more archived in /var/hasplm/installed/68704.bck folder as this generates errors in the HASP error.log file. They are now moved to /var/hasplm.bck

  • Update in 'Request for new license or license update (send C2V file)' option: the update option 1 requires at least a USB license dongle or a software license already installed.

  • When starting the menu, a check is performed in the root crontab file and if entries related to Charon are found, a message is displayed asking to remove or comment them and use the 'Manage recurring jobs' option to recreate these entries (which is done in the /etc/cron.d/charon file)

  • 'Manage recurring jobs' menu option: now checks if Charon related entries are still present in the root crontab file and asks for editing it before updating the /etc/cron.d/charon file

  • Added a check in the 'HASP license details' menu option to ensure 'atd' has been enabled and is running (this is mandatory to read license content via a remote connection)

January, 20th 2021 - kit version 1.4.5

Problems fixed by this patch

  • Updated message related to _fmt.v2c files in 'License update tool (apply V2C file)' menu option

  • License expiration check: bug solved with 'no expired product found' message, counters were not updated correctly + email layout update

  • In case the emulator process has to be killed, 5 tries are performed with SIGTERM signal, if not successful a SIGKILL is sent. This is to try to avoid cases where the license is not freed after the process is killed

  • Fixed issues when trying to unbind/bind USB controller when no one is defined on the Linux server

December, 23th 2021 - kit version 1.4.4

Problems fixed by this patch

  • Issue solved when generating C2V files: licenses provided by other hosts than the local one will be skipped during the generation process

December, 21th 2021 - kit version 1.4.3

Problems fixed by this patch

  • Issue solved when generating a C2V file when a software license and a dongle were present on the server and the 'menu' was executed from a remote session.

October, 7th 2021 - kit version 1.4.2

Problems fixed by this patch

  • Rewording when displaying licenses found to make the difference between local licenses and remote licenses

October, 7th 2021 - kit version 1.4.1

Problems fixed by this patch

  • The 'HASP license details' menu option:

    • failed to read licenses when a dongle and a software license were present on the server

    • did not correctly display license details after viewing license content when a USB dongle and a software license were present

September, 7th 2021 - kit version 1.4

New features

  • After Charon-PAR installation from menu option 1, if the PATH is not defined, the /etc/profile.d/charon.sh file is created automatically and it is asked to either execute it or logout/login to define the correct PATH to /opt/charon/bin

  • When running the 'menu', checks are performed for 'atd' service: enabled and active. If this is not the case, alerts may not be sent and license could not be read from remote connection.

  • License expiration check now displays the number of dongles connected and the number of software licenses found.

  • When a virtual machine process ends abnormally, an entry in its log file is added with FATAL severity level (1). It provides information on the event (example: signal/KILL if the process got killed)

  • When editing stop, pre-start and check scripts, if vim is selected, a special vimrc file is used for ease of reading on black background screens and white background screens.

  • During setup, if LS_COLORS is defined, the 'ls' command will highlight .cfg, and .dsk files.
    Note: in case of Toolkit upgrade, please run # ./menusetup -a

  • crontab file is no more /var/spool/cron/root but /etc/cron.d/charon (2)

  • When displaying list of virtual machines, the number of warning, error and fatal messages found in the log file is displayed (if greater than 0).

  • The 'MPE system fail' message in the log file is now considered as a failure message (3).

  • License expiration check now alerts in case a cloned Software License is possibly found.

  • Alert emails now contain the kit version for ease of support (4).

  • 'Request for new license or license update' and 'License update tool' now stop if the 'aksusbd' service is not running

(1): In case of Toolkit upgrade, this requires the systemd service to be updated (ExecStopPost line to add, this will be notified when displaying the virtual machines list). In this case, open the 'menu" → 'VM Management' → 'Manage 'systemd' services' and edit the .service file.

(2): In case of Toolkit upgrade, this requires the lines related to Charon in the /var/spool/cron/root file to be deleted and the menu option '13 - Manage recurring jobs' to be executed

(3): In case of Toolkit upgrade, this requires the log monitoring processes to be restarted from the menu option "9 - Manage monitored guests logs" then "8 - Restart all log monitoring services"

(4): In case of upgrade, please update the alert script (if not already customized) from "menu" → "14 - Alerts management" → "6 - Update/reinstall alert script".

Problems fixed

  • 'ed' added as a mandatory package

  • 'mailx' added as a (highly) recommended package

  • 'vim' added as a recommended package

  • 'lsusb' required executable replaced by 'usbutils' required package

  • Fixed a problem to detect network interface status with new V3.0.1 syntax

  • 'ifconfig' commands used to get NIC information replaced by 'ip'

  • If a network configuration issue is detected when starting a virtual machine, the message that was sent was related to Linux 6. It now asks correctly to restart the NetworkManager service.

  • If 'rsh' needs to be installed for clean shutdown on RHEL 8, the installation procedure is detailed in the readme file ('menu' -> 'VM Management' → 'Create/Edit guest stop script' → 'Read how-to setup 'rsh' with HP-UX file')

  • For CentOS and RHEL 8, if 'yum' is not present, 'dnf' is used instead

  • With the latest version of Charon-PAR, glibc.i686 is not more needed. The check is then removed from the "Install/Upgrade/Remove Charon" menu option.

  • The vmlist command did not display Charon-PAR installed version

  • For CentOS, the service status reported by 'logview' and 'logtail' commands reported unknown service state. Workaround added to get the ActiveState service parameter status.

  • When checking the license expiration interactively, if a software license was present and a dongle was connected, only the software license was displayed. This did not affect automated checks executed from the crontab.

  • When using the "logtail" command, the continuous view is not stopped when a virtual machine started or stopped message is found. Also, when aborted, it does not stop other logtail commands running on the same server.

  • License expiration check: if more than one license available, if one was about to expired or had expired but not the other, the alert was not correct (no information below the one that was ok)

  • Menu send log options:

    • the charon-report utility from kits 2.0 and below asks for email address even if option -e is not used and the report is generated is /root, not in /tmp. This special case is now taken into account

    • updated for rotated log files / kit 3.0.4

  • When sending logs with the options '10 - Send configuration and log files via email', log files are displayed in reverse order in the email body

  • Several issues solved due to log file names change starting with Charon-PAR 3.0.4



© Stromasys, 1999-2025  - All the information is provided on the best effort basis, and might be changed anytime without notice. Information provided does not mean Stromasys commitment to any features described. 
Need fast, reliable migration? We have done it countless times. Talk to an expert