logs

The blocklet server logs command provides a quick and organized way to find the locations of log files for both the Blocklet Server daemon and any installed blocklets. This is essential for troubleshooting issues, monitoring activity, and debugging applications.

For a live status check of your server and blocklets, see the blocklet server status command. For general environment details, refer to blocklet server info.

Usage#

This command is straightforward and does not accept any arguments.

Understanding the Output#

The command's output is organized into sections for the Blocklet Server daemon and for each installed blocklet.

Blocklet Server Logs#

This section details the core logs generated by the Blocklet Server daemon. It provides the main directory for daemon logs and a list of the log file types you can expect to find there.

File Pattern or Entry	Description
Daemon Logs Directory	The absolute path to the directory containing all daemon-related logs.
Latest logs	A direct path to the most recent business log file (daemon-<date>.log).
access-<date>.log	Contains HTTP access logs, which are rotated daily.
daemon-<date>.log	The main business logic log for the server, rotated daily.
daemon-error-<date>.log	Contains only error-level logs from the server, rotated daily.
service.log	Logs related to the underlying service manager for the node.
stderr.log	Captures the standard error stream of the server process.
stdout.log	Captures the standard output stream of the server process.

Blocklet-Specific Logs#

If the Blocklet Server is running and has blocklets installed, the command will list the log files for each one, identified by its name and version.

File	Description
Output	The path to output.log, which contains the standard output from the blocklet's main process.
Error	The path to error.log, which contains the standard error output from the blocklet's main process.

Example#

Running blocklet server logs in a typical environment might produce the following output:

Notes#

• If Blocklet Server is not running, the command will only show the paths for the daemon logs and print a warning. Blocklet-specific log paths cannot be determined without a running server. You can start it with blocklet server start.
• If you see a No blocklets installed yet warning, it means the server is running but has no blocklets currently deployed on it.

Once you have located the log files, you can use standard command-line tools like tail, less, or cat to inspect their contents. For real-time logs during active development, consider using the blocklet dev command, which streams logs directly to your terminal.