Toolserver-l

toolserver-l@lists.wikimedia.org

1612 discussions

Strangely slow query
by Carl (CBM) 10 Oct '11

10 Oct '11

I am getting a lot of emails about the following query taking too long and being killed on thyme: SELECT ns_id, ns_name FROM toolserver.namespacename where (ns_type = 'canonical' or ns_type = 'primary') and dbname = 'enwiki_p' Some of these emails claim that query ran over 3000 seconds. This particular query should be quite fast. Is something up with the db server? - Carl

2 1

Toolserver's disk space issue ?
by Toto Azéro 09 Oct '11

09 Oct '11

Hi all ! I've noticed that I cannot edit my crontab anymore… Indeed, if I type "cronie -e", I get the following error : « /tmp/crontab.XXXX6DaGnD: No space left on device. » Then I reminded the mail that Daniel Kinzler sent to the mailing list a few days ago ("Toolserver status, and what WMDE is doing about it"). He explained that, unfortunately, the TS was « running out of disk space now ». Moreover, I keep getting mail errors, with the same error report : « Unable to run job: job rejected: no script in your request. Exiting. » Are both these problems linked to a lack of disk space ? If so, maybe every user might try to clear his home, in the aim to free some memory ? Or maybe is there something that I misunderstood ? Regards, — Toto Azéro

2 2

Attention developers (Gadgets, user/site scripts, Toolserver tools, MediaWiki extensions, ..)
by Krinkle 05 Oct '11

05 Oct '11

