Luna Shell: Command Logging
Command logging records administrator actions in a log file.
|
Facility Keyword |
Software Process |
Log File |
|---|---|---|
|
|
|
|
Expected Log Messages
The following log messages are normal and expected entries in the log files for all LunaSH commands.
2012 Feb 29 12:05:01 myLuna local5 info lunash [1234]: info : 0 : Command: hsm show : admin : Console 2012 Feb 29 12:05:01 myLuna local5 info lunash [1234]: info : 0 : Command: my file list : monitor : 192.168.0.100/40847
Every administrative command executed within the secure Luna shell results in a log message to lunalogs. This message records the command return code (e.g., 0), the command (e.g., lunash:>hsm show and lunash:>my file list), the user account (e.g., admin and monitor) and the connection of the secure shell (e.g., Console and 192.168.0.100/40847 – the IP address and outgoing port number on client system).
2012 Feb 29 12:05:01 myLuna local5 info lunash [1234]: info : 0 : Lush user login : admin : Console 2012 Feb 29 12:05:01 myLuna local5 info lunash [1234]: info : 0 : Lush user login : monitor : 192.168.0.100/4084
A slightly different formatted log message records the login action.
Unexpected Log Messages
Under normal circumstances, you should not see any of these log messages. If you do so, please consult the user documentation for guidance on how to correct the problem.
Token State and Login Errors
2012 Feb 29 12:05:01 myLuna local5 warn lunash [1234]: HSM Admin Login: incorrect password or PED key 2012 Feb 29 12:05:01 myLuna local5 warn lunash [1234]: HSM Admin Login: HSM Zeroized due to three consecutive bad login attempts. 2012 Feb 29 12:05:01 myLuna local5 warn lunash [1234]: Backup Token Admin Login: incorrect password or PED key 2012 Feb 29 12:05:01 myLuna local5 warn lunash [1234]: Backup Token Admin Login: HSM Zeroized due to three consecutive bad login attempts.
On backup and restore operations, these messages indicate failure to successfully authenticate because of either incorrect credentials or the HSM/token being in a state that disallows authentication (i.e., zeroized).
Configuration File Error
2012 Feb 29 12:05:01 myLuna local5 info lunash [1234]: Config file for overriding hsm slot exists, but there is a problem reading it..
This message indicates that a lush utility was unable to read the slot number from a configuration file used to define a specific HSM slot identifier. This message is unexpected: contact Thales Technical Support for guidance on what to do next.
Node Not Loaded
2012 Feb 29 12:05:01 myLuna local5 err lunash [1234]: Node not loaded: hsm ped set
This message indicates that the LunaSH interpreter was unable to load the logged node on start up. This message is unexpected: contact Thales Technical Support for guidance on what to do next.
