Re: [Toolserver-l] Golem issues

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mashiah Davidson: > Currently I am not sure the difference is caused by the fact that > rules for links taking/not taking into account are different because > the difference in results looks too huge. There are no rules for this at the moment, it will

Re: [Toolserver-l] Reimport of s4 on hyacinth and cassia

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This maintenance is now complete, and s4 has moved back to cassia, the original server. - river. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (HP-UX) iEYEARECAAYFAku0/xgACgkQIXd7fCuc5vKXugCfVLmaxN6DeH75myXslZTMd0vO ulcAoI2rTJYW4bJ2pkU

Re: [Toolserver-l] Golem issues

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mashiah Davidson: > > * Build a graph of Wikipedia articles in the main namespace, with > >  wikilinks as vertexes.  Since some pages are not reachable from other > >  pages, this is actually N disconnected graphs. > > * Remove all edges which refer to

Re: [Toolserver-l] Golem issues

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mashiah Davidson: > > Could you (or someone) describe exactly what Golem does, and provide an > > example of its output format? > I think, I can do this. Let say next weekend. Okay. Well, in the mean time, I find this an interesting problem, so I h

Re: [Toolserver-l] Golem issues

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 River Tarnell: > Could you (or someone) describe exactly what Golem does, and provide an > example of its output format? Okay, so based on lvova's presentation, it seems like it does this: * Build a graph of Wikipedia articles in the mai

Re: [Toolserver-l] Golem issues

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alex Rave: > analyse. Improvement may go faster: there is only one programmer now in > project - Mashiah, and if anybody wants to help him and participate in code > improving, he is free to join. Could you (or someone) describe exactly what Golem does

[Toolserver-l] Reimport of s4 on hyacinth and cassia

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, As our master copy of s4 is missing parts of the database (TS-583), I will reimport the database today. While this is in progress, there will be no commonswiki_p database on cassia, the server for s3 and s6. The import should only take an hour o

Re: [Toolserver-l] Server switch for s3/s4/s6, Monday morning UTC

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mashiah Davidson: > I guess it is not possible to reduce the limit in the bot and keep > bot's performance at least on the same level at the same time. You > know administration well, I know the application domain of > connectivity analysis. > > I rea

Re: [Toolserver-l] Page view stats

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Lars Aronsson: > Is page view statistics (as in stats.grok.se) being imported to the > toolserver and available in a database for quick reference? A user has made this available in raw form at /mnt/user-store/stats. We are currently working on making

Re: [Toolserver-l] Server switch for s3/s4/s6, Monday morning UTC

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mashiah Davidson: > The other problem is that once the limit had taken place two years ago > I would never go with creating this tool, but I did; and this means > I've spent a huge part of my life for nothing and a few other people > did the same. I'm

Re: [Toolserver-l] Server switch for s3/s4/s6, Monday morning UTC

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mashiah Davidson: > From what I remember, there were a lot of various reasons why ts > crashed. Yes, I'm quite aware of the various reasons for things crashing or running much slower than they should. One of these reasons is MySQL running out of memo

Re: [Toolserver-l] Server switch for s3/s4/s6, Monday morning UTC

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Aryeh Gregor: > although writes might be slower across the board. Shouldn't be *much* slower, since all writes go to nvram cache anyway. Most of the overhead would be InnoDB/OS processing. - river. -BEGIN PGP SIGNATURE- Version: GnuPG

Re: [Toolserver-l] Server switch for s3/s4/s6, Monday morning UTC

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mashiah Davidson: > > Hm... I knew I forget to mention something.  Yes, > > maximum_max_heap_table_size is now set to 128MB. > This disables my tool to be functional. > > 4GB is *way* too much; we don't have even close to that much free memory > >

Re: [Toolserver-l] Software upgrades

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andrew Dunbar: > It turned out there were stale modules in /usr/share/perl5/ Okay, I assumed you were talking about willow (since the thread was about software upgrades on Solaris), but /usr/share/perl5 only exists on Linux. I suggest filing a TS is

Re: [Toolserver-l] Server switch for s3/s4/s6, Monday morning UTC

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mashiah Davidson: > did you change the upper limit for @@max_heap_table_size on cassia? Hm... I knew I forget to mention something. Yes, maximum_max_heap_table_size is now set to 128MB. > With such a limitation I can say I spen years of coding for n

