Wearg - Revision history

Dereckson: /* MariaDB server connectivity */

2026-03-21T09:48:02Z

MariaDB server connectivity

← Older revision		Revision as of 09:48, 21 March 2026
Line 27:		Line 27:
	If the MariaDB connection is broken, <code>.+log [server] message works</code>, but not directly <code>[server] message</code>.		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		* Short-term solution: <code>.tcl sqlrehash</code> in the Wearg partyline
	Long-term solution: {{T\|2282}}		* Long-term solution: automate reconnect with {{T\|2282}}

Dereckson at 09:47, 21 March 2026

2026-03-21T09:47:30Z

← Older revision		Revision as of 09:47, 21 March 2026
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}}

213.189.173.103: Created page with "Wearg is an eggdrop and a notifications clients. Services → Notifications center → broker →..."

2016-09-05T00:14:05Z

Created page with "Wearg is an eggdrop and a notifications clients. Services → Notifications center → broker →..."

New page

Wearg is an eggdrop and a notifications clients.

Services → [[Operations grimoire/Notifications center|Notifications center]] → [[Operations grimoire/Broker|broker]] → Wearg

== 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:

# Check we're connected through <code>.tcl mq connected</code>
# If so, disconnect it with <code>.tcl mq disconnect</code>
# Check timer through .tcl utimers, you should have one (and only one) timer with ::broker::on_tick as callback
## Too many timers? kill extra timers with <code>.tcl killutimer timer<id></code>, good luck for the guess the second game
## No timer? <code>.tcl broker::on_tick</code>
# 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