-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
As announced in previous mails, the new web server (ortelius) is now
serving requests. For now there are two separate sets of log files, one
on each server. We hope to combine these into one log file soon, but
until then, you can force a request to go to a particular server for
testing with a URL like <http://wolfsbane.toolserver.org/~jsmith/>, so
you know where to find the logfiles.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (HP-UX)
iEYEARECAAYFAkvs+MoACgkQIXd7fCuc5vJyBgCgjCR8CK9PXfEczGZZY4oMgyp3
81cAoMKYutcbeaz12PMu4l/lf7PAsQbw
=N7+/
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
We have now re-added hyacinth as the s3/s4/s6 fast server. We will
monitor its performance over the next few days.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (HP-UX)
iEYEARECAAYFAkvpa8oACgkQIXd7fCuc5vIlVACgrIQTZMMgBCDSJxRWK7QUFk39
2GYAnRgHwa5rcpXlCJEik28r3h6DmR0n
=gZFC
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
On Wednesday night (or possibly Thursday morning) UTC, we will do some
maintenance on wolfsbane, the web server. This will at least involve a
reboot (5-10 minutes downtime). There may be some additional
interruption for network configuration changes, but I'll try to keep
that to a minimum.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (HP-UX)
iEYEARECAAYFAkvhWmQACgkQIXd7fCuc5vJgGACeIF8OfkiNo9zHesY2BJzkYlDJ
cVMAn2v50Dpm1LYwJKCeDeumskO4e2LV
=KJvy
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I am about to move user databases (sql) from zedler to adenia. This
will involve a few hours read-ony time while the data is copied.
Sorry for the short notice for this maintenance.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (HP-UX)
iEYEARECAAYFAkviE7EACgkQIXd7fCuc5vL0XACfQL14ccrxavqft8WFBPk+d3GV
08IAn12eeuL8bTRtkflRxX+K5HZSDQWC
=tFCr
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
Anyone who has OSM tools running on cassini should now start moving them
to the normal Toolserver and accessing the database and renderd on
sql-mapnik (ptolemy). We will be repurposing cassini once all tools
have moved.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (HP-UX)
iEYEARECAAYFAkvZ2GgACgkQIXd7fCuc5vKj/wCeMBBU2v+xnFS754tBE2UANdZU
UQsAnRQQLe5hWg41RK6Y0Iqrg/Fy0ikd
=koHo
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
In the near future we plan to add an additional web server to the
Toolserver. This will provide redundancy if either server fails, as
well as increasing capacity. Each server will be identically configured
(with the same OS, software, etc.), and HTTP requests will be
distributed evenly between the systems.
Some tools may require changes to function correctly in this
environment:
* Any tool which stores data on a local disk (e.g. /tmp or /var/tmp)
and expects to retrieve the data in a different request may find the
data is not present if the subsequent request runs on a different web
server. To fix this, such data should be stored in a location
accessible from all systems (e.g. $HOME).
* Web frameworks supporting HTTP sessions often use local storage for
session data. This will not work over multiple servers, for the same
reason as local files. To fix this, configure your framework to store
session data in $HOME or a MySQL database instead of local files.
(No changes are needed for PHP, which is already configured this way.)
* Tools which expect server-specific details (e.g. hostname or IP
address) to remain the same will not work. This is always a bad idea,
but will now not work at all.
* Tools which require some kind of separate daemon will need to start
the daemon on both systems, or communicate with the daemon over the
network.
* Initially, there will be independent access and error logs for
each system. To ease debugging of scripts, it will be possible to use
a URL like <http://wolfsbane.toolserver.org/~jsmith/mytool/> to force
the request to a particular system. However, such URLs should not be
used for any other purpose, since server names can change at any time,
which would break the URLs.
In the future, we hope to have unified logs for all web servers.
We plan to have the additional web server operational within the next
week or two.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (HP-UX)
iEYEARECAAYFAkvhHYgACgkQIXd7fCuc5vJNWwCff61+e57wgUfu1qr2DTBvLSF7
gtsAnRi2o0Fz7hlLCwNchPDhWqLWBkhS
=3a/4
-----END PGP SIGNATURE-----
> From a Toolserver account? just query the db or from a non toolserver
> use, probably just the API from the wmf servers but if you cause too
> much load you would get blocked.
The article text can not be fetched from the database on the toolserver.
Using the API would work just as well as Special:export, as long as as many
pages are fetched at a time as possible. One request per page would suck.
-- daniel
Looks like the API will do the trick - I can get 50 articles at a time. Someone asked what I'm up to - I'm setting up a cache of pages with hatnotes that link to disambig pages, to begin the process of identifying intentional vs. non-intentional disambig links. I plan to refresh the cache daily, which will definitely involve re-checking hundreds of articles, if not thousands.
- Jason
What is the best way to get the current text of an article from the Toolserver these days - the API, WikiProxy, or something else? I need to examine thousands of pages on a daily basis and want to streamline the process as much as possible.
Thanks,
Jason
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
We are about to enable fast servers for s3/s4/s6 (on hyacinth) and s2/s5
(on yarrow). These work the same as the fast servers for s1; just
connect to sql-sX-fast, or XXwiki-p.fastdb.toolserver.org to use them.
This will also provide redundant access to the wiki databases (but not
user databases) when the primary database is offline.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (HP-UX)
iEYEARECAAYFAkvbK28ACgkQIXd7fCuc5vJK4gCfVOw2gDq1wJd1XRJtsKRKQEO4
DzUAoIn03cy78eRYt1X80sRQDp15+s9H
=CX4L
-----END PGP SIGNATURE-----