Operations grimoire/Checklist router post-restart - Revision history

Dereckson: +cats

2024-10-26T20:36:23Z

+cats

← Older revision		Revision as of 20:36, 26 October 2024
Line 19:		Line 19:

	[https://devcentral.nasqueron.org/T1862 T1862] offers to detect MySQL issues and reconnect.		[https://devcentral.nasqueron.org/T1862 T1862] offers to detect MySQL issues and reconnect.

			[[Category:Operations grimoire]]
			[[Category:IRC bots]]

Dereckson at 21:35, 12 May 2023

2023-05-12T21:35:41Z

← Older revision		Revision as of 21:35, 12 May 2023
Line 4:		Line 4:

	To partially prevent this, a blue/green deployment or immutable artifacts should be encouraged. It's recommended for the next non urgent upgrade to create router-002 and move GRE connections to it. The checklist should still be checked.		To partially prevent this, a blue/green deployment or immutable artifacts should be encouraged. It's recommended for the next non urgent upgrade to create router-002 and move GRE connections to it. The checklist should still be checked.

			As most services are currently on hyper-001, they don't need the router to communicate, so lot of things will still be working.

	== IRC eggdrops ==		== IRC eggdrops ==

			They require a GRE tunnel between server with viperserv role and the router to connect to both complector (Vault) and a db-B server (MariaDB).

			On Libera:
	* Dæghrefn: MySQL is normally at periodic interval reconnected, but you can trigger this with <code>.tcl sqlrehash</code>		* Dæghrefn: MySQL is normally at periodic interval reconnected, but you can trigger this with <code>.tcl sqlrehash</code>
	* Wearg: MySQL does NOT reconnect, and that will probably exit from the timer		* Wearg: MySQL does NOT reconnect, and that will probably exit from the timer

Dereckson: Created page with "A router-001 restart severes GRE tunnels and their existing TCP connections. As such, this checklist notes the known issues when private network is disrupted. To partially prevent this, a blue/green deployment or immutable artifacts should be encouraged. It's recommended for the next non urgent upgrade to create router-002 and move GRE connections to it. The checklist should still be checked. == IRC eggdrops == * Dæghrefn: MySQL is normally at periodic interval reco..."

2023-05-12T21:33:20Z

Created page with "A router-001 restart severes GRE tunnels and their existing TCP connections. As such, this checklist notes the known issues when private network is disrupted. To partially prevent this, a blue/green deployment or immutable artifacts should be encouraged. It's recommended for the next non urgent upgrade to create router-002 and move GRE connections to it. The checklist should still be checked. == IRC eggdrops == * Dæghrefn: MySQL is normally at periodic interval reco..."

New page

A router-001 restart severes GRE tunnels and their existing TCP connections.

As such, this checklist notes the known issues when private network is disrupted.

To partially prevent this, a blue/green deployment or immutable artifacts should be encouraged. It's recommended for the next non urgent upgrade to create router-002 and move GRE connections to it. The checklist should still be checked.

== IRC eggdrops ==

* Dæghrefn: MySQL is normally at periodic interval reconnected, but you can trigger this with <code>.tcl sqlrehash</code>
* Wearg: MySQL does NOT reconnect, and that will probably exit from the timer
** <code>.tcl sqlrehash</code> to reconnect to MySQL
** <code>.tcl broker::on_tick</code> to reconnect to broker and start timer to get message
** <code>.tcl utimers</code> to ensure timer is good, you should see a <code>:broker::on_tick</code> timer

[https://devcentral.nasqueron.org/T1862 T1862] offers to detect MySQL issues and reconnect.