logs

Locate Synchronet BBS log sources across Windows and *nix systems.

107|19|Updated Sep 4, 2020
One-click install
npx skills add https://github.com/SynchronetBBS/sbbs --skill logs-synchronetbbs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: logs
Source: https://github.com/SynchronetBBS/sbbs/tree/main/.claude/skills/logs
Command: npx skills add https://github.com/SynchronetBBS/sbbs --skill logs-synchronetbbs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sysops and developers working with Synchronet BBS often waste time searching the wrong log files when troubleshooting issues, as log locations vary drastically based on operating system, daemon mode, init system, and whether multiple BBS instances share storage. This Skill eliminates that guesswork by providing a complete map of all possible log sources and the conditions that determine where each log line is written.

Core Features & Use Cases

  • Cross-platform log mapping: Covers Windows (sbbsctrl, NT Services, console) and *nix (syslog, journalctl, interactive stdout) log sources, including per-category data files like hack.log, error.log, and HTTP access logs.
  • Edge case handling: Addresses common traps like multi-instance shared text directories causing cross-BBS ip.can entries, Windows-specific sbbsctrl log files appearing on *nix systems, and post-rotation empty log files.
  • Use Case: If you are investigating a web rate-limit block or a failed login attempt, this Skill tells you exactly which log source to check first, how to tail it live, and how to cross-reference related entries like ip.can filters.

Quick Start

Use the logs skill to identify the correct log source to investigate a recent web rate-limit block on your Synchronet BBS.

Frequently Asked Questions about logs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Where do I find Synchronet BBS log files on Linux and Windows?

Synchronet BBS log files are located across different paths depending on the OS and mode. On Linux, check syslog or journalctl for daemon modes, while Windows uses sbbsctrl logs and NT Services console outputs.

How do I troubleshoot a failed login attempt in Synchronet BBS?

To troubleshoot failed login attempts in Synchronet BBS, locate the correct log source using your OS and instance type, then tail the live log and cross-reference related entries like the ip.can filter file for blocks.

Does Synchronet BBS logging work differently for multi-instance deployments?

Multi-instance Synchronet BBS deployments can share text directories, causing cross-BBS ip.can entries and mixed log outputs. You must identify the specific instance and its storage path to isolate the correct log source.

What is the best way to monitor Synchronet BBS web server rate-limit blocks?

To monitor web rate-limit blocks in Synchronet BBS, identify the HTTP access logs and data files for your specific platform. You can tail these logs live to view blocked attempts and cross-reference ip.can filters.

Why are my Synchronet BBS log files empty after rotation?

Empty Synchronet BBS log files often occur post-rotation when the daemon continues writing to the old file descriptor. Restarting the service or checking the active journalctl or syslog stream resolves the visibility issue.

Can I use MQTT streams for Synchronet BBS log correlation across hosts?

MQTT streams are supported for Synchronet BBS log correlation across hosts. You can subscribe to the MQTT topics to aggregate logs from multiple instances for cross-host troubleshooting and server crash analysis.