Re: [Toolserver-l] commonswiki status

2009-08-20 Thread Fahad Sadah
2009/8/20 Bryan Tong Minh : > On Thu, Aug 20, 2009 at 5:06 PM, James Hare wrote: >> On Aug 20, 2009, at 7:56 AM, emijrp wrote: >> >> river, you rock >> >> Darn it son, why did you top post? >> >> 2009/8/19 Christopher Grant >>> > [...] > > New style, middle posting? :) > > ___

Re: [Toolserver-l] commonswiki status

2009-08-20 Thread Bryan Tong Minh
On Thu, Aug 20, 2009 at 5:06 PM, James Hare wrote: > On Aug 20, 2009, at 7:56 AM, emijrp wrote: > > river, you rock > > Darn it son, why did you top post? > > 2009/8/19 Christopher Grant >> [...] New style, middle posting? :) ___ Toolserver-l mailing

Re: [Toolserver-l] commonswiki status

2009-08-20 Thread James Hare
On Aug 20, 2009, at 7:56 AM, emijrp wrote: river, you rock Darn it son, why did you top post? 2009/8/19 Christopher Grant On Wed, Aug 19, 2009 at 1:30 AM, River Tarnell > wrote: > commons has now been reimported and is available on all servers. thank you river - Chris On Wed, Aug 19, 2

Re: [Toolserver-l] commonswiki status

2009-08-20 Thread emijrp
river, you rock 2009/8/19 Christopher Grant > On Wed, Aug 19, 2009 at 1:30 AM, River Tarnell < > ri...@loreley.flyingparchment.org.uk> wrote: > > commons has now been reimported and is available on all servers. > thank you river > > - Chris > > > On Wed, Aug 19, 2009 at 1:30 AM, River Tarnell <

Re: [Toolserver-l] commonswiki status

2009-08-19 Thread Christopher Grant
On Wed, Aug 19, 2009 at 1:30 AM, River Tarnell < ri...@loreley.flyingparchment.org.uk> wrote: > commons has now been reimported and is available on all servers. thank you river - Chris On Wed, Aug 19, 2009 at 1:30 AM, River Tarnell < ri...@loreley.flyingparchment.org.uk> wrote: > -BEGIN PGP

Re: [Toolserver-l] commonswiki status

2009-08-18 Thread River Tarnell
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 commons has now been reimported and is available on all servers. - river. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (HP-UX) iEYEARECAAYFAkqK5SoACgkQIXd7fCuc5vKCdACfUFm/6uX50n/xVzNyasLGDnJg Y2AAoJ4WveeBhvd0LzKdt6fJl18vWHL1 =1R5k

Re: [Toolserver-l] commonswiki status

2009-08-18 Thread Platonides
DaB. wrote: > BTW: If the wm-server-admins hadn't drop commons from s2, we wouldn't need a > dump ;) Sure. What about restricting drops so they aren't replicated? That would make toolserver resistant against some datalosses at tampa (including careless sysadmins ;) ). However, a subsequent create

Re: [Toolserver-l] commonswiki status

2009-08-18 Thread River Tarnell
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Platonides: > If the dump is there, then the only remaining task is reimporting it > [before binlogs are deleted], which shouldn't be much an issue. actually, while importing the dump we found a regression (bug) in the newer version of MySQL that we r

Re: [Toolserver-l] commonswiki status

2009-08-17 Thread DaB.
Hello, Am Dienstag 18 August 2009 00:37:40 schrieb Platonides: > Reading DaB message, I thought the problem was taking a dump I tought so, yes. BTW: If the wm-server-admins hadn't drop commons from s2, we wouldn't need a dump ;) Sincerly, DaB. -- wp-blog.de signature.asc Description: This

Re: [Toolserver-l] commonswiki status

2009-08-17 Thread Platonides
River Tarnell wrote: > Platonides: >> They should have kept a s2 slave so toolserver could get a dump from it. > > why? we already have a dump from an s4 slave. > > - river. Reading DaB message, I thought the problem was taking a dump, since it was harder to take a s4 slave out of rotatio

Re: [Toolserver-l] commonswiki status

