Operations grimoire/Restart a Docker engine - Revision history

Dereckson at 21:40, 12 May 2023

2023-05-12T21:40:13Z

← Older revision		Revision as of 21:40, 12 May 2023
Line 1:		Line 1:
			'''This containers historical notes from 2016. This page reflect only partially the current state of our Docker engines. Yet, the broker/Wearg thing is for example still current in 2023.'''

	== Restart ==		== Restart ==
	A lot of vital components are managed by Docker.		A lot of vital components are managed by Docker.
Line 10:		Line 12:
	== Services needing manual tweaking after container restart ==		== Services needing manual tweaking after container restart ==
	=== Phabricator instances ===		=== Phabricator instances ===
	DevCentral ~~needs~~:		If DevCentral complains SSH hosting or daemons isn't available:

	# ~~bin/phd~~ status		# sv status sshd-hosting (if needed sv start sshd-hosting)
	~~# bin/phd stop <the PID of PhabricatorBot>~~
	# sv restart phd		# sv restart phd
	~~# chpst -u app bin/phd launch PhabricatorBot /opt/phabricator/conf/xessife.json~~

	Other instances ~~needs~~ a <code>sv restart phd</code>.		Other instances need only a <code>sv restart phd</code>.

	=== Broker ===		=== Broker ===

Dereckson: /* Error response from daemon: Unknown runtime specified oci */

2017-02-14T03:03:00Z

Error response from daemon: Unknown runtime specified oci

