[Toolserver-l] Burnbridges question

dpl@nightshade:~$ cat public_html/.htaccess Redirect permanent /~dpl http://tools.wmflabs.org/dplbot Should I just ignore the message and complete burnbridges anyway? -- Russell Blau russb...@imapmail.org ___ Toolserver-l mailing list (Tool

[Toolserver-l] MySQL problems?

MySQL servers seem to be unresponsive. On willow, both "mysql -h sql-s1-user" and "mysql -h sql-s1-rr" hang for extremely long times. ___ Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org) https://lists.wikimedia.org/mailman/listinfo/toolserv

Re: [Toolserver-l] SQL S1

On Jun 3, 2013, at 6:21 PM, "DaB." wrote: > Hello, > At Monday 03 June 2013 16:20:52 DaB. wrote: >> I am getting a ERROR 2003 (HY000): when trying to connect. > > fixed. Tested also the other connections and found no problems there. russell@willow:~$ mysql -h sql-s1-user

[Toolserver-l] Running Pywikipedia (rewrite) bots on Tools Labs

their bot(s) running on Labs, feel free to add instructions for that process, too. [1] https://wikitech.wikimedia.org/wiki/User:Russell_Blau/Using_pywikibot_on_Labs -- Russell Blau russb...@imapmail.org ___ Toolserver-l mailing list (Toolser

Re: [Toolserver-l] Status of the toolserver

to the ML. Is the current outage of replication on sql-s1-user (now approaching 48 hours) related to this ha-node problem? At least some other dbs seem to still have replication working. -- Russell Blau russb...@imapmail.org ___ Toolserver

Re: [Toolserver-l] enwiki_p

On Sat, Mar 23, 2013, at 01:31 PM, DaB. wrote: > > While we speak of enwiki: The import of commons on the new server is > done. By > Sunday or Monday evening we should have a complete and up2date sql-s1-rr > again. Is there any update on this? AFAICT, sql-s1-rr is still pointing to rosemary (s

Re: [Toolserver-l] S1

On Sat, Nov 17, 2012, at 05:32 PM, DaB. wrote: > Hello, > At Saturday 17 November 2012 23:23:34 DaB. wrote: > > do we have an updated ETA on a non-corrupt s1? > > we were not able to reach Mark or someone from the datacenter yet for a > reboot of thyme. When thyme is rebooted we have to announce t

Re: [Toolserver-l] s1 replag update, suggestion, and question

rl, that is a good idea and I've stopped all the scheduled dpl project jobs that usually run on thyme, for 24 hours, to see if that helps. If anyone else could temporarily shut down their tools to help reduce the load on the server, maybe we can all help improve the recovery rate. --

Re: [Toolserver-l] s1 replag update, suggestion, and question

the replag is continuing to increase. This is very worrisome, and possibly there is something else going on there that the SHA-1 updates have been masking. All the TS admins seem to be on summer holiday; is there anyone around who has mysql root access and can look for problems on thyme? --

Re: [Toolserver-l] s1 replag update, suggestion, and question

ng the performance of your application if you don't. The address "enwiki-p.db.toolserver.org" points to the sql-s1-user copy, and is deprecated; you ought to be using either "enwiki-p.rrdb.toolserver.org" or "enwiki-p.userdb.toolserver.org" instead. [1]

[Toolserver-l] s1 replag update, suggestion, and question

so far has not been encouraging. Question for those of you who operate and/or use tools that access s1 (enwiki): would you be willing to accept several hours of service outage and the other downsides in exchange for getting rid of the 14-day replag? -- Russell Blau r

Re: [Toolserver-l] s1 replag, some observations

On Thu, Jul 12, 2012, at 01:29 AM, Platonides wrote: > On 11/07/12 16:14, Russell Blau wrote: > > I'm glad to know that the appearance was deceiving. Having data from > > rosemary now, > > I come up with an estimated completion date there of July 30, assuming > >

Re: [Toolserver-l] s1 replag, some observations

the appearance was deceiving. Having data from rosemary now, I come up with an estimated completion date there of July 30, assuming that the rate at which updates are received from WMF does not change. -- Russell Blau russb...@imapmail.org ___ Toolserve

[Toolserver-l] s1 replag, some observations

lysis shows that, at this rate, completing the 230,000,000 remaining unpopulated revisions will take about 27 more days (estimated completion Aug 6 at 17:48 UTC). Anyone who relies on use of the enwiki_p database should expect a prolonged continuation of degraded service and steadily increasing r

Re: [Toolserver-l] SSH client for iPad

SSH Term Pro works, too; I think it cost $4.99. Sent from a handheld device. On Jun 22, 2012, at 9:13 PM, Ja Ga wrote: > Hey does anyone know of an iPad app that successfully SSH's to Toolserver? > The freebies aren't working for me and I'd like to know it will work before I > plunk down cash

Re: [Toolserver-l] Anoter SGE question

On Sun, Jun 17, 2012, at 02:29 PM, Dr. Trigon wrote: > > So why are some of my cronie-jobs or qcronsub calls (typically 1 per > day) silently dropped? > I have been having similar experiences lately, and opened a JIRA bug [1] to report it. So far, after more than a week, there have been no other

[Toolserver-l] s1 replication question

I note that MNT-1225, which was originally projected to take over 24 hours, is now closing in on 72 hours and there doesn't seem to be any meaningful way to project a completion time. Nothing we can do about that now, of course. But, I am wondering whether it was necessary to run these update

Re: [Toolserver-l] Data of s1 (enwiki) probably corrupted

"DaB." on Wednesday, January 25, 2012 9:42 AM: because of a wmf-master-change last week (when Nosy and I were in the datacenter) and a mistake on our side, the data of s1 which were inserted after 18. January are proberly defect or wrong. I already requested a new dump and will inform you, when

Re: [Toolserver-l] Data of s1 (enwiki) probably corrupted

I'll understand if you can't answer this yet, but is there any estimate of how long s1 replication will be unavailable (hours, days, weeks)? ___ Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org) https://lists.wikimedia.org/mailman/listinfo/

