title: MardisOpsBot description: Telegram ops bot for monitoring and controlling mardisbot.service host: tg_bots-vm status: active last_reviewed: 2026-09-10 owner: gmikcon confidence: 100 review_interval: 90
Telegram ops bot for monitoring and controlling mardisbot.service (see 10-systems/bots/mardisbot.md).
Naming warning: there are TWO similarly named hosts. This bot lives on the VM
tg_bots(192.168.1.254, hostnametgbots) — NOT on the external VPStgbots(192.168.1.178, hostnamevmk).
tg_bots, 192.168.1.254 (libvirt on bserv 192.168.1.130)ubuntu (password in gnexus-creds secret "tgbots"; sudo uses the same password)/home/ubuntu/bots/MardisOpsBotbot.py (venv: /home/ubuntu/bots/MardisOpsBot/venv, Python 3.10).env in project dir (bot token, not documented here)mardisops.service — active (running), enabled/etc/systemd/system/mardisops.service/etc/sudoers.d/99-mardisops-sudoers (root:root, 0440, visudo -c OK) allows user ubuntu NOPASSWD for: systemctl status/is-active/is-enabled/show mardisbot.service, systemctl restart mardisbot.service, and journalctl -u mardisbot.service *.sudo systemctl status mardisops.service sudo journalctl -u mardisops.service -f sudo systemctl restart mardisops.service
ops bot starting; admins=[] (max 3) — admins are enrolled via Telegram (maximum 3)polling started