2009-08-17 Thread River Tarnell
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Platonides: > They should have kept a s2 slave so toolserver could get a dump from it. why? we already have a dump from an s4 slave. - river. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (HP-UX) iEYEARECAAYFAkqJ2QwACgkQIXd7fCuc5vI8Lg

Re: [Toolserver-l] commonswiki status

2009-08-17 Thread Platonides
River Tarnell wrote: > Platonides: >> Wouldn't that have required making a dump of the db to reimport it at >> the new cluster? > > no. s4 was created by taking existing s2 slaves and removing all > databases which were not commons. then commonswiki was dropped on the > remaining s2 servers. >

Re: [Toolserver-l] commonswiki status

2009-08-17 Thread River Tarnell
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Platonides: > Wouldn't that have required making a dump of the db to reimport it at > the new cluster? no. s4 was created by taking existing s2 slaves and removing all databases which were not commons. then commonswiki was dropped on the remaining s

Re: [Toolserver-l] commonswiki status

2009-08-17 Thread Platonides
DaB. wrote: > Hello, > Am Montag 17 August 2009 21:44:28 schrieb Carl Fürstenberg: >> Perhaps there would be an idea to initiate an other dev to be able to >> do such work. > > it is not this easy as you think. For taking a dump, a db-slave of the wm- > cluster has to taken away from the cluster.

Re: [Toolserver-l] commonswiki status

2009-08-17 Thread DaB.
Hello, Am Montag 17 August 2009 21:44:28 schrieb Carl Fürstenberg: > Perhaps there would be an idea to initiate an other dev to be able to > do such work. it is not this easy as you think. For taking a dump, a db-slave of the wm- cluster has to taken away from the cluster. That means that the clus

Re: [Toolserver-l] commonswiki status

2009-08-17 Thread River Tarnell
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Carl Fürstenberg: > Perhaps there would be an idea to initiate an other dev to be able to > do such work. that would be nice. do you know someone who can be approved for both Toolserver and Wikimedia root access and who has time to be a TS admin? in

Re: [Toolserver-l] commonswiki status

2009-08-17 Thread Carl Fürstenberg
On Mon, Aug 17, 2009 at 21:37, River Tarnell wrote: > > i guess it's hard to believe, but there are times in my life when i'm > doing things which aren't related to the Toolserver. > Perhaps there would be an idea to initiate an other dev to be able to do such work. -- /Carl Fürstenberg _

Re: [Toolserver-l] commonswiki status

2009-08-17 Thread River Tarnell
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Maarten Dammers: > What's the reason why it can't be done right away? i guess it's hard to believe, but there are times in my life when i'm doing things which aren't related to the Toolserver. - river. -BEGIN PGP SIGNATURE- Version: G

Re: [Toolserver-l] commonswiki status

2009-08-17 Thread Maarten Dammers
River Tarnell schreef: > Maarten Dammers: > >> Any idea when? >> > no. > What's the reason why it can't be done right away? What's delaying the import? Maarten ___ Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org) https://lists.w

Re: [Toolserver-l] commonswiki status

2009-08-17 Thread River Tarnell
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Maarten Dammers: > Any idea when? no. - river. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (HP-UX) iEYEARECAAYFAkqJsAcACgkQIXd7fCuc5vLJkQCgtQXd0hK0/nfPpLC7vmj32/cQ JIYAnRW2++A1yBtSJRcoTUlXYSeNQF0O =8swi -END PGP SIGNATURE- _

Re: [Toolserver-l] commonswiki status

2009-08-17 Thread Maarten Dammers
River Tarnell schreef: > due to some confusion during Wikimedia's move of commons to a new > cluster, the database was dropped on the Toolserver and is not > available. we will do a reimport at some point to bring it back. > At some point? Any idea when? Commons stops functioning without the s

[Toolserver-l] commonswiki status

2009-08-16 Thread River Tarnell
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 hi, due to some confusion during Wikimedia's move of commons to a new cluster, the database was dropped on the Toolserver and is not available. we will do a reimport at some point to bring it back. - river. -BEGIN PGP SIGNATURE- Vers