View Logs

The blocklet server logs command is an essential tool for debugging and monitoring. It displays the locations of all relevant log files for the Blocklet Server daemon and each installed blocklet, helping you quickly identify and resolve issues.

Usage#

To view the log file paths, execute the following command in your terminal:

The command will print a structured list of paths for the server's daemon logs and then list the specific log files for each installed blocklet.

Example Output#

Here is a sample output from running the command on a server with a couple of blocklets installed:

Understanding the Log Files#

The output is divided into two main sections: server-level logs and blocklet-specific logs.

Server Daemon Logs#

All server-level logs are stored within the Daemon Logs Directory. The different log files are categorized to help you find information efficiently.

File Pattern	Description
access-<date>.log	Contains daily rotated access logs for the server.
daemon-<date>.log	Stores general business and operational logs, rotated daily.
daemon-error-<date>.log	Collects error-specific logs, also rotated daily.
service.log	Logs from the underlying node service manager.
stderr.log	Captures the standard error stream from the main server process.
stdout.log	Captures the standard output stream from the main server process.

Individual Blocklet Logs#

For each installed blocklet, the command lists two primary log files:

• Output: The path to the blocklet's standard output log (output.log).
• Error: The path to the blocklet's standard error log (error.log).

Note: The Blocklet Server must be running for the command to list the log paths for individual blocklets. If the server is stopped, it will only display the server-level log paths along with a warning message.

After diagnosing issues with logs, you might need to manage your server's version. Learn how in the next section: Upgrade Server.