Re: [Toolserver-l] Submitting Python jobs to SGE from cron

Submitting Python jobs to SGE from cron > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Russell Blau: >> With these scripts in your home directly, you can then set up a cron job >> to >> run any Python script using the following syntax in your crontab: > >>

[Toolserver-l] Submitting Python jobs to SGE from cron

Since a number of users seem to be struggling with the conversion to Solaris, I thought I would share the scripts I have been using to start my Python bots from Solaris cron using the job server. If you want to use these, be sure to substitute your username for "username" in the last line of l

Re: [Toolserver-l] Set your default license

River Tarnell: > Russell Blau: >> How does one know what their LDAP password is? > > You can set it by running "setpass". Turns out it was already set. Nightshade accepted my current password in 'setlicense&

Re: [Toolserver-l] Set your default license

"River Tarnell" wrote: > Hi, > > We have now introduced the concept of a default license for each > account. This is documented on the wiki: > . > > In the future, selecting a default license will be required at account > creation time (for new

Re: [Toolserver-l] nightshade was rebooted

Yesterday I happened to be looking at http://status.toolserver.org/ and I noticed that the timestamp was about 45 minutes in the future -- of course, you will see this phenomenon only if you happen to load the page within an hour after it has been edited, which is infrequent. However, it seems to

Re: [Toolserver-l] where's enwiki_p on s1?

"Andrew Garrett" > This is totally unproductive, unwelcome and unnecessary. Please go > away if this is the sum of your contribution to this list. > > You seem to be making sarcastic comments attacking toolserver admins > for making an estimate an order of magnitude or two about how long the > s1

Re: [Toolserver-l] where's enwiki_p on s1?

"Carl Fürstenberg" wrote: > > Sadly the status hasn't changed much in the last days, I think people > wonder if you have an clue when it might be done, is it days, weeks or > months we are talking about? River Tarnell wrote at Fri Jul 31 20:42:13 UTC 2009: > River Tarnell: > > there will be a