Toolserver-l

toolserver-l@lists.wikimedia.org

1612 discussions

google analytics (and similar services)
by DaB. 14 Sep '10

14 Sep '10

Hello all, I was noticed by a user today that a few web-tools on the toolserver (at least 3) uses google analytics and violates our rules with that. No user is allowed to "publish connection data, especially IP addresses, of other people " [1]; "publish" means also "give data away to (other) companies or webpages". I will message these users separately, so that they can remove the problem themself soon. If you (because of nescience or ignorance) include a service like google analytics in your tools too, please remove it too very soon. Sincerly and good night, DaB. [1] https://wiki.toolserver.org/view/Rules#Privacy_Policy - point 2 -- Userpage: [[:w:de:User:DaB.]] — PGP: 2B255885

4 3

Conversion of nightshade to Solaris
by River Tarnell 14 Sep '10

14 Sep '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, After some internal discussion and previous consultation with users, we have decided to standardise on Solaris for the login and web servers. We will therefore be converting nightshade from Linux to Solaris at some point in the future. There is no fixed time frame for this at moment, but it won't happen sooner than a month from now, and we won't do anything until we are satisfied that all tools (and users) are ready for the migration. To start with, we want to identify and fix any issues which prevent users from moving their tools to Solaris. This will mainly include: * Software which needs to be installed or updated * Behaviour differences between Linux and Solaris where the Linux behaviour is more correct or preferable. Please take a moment to test your tools on willow, the existing Solaris login server. If you find any issues, please open a ticket in JIRA, and include [solaris] in the subject line so we can easily identify them. Software on Solaris is often newer than the software on the Linux login server. This isn't a problem that can be fixed (since the software will eventually be updated anyway), but during the migration period, we can install more recent versions on Linux as well to allow interoperability. The easiest way for users to migrate is probably to ensure your tools work on both systems; you can then continue to run them on Linux for now (if you want), and there will be no work required once the conversion is done. Some differences between the two operating systems are documented on the wiki at <https://wiki.toolserver.org/view/Solaris>. - river. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (FreeBSD) iEYEARECAAYFAkyOOnsACgkQIXd7fCuc5vLvAwCgj5P6LFyP0aAxod1NrUfYncsT P1IAoIjzptaK7pQbDncna5rlIshVGSDE =r4o1 -----END PGP SIGNATURE-----

4 5

need CPAN module installed on nightshade
by Ted Timmons 13 Sep '10

13 Sep '10

I'm a newbie to the toolserver world. Who do I contact to get perl's Time::ParseDate installed on a toolserver (specifically, nightshade)? -tedder

6 10

Maintenance: user-store; all database clusters tonight
by River Tarnell 13 Sep '10

13 Sep '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 (I have the impression that our maintenance notices are not always very clear, since people are sometimes surprised when we carry out previously-announced maintenance. So, here's a new and hopefully improved notification format.) This is a maintenance notification for tonight (Saturday 11th) UTC. The following services will be affected: Service | Expected impact - --------------------------------+----------------------------------- s1 cluster | User databases unavailable for < 10 minutes s2 cluster | Entire cluster unavailable for < 10 minutes s3 cluster | User databases unavailable for < 10 minutes s4 cluster | User databases unavailable for < 10 minutes s5 cluster | Entire cluster unavailable for < 10 minutes s6 cluster | User databases unavailable for < 10 minutes user databases (sql) | Unavailable for < 10 minutes user-store filesystem | Unavailable for < 20 minutes NFS, LDAP, misc services: | None expected, but at risk during maintenance. SVN, phpMyAdmin, SGE, tsbot, | mail forwarding, DNS, | sql-toolserver database | All other services | No impact Start time: Sunday, 12th September, 12AM UTC End time: Sunday, 12th September, 3AM UTC Details: Tonight we will complete the upgrade to Solaris 10 Update 9 on the remaining servers. This requires under 10 minutes downtime while each system reboots. Since we will be upgrading the primary server in each cluster, which holds user databases, these will be unavailable during the reboot. Access to replicated databases will not be interrupted, since queries will be directed to the alternative server while one is rebooted. The exception is s2/s5 and sql (user databases), which currently have only one server. They will therefore be unavailable during the reboot. - river. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (FreeBSD) iEYEARECAAYFAkyLn7IACgkQIXd7fCuc5vLGIQCeOzuSSxfnVcwKaPz4JU4I15WL 864Ani/mUI0ed+8nfnocP3rVep+P64X6 =GEkv -----END PGP SIGNATURE-----

4 4

Mail changes
by River Tarnell 11 Sep '10

11 Sep '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, We have replaced sendmail on the Solaris login servers with the Postfix MTA. This should not make any difference to users, except that it should fix the problem with cron mails not being delivered. - river. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (FreeBSD) iEYEARECAAYFAkyLxVsACgkQIXd7fCuc5vKBewCeLfsdZ7frvaC/SI4LM03XWCsC qaUAoITvPv6ULwCViT1jfDrYTDYEElMs =KyjE -----END PGP SIGNATURE-----

1 0

cron and email
by Andrew Steinborn 11 Sep '10

11 Sep '10

I am not getting cron emails, and think that my cron tasks are not working. They are run on willow, and I think that this is related to the upgrade done.

4 6

Maintenance on hyacinth (s3/s4/s6); login/web servers
by River Tarnell 11 Sep '10

11 Sep '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Later tonight we will upgrade the OS on hyacinth (s3/s4/s6 server). This will involve ~30 minutes downtime, but should have no impact on users. We will also upgrade the OS on willow at the same time, which should require <10 minutes downtime. If there are no problems with that upgrade, we will also upgrade the web servers (wolfsbane & ortelius); but the cluster software makes this upgrade more intricate, so it may not be completed tonight. That will have no impact on users, since web requests will be served by the other server while one is being upgraded. This maintenance will take place around 12AM UTC on Saturday (11th). - river. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (FreeBSD) iEYEARECAAYFAkyKUDkACgkQIXd7fCuc5vIJ3QCfWbdwQ+I/pzof66ffUZwklkwa SUYAoLyp7quTM0LCLlTw9vqIQLyhwTnI =/o9r -----END PGP SIGNATURE-----

3 6

user-store disk usage
by River Tarnell 10 Sep '10

10 Sep '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, If you are currently using disk space on user-store, please check your usage and delete any unneeded files. There is only 70GB of space left on the volume now. (I will produce a more detailed report of who's using space later...) - river. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (FreeBSD) iEYEARECAAYFAkyGPtIACgkQIXd7fCuc5vIiPQCgv7cTh9bV2gPP9TFhr8K2ZlQG vRYAoL05w9TKADrJ70KEvtNjCGVhctjr =0JWw -----END PGP SIGNATURE-----

8 15

Enable GZip-Compressin on Zeus [was: Javascript Libs]
by Peter Körner 08 Sep '10

08 Sep '10

Am 08.09.2010 20:56, schrieb Tim Alder: > Fine, but we need way to transfer this scripts over the network as gzip. > So your OpenLayer.js is 856 kB big and needs 1.38s for transfer. > I use php for compression, so it looks for the client like normal > JavaScript. My OpenLayers-original2-9.js.php that I use in > OSM-Gadget need 193 kB (the same like that from openlayers.org) and > needs 0.53 sec for transfer. Yes, that's true. I've looked around for Zeus Webserver configuration but I didn't manage it to compress the files while respecting the accept header. I'd like to ask toolserver-l first if anyone knows a smarter way. > For the Openlayers application in Geohack of the german WP I removed all > unnecessary features (with the help Openlayerer.org + Try&Error) so I > come to 82 kB with compression. If you want me to host that smaller version on the osm-account, please send a link to fetch it from. > PHP is the only way I know to start the gzhandler, there are surely > better ways for admins in server-preferences. > It's seem not usefull to compress a file everytime new. We could cache it there and check filemtime every now and then. It could maybe even be hidden using Zeus' rewrite support, but I'm sure there are better options to get the Zeus Webserver to compress files. > The Jquery-skript have also in the latest directory the actual > version-number in the filename. perhaps also not optimal. Fixed that. > What I miss is the OpenStreetMap.js from Openstreetmap.org or is this > not wanted? I just missed it: <http://toolserver.org/~osm/libs/openstreetmap/latest/> > I think a central point for this scripts is the best way, because I > don't need to update it for my own > and we should surely go away from highloaded OpenLayers-Servers, > but we should optimize it a little bit more. Please don't expect to find always the latest version there. I might update them every now and then and of course I will if someone asks for. Peter

1 0

High replag on s2/s5
by River Tarnell 28 Aug '10

28 Aug '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, There is currently a large amount of replication lag on the s2/s5 server. This might be related to a failed disk which will be replaced next week. In the mean time we will continue to monitor it. - river. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (FreeBSD) iEYEARECAAYFAkx3s/QACgkQIXd7fCuc5vJIJACfTKk8rhp3G7R3+Idn0ZT7pGf6 o9gAn0A8gqVS9OGnNy+xm46dpst7z0KO =RKXX -----END PGP SIGNATURE-----

1 1

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

Toolserver-l