You are browsing a read-only backup copy of Wikitech. The live site can be found at wikitech.wikimedia.org

Application servers: Difference between revisions

From Wikitech-static
Jump to navigation Jump to search
imported>Alex Monk
No edit summary
imported>Krinkle
No edit summary
 
(32 intermediate revisions by 18 users not shown)
Line 1: Line 1:
The Apache configs are maintained in a Git repository at [https://github.com/wikimedia/operations-puppet/tree/production/modules/mediawiki/files/apache/sites operations/puppet.git:/modules/mediawiki/files/apache/sites/]. Before July 11th 2012 these were in Subversion.
{{Navigation Wikimedia infrastructure|expand=mw}}
{{See|See also '''[[Application servers/Runbook]]''' for how to perform common tasks, or diagnose issues.}}


==Deploying config==
The '''Application servers''' (or '''app servers''') are the several hundred Apache servers that run [[MediaWiki]] (PHP application).
It is suggested that you may wish to place any configuration updates on the [[Deployments]] page.  A bad configuration going live can easily result in a site outage.


* Submit change to [[gerrit]] in the <code>modules/mediawiki/files/apache/sites</code> directory (project: operations/puppet)
==Service==
* disable puppet across the mw-cluster (so you can test the change to a single host): <code>salt --batch-size=25% 'mw*' cmd.run 'puppet agent --disable'</code>
Puppet roles:
* Merge via gerrit
* <code>mediawiki::appserver</code>, <code>mediawiki::canary_appserver</code>
* on [[palladium]]: <code>puppet merge</code>
* <code>mediawiki::appserver::api</code>, <code>mediawiki::appserver::canary_api</code>
{{warning}} check if the config does not break Apache! You can do this by just disabling puppet on the appservers, run the puppet tagged run to a single server and restarting that manually before pushing out to all. Use a test script to check multiple URLs to see if redirect changes work.
* <code>mediawiki::maintenance</code>
* go to one server and manually re-enable puppet & run puppet
* <code>mediawiki::jobrunner</code>
:* confirm the configuration changes go through
* go to one mw server and do <code>apache2ctl configtest</code>
* create a plain text file with some significant URLs you touched and use "apache-fast-test url.file mw1234" on tin to test against your one test host.
* once test works, re-enable puppet across the mw hosts: <code>salt --batch-size=25% 'mw*' cmd.run 'puppet agent --enable'</code>
* sync the code via a tagged puppet run on appservers: <code>salt --batch-size=25% 'mw*' cmd.run 'puppet agent -t --tags mw-apache-config'</code>


* Test change from external
Relevant puppet classes:
* <code>[https://gerrit.wikimedia.org/g/operations/puppet/+/HEAD/modules/profile/manifests/mediawiki/webserver.pp profile::mediawiki::webserver]</code>, this provisions Apache, and any other packages or resources needed by MediaWiki on app servers.
** <code>[https://gerrit.wikimedia.org/g/operations/puppet/+/HEAD/modules/profile/manifests/mediawiki/httpd.pp profile::mediawiki::httpd]</code>, the Apache service.
** <code>[https://gerrit.wikimedia.org/r/plugins/gitiles/operations/puppet/+/HEAD/modules/mediawiki/manifests/web/prod_sites.pp mediawiki::web::prod_sites]</code>, the Apache configuration for all production websites (including wikipedia.org).
** Additional Apache configurations are at [https://github.com/wikimedia/operations-puppet/tree/production/modules/mediawiki/files/apache/sites modules/mediawiki/files/apache/sites/]. Prior to 2012, Apache configuration were in a Subversion repository.


==Restarting==
==Architecture==
{{See also|MediaWiki at WMF|HTTP timeouts#App servers}}


===All===
The application servers are load-balanced via [[LVS]]. Connections between our CDN (HTTP cache proxies) and app servers are encrypted with TLS, which is terminated locally on the app server using [[Envoy]]. Envoy then hands the request off to the local Apache.
Use [[Salt]] from a salt master like [[palladium]].


===One, to test a change===
'''Apache''' is in charge of handling redirects, rewrite rules, and determining the [[MediaWiki at WMF#Document root|document root]]. It then uses <code>php-fpm</code> to invoke the MediaWiki software.
Ssh to the web server you want to test on. Then restart apache on that web server only. Test your change with curl, as with this foundation example:


<code>curl -H 'Host: wikimediafoundation.org' "http://localhost/fundraising"</code>
The Apache [https://httpd.apache.org/docs/2.4/mpm.html MPM] we use is [https://httpd.apache.org/docs/2.4/mod/worker.html mod_worker]</code>, which decides how <code>php-fpm</code> processes are spawned.
 
The raw HTML for the page will now be displayed in your window. You can copy and paste that into a file on your hard drive and open it with your browser to see the effect. Host is the name of the web site after the http:// part in your browser URL area. GET /fundraising is the part after the site name. The example gets http://wikimediafoundation.org/fundraising.


==Logging==
==Logging==


Apache errors are logged to /a/mw-log/apache2.log on fluorine.
Apache errors are logged to <code>/srv/mw-log/apache2.log</code> on <code>mwlog1001</code>.
 
Apache access logs are mostly disabled. Webalizer statistics are made using the [[squids]] logs instead.
 
==Apache setup checklist==
 
* Follow the [[Automated installation]] instructions for the base install
* Run the following on the server:
:* <tt>apt-get update && apt-get dist-upgrade -y && apt-get install wikimedia-task-appserver && reboot && exit </tt>
* Wait for the server to come back online, ensure it starts apache correctly
** <tt>echo 'GET /' | nc localhost 80</tt> or any of the number of tests listed below
* If the server is part of the memcached group, follow instructions on [[Memcached]]
* Run the setup of [[Ganglia]]
* If the server is new, you will need to do the following:
:* Login to the LVS server for apaches (lvs3 as of 2009-02-13) and add the new servers to /etc/pybal/apaches
* If the server is not new do the following:
:* Ensure the server is now enabled in pybal on the LVS server in the file /etc/pybal/apaches
* You will need to add the server to [[DSH]] groups if new, or check if they are commented, if the server is not new:
:* Add/Uncomment the host to /usr/local/dsh/node_groups/apaches and mediawiki-installation, as well as any other groups needed
:* Reload nagios to accept the changes to the node groups:
::* <tt>cd /home/wikipedia/conf/nagios && ./sync </tt>
* Verify that the server is tacking traffic and doing work
:* <tt>ipvsadm -L | grep SERVERNAME </tt>
:* traffic logs?
 
==Test cases==
 
Here are some test cases you can use to test the apache configuration after changing something.
 
<pre>
GET /wiki/Foo HTTP/1.1
Host: en.wikipedia.org
User-agent: testthing
 
GET /wiki/Foo HTTP/1.1
Host: www.wikipedia.org
User-agent: testthing
 
GET / HTTP/1.1
Host: en2.wikipedia.org
User-agent: testthing
 
GET /wiki/Main_Page HTTP/1.1
Host: www.wikipedia.com
User-agent: testthing


GET / HTTP/1.1
Apache access logs are mostly disabled. Statistics are drawn from [[Varnish]] front ends instead.
Host: wikipedia.com
User-agent: testthing


GET / HTTP/1.1
== Hardware repair ==
Host: wikibooks.org
{{Outdated-inline|year=2015}}
User-agent: testthing


GET / HTTP/1.1
Host: wikiquote.org
User-agent: testthing
GET / HTTP/1.1
Host: dk.wikipedia.org
User-agent: testthing
GET / HTTP/1.1
Host: foo.wikipedia.org
User-agent: testthing
GET /wiki/Main_Page HTTP/1.1
Host: test.wikipedia.org
User-agent: testthing
GET / HTTP/1.1
Host: webshop.wikipedia.org
User-agent: testthing
GET / HTTP/1.1
Host: boards.wikimedia.org
User-agent: testthing
GET /wiki/Foo HTTP/1.1
Host: en.wikipedia.org
User-Agent: Exalead
GET /wiki/Foo HTTP/1.1
Host: meta.wikimedia.org
User-agent: testthing
GET / HTTP/1.1
Host: en.wiktionary.org
User-agent: testthing
</pre>
== Hardware Repair ==
==== Application Servers ====
When taking down application servers (running mediawiki) for things like disk replacement or other hardware repair, _do not forget to_:
When taking down application servers (running mediawiki) for things like disk replacement or other hardware repair, _do not forget to_:
* before: remove from dsh group
* before: remove from dsh group
Line 135: Line 42:
See [[pybal]]. You can just grep for the server name and set 'enabled': False and save.
See [[pybal]]. You can just grep for the server name and set 'enabled': False and save.
* before: check nobody is scapping right now (best: announce with a !log line in IRC)
* before: check nobody is scapping right now (best: announce with a !log line in IRC)
This is an IRC thing on freenode in #wikimedia-dev/-tech-/-operations
This is an IRC thing on libera.chat in {{irc|wikimedia-dev}}/{{irc|wikimedia-tech}}/{{irc|wikimedia-operations}}
* during: acknowledge Icinga monitoring checks (best: with related ticket number as comment)
* during: acknowledge Icinga monitoring checks (best: with related ticket number as comment)
Do this by logging in via browser on icinga.wikimedia.org. search for the hostname, check all services and use the "acknowledge" option. You'll see the IRC bots outputting this as well and they will stop repeating things over and over in the channels.
Do this by logging in via browser on icinga.wikimedia.org. search for the hostname, check all services and use the "acknowledge" option. You'll see the IRC bots outputting this as well and they will stop repeating things over and over in the channels.
Line 143: Line 50:
Revert the above.
Revert the above.


 
== See also ==
* [[Apache log format]]
* [[UID]]


[[Category:Servers by usage| Apache]]
[[Category:Servers by usage| Apache]]
[[Category:MediaWiki production| ]]
[[Category:SRE Service Operations]]

Latest revision as of 02:30, 1 May 2022

The Application servers (or app servers) are the several hundred Apache servers that run MediaWiki (PHP application).

Service

Puppet roles:

  • mediawiki::appserver, mediawiki::canary_appserver
  • mediawiki::appserver::api, mediawiki::appserver::canary_api
  • mediawiki::maintenance
  • mediawiki::jobrunner

Relevant puppet classes:

Architecture

The application servers are load-balanced via LVS. Connections between our CDN (HTTP cache proxies) and app servers are encrypted with TLS, which is terminated locally on the app server using Envoy. Envoy then hands the request off to the local Apache.

Apache is in charge of handling redirects, rewrite rules, and determining the document root. It then uses php-fpm to invoke the MediaWiki software.

The Apache MPM we use is mod_worker, which decides how php-fpm processes are spawned.

Logging

Apache errors are logged to /srv/mw-log/apache2.log on mwlog1001.

Apache access logs are mostly disabled. Statistics are drawn from Varnish front ends instead.

Hardware repair

When taking down application servers (running mediawiki) for things like disk replacement or other hardware repair, _do not forget to_:

  • before: remove from dsh group

These are in puppet, operations/puppet repo, in modules/dsh/files/group. The important one for Mediawiki sync is "mediawiki-installation".

  • before: de-pool in pybal
  • TODO: Document what to do if it's a scap proxy (see hieradata/common/dsh/config.yaml)

See pybal. You can just grep for the server name and set 'enabled': False and save.

  • before: check nobody is scapping right now (best: announce with a !log line in IRC)

This is an IRC thing on libera.chat in #wikimedia-dev connect/#wikimedia-tech connect/#wikimedia-operations connect

  • during: acknowledge Icinga monitoring checks (best: with related ticket number as comment)

Do this by logging in via browser on icinga.wikimedia.org. search for the hostname, check all services and use the "acknowledge" option. You'll see the IRC bots outputting this as well and they will stop repeating things over and over in the channels.

  • after: re-add to dsh groups

Revert the above.

  • after: re-pool in pybal

Revert the above.

See also