Page MenuHomeLubuntu Development

Deal with Lugito notifications
Open, NormalPublic

Description

Sometimes Lugito (our trusty IRC notifications bot) has some sort of error and I have to manually go in and Ctrl + C the tmux session, and then restart. This is less than ideal, and if I go a few days without having the time to SSH in, it can be problematic.

The problem is also that when Lugito rejoins, it spams notifications that have been queued up.

This task is twofold:

  1. Find out why Lugito keeps failing on us and patch it up.
  2. To discuss our options for (and potentially the usefulness of) project notifications.

Event Timeline

tsimonq2 triaged this task as Normal priority.Fri, Aug 2, 8:35 PM
tsimonq2 created this task.

Without any log files or stack traces, it is quite challenging to find out the reason. (Maybe you have to clean the logfile from access tokens and other sensitive data prior to publish them)

Isn't Lugito running as a systemd unit? It looks like as if it could be handled all by systemd:

Restart=always
RestartSec=5

and you can use journalctl -u $lugito.service to investigate.