← Older revision		Revision as of 03:03, 14 February 2017
Line 75:		Line 75:
	You can, change the runtime in the container configuration following instructions from [https://umbra.xyz/fix-docker-unknown-runtime-specified-oci-error/ this post].		You can, change the runtime in the container configuration following instructions from [https://umbra.xyz/fix-docker-unknown-runtime-specified-oci-error/ this post].

	Do that only for containers you don't want to respin (e.g. devcentral). Others you can safely rm and respin.		Do that only for containers you don't want to respin (e.g. devcentral). Others you can safely rm and respin instead.

Dereckson: /* Troubleshooting */

2017-02-14T03:02:28Z

Troubleshooting

← Older revision		Revision as of 03:02, 14 February 2017
Line 67:		Line 67:

	Commit a backup Docker image based on the current content with with docker commit <name> <name>-bak. That will allow investigation.		Commit a backup Docker image based on the current content with with docker commit <name> <name>-bak. That will allow investigation.

			=== Error response from daemon: Unknown runtime specified oci ===
			The container doesn't use the current runtime.

			It's currently <code>docker-runc</code> but was previously for a short time <code>oci</code>.

			You can, change the runtime in the container configuration following instructions from [https://umbra.xyz/fix-docker-unknown-runtime-specified-oci-error/ this post].

			Do that only for containers you don't want to respin (e.g. devcentral). Others you can safely rm and respin.

Dereckson: /* What containers need MySQL and symptoms when not reachable? */ How to check CI?

2016-07-22T23:11:09Z

What containers need MySQL and symptoms when not reachable?: How to check CI?

← Older revision		Revision as of 23:11, 22 July 2016
Line 39:		Line 39:
	! Container !! MySQL priority !! Symptom when not running		! Container !! MySQL priority !! Symptom when not running
	\|-		\|-
	\| silly_bardeen \|\| Needed for some CI tasks \|\| Jenkins jobs '''test-auth-grove-*''' will fail:~~<br />~~PHPUnit test issue: \Tests\Models\UsersTest::testTryGetFromExternalSource<br />PDOException: SQLSTATE[HY000] [2002] php_network_getaddresses: getaddrinfo failed: Name or service not known		\| silly_bardeen \|\| Needed for some CI tasks \|\| Jenkins jobs '''test-auth-grove-*''' will fail:

			PHPUnit test issue: \Tests\Models\UsersTest::testTryGetFromExternalSource<br />
			PDOException: SQLSTATE[HY000] [2002] php_network_getaddresses: getaddrinfo failed: Name or service not known

			To test if all works:
			<pre>
			$ su app
			$ cd ~/workspace/test-auth-grove-php
			$ phpunit --no-coverage
			OK (37 tests, 58 assertions)
			</pre>
	\|-		\|-
	\| cachet \|\| High \|\| App doesn't work		\| cachet \|\| High \|\| App doesn't work

Dereckson: /* Troubleshooting */

2016-07-22T23:04:39Z

Troubleshooting

@@ Line 30: / Line 30: @@
 == Troubleshooting ==
-=== When MySQL isn't reacheable ===
+=== When MySQL isn't reachable ===
 If the MySQL container (acquisitariat) IP changed, you need to tweak /etc/hosts in every depending container (Phabricator instances, cachet, pad, login) and ensure there is a <code><correct IP> mysql</code> line.
 === When a container doesn't want to restart ===

Dereckson: /* Restart */

2016-07-22T03:10:06Z

Restart

← Older revision		Revision as of 03:10, 22 July 2016
Line 6:		Line 6:
	# Restart Docker engine		# Restart Docker engine
	# Restart containers, either manually, either with the docker-containers systemd unit		# Restart containers, either manually, either with the docker-containers systemd unit
	# Run [[Operations grimoire/~~production~~ tests\|production tests]]		# Run [[Operations grimoire/Production tests\|production tests]]

	== Services needing manual tweaking after container restart ==		== Services needing manual tweaking after container restart ==

Dereckson at 20:15, 21 July 2016

2016-07-21T20:15:11Z

← Older revision		Revision as of 20:15, 21 July 2016
Line 1:		Line 1:
	A lot of vital components ~~belong to~~ Docker.		== Restart ==
			A lot of vital components are managed by Docker.

	Ideally, we should have redundancy to avoid container lost.		Ideally, we should have redundancy to avoid container lost.

	# Restart Docker engine		# Restart Docker engine
	# Restart containers, either manually, either with docker-containers systemd unit		# Restart containers, either manually, either with the docker-containers systemd unit
	# Run [[Operations grimoire/production tests\|production tests]]		# Run [[Operations grimoire/production tests\|production tests]]
	~~# Run~~

	== Services needing manual tweaking after container restart ==		== Services needing manual tweaking after container restart ==

Dereckson: Created page with "A lot of vital components belong to Docker. Ideally, we should have redundancy to avoid container lost. # Restart Docker engine # Restart containers, either manually, either..."

2016-07-21T20:07:12Z

Created page with "A lot of vital components belong to Docker. Ideally, we should have redundancy to avoid container lost. # Restart Docker engine # Restart containers, either manually, either..."

New page

A lot of vital components belong to Docker.

Ideally, we should have redundancy to avoid container lost.

# Restart Docker engine
# Restart containers, either manually, either with docker-containers systemd unit
# Run [[Operations grimoire/production tests|production tests]]
# Run

== Services needing manual tweaking after container restart ==
=== Phabricator instances ===
DevCentral needs:

# bin/phd status
# bin/phd stop <the PID of PhabricatorBot>
# sv restart phd
# chpst -u app bin/phd launch PhabricatorBot /opt/phabricator/conf/xessife.json

Other instances needs a <code>sv restart phd</code>.

=== Broker ===
Wearg needs to be manually reconnected to the broker:

# .tcl mq disconnect
# .tcl utimers and kill remaining timers if needed
# .tcl mq broker::connect
# .tcl broker::on_tick

That requires a owner access to Wearg (ping Dereckson).

== Troubleshooting ==
=== When MySQL isn't reacheable ===
If the MySQL container (acquisitariat) IP changed, you need to tweak /etc/hosts in every depending container (Phabricator instances, cachet, pad, login) and ensure there is a <code><correct IP> mysql</code> line.

=== When a container doesn't want to restart ===
Try first to see what happens with docker logs <container name>.

If that doesn't work, go to the services section of the grimoire and reprovision it.

Commit a backup Docker image based on the current content with with docker commit <name> <name>-bak. That will allow investigation.