Newer
Older
gnexus-book / 10-systems / bots / mardisbot.md

title: MardisBot description: Telegram bot for Mardis group host: tgbots status: missing last_reviewed: 2026-09-10 owner: gmikcon confidence: 95 review_interval: 90

source_of_truth: live_system

MardisBot

Telegram bot for the Mardis group, previously deployed on the tgbots VPS.

STATUS 2026-09-10: NOT DEPLOYED. An exhaustive read-only audit of tgbots (192.168.1.178) on 2026-09-10 found no Telegram bot running or installed anywhere on the host. The host was rebuilt around 2026-08-27 (system directories re-created, uptime reset) and MardisBot was not redeployed afterwards. The deployment details below are historical and no longer match the live system.

Historical deployment details (no longer present)

  • Host: tgbots (192.168.1.178)
  • User: ubuntu
  • Project Path: /home/ubuntu/bots/MardisBot — directory does not exist
  • Virtual Environment: /home/ubuntu/bots/MardisBot/venv — does not exist
  • Main Script: bot.py

Historical systemd service

  • Service Name: mardisbot.service — unit does not exist (systemctl status mardisbot.service → "could not be found"; no journal history for the unit)
  • Unit File: /etc/systemd/system/mardisbot.service — absent
  • Restart Policy: always, interval 30 seconds

Service management (if redeployed)

# Check status
sudo systemctl status mardisbot.service

# View logs
sudo journalctl -u mardisbot.service -f

# Restart service
sudo systemctl restart mardisbot.service

Dependencies (historical)

Installed via pip in the local venv:

  • python-telegram-bot[job-queue]
  • python-dotenv

2026-09-10 audit evidence (tgbots)

  • No bot-like processes in ps auxww (only system daemons, postgres, and the marginator gunicorn on port 5001).
  • No bot systemd units; only marginator.service exists in /etc/systemd/system/.
  • Docker: only marginator-caddy-1, marginator-backend-1, marginator-db-1 (all Up). No bot containers or images.
  • No cron jobs, no tmux/screen sessions, no bot project directories.
  • Filesystem-wide token search (bot[0-9]{6,10}:... pattern) over /home /opt /srv /etc /usr/local /var: zero matches.
  • Listening ports: 22 (sshd), 443/8080 (caddy), 5001 (marginator backend), 53 (resolved), 46831 (containerd). No bot listener.
  • No outbound connections to Telegram API IP ranges (149.154.x, 91.108.x).
  • No python-telegram-bot/aiogram/telebot/pyrogram packages on host or in the marginator backend container; no telegram mentions in apt history.