Hi,
I created the following patch, infra cores must approve that:
https://review.openstack.org/285641 Add ssh key of JP Maxwell to wiki.o.o
Marton
On Sat, Feb 27, 2016 at 6:41 AM JP Maxwell wrote:
> Marton has SSH access and applied a patch earlier today. It appears the
> spam continues to fl
Marton has SSH access and applied a patch earlier today. It appears the
spam continues to flow:
https://wiki.openstack.org/wiki/40_Thoughts_Of_Using_Open_Shelves_On_A_Kitchen
Marton let me know if you can look at it some more or Infra if you want to
give me SSH I'll do so as well in the morning
Super thankful for all the folks that have jumped in over the last
couple of days to help with the puppetization, etc... I just feel like
we're taking a very wrong approach here.
Paul Belanger wrote:
Right, and I don't have an issue with that approach. Based on the work we did
yesterday, anyb
A quick google indicates this may be an unrelated issue that should be fixed,
but I don’t *think* it is related to the spam.
J.P. Maxwell | tipit.net [http://tipit.net] | fibercove.com
[http://www.fibercove.com]
On Fri, Feb 26, 2016 at 11:56 AM, Marton Kiss wrote:
I'm going to get a dinner, but
Yeah, I checked it and it is internal job runner:
https://www.mediawiki.org/wiki/Manual:Job_queue
M.
On Fri, Feb 26, 2016 at 7:00 PM JP Maxwell wrote:
> A quick google indicates this may be an unrelated issue that should be
> fixed, but I don’t *think* it is related to the spam.
>
> *J.P. Maxwe
I'm going to get a dinner, but I'll be on irc after, so if I can help
somehow, I will be here. #openstack-infra mrmartin
M.
On Fri, Feb 26, 2016 at 6:51 PM Paul Belanger wrote:
> On phone but patch puppet-mediawiki and enable captcha for all pages. We
> only did edit and create
> On Feb 26, 201
On the wiki instance, my ssh access is working now. What I see in the logs
are the continuous POST requests.
M.
On Fri, Feb 26, 2016 at 6:42 PM JP Maxwell wrote:
> Marton
>
> Where are you seeing the logs?
>
> Paul
>
> The point is that to comment out a line in VI and watch the logs in
> anothe
Marton
Where are you seeing the logs?
Paul
The point is that to comment out a line in VI and watch the logs in another
window takes about a minute or two. To submit a patch, get approval, push, ask
someone to share the logs takes a lot longer and relies on other people.
I understand the need for op
I see a ton of incoming post requests:
POST
/w/index.php?title=Special%3ARunJobs&tasks=jobs&maxjobs=1&sigexpiry=1456508270&signature=571cfb216f944b15d2eee1c0253d08b77003328e
M.
On Fri, Feb 26, 2016 at 6:35 PM Marton Kiss wrote:
> Oh, I can login. So what we need?
>
> M.
>
> On Fri, Feb 26, 201
On Fri, Feb 26, 2016 at 11:29:31AM -0600, JP Maxwell wrote:
> I think what Jimmy is referring to is what I was suggesting by removing the
> extensions / making the question impossible to answer. Basically a series of
> rapid fire changes while tailing the logs and seeing what stops the spam.
> Once
Oh, I can login. So what we need?
M.
On Fri, Feb 26, 2016 at 6:33 PM JP Maxwell wrote:
> I think what Jimmy is referring to is what I was suggesting by removing
> the extensions / making the question impossible to answer. Basically a
> series of rapid fire changes while tailing the logs and se
I think what Jimmy is referring to is what I was suggesting by removing the
extensions / making the question impossible to answer. Basically a series
of
rapid fire changes while tailing the logs and seeing what stops the spam.
Once
you know what worked then you can submit as an official patch. B
On Fri, Feb 26, 2016 at 11:08:18AM -0600, Jimmy McArthur wrote:
> Given the state of the wiki a the moment, I think taking the quickest path
> to get it fixed would be prudent. Is there a way we can get JP root access
> to this server, even temporarily? We get 25% of our website traffic (2
> millio
Given the state of the wiki a the moment, I think taking the quickest
path to get it fixed would be prudent. Is there a way we can get JP root
access to this server, even temporarily? We get 25% of our website
traffic (2 million visitors) to the wiki. I realize we're all after the
same thing, b
On Fri, Feb 26, 2016 at 10:12:12AM -0600, JP Maxwell wrote:
> But if you wanted to upgrade everything, remove the mobile view extension,
> test in a dev/staging environment then deploy to production fingers
> crossed, I think that would be a valid approach as well.
>
Current review up[1]. I'll lau
But if you wanted to upgrade everything, remove the mobile view extension,
test in a dev/staging environment then deploy to production fingers
crossed, I think that would be a valid approach as well.
J.P. Maxwell | tipit.net | fibercove.com
On Feb 26, 2016 10:08 AM, "JP Maxwell" wrote:
> Plus on
Plus one except in this case it is much easier to know if our efforts are
working on production because the spam either stops or not.
J.P. Maxwell | tipit.net | fibercove.com
On Feb 26, 2016 9:48 AM, "Paul Belanger" wrote:
> On Fri, Feb 26, 2016 at 09:18:00AM -0600, JP Maxwell wrote:
> > I reall
On Fri, Feb 26, 2016 at 09:18:00AM -0600, JP Maxwell wrote:
> I really think you might consider the option that there is a vulnerability
> in one of the extensions. If that is the case black listing IPs will be an
> ongoing wild goose chase.
>
> I think this would be easily proven or disproven by
On Fri, Feb 26, 2016 at 10:34:56AM +, Marton Kiss wrote:
> I've deployed the mediawiki using our puppet modules to my dev machine, and
> we have more problems here:
> [image: The MediaWiki logo] MediaWiki 1.27 internal error
>
> MediaWiki 1.27 requires at least PHP version 5.5.9, you are using
I really think you might consider the option that there is a vulnerability
in one of the extensions. If that is the case black listing IPs will be an
ongoing wild goose chase.
I think this would be easily proven or disproven by making the questy
question impossible and see if the spam continues.
On Thu, Feb 25, 2016 at 08:10:34PM -0800, Elizabeth K. Joseph wrote:
> On Thu, Feb 25, 2016 at 6:35 AM, Jeremy Stanley wrote:
> > On 2016-02-25 02:46:13 -0600 (-0600), JP Maxwell wrote:
> >> Please be aware that you can now create accounts under the mobile
> >> view in the wiki native user table.
Yeah, I'm waiting for my ssh access, it will arrive soon, so I can do a
proper clone of the site. Anyway it is interesting that mediawiki is
rendering a different output based on user agent.
M.
On Fri, Feb 26, 2016 at 2:41 PM JP Maxwell wrote:
> Marton
>
> Make sure you are using the right upst
Marton
Make sure you are using the right upstream repository. They are in version
1.25. Check out: https://wiki.openstack.org/wiki/Special:Version
Not that it shouldn't all be upgraded ;) be aware there seem to be config
file formatting differences in the latest version vs 1.25 as well.
J.P. Max
I've deployed the mediawiki using our puppet modules to my dev machine, and
we have more problems here:
[image: The MediaWiki logo] MediaWiki 1.27 internal error
MediaWiki 1.27 requires at least PHP version 5.5.9, you are using PHP
5.3.10-1ubuntu3.21.
Supported PHP versions
Please consider upgrad
On 2016-02-26 10:51:12 +0100 (+0100), Thierry Carrez wrote:
> Spencer Krum wrote:
> [...]
> > * This is the first infra sprint that wasn't focused on 'infra
> > 101' training for brand new contributors. Several attendees said
> > they felt they got a lot more work done at this sprint than when
> >
Spencer Krum wrote:
Things that went well:
* Many people expressed that focusing on a single topic made the event
great.
I think that's a very good point. I think we had three types of midcycle
events. In the first one you meet to get together to know each other
better and converge on a comm
26 matches
Mail list logo
