Re: DNS-problems

On 30 November 2011 23:31, DeltaQuad <deltaquadwiki <at> gmail.com> wrote:
> But wouldn't a DNS issue with attempting to contact the database by
> hostname bring up such error? (Because the ACC project issue started
> just yesterday or so (in my timezone).

That's not related.

A DNS error wouldn't cause MySQL to report "too many connections".

Simon

Re: Cron <deltaquad <at> willow> cronsub UAABot $HOME/UAA/UAA.py

Say what? (Sorry this is the kinda stuff I don't understand yet).

FYI The cronie was installed on willow and this has ran plenty of times
before.

--DQ

On 06/12/2011 07:27, Cron Daemon wrote:
> error: failed receiving gdi request response for mid=1 (got syncron message receive timeout error).

Toolserver unreachable

Hello,

the toolserver is currently unavailable. I did not  expect a "ifconfig -a status" to hang the maschine but
rebooting failed because the remote console (ilom) was unable to restart the system.
Someone from the data center in Tampa will go and try to reanimate the server.

Will keep you updated.

Cheers
 	nosy

Fwd: Help us shape the future data/research infrastructure for Wikimedia

Dario Taraborelli, a Wikimedia Foundation research analyst, wants to
make sure that the Wikimedia data sources and infrastructure that we
provide serve your needs, present and future.  So please take this short
survey (see below).  Thanks.

-Sumana Harihareswara, WMF volunteer development coordinator

> Dear all,
> 
> apologies for cross-posting. 
> 
> I'd like to ask you to take a moment and help us understand how to better serve the research / data mining /
mashup developer community with Wikimedia data: http://bit.ly/WikimediaData
> If you are interested in working with our data please take this survey and help us circulate the link among
your contacts, or just retweet http://twitter.com/#!/ReaderMeter/status/143843238837620736
> 
> Best,
> Dario

Re: Toolserver unreachable

hello all,
At Wednesday 07 December 2011 20:31:20 DaB. wrote:
> Someone from the data center in Tampa will go and try to reanimate the
> server.
> 
> Will keep you updated.

the problem was fixed with MNT-1151. Maybe the original email was a little be 
exaggerate, the toolserver itself was working (login, webpages and tools), but 
no peripherie (like jira, the wiki and fisheye) and no replication was running 
during the outtake.

The announced maintenance is starting now.

Sincerly,
DaB.

--

-- 
Userpage: [[:w:de:User:DaB.]] — PGP: 2B255885

hello all,
At Wednesday 07 December 2011 20:31:20 DaB. wrote:
> Someone from the data center in Tampa will go and try to reanimate the
> server.
> 
> Will keep you updated.

the problem was fixed with MNT-1151. Maybe the original email was a little be 
exaggerate, the toolserver itself was working (login, webpages and tools), but 

Re: Fwd: Help us shape the future data/research infrastructure for Wikimedia

<div>
<p></p>
<p>Dennis Tobar<br></p>
<div class="gmail_quote">El 07/12/2011 16:33, "Sumana Harihareswara" &lt;<a href="mailto:sumanah <at> wikimedia.org">sumanah <at> wikimedia.org</a>&gt; escribi&oacute;:<br type="attribution"><blockquote class="gmail_quote">
Dario Taraborelli, a Wikimedia Foundation research analyst, wants to<br>
make sure that the Wikimedia data sources and infrastructure that we<br>
provide serve your needs, present and future. &nbsp;So please take this short<br>
survey (see below). &nbsp;Thanks.<br><br>
-Sumana Harihareswara, WMF volunteer development coordinator<br><br>
&gt; Dear all,<br>
&gt;<br>
&gt; apologies for cross-posting.<br>
&gt;<br>
&gt; I'd like to ask you to take a moment and help us understand how to better serve the research / data mining / mashup developer community with Wikimedia data: <a href="http://bit.ly/WikimediaData" target="_blank">http://bit.ly/WikimediaData</a><br>

&gt; If you are interested in working with our data please take this survey and help us circulate the link among your contacts, or just retweet <a href="http://twitter.com/#!/ReaderMeter/status/143843238837620736" target="_blank">http://twitter.com/#!/ReaderMeter/status/143843238837620736</a><br>

&gt;<br>
&gt; Best,<br>
&gt; Dario<br><br><br><br>
_______________________________________________<br>
Toolserver-l mailing list (<a href="mailto:Toolserver-l <at> lists.wikimedia.org">Toolserver-l <at> lists.wikimedia.org</a>)<br><a href="https://lists.wikimedia.org/mailman/listinfo/toolserver-l" target="_blank">https://lists.wikimedia.org/mailman/listinfo/toolserver-l</a><br>
Posting guidelines for this list: <a href="https://wiki.toolserver.org/view/Mailing_list_etiquette" target="_blank">https://wiki.toolserver.org/view/Mailing_list_etiquette</a><br>
</blockquote>
</div>
</div>

Dumps handling / storage / updating etc...

Hi,

currently there is quite a big mess in how dump files are handled. They are located in several locations
without any system in it, some locations are public, some private, thus there are obviously duplicates
which eat the space etc. Also their naming differs.

Hence I've got this proposal:

I would like to set up the system for overal handling of dumps which includes system of their storage,
naming/linking and updating.

That would help to lower down the used space, easier transfer of the entire dump storage (i.e. in future we
could have dedicated HDD(s) to dumps only), easier maintenance etc.

The idea of storage system, naming and linking is nearly complete, maintenance scripts work, but might be
tweaked in some cases, some additional scripts might be necessary.

I think that this could be multi maintainer project for couple people (in case one is not around, other one
can step in), so is there anybody active interested in joining?

---- FOR THOSE WHO USE DUMPS ----

When moving to the new system this would mean to you:
1) you would have to submit a list of dumps you use
2) you would have to update your tools which use dumps to use the shared dumps

For some time during the transition we would keep symlinks on old locations (instead of the files
themselves) but the final step is to have dumps only on one place.

Questions, comments, suggestions?

Kind regards

Danny B.

Re: Dumps handling / storage / updating etc...

Am 09.12.2011 12:41, schrieb Danny B.:
> Questions, comments, suggestions?

When you have data to share, the main problem is usually finding someone 
who is able and willing to store multi-gigabyte files on their server 
and provide the necessary bandwith for downloaders.

Collecting all dumps in one place begins with building a 
hosting-location with some terabytes of storage and a fast connection.

Peter

Re: Dumps handling / storage / updating etc...

> ------------ Původní zpráva ------------
> Od: Peter Körner <osm-lists <at> mazdermind.de>
> ----------------------------------------
> When you have data to share, the main problem is usually finding someone 
> who is able and willing to store multi-gigabyte files on their server 
> and provide the necessary bandwith for downloaders.
> 
> Collecting all dumps in one place begins with building a 
> hosting-location with some terabytes of storage and a fast connection.

We already have these dumps stored in /mnt/user-storage/<various places> as well as lot of people have
them in their ~.

The purpose is to have them only on one place, since now they are very often duplicated and on many places.

Also, only those dumps, which are being used by TS users are supposed to be stored, the proposal is not about
mirroring the dumps.wikimedia.org...

Danny B.

Re: Dumps handling / storage / updating etc...

Am 09.12.2011 12:52, schrieb Danny B.:
> We already have these dumps stored in /mnt/user-storage/<various places>  as well as lot of people have
them in their ~.
I'm sorry I've missed that this mail was on the Toolserver-Mailinglist.

Never mind.

Peter