Hi all, If you write, maintain or are otherwise active in development, and directly or indirectly make use of MediaWiki, then you should subscribe to: mediawiki-api-announce(a)lists.wikimedia.org That is a mailing list that only brings important announcements for developers that use MediaWiki as an API. Note that this list is not limited to API as "api.php" but about MediaWiki as a application programming interface (API) in general. Subjects that have announcements on that list: * Important changes in database schema (columns or tables added, removed or changed in such a way that you should change your queries. Think for example of the addition of rev_deleted, queries should most likely query for rev_deleted=0 now). * Changes in the JavaScript API (methods being deprecated or removed in the mediawiki.js library etc. as well as upgrades of third-party libraries that ship with MediaWiki, such as jQuery). * Major changes to the HTML layout (such as the change for the sidebar id to #mw-panel) * Hooks in MediaWiki PHP. Mostly for extension developers. Changes or deprecation of hooks. * And last but not least, the api.php itself. All major changes. === Although time will learn how the list is used, to readers and writers of this list: "All subjects should clearly indicate what needs changing and when!" For example "Vector skin sidebar html ID changes to '#mw-panel' in 1.17". Also, whenever Wikimedia has scheduled a deployment of revision(s) or entire branches that expose any change that was previously announced, a new mail should be sent here to remind/summarize upcoming changes (since gadgets should/can't be changed until the new version is deployed but new versions can be prepared or tested in advance) Hope to see you soon on mediawiki-api-announce(a)lists.wikimedia.org :) Please reply-to to wikitech to keep discussions about this central. -- Krinkle

3 2

Toolserver status, and what WMDE is doing about it
by Daniel Kinzler 05 Oct '11

05 Oct '11

(sorry for the repost, the original mail got the wrong subject line by mistake) Dear Toolserver Users As you have probably notices, things havn't been going to well with the toolserver lately. The main reason is that River is no longer available as much as before, and we do not have a replacement. DaB is doing what he can, but far too often, there's simply no one to fix things when they break. Also, our plans to buy more storage went on hold because of this situation, and so we are running out of disk space now. Which causes more things to break. So, what is Wikimedia Germany doing about this? Here is what: * Sebastian Sooth has taken charge of IT management at WMDE. He's way better at this stuff than me, so that will help. * We are hiring an interim admin. I hope we'll have the contract finalized by next week. * We will buy and install more storage. The new admin will plan that in coordination with DaB, Sebastian and me. Expect this to take at least 8 weeks before we have everything installed. * Meanwhile, we'll try to assess and fix any other issues that have piled up over the last couple of months. * In the process, we'll create and improve documentation of the cluster, so it becomes easier for people with access but little knowledge (like myself) to fix things when they break. * We will run a proper job offer for a payed toolserver admin. The idea is to eventually have two payed (part time) system admins. The job offer will be posted to toolserver-l. I know things havn't been for the best lately, but I believe we are getting a grip on the problem now. If you have any questions, please contact me. Regards, Daniel Kinzler Wikimedia Deutschland e.V. _______________________________________________ Toolserver-l mailing list (Toolserver-l(a)lists.wikimedia.org) https://lists.wikimedia.org/mailman/listinfo/toolserver-l Posting guidelines for this list: https://wiki.toolserver.org/view/Mailing_list_etiquette

2 1

Re: [Toolserver-l] [Internal-l] toolserver
by Daniel Kinzler 05 Oct '11

05 Oct '11

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear Toolserver Users As you have probably notices, things havn't been going to well with the toolserver lately. The main reason is that River is no longer available as much as before, and we do not have a replacement. DaB is doing what he can, but far too often, there's simply no one to fix things when they break. Also, our plans to buy more storage went on hold because of this situation, and so we are running out of disk space now. Which causes more things to break. So, what is Wikimedia Germany doing about this? Here is what: * Sebastian Sooth has taken charge of IT management at WMDE. He's way better at this stuff than me, so that will help. * We are hiring an interim admin. I hope we'll have the contract finalized by next week. * We will buy and install more storage. The new admin will plan that in coordination with DaB, Sebastian and me. Expect this to take at least 8 weeks before we have everything installed. * Meanwhile, we'll try to assess and fix any other issues that have piled up over the last couple of months. * In the process, we'll create and improve documentation of the cluster, so it becomes easier for people with access but little knowledge (like myself) to fix things when they break. * We will run a proper job offer for a payed toolserver admin. The idea is to eventually have two payed (part time) system admins. The job offer will be posted to toolserver-l. I know things havn't been for the best lately, but I believe we are getting a grip on the problem now. If you have any questions, please contact me. Regards, Daniel Kinzler Wikimedia Deutschland e.V. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk6MP5kACgkQG0czJgig8U814wCdGX/SfM9CDivdFCN0Wt645C8e knQAn3lJLDO5RGBc2klYh7hjYcMsJwWc =9RPJ -----END PGP SIGNATURE-----

1 0

Sql-s2-replag and itwiki
by DaB. 05 Oct '11

05 Oct '11

Hello all, itwiki does some kind of strike at the moment and no edits happen. So if you use it for calculating the replag of the cluster S2 you will fail. I suggest a switch to nlwiki. Sincerly, DaB. -- Userpage: [[:w:de:User:DaB.]] — PGP: 2B255885

1 0

sql-s1-userr no longer have commons
by DaB. 03 Oct '11

03 Oct '11

Hello all, today the sql-partion on thyme (the server which hosts sql-s1-user) finaly became full so replication was not longer possible. The German Verein works on a solution to expand the disc-capazity but that will take some time. As interim-solution, I dropped the copy of commons on thyme. So that reason it will not longer be possible to join enwiki with commons AND a user-database. If you need to join enwiki with commons you can still use sql-s1-rr and if you need to join enwiki with a user-database you can still use sql-s1-user. I will try to setup federation to fix this, but I'm not sure if it will works. Sincerly, DaB. -- Userpage: [[:w:de:User:DaB.]] — PGP: 2B255885

1 0

Outage
by John 02 Oct '11

02 Oct '11

I cannot log into nightshade or wolfsbane, toolserver.org is down and so is my web content, however JIRA is still up. John

5 6

Downtime between 19:07 and 19:38
by DaB. 27 Sep '11

27 Sep '11

Hello all, between 19:07 and 19:38 (UTC) the toolserver was non-accessable from outside and sql-using inside was also not possible (I guess several other things failed too). The reason was that one of our high-availability-servers half- crashed and the other didn't notice it and some services were splitted between them. A rebooting of the half-crashed fixed this. FYI. Sincerly, DaB. -- Userpage: [[:w:de:User:DaB.]] — PGP: 2B255885

1 0

SQL-s5 maybe broken
by DaB. 27 Sep '11

27 Sep '11

Hello all, the master-switch of s5 [1] last night didn't go as smooth as normal. I had to restart the replication several times; this COULD have resulted in a corruption of 1 or more databases on the cluster. If you notice something strange, please open a JIRA-bug and I will look at it. In worst case I have to reimport s5 at some time in the future. Sincerly, DaB. [1] https://jira.toolserver.org/browse/MNT-1099 -- Userpage: [[:w:de:User:DaB.]] — PGP: 2B255885

1 0

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