Re: [Toolserver-l] Server switch for s3/s4/s6, Monday morning UTC

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This maintenance is now completed. - river. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (HP-UX) iEYEARECAAYFAkuwUBsACgkQIXd7fCuc5vJs6ACdHa12GM0+qHkV2ldZaowTSHbR qiwAn0jpbY30nGeJ5V7WK6la9UPuL6qw =cp5L -END PGP SIGNATURE-

[Toolserver-l] Server switch for s3/s4/s6, Monday morning UTC

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, On Monday morning we will switch these clusters from the current server (hyacinth) to cassia due to previously announced problems with hyacinth. This will involve a couple of hours read-only time while the user databases are copied. There should

Re: [Toolserver-l] Conversion of nightshade to Solaris - discussion

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Aryeh Gregor: > All the commands for managing system startup, controlling services, > dealing with the filesystem and disks, debugging, etc., etc. are > totally different between Linux and Solaris. [...] You also have to > install all software twice,

[Toolserver-l] Conversion of nightshade to Solaris - discussion

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, As mentioned previously, we are considering a proposal to convert nightshade (the Linux login server) to Solaris. Before making a decision on this, I'd like some input from users. If you have a moment, please have a look at this wiki page:

Re: [Toolserver-l] Software upgrades

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andrew Dunbar: > It seems there are some very stale old modules still installed which > seem to now be considered defacto standard by the Perl community. POE > and its child classes such as POE::Component::IRC for example. Are you asking for these mod

[Toolserver-l] hyacinth outage

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Over the last week we've had a few outages on hyacinth, the server for s3, s4 and s6, caused by MySQL crashing. We expect cassia (the remaining new database server) to be working this week, at which point we will replace hyacinth until we can det

Re: [Toolserver-l] [Toolserver-announce] zedler (sql) was rebooted

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 We have worked around the problem for now, and zedler is back up. - river. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (HP-UX) iEYEARECAAYFAkuqT3AACgkQIXd7fCuc5vKzOACfanVbumsF8kAhs9o8DRYlZMeB 4j0AoJUbmCqM0iXfXigsYzDX/AQgfGs/ =d5oA --

Re: [Toolserver-l] zedler (sql) was rebooted

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 We have determined that this failure was due to overheating. The server has been shut down again, and it's possible the problem might affect other servers in the same rack. We have asked the colo to investigate. - river. -BEGIN PGP SIGNA

[Toolserver-l] zedler (sql) was rebooted

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, At around 16:48 UTC, zedler (sql) became unresponsive and was rebooted. - river. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (HP-UX) iEYEARECAAYFAkuqQoIACgkQIXd7fCuc5vJbXwCeNQ83Rbo7i0psQ0HRQOTo1GRh 0WIAoLJggS/nJcEdvDUL/dvvBfBUVd

Re: [Toolserver-l] Software upgrades

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andrew Dunbar: > > Compress::Zlib is not an installed module on wolfsbane > Sorry please ignore. I installed Compress::Zlib locally and thought it > didn't work but I didn't see I had two copies of my tool with similar > names and was testing a differ

[Toolserver-l] Software upgrades

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Today we upgraded some software on the Solaris login servers (willow and wolfsbane). Notable upgrades include Perl 5.10.1, Python 2.6.5, git 1.7.0.3, GNU bash 4.1 and Mercurial 1.5. A full list of upgrades is available at

[Toolserver-l] nightshade was rebooted

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, At 04:40 UTC nightshade became unresponsive and was rebooted. No other servers were affected. - river. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (HP-UX) iEYEARECAAYFAkunnpgACgkQIXd7fCuc5vJelwCfYPlIDrR6nEUyuZHAeqfu8FQT z5wAoLp

[Toolserver-l] Python change

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Unless you build your own Python extensions in C, you can ignore this message. Hi, I'm about to install an new version of Python on the Solaris login servers. This is identical to the existing version, except it removes the definitions of _XOPEN_SOU

[Toolserver-l] MySQL upgrade on rosemary (s1-fast)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Wednesday morning UTC I will upgrade MySQL on rosemary. This will involve about 20 minutes downtime while the server restarts. Queries will be served by sql-s1 while s1-fast is down. - river. -BEGIN PGP SIGNATURE- Version: GnuPG

