title: MardisBot description: Telegram bot for Mardis group host: tgbots status: missing last_reviewed: 2026-09-10 owner: gmikcon confidence: 95 review_interval: 90
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.
tgbots (192.168.1.178)ubuntu/home/ubuntu/bots/MardisBot — directory does not exist/home/ubuntu/bots/MardisBot/venv — does not existbot.pymardisbot.service — unit does not exist (systemctl status mardisbot.service → "could not be found"; no journal history for the unit)/etc/systemd/system/mardisbot.service — absentalways, interval 30 seconds# Check status sudo systemctl status mardisbot.service # View logs sudo journalctl -u mardisbot.service -f # Restart service sudo systemctl restart mardisbot.service
Installed via pip in the local venv:
python-telegram-bot[job-queue]python-dotenvps auxww (only system daemons, postgres, and the marginator gunicorn on port 5001).marginator.service exists in /etc/systemd/system/.marginator-caddy-1, marginator-backend-1, marginator-db-1 (all Up). No bot containers or images.bot[0-9]{6,10}:... pattern) over /home /opt /srv /etc /usr/local /var: zero matches.