Collecting LucidLink Client Logs

Team LucidLink
Team LucidLink
  • Updated

From time to time issues happen. When liaising with LucidLink Support, you might be asked to collect and provide the client logs. See Submit a Support Ticket Effectively KB article.

The most efficient method is to upload a Diagnostic Report and provide the accompanying 'Reference ID' with your Support Ticket.

To locate your logs yourself it is specific to the operating system environment as to where these resources are located. See this KB article for a detailed explanation on our LucidLink client folder structure.

Default LucidLink Filespace cache and configuration root-path locations when utilizing our LucidApp 2.5 and above are located in the user profile or home folders as hidden .lucid sub directories and an instance_id sub folder for each multiple Filespaces linked.

Within this instance_id directory is the Lucid.log file. Our LucidApp app.log is located in the base .lucid folder. See below in this article for identifying your Filespace instance_id.

Previous LucidApp versions prior to 2.5 will utilize the user profile or home folders as hidden .lucid for Lucid.log and app.log.

Lucid daemon from the command-line will utilize a default root-path and config-path of user profile or home folders as hidden .lucid folder, unless specifically specified by a separate --root-path and --config-path daemon options.

To view the contents of your Lucid.log based on your operating system you can open it within a text viewer and or editor.

Windows: accessible through Explorer or command line.

    1. Launch File Explorer

CL1.png

    2. Navigate to C:\Users and select your User profile directory

    3. Locate the .lucid and app.log and appropriate instance_id folder for your Lucid.log to upload.

Please make sure you check the Lucid.log time and date stamps to ensure you are uploading the most current version.
Note: There might be a legacy Lucid.log within the .lucid left over from a previous client version.

LucidApp Lucid.log via command-line:

notepad.exe C:\Users\%username%\.lucid\<instance_id>\Lucid.log 
notepad.exe %userprofile%\.lucid\<instance_id>\Lucid.log

Alternative Windows core (non-LucidApp) or via command-line:

notepad.exe C:\Users\%username%\.lucid\Lucid.log
notepad.exe %userprofile%\.lucid\Lucid.log

Location of Lucid.log when running as a Windows as a Service.

C:\Windows\System32\config\systemprofile\.lucid

    

macOS: available within Finder or via terminal.

    1. Launch Finder

CL3.png

    2. Select the Go menu and Home 

CL4.png

    3. Once within Home press press Command + Shift + . (dot) to expose the hidden .lucid folder

On macOS the .lucid folder is a hidden folder, which means that you may have to press Command + Shift + . (dot) when viewing the user home directory in Finder

    4. Locate the .lucid and app.log and appropriate instance_id folder for your Lucid.log to attach to your support ticket

Please make sure you check the Lucid.log time and date stamps to ensure you are uploading the most current version.
Note: There might be a legacy Lucid.log within the .lucid left over from a previous client version.

Alternatively via Terminal

open -e $HOME/.lucid/<instance_id>/Lucid.log
open -e ~/.lucid/<instance_id>/Lucid.log

 

Linux: via terminal or file browser.

1. Launch your File Browser and navigate to Home, within you will find a .lucid folder and subsequent app.log along with an appropriate instance_id folder for your Lucid.log for your support ticket.  

Please make sure you check the Lucid.log time and date stamps to ensure you are uploading the most current version.
Note: There might be a legacy Lucid.log within the .lucid left over from a previous client version.

Open Lucid.log via Terminal

vi ~/.lucid/<instance_id>Lucid.log

It might make sense to copy the Lucid.log to the Desktop:

cp ~/.lucid/<instance_id>/Lucid.log ~/Desktop/Lucid.log

Note: an app.log file located within the root .lucid folder, sometimes we might request this additional file.

If the log file has grown to a size not suitable for the traditional transport methods (email/upload) please compress (.zip/.rar) as compaction will dramatically reduce this file for easier handling.

In certain situations under increased log entries our logs rotate and you will notice additional Lucid.log*.gz files - we will require all associated *.gz files.

 

Identifying your Filespace instance_id.

When connected to a Filespace you can identify your instance_id via the command-line.

lucid list
If you have launched LucidApp and discovered your Filespace but not yet connected by validating your user credentials lucid list will output your instance_id with your Filespace status of <unknown> and unlinked.

When the LucidLink client is connected to a Filespace Identify your Filespace root-path and or your config-path.

lucid status
lucid info

Was this article helpful?

2 out of 3 found this helpful

Have more questions? Submit a request

Comments

0 comments

Article is closed for comments.