Re: [Toolserver-l] sql-s1 reimport, Monday morning UTC

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This maintenance is now complete. - river. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (HP-UX) iEYEARECAAYFAkuejrcACgkQIXd7fCuc5vKExwCeOcwTV1v5xMXMFRAJz2qlbCUK aGQAoI2caVzBbKqnJye2MQmUGtG4e5z8 =oTXi -END PGP SIGNATURE- _

[Toolserver-l] sql-s1 reimport, Monday morning UTC

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Tomorrow morning (UTC) I will reimport sql-s1's copy of enwiki from sql-s1-fast. sql-s1 will be read-only while user databases are dumped, then offline while data is copied from sql-s1-fast. While sql-s1 is offline, all queries will be redirecte

Re: [Toolserver-l] s3/s4/s6 server switch tonight

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This is now complete. - river. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (HP-UX) iEYEARECAAYFAkucLSkACgkQIXd7fCuc5vLsjgCffJUEfhhClInSlc6e0bdM237T 5xwAoLAjOp6jF0WPkuTtfx8EjRgR32gq =8Ap+ -END PGP SIGNATURE- _

Re: [Toolserver-l] [Toolserver-announce] s3/s4/s6 server switch tonight

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 River Tarnell: > Tonight (UTC) we will switch the database for s3, s4 and s6 from the > current server (yarrow) to a new server (hyacinth). This will require > making the current server read-only, dumping user databases, and > importing

[Toolserver-l] s3/s4/s6 server switch tonight

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Tonight (UTC) we will switch the database for s3, s4 and s6 from the current server (yarrow) to a new server (hyacinth). This will require making the current server read-only, dumping user databases, and importing them to the new server. This ma

Re: [Toolserver-l] commonswiki updates

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Aryeh Gregor: > According to > , > the process still basically involves shutting down the server so that > the file is clean (no outstanding transactions). As far as I know, this still

[Toolserver-l] PHP was upgraded to 5.3.2

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, PHP on willow and wolfsbane (the web server) was upgraded to 5.3.2. This should introduce no incompatible changes for users. A full changelog is available at . - river. -BEGIN PGP SIGNATURE--

