![\"\"](\"https:\/\/portal.staylinked.com\/sl\/kb\/wp-content\/uploads\/2019\/08\/Flowchart.jpg\")
<\/figure>\n\n\n\nThe log files listed in the following sections do not include the entire list of available logs. Various features will have their own additional log files. This article is designed to describe the most common files and the issues they may help diagnose.<\/p>\n\n\n\n
Additional guides are available for more information on other logging uses, such as the Statistics Log<\/a> and Client-Server Connectivity<\/a> Articles.<\/p>\n\n\n\n Please be sure to contact StayLinked technical support for any issues. These logs can contain abbreviations and references that are misleading to the untrained user. For example, references in the socket log to \u2018DATA LOSS\u2019 are a reference to the L<\/strong>ast O<\/strong>bserved S<\/strong>erver S<\/strong>equence and do not actually represent the loss of any data or transactions.<\/p>\n\n\n\n Session-specific log files are disabled by default. Enable these logs in the Server Configuration > Server Settings section of the StayLinked Administrator.<\/p>\n\n\n\n Setting the logging level includes the log\nfiles above the selected level. This means that a setting of Socket Level would\ninclude session, handler and socket log files for each client connection in the\nIP range. Leaving the range blank will create log files for all connections.\nThis means that a server with 100 sessions and socket logging would create 300\nnew files. Disk storage space may be impacted by log files on systems that\ngenerate large file size and\/or quantity.<\/p>\n\n\n\n Server systems that have operating system\nlimits on threads_process or open_files may be impacted by these additional log\nfiles. Servers reaching their configured limits may result in poor performance\nor be unable to start new connections. Please review the Server Tuning Guide\nfor more detailed information on these parameters.<\/p>\n\n\n\n StayLinked Client-Server Encryption in the\nlower right corner of this dialogue should typically be set to \u2018None\u2019 during\nlogging. Using Level 1 encryption will generate encrypted log files that will\nbe generally unusable.<\/p>\n\n\n\n Once enabled, these log files will be\ngenerated for all new StayLinked sessions. Devices that have an existing\nsession will not be logged until the session is ended and a new one has been\nstarted. Likewise, sessions that are generating logs will continue to do so if\nlogging is disabled until a new session is started. You can confirm the start\ntime of each session in the Administrator\u2019s list of all connections.<\/p>\n\n\n\n Note the ability to enable\/disable the StdErr and StdOut logs. You can set the number of days to clean up old log files, but this will not affect general server logs.<\/p>\n\n\n\n Files viewed using the StayLinked Administrator will open in a \u2018File Viewer\u2019 window. This viewer will only display the tail 64k of any file.<\/strong> Attempting to copy and paste data from this window may lose important details, depending on what application the data is pasted to. For these reasons, it is recommended that the original files are opened using Notepad or a similar text editing program that does not process formatting codes.<\/p>\n\n\n\n General server log files can be opened from\nthe Logs pulldown menu across the top of the Administrator. Individual session\nlogs can be accessed from the Administrator\u2019s connections list using the View\ncontext menu by right clicking a session.<\/p>\n\n\n\n Some logs, like the proxy log can only be accessed from the StayLinked server\u2019s logs subdirectory.<\/p>\n\n\n\n If you want StayLinked support to help review log files, it\u2019s important that you do not cut-and-paste from the File Viewer used by the Administrator. You\u2019ll want to get a copy of the actual log file. All log files may be retrieved from their source location with the exception of the Analysis log, which is created by the StayLinked Administrator from the Handler log. Server and session-specific logs can be found in the Server\u2019s logs subdirectory.<\/p>\n\n\n\n The best way to collect log files is from the right-click menu option to 'Zip All Logs<\/strong>'. This menu option appears for both the Server and Session-Specific files, depending on the location of your click. Older Administrator versions will only offer the specific files, while the zip option collects them all and places them in a ZIP of your desired location.<\/p>\n\n\n\n If a file is opened using the Administrator, a copy is downloaded from the server and placed on the Administrator PC. There are multiple possible locations for the storage of these copies, depending on the version and storage mode<\/a> of the Administrator:<\/p>\n\n\n\n Some portions of this file path may be hidden directories. You can manually type the path names into your address bar if the directory does not appear or change your view options to show hidden files and directories. <\/p>\n\n\n\n The Administrator copies are a snapshot of when\neach file was collected. The server copy will continue to update with new\ninformation, but only gathering a new copy at the Administrator will update the\nlocal copy.<\/p>\n\n\n\n For easy access, the file viewer includes options in the File menu that will open the file in Notepad, Open the standard administrator logs directory or open the current virtual store directory. Depending on the authority level of the Administrator program, the local copies of any file displayed by the viewer will be stored in one of these locations. This includes the analysis log when created as described later in this article.<\/p>\n\n\n\n New with Administrator and Server v15.1 build 208 are options to collect related log files in a single ZIP file. This gathers and compresses the entire set of files, bypassing the file viewer.<\/p>\n\n\n\n General Server logs can be packaged from the Logs pulldown menu at the top of the Administrator.<\/p>\n\n\n\n Session-specific logs can be gathered from the Connections List under the View context menu when right clicking on a session.<\/p>\n\n\n\n An option exists in the keyboard map for any device type to save a log snapshot. This allows users to press a key combination to immediately set aside the current sessions-specific log files for that device. This allows users to save a snapshot as soon as an issue takes place, allowing support to review the end of the current log for the event and without having to worry about the files rolling over and losing the event. <\/p>\n\n\n\n Each time this key is invoked, the session, handler and socket logs will be zipped into a log package and stored in the Server\u2019s log directory. This makes the log files pre-packaged for sending to StayLinked and makes sure that the files take place right after the event. This prevents the files from being lost in the time between the event and the user notifying you of the event.<\/p>\n\n\n\n StayLinked includes many different log files. This article is an overview of the most common files, a little information about what they contain and some examples of how you might use them to get a clear picture of the transactions taking place. Different logs will show different parts of the…<\/p>\n","protected":false},"author":7,"comment_status":"open","ping_status":"closed","template":"","format":"standard","meta":[],"ht-kb-category":[24],"ht-kb-tag":[],"yoast_head":"\nEnable Session-Specific Logging<\/h2>\n\n\n\n
![\"\"](\"https:\/\/portal.staylinked.com\/sl\/kb\/wp-content\/uploads\/2019\/08\/Server-Settings.jpg\")
<\/figure>\n\n\n\nViewing Log Files<\/h2>\n\n\n\n
![\"\"](\"https:\/\/portal.staylinked.com\/sl\/kb\/wp-content\/uploads\/2019\/08\/File-Viewer-for-handler-Log.png\")
<\/figure>\n\n\n\nRetrieving Files<\/h2>\n\n\n\n
![\"\"](\"https:\/\/portal.staylinked.com\/sl\/kb\/wp-content\/uploads\/2019\/08\/Tips-for-sending-files.jpg\")
<\/figure><\/div>\n\n\n\nGeneral Server Logs<\/h3>\n\n\n\n
![\"\"](\"https:\/\/portal.staylinked.com\/sl\/kb\/wp-content\/uploads\/2020\/08\/LogFileRetrieval.01.jpg\")
<\/figure>\n\n\n\nSession Specific Logs<\/h3>\n\n\n\n
![\"\"](\"https:\/\/portal.staylinked.com\/sl\/kb\/wp-content\/uploads\/2020\/08\/LogFileRetrieval.02.jpg\")
<\/figure>\n\n\n\nLog Snapshot<\/h2>\n\n\n\n
![\"\"](\"https:\/\/portal.staylinked.com\/sl\/kb\/wp-content\/uploads\/2019\/08\/Update-entry-key.jpg\")
<\/figure>\n\n\n\nGeneral Server Logs<\/a><\/h2>\n\n\n\n
Session-Specific Log Files<\/a><\/h2>\n","protected":false},"excerpt":{"rendered":"