Wearg: Difference between revisions

From Nasqueron Agora
Created page with "Wearg is an eggdrop and a notifications clients. Services → Notifications centerbroker →..."
 
No edit summary
Line 1: Line 1:
Wearg is an eggdrop and a notifications clients.
Wearg is an eggdrop and a notifications client.


== Features ==


Services [[Operations grimoire/Notifications center|Notifications center]] [[Operations grimoire/Broker|broker]] Wearg
Wearg handles two important workflows for the Nasqueron Operations SIG:
 
* Publish notifications on IRC channels: Services --HTTPS--> [[Operations grimoire/Notifications center|Notifications center]] --AMQP--> [[Operations grimoire/RabbitMQ|broker]] --AMQP--> Wearg --IRC--> Channel publication
* Allow to log to servers log: Channel publication --HTTPS--> Nasqueron API --IO--> servers log


== Troubleshoot ==
== Troubleshoot ==
Line 17: Line 21:
# Ask next message in the queue .tcl mq get wearg-notifications
# Ask next message in the queue .tcl mq get wearg-notifications
# If stuck at the previous operation, close the connection through the broker interface: http://white-rabbit.nasqueron.org:15672/#/connections (username is daeghrefn, source IP is 212.83.187.132). This method is pretty effective
# If stuck at the previous operation, close the connection through the broker interface: http://white-rabbit.nasqueron.org:15672/#/connections (username is daeghrefn, source IP is 212.83.187.132). This method is pretty effective
=== Can't publish to servers log ===
==== MariaDB server connectivity ====
If the MariaDB connection is broken, <code>.+log [server] message works</code>, but not directly <code>[server] message</code>.
Short-term solution: <code>.tcl sqlrehash</code> in the Wearg partyline
Long-term solution: {{T|2282}}

Revision as of 09:47, 21 March 2026

Wearg is an eggdrop and a notifications client.

Features

Wearg handles two important workflows for the Nasqueron Operations SIG:

  • Publish notifications on IRC channels: Services --HTTPS--> Notifications center --AMQP--> broker --AMQP--> Wearg --IRC--> Channel publication
  • Allow to log to servers log: Channel publication --HTTPS--> Nasqueron API --IO--> servers log

Troubleshoot

No messages are received

Check through another client (the CLI client for example) all works fine at notifications center and broker level.

If so:

  1.  Check we're connected through .tcl mq connected
  2. If so, disconnect it with .tcl mq disconnect
  3. Check timer through .tcl utimers, you should have one (and only one) timer with ::broker::on_tick as callback
    1. Too many timers? kill extra timers with .tcl killutimer timer<id>, good luck for the guess the second game
    2. No timer? .tcl broker::on_tick
  4. Ask next message in the queue .tcl mq get wearg-notifications
  5. If stuck at the previous operation, close the connection through the broker interface: http://white-rabbit.nasqueron.org:15672/#/connections (username is daeghrefn, source IP is 212.83.187.132). This method is pretty effective

Can't publish to servers log

MariaDB server connectivity

If the MariaDB connection is broken, .+log [server] message works, but not directly [server] message.

Short-term solution: .tcl sqlrehash in the Wearg partyline Long-term solution: T2282