Wikipedia:Toolserver/status: Difference between revisions
Status: zedler up; yarrow up; Replag: s1 0h 0m 0s; s2 0h 0m 13s; s3 0h 0m 4s; |
Status: zedler up; yarrow up; Replag: s1 0h 0m 2s; s2 0h 0m 48s; s3 0h 0m 3s; |
||
| Line 6: | Line 6: | ||
|- |
|- |
||
! Last update |
! Last update |
||
| <!--update--> |
| <!--update-->04:00, 21 August 2008 (UTC)<!--update--> |
||
|- |
|- |
||
!MySQL vandale |
!MySQL vandale |
||
| Line 18: | Line 18: | ||
|- |
|- |
||
!Replag s1 |
!Replag s1 |
||
| <!--s1-->0h 0m |
| <!--s1-->0h 0m 2s<!--s1--> |
||
|- |
|- |
||
!Replag s2 |
!Replag s2 |
||
| <!--s2-->0h 0m |
| <!--s2-->0h 0m 48s<!--s2--> |
||
|- |
|- |
||
!Replag s3 |
!Replag s3 |
||
| <!--s3-->0h 0m |
| <!--s3-->0h 0m 3s<!--s3--> |
||
|- |
|- |
||
| colspan="2" style="text-align:center;" |''[[tools:~leon/stats/replag/all/replag-daily.png|Replication-Lag daily graph]]'' |
| colspan="2" style="text-align:center;" |''[[tools:~leon/stats/replag/all/replag-daily.png|Replication-Lag daily graph]]'' |
||
Revision as of 04:00, 21 August 2008
| Last update | 04:00, 21 August 2008 (UTC) |
|---|---|
| MySQL vandale | up |
| MySQL zedler | up |
| MySQL yarrow | up |
| Replag s1 | 0h 0m 2s |
| Replag s2 | 0h 0m 48s |
| Replag s3 | 0h 0m 3s |
| Replication-Lag daily graph | |
This box shows the status of the Toolserver. This is a server from Wikimedia Deutschland that provides users a place to host their tools, such as web services and bots.
The information is updated hourly by BryanBot. If there is no update after an hour, it is likely that the entire Toolserver is down. It is possible that while the user bot (BryanBot) is up, the database (MySQL) is down. When MySQL is down, bots and web services that require MySQL will not function.
The Toolserver database contains a replica of all Wikimedia wiki databases. Replication lag indicates how far the replication is behind real time. Services that read information from those databases will not return actual values, but values as they were at a time interval equal to the lag earlier. Replication lag particularly concerns Duesentrieb's check usage, which will return out-dated information if replication lag is too high.
Different wikis are on different database clusters (s1, s2 and s3) and can thus have a different replication lag. See this post for information on s1, s2 and s3. The English Wikipedia is on s1.