[Toolserver-l] daphne (s2, s5) maintenance, Thursday 25th

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I will reboot daphne this Thursday for an OS upgrade. s2/s5 will be offline for around 15 minutes while this is in progress. This issue is being tracked in JIRA as MNT-311. - river. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (

Re: [Toolserver-l] Cannot log in on Toolserver any more

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Chris Ritter (Yellowcard): > Host name: login.toolserver.org The alias "login.toolserver.org" is deprecated and shouldn't be used anymore. You probably want to replace it with "nightshade.toolserver.org", which is the server login refers to. (However

Re: [Toolserver-l] toolserver.org landing page

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ryan Kaldari: > All the menus, headers, and footers are missing from the page. I > loaded it on two different computers (and 3 > different browsers to confirm). Here's a screenshot: > http://www.angelblade.com/toolserverhomepage.jpg This is how it's m

Re: [Toolserver-l] toolserver.org landing page

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ryan Kaldari: > It looks like the toolserver homepage is broken now: http://toolserver.org/ It looks fine to me. Could you describe what problem you see? - river. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (HP-UX) iEYEARECAAYFAkuC

Re: [Toolserver-l] what's the best way to convert SVGs to PNGs on the toolserver?

Peter Körner: > I'm not able to execute strace on willow or via http on wolfsbane: The equivalent of the Linux "strace" utility on Solaris is "truss". Solaris "strace" is something completely unrelated. - river. smime.p7s Description: S/MIME Cryptographic Signature ___

Re: [Toolserver-l] what's the best way to convert SVGs to PNGs on the toolserver?

Ryan Kaldari: > Could this have anything to do with the rsvg security patch? No, because nightshade runs Linux, and the Linux version of rsvg does not contain the patch. - river. smime.p7s Description: S/MIME Cryptographic Signature ___ Tools

Re: [Toolserver-l] what's the best way to convert SVGs to PNGs on the toolserver?

Christian Thiele: > I don't know about security problems, but as I understood, you create the > SVGs for your own, so this shouldn't be a problem. The security problem with rsvg, at least when called from the command line, is that it will honour any external file references in the SVG file. If y

Re: [Toolserver-l] Changes to expired accounts web hosting

Nikola Smolenski: >I suggest to change this to simply: "licensed under the GNU GPL v3 or any >later version." I don't think this is a good idea. The GPL is one of the most restrictive open source licenses and using it automatically could hinder reuse later. A better choice might be something l

Re: [Toolserver-l] Changes to expired accounts web hosting

James Forrester: > Actually, "we" have had a very long-term rule that we don't use > non-OSS software as a part of the Wikimedia "stack". Actually, if such a rule exists, it was and still is frequently broken. The response I got when I asked about this was not "we don't use closed source softwa

Re: [Toolserver-l] Changes to expired accounts web hosting

Petr Kadlec: > Note that it is also possible some tools _cannot_ be freely licensed, > because they contain/use third-party code/libraries not under a free > license. This is only the case if they actually derive the third-party code. Just linking to it is fine (possibly not for GPL, but for mor

Re: [Toolserver-l] Changes to expired accounts web hosting

Martin Peeks: > The default copyright stance, unless a licence specifies otherwise, is > "All Rights Reserved". I don't think we have the right to enforce a > licence that is all about freedom unless a user opts-in. We can require that all users use a free license for their tools, make this clear

[Toolserver-l] Shutdown of stable

Hi, The stable server will be shut down permanently in two weeks, i.e. on the 18th. This follows a 4 month migration period for moving tools. Any tools that have not yet migration will be inaccessible after that date. (However, any remaining files will be backed up.) hyacinth (the current s

Re: [Toolserver-l] Changes to expired accounts web hosting

Platonides: > It doesn't seem to have changed. gmaxwell account expired time ago. > However, its files can still be accessed > http://toolserver.org/~gmaxwell/election_analysis/2008/GRAPH_3_totals.png # acctexp gmaxwell The account "gmaxwell" will expire on Tuesday, 01 June 2010. - river. s

Re: [Toolserver-l] Changes to expired accounts web hosting

Mike.lifeguard: > In the past, when people disappeared, their tools would (maybe) keep > working. Now that we *know* they will stop working once the account is > expired, do we know how requests for sourcecode for a tool will be > handled, in case someone wants to revive it? Currently we don't hav

Re: [Toolserver-l] Changes to expired accounts web hosting

Eusebius: > The "gallery" tool integrated into WM Commons is now unavailable, I > assume it is a direct consequence of this change. Yes, but unintentional. This should be fixed now. - river. smime.p7s Description: S/MIME Cryptographic Signature

[Toolserver-l] Changes to expired accounts web hosting

Hi, In the past, when an account was expired, it was still possible to access its public_html. This has now changed. Any HTTP requests to an expired account will return an error page indicating that the account has expired. The files in public_html are not deleted, and will become accessible

[Toolserver-l] DNS aliases for fast database servers

Hi, There are now DNS aliases for the fast database servers, under fastdb.toolserver.org. For example, if you currently connect to enwiki-p.db.toolserver.org, connect to enwiki-p.fastdb.toolserver.org instead to use the fast server. (For now only enwiki has a fast server, but we will be adding t

[Toolserver-l] Unplanned downtime, 2009-02-01

Hi, There was some unplanned downtime on the HA cluster today causing an outage of the platform. The downtime was caused by an upgrade of the software on one node. We will investigate the cause of the failure before upgrading the other node. Due to the nature of the NFS failure, you may need to

Re: [Toolserver-l] Changes to replicated wiki databases

This change is now live for s1, so connections to 'sql-s1-fast' will connect to the fast database server. Queries on this server will be automatically killed after 60 seconds. - river. smime.p7s Description: S/MIME Cryptographic Signature ___

Re: [Toolserver-l] Introducing the jobserver

River Tarnell: > In the future the jobserver will have additional functionality, including > scheduled jobs (to replace cron with a single integrated solution). If you > have any other feature requests, you should list them on the wiki. Scheduled jobs are now implemented. Someo

[Toolserver-l] Introducing the jobserver

Hi, Our trained monkeys have been working non-stop for the last week on a new piece of software for the Toolserver: the jobserver. This software is now ready for testing. The jobserver is an alternative to cron/phoenix for starting long-running jobs. Instead of having to invoke phoenix regul

[Toolserver-l] Webserver maintenance tonight

Hi, Tonight I will upgrade the web server software on wolfsbane. Total downtime for the upgrade should be around 5 minutes. There will be no user-visible changes. This issue is being tracked in JIRA as MNT-177. - river. smime.p7s Description: S/MIME Cryptographic Signature ___

[Toolserver-l] sep11 and closed_zh_tw wikis will be dropped

Hi, The above two wikis will be dropped from the cluster, as they are obsolete. They have already been removed from the toolserver.wiki table. - river. smime.p7s Description: S/MIME Cryptographic Signature ___ Toolserver-l mailing list (Toolser

[Toolserver-l] s1 server switch

Hi, Later tonight I will be switching s1 to a new server, as described at . - river. smime.p7s Description: S/MIME Cryptographic Signature ___ Toolserver-l maili

[Toolserver-l] MySQL maintenance tonight

Hi, We will be performing maintenance on MySQL tonight to fix the 'host is blocked because of too many connection errors' problem. This is being done earlier than expected because it's required for the new load-balanced MySQL servers. The total downtime should be under 20 minutes per server.

[Toolserver-l] Changes to replicated wiki databases

Hi, Over the next couple of weeks we will be making some changes to the way that wiki databases work on the Toolserver. Currently, each cluster (s1..s6) has only a single Toolserver slave. (For example, s1 is on yarrow and no other server). We will be adding an additional server to each cluste

[Toolserver-l] cache.stable.toolserver.org EOL

Hi, I am about to decommission cache.stable.toolserver.org. Requests to the host will still work as before, but will go straight to the web server without being cached. This may return in the future as a cache for toolserver.org instead. - river. smime.p7s Description: S/MIME Cryptogra

Re: [Toolserver-l] Web applications maintenance

This has been completed successfully. - river. smime.p7s Description: S/MIME Cryptographic Signature ___ Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org) https://lists.wikimedia.org/mailman/listinfo/toolserver-l Posting guidelines for

[Toolserver-l] Web applications maintenance

Hi, amaranth (which serves web applications including JIRA and the wiki) is being shut down now in order to move it to a different rack. This will take a few minutes. Sorry about the short notice. - river. smime.p7s Description: S/MIME Cryptographic Signature _

[Toolserver-l] yarrow (s1/3/4/6) restart

Hi, yarrow, the database server for s1, s3, s4 and s6, has started to use too much memory and is swapping, which results in unacceptable performance. As a temporary workaround we will reduce the InnoDB buffer pool size and restart the server. The server will be offline for about 20 minutes wh

[Toolserver-l] s1 reimport

Hi, I am currently importing s1 into one of the new database servers to replace the damaged copy on rosemary. After the import is down, I will switch the s1 server, then put it in read-only mode to copy user databases. Downtime will be about half an hour to switch servers, and possibly a coup

[Toolserver-l] Maintenance later today on amaranth

Hi, amaranth will be rebooted later today to upgrade its operating system. This will result in about 5 minutes downtime of the web applications (JIRA, wiki, etc). - river. smime.p7s Description: S/MIME Cryptographic Signature ___ Toolserver-l

Re: [Toolserver-l] Issue with Toolserver email forwarding (usern...@toolserver.org)

Hi, I'm about to switch mail.toolserver.org to a new host, which will resolve the mail forwarding issue. This may take up to an hour to propagate in DNS. - river. smime.p7s Description: S/MIME Cryptographic Signature ___ Toolserver-l mailing lis

Re: [Toolserver-l] Setting default character set on Zeus?

Marcin Cieslak: > Those files are served with > Content-Type: text/plain > and I'd like to see them: > Content-Type: text/plain; charset=utf-8 AddType text/plain;charset=UTF-8 txt or: DefaultType text/plain;charset=UTF-8 - river. smime.p7s Description: S/MIME Cryptographic Sign

[Toolserver-l] Maintenance, Monday 4th

Hi, In addition to the previously announced maintenance, we will perform the following additional maintenance on Monday, 4th January depending on whether there is enough time: * willow will be upgraded to Solaris 10 Update 8. (Downtime: 5 minutes) * We will add some patches to the NFS/LDAP clu

Re: [Toolserver-l] [Toolserver-announce] MySQL upgrades on Sunday

Correction: this maintenance will be on Monday, 4th January at 1-2AM UTC. - river. smime.p7s Description: S/MIME Cryptographic Signature ___ Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org) https://lists.wikimedia.org/mailman/

[Toolserver-l] MySQL upgrades on Sunday

Hi, On Sunday, 3rd January around 1-2AM UTC, I will be upgrading MySQL on the database servers. At the same time, the operating system will be upgraded. Total downtime will be around 30 minutes to upgrade MySQL, and 5 minutes to upgrade the OS. There should be no user-visible impact from the

[Toolserver-l] wolfsbane

Hi, wolfsbane (web server) was rebooted to complete the previously announced maintenance, and at the same time it was upgrade to Solaris 10 Update 8. This should have no impact on users. These issues are being tracked in JIRA as MNT-90 (/tmp issue) and MNT-108 (upgrade). - river. smime

[Toolserver-l] libjpeg was upgraded

Hi, You can ignore this message unless you have C or C++ programs or libraries linked directly against 'libjpeg', the IJG JPEG library. (The vast majority of users will not have any such programs.) libjpeg on the Solaris systems (willow and wolfsbane) has been upgraded from version 6b to version

Re: [Toolserver-l] PHP upgrade

Peter Körner: >> PHP was upgrade to 5.3.1. > Cool, thank you! PHP 5.3 has many cool features, like Closures and > Namespaces. I'm happy to be able to use them on the Toolservers. The upgrade was only from 5.3.0, which we've been using for months. I don't think 5.3.1 has any new features.

[Toolserver-l] PHP upgrade

Hi, PHP was upgrade to 5.3.1. At the same time, the PHP PDO MySQL module was enabled. This should have no impact on users (unless you want to use PDO). - river. smime.p7s Description: S/MIME Cryptographic Signature ___ Toolserver-l mailing list

[Toolserver-l] MySQL crash on yarrow

Hi, MySQL on yarrow (s3, s4, s6) crashed and restarted. This is a known problem and has happened before; however, we've now made a configuration change that might prevent it from happening in the future. This issue is being tracked in JIRA as MNT-58. - river. smime.p7s Description: S/

[Toolserver-l] Web server (wolfsbane) will be rebooted)

Hi, The web server wolfsbane will be rebooted later tonight to change a configuration setting. Web tools will be offline for about 10 minutes while this is in progress. This issue is being tracked in JIRA as MNT-90. - river. smime.p7s Description: S/MIME Cryptographic Signature _

Re: [Toolserver-l] Reminder: move your projects off stable

Maarten Dammers: >> delinker has moved. > Come on River, we moved ages ago, don't include us here. I guess your definition of "ages" is different from mine, because according to the log file, delinker was running yesterday. [2009-12-28 12:28:46] Deleted image: File:40024 at Llandudno Junctio

Re: [Toolserver-l] Linux/Solaris

On 28/12/2009 08:13 PM, Mike.lifeguard wrote: > Which admins? I know River is very experienced with Solaris - but are > the other sysadmins more experienced with Solaris than linux as well? We had a long discussion about this in the admins IRC channel... we all agree that having two separate OSs i

Re: [Toolserver-l] Linux/Solaris

On 28/12/2009 07:28 PM, Carl (CBM) wrote: > 1) An easy-to-use compilation environment for C and C++. I am not > really able to compile Perl modules on willow, despite spending quite > a while hacking at it. I know some people had issues with this but I never really saw a proper description of the

Re: [Toolserver-l] Linux/Solaris

On 28/12/2009 07:00 PM, Carl Fürstenberg wrote: > I have a tone of local compiled (xs) perl modules which will most > certainly break, and I really don't know if I can magically convert my > $HOME/.cpan to solaris without much great pain I see. > have you installed all perl modules which where in

Re: [Toolserver-l] Linux/Solaris

On 28/12/2009 06:40 PM, John Doe wrote: Is there any particular place that we need to report these differences that may need adjusted or things need added? If you plan on actually using it, then file a request in JIRA. Otherwise the mailing list is fine. If we ever actually decide to stop us

Re: [Toolserver-l] Linux/Solaris

On 28/12/2009 06:02 PM, Pietrodn wrote: Just a question: why is Solaris more suitable for us than Linux? It's not really a question of "more suitable". The Toolserver has always been Solaris, mostly because I was the first TS admin, and Solaris is what I know. The Linux server(s) were adde

[Toolserver-l] Linux/Solaris

Hi, So, currently we have two login servers, one which runs Linux and one which runs Solaris. This greatly complicates system administration (as everything has to be done twice), and confuses users, since things are different between the two login servers, and between the Linux login server

[Toolserver-l] Toolserver wiki (wiki.toolserver.org) will be upgraded

Hi, Later tonight (UTC) I will upgrade the Toolserver wiki to the current MediaWiki trunk version. There will be a brief outage of the wiki while this is done. This issue is being tracked in JIRA as MNT-78. - river. smime.p7s Description: S/MIME Cryptographic Signature __

[Toolserver-l] Reminder: move your projects off stable

Hi, As announced two months ago, we are planning to EOL the stable server in favour of multi-maintainer projects on the normal Toolserver. The following projects are still running on the stable server: * geohack * wma * delinker We intend to repurpose the hardware currently used for the stabl

[Toolserver-l] Issue with Toolserver email forwarding (usern...@toolserver.org)

Hi, There is currently an open issue that is preventing updates to the Toolserver email configuration from propagating to the mail server. This means that email forwarding for newly created accounts is not working, and changes to your Toolserver email address (using setmail) will not take ef

[Toolserver-l] Unscheduled downtime, Wed 16th

hi, we had an outage of ~5 hours affecting all login servers from 04:15 UTC to around 09:30 UTC. the issue was fixed fairly quickly once noticed, but it took some time for an admin to be contacted. the outage was caused by a misconfiguration on the cluster which prevented switching the NFS servi

Re: [Toolserver-l] [Wikitech-l] Wikimedia IRC Group Contacts looking for a developer

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Q: > Stable was EOL'd a while back[1] and it was notified that all projects > on stable should convert to multi-maintainer projects on the 'normal' TS > soonish. this is not yet completed and nothing on stable has been deleted. - river. ---

[Toolserver-l] OpenStreetMap Mapnik data now available

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 hi, previously we had a copy of the OSM mapnik database on cassini. this database has now moved to ptolemy, and is accessible to all users from the normal login/web servers. to use it, connect to the "osm_mapnik" database on the host "sql-mapnik".

Re: [Toolserver-l] [Toolserver-announce] zedler (SQL) will be rebooted

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 this maintenance was completed successfully. - river. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (HP-UX) iEYEARECAAYFAksVgjcACgkQIXd7fCuc5vLCvwCfQu8okClyT3lvqfWwx1UZcFtH hCsAnRPpVrta/+mMXA5cqXVritOUl3sF =kVUc -END PGP SIGNATURE--

[Toolserver-l] zedler (SQL) will be rebooted

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 hi, zedler, which serves 'sql' (user databases), will be rebooted later today to see if it fixes an issue with its disk array. this will cause an outage of around 10 minutes for user databases. this issue is being tracked in JIRA as MNT-14.

Re: [Toolserver-l] disk quotas

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 "Stefan Kühn": > In the last time I play more and more with MySQL. Is there a limit for > data in this database for one user? If not, then I will try to change > the script, so that this script put this data into the database. there is no technologica

Re: [Toolserver-l] disk quotas

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 James Hare: > Pardon the noob question, but how can I tell how much disk space my account > is using? $ quota -v - river. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (HP-UX) iEYEARECAAYFAksB8WEACgkQIXd7fCuc5vIl7QCeMxeVdJFpscomZjTWMr+

Re: [Toolserver-l] disk quotas

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 River Tarnell: > to avoid this happening in the future, we will be bringing > back disk quotas ... on the /home filesystem. there will be no quotas (for now) on the user-store filesystem - river. -BEGIN PGP SIGNATURE- Version:

Re: [Toolserver-l] contests tool is ready for use

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ryan Kaldari: > The only thing I'm still waiting on is the creation of the > multi-maintainer account: > https://jira.toolserver.org/browse/TS-388 this issue was resolved 12 hours ago. - river. -BEGIN PGP SIGNATURE- Version: GnuPG v1.

[Toolserver-l] disk quotas

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 hi, one of the problems we often see on the Toolserver is users accidentally using too much disk space (for example, broken tools generating 100GB logfiles). to avoid this happening in the future, we will be bringing back disk quotas over the next we

Re: [Toolserver-l] NFS maintenance tonight

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 this maintenance was completed successfully. - river. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (HP-UX) iEYEARECAAYFAksArLYACgkQIXd7fCuc5vKkPwCghfHpdkyNTINOo5ZVt4jJ6xpy /M0AnjGt5VsgGddeskR8bPEKhUfwscVR =sQWW -END PGP SIGNATURE--

<    1   2   3   4   5   6   7   8   9   >