admin-how-to - Revision history

GRegorLove: how to: create new wiki accounts

2021-02-17T00:55:45Z

how to: create new wiki accounts

← Older revision		Revision as of 00:55, 17 February 2021
Line 2:		Line 2:

	This is a reference for various tasks that admins may have to perform.		This is a reference for various tasks that admins may have to perform.

			== create new wiki accounts ==
			Public account creation is currently restricted, so an admin will need to create new accounts when requested.

			* In a private message, confirm with the person what their desired username is
			* Open [[Special:CreateAccount]]
			* Enter the desired username and a random password -- use a random password generator like [https://my.norton.com/extspa/idsafe?path=pwd-gen Norton's Password Generator]
			* In a private message, let the person know the password
			* Instruct them to log in and change their password

	== web server restart ==		== web server restart ==

2020-07-18T16:20:50Z

Replace <entry-title> with {{DISPLAYTITLE:}}

← Older revision		Revision as of 16:20, 18 July 2020
Line 1:		Line 1:
	~~<entry-title>~~admin how-to~~</entry-title>~~		{{DISPLAYTITLE:admin how-to}}

	This is a reference for various tasks that admins may have to perform.		This is a reference for various tasks that admins may have to perform.

2017-03-28T17:35:31Z

irc

← Older revision		Revision as of 17:35, 28 March 2017
Line 93:		Line 93:

	Well below 100% usage. If you're seeing something >50%, you might want to look at purging old logs.		Well below 100% usage. If you're seeing something >50%, you might want to look at purging old logs.


			== irc ==
			[[Loqi]] is in the #microformats [[irc]] channel and logs to https://chat.indieweb.org/microformats
			* If not (either), see https://indieweb.org/Loqi for instructions

			[[Loqi]] passes along wiki edits to the [[irc]] channel as well
			* If not, check {server-www-home}/wiki/LocalSettings.php for $wgRC2UDPAddress and make sure it is set to the right host (or IP) (e.g. 'freenode.loqi.me').
			** Log any changes you make (at least locally yourself), so you can revert anything in case something unexpected/unrelated goes wrong, then investigate after reverting so people can keep using the site.
			** Changes should take effect immediately after edits to LocalSettings.php are saved (no need to restart MediaWiki or Apache).

	== wordpress ==		== wordpress ==
Line 99:		Line 109:
	<a href="<?php bloginfo('rss2_url'); ?>" id="footer-feed">RSS Feed</a>		<a href="<?php bloginfo('rss2_url'); ?>" id="footer-feed">RSS Feed</a>
	</source>		</source>


	== server transition steps ==		== server transition steps ==

2012-12-04T00:18:34Z

mail server restart: mail server debugging

← Older revision		Revision as of 00:18, 4 December 2012
Line 65:		Line 65:

	Last param options are: stop/start/restart		Last param options are: stop/start/restart

			=== mail server debugging ===
			To check to see if unix permissions are compatible with what Mailman needs, you can:
			* ssh into the server and then do:
			* <kbd>sudo /usr/lib/mailman/bin/check_perms -f</kbd>

			The -f reports which directories or binaries had to be changed.

	== reboot entire server ==		== reboot entire server ==

2012-12-04T00:16:14Z

mail server restart

← Older revision		Revision as of 00:16, 4 December 2012
Line 57:		Line 57:

	… and then proceed to restart as before.		… and then proceed to restart as before.

			== mail server restart ==
			If sending mail to a list address doesn't seem to send it along (nor appear in the archives), try restarting Mailman:

			* ssh into the server and then do:
			* <kbd>sudo /usr/lib/mailman/bin/mailmanctl restart</kbd>

			Last param options are: stop/start/restart

	== reboot entire server ==		== reboot entire server ==

2012-10-16T22:03:42Z

web server restart: update location of error log

← Older revision		Revision as of 22:03, 16 October 2012
Line 13:		Line 13:
	* ssh into the server		* ssh into the server
	* check for web server errors (sometimes this can reveal the source of a problem)		* check for web server errors (sometimes this can reveal the source of a problem)
	** <code>tail /var/log/~~httpd~~/~~error_log~~</code>		** <code>tail /var/log/apache2/error.log</code>
	* find the apache install (it might not be where you expect it or it might have moved)		* find the apache install (it might not be where you expect it or it might have moved)
	** <code>locate apache</code>		** <code>locate apache</code>

2012-10-16T21:50:15Z

reboot entire server: check disk space

← Older revision		Revision as of 21:50, 16 October 2012
Line 67:		Line 67:

	After about 10-15 seconds at most, you should be able to load microformats.org pages as before, and they should load fairly quickly.		After about 10-15 seconds at most, you should be able to load microformats.org pages as before, and they should load fairly quickly.

			== check disk space ==
			After rebooting, check disk space in case the server has somehow filled (or is getting close to filling) its disks. From the ssh command line, do:
			* df
			You should see something like:
			<source lang=text>
			Filesystem 1K-blocks Used Available Use% Mounted on
			/dev/vzfs 80000000 15072204 64927796 19% /
			</source>

			Well below 100% usage. If you're seeing something >50%, you might want to look at purging old logs.

	== wordpress ==		== wordpress ==

2012-10-16T21:47:04Z

another out of memory message you might see

← Older revision		Revision as of 21:47, 16 October 2012
Line 40:		Line 40:
	* report back on IRC or Twitter to whoever pointed out that the server was down.		* report back on IRC or Twitter to whoever pointed out that the server was down.

	If the server is (still) sluggish to respond, you may need to reboot the entire server (see below, [[#reboot_entire_server]]).		If you see an error like:
			<source lang=text>-bash: fork: Cannot allocate memory</source>
			or if the server is (still) sluggish to respond, you may need to reboot the entire server (see below, [[#reboot_entire_server]]).

	=== semaphore exhaustion ===		=== semaphore exhaustion ===

2012-06-20T13:37:34Z

wordpress

← Older revision		Revision as of 13:37, 20 June 2012
Line 65:		Line 65:

	After about 10-15 seconds at most, you should be able to load microformats.org pages as before, and they should load fairly quickly.		After about 10-15 seconds at most, you should be able to load microformats.org pages as before, and they should load fairly quickly.

			== wordpress ==
			RSS feed link:
			<source lang=php>
			<a href="<?php bloginfo('rss2_url'); ?>" id="footer-feed">RSS Feed</a>
			</source>

	== server transition steps ==		== server transition steps ==

2012-04-30T10:41:16Z

reboot entire server

← Older revision		Revision as of 10:41, 30 April 2012
Line 39:		Line 39:
	* now try browsing to http://microformats.org/ and make sure it loads		* now try browsing to http://microformats.org/ and make sure it loads
	* report back on IRC or Twitter to whoever pointed out that the server was down.		* report back on IRC or Twitter to whoever pointed out that the server was down.

			If the server is (still) sluggish to respond, you may need to reboot the entire server (see below, [[#reboot_entire_server]]).

	=== semaphore exhaustion ===		=== semaphore exhaustion ===
Line 53:		Line 55:

	… and then proceed to restart as before.		… and then proceed to restart as before.

			== reboot entire server ==
			If the web server is very slow to respond, especially after attempting to restart it as above, then you may need to reboot the entire server.

			* ssh into the server, and then do:
			* <kbd>sudo reboot -n</kbd>

			You'll need to close your ssh window and reconnect.

			After about 10-15 seconds at most, you should be able to load microformats.org pages as before, and they should load fairly quickly.

	== server transition steps ==		== server transition steps ==