Is there any reason a stock mediawiki installation would peg the cpu usage on a server?
On Mon, Feb 28, 2011 at 6:05 PM, Erik Luken eluken@pentarch.org wrote:
Is there any reason a stock mediawiki installation would peg the cpu usage on a server?
Yes. See http://www.mediawiki.org/wiki/Manual:Performance_tuning
On 01/03/11 10:05, Erik Luken wrote:
Is there any reason a stock mediawiki installation would peg the cpu usage on a server?
Yes. Usually this happens in response to some kind of web request. Perhaps if you could give details of the requests being made to the wiki, then we could help you to figure out why this is happening in your case.
-- Tim Starling
-----Original Message----- From: Tim Starling Sent: Monday, February 28, 2011 10:28 PM To: mediawiki-l@lists.wikimedia.org Subject: Re: [Mediawiki-l] Excessive cpu usage
On 01/03/11 10:05, Erik Luken wrote:
Is there any reason a stock mediawiki installation would peg the cpu usage on a server?
Yes. Usually this happens in response to some kind of web request. Perhaps if you could give details of the requests being made to the wiki, then we could help you to figure out why this is happening in your case.
-- Tim Starling
All I have are partial logs from my domain host showing CPU percentages of 100+% tied to index.php of the wiki. Beyond that, I've got nothing.
Erik Luken wrote:
All I have are partial logs from my domain host showing CPU percentages of 100+% tied to index.php of the wiki. Beyond that, I've got nothing.
As everything goes through index.php, that doesn't say much. Perhaps you could match the timestamps with the request log. You haven't disabled the page cache or installed an extension which disables it, right?
From: Platonides Sent: Wednesday, March 02, 2011 5:47 PM To: mediawiki-l@lists.wikimedia.org Subject: Re: [Mediawiki-l] Excessive cpu usage
Erik Luken wrote:
All I have are partial logs from my domain host showing CPU percentages of 100+% tied to index.php of the wiki. Beyond that, I've got nothing.
As everything goes through index.php, that doesn't say much. Perhaps you could match the timestamps with the request log. You haven't disabled the page cache or installed an extension which disables it, right? -----Original Message-----
That would be correct. I made some changes based on previous messages and they are monitoring again. Hopefully the changes made will solve the issue.
I've run into a strange issue whereby logging into a wiki as an externally authenticated user from one computer, then logging into the wiki from a second computer as the same user (also externally authenticated) will log the user out of the wiki on the first computer. This only happens with users who are authenticating externally. Locally authenticated user accounts (e.g., WikiSysop) are fine and can log in from many computers without affecting each other.
I think I've tracked it down to the "user_token" field in the User table of the database. It changes for every login of an externally authenticated user. It remains unchanged for local users when they login. I believe this is invalidating the cookies of the first login by the second login changing the value of user_token in the database and thus setting the first logged-in user's session to anonymous (from what I could gather reading the User.php code). My understanding is that the user_token is only changed when the user is initially created and when the password is reset, but for my externally authenticating users it happens at every login.
Has anyone seen this before and if so is there a reasonable fix? This is becoming a nuisance for some of my users who login a wiki using the same account from two or more machines.
Thanks in advance for any pointers...
-Jim
On Thu, Mar 3, 2011 at 12:19 PM, Sullivan, James (NIH/CIT) [C] < sullivan@mail.nih.gov> wrote:
I've run into a strange issue whereby logging into a wiki as an externally authenticated user from one computer, then logging into the wiki from a second computer as the same user (also externally authenticated) will log the user out of the wiki on the first computer. This only happens with users who are authenticating externally. Locally authenticated user accounts (e.g., WikiSysop) are fine and can log in from many computers without affecting each other.
I think I've tracked it down to the "user_token" field in the User table of the database. It changes for every login of an externally authenticated user. It remains unchanged for local users when they login. I believe this is invalidating the cookies of the first login by the second login changing the value of user_token in the database and thus setting the first logged-in user's session to anonymous (from what I could gather reading the User.php code). My understanding is that the user_token is only changed when the user is initially created and when the password is reset, but for my externally authenticating users it happens at every login.
user_token is used for the "remember my login" cookie; the fact that it resets when doing a login on a new computer/browser has been a problem for a long time, though if a session remains open on another machine/browser it'll stay valid.
Sounds like the external auth system being used isn't handling the regular session authentication for some reason, and relies on setting the cookie to match the user_token value... Is this one of the standard external auth plugins or a custom one?
-- brion
mediawiki-l@lists.wikimedia.org