Last modified: 2014-02-27 19:18:07 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 60844 - Default for $wgMaxShellMemory too low
Default for $wgMaxShellMemory too low
Status: NEW
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
1.23.0
All All
: Normal major (vote)
: ---
Assigned To: Nobody - You can work on this!
: performance
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-02-04 20:16 UTC by Mark A. Hershberger
Modified: 2014-02-27 19:18 UTC (History)
3 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Mark A. Hershberger 2014-02-04 20:16:00 UTC
Reported on Support Desk [[mw:Thread:Project:Current issues/Default for $wgMaxShellMemory too low]].

  since update to mediawiki 1.22 I got many errors like this in my logs:

    PHP Warning: PHP Startup: Unable to load dynamic library '/usr/lib64/php/modules/xmlreader.so'...
  
  after some googeling I found out that due to some changes in mediawiki, the
  default for $wgMaxShellMemory is too low, even the raised one from 1.22
  
  raising $wgMaxShellMemory to 512000 solved the problem for me.

Seems like a no-brainer to raise it...
Comment 1 Kevin Israel (PleaseStand) 2014-02-05 01:32:16 UTC
If raising $wgMaxShellMemory did in fact stop the warnings, this may be yet another issue caused by ccabd0efb05e (the job queue change)...
Comment 2 Mark A. Hershberger 2014-02-05 15:45:34 UTC
(In reply to comment #1)
> If raising $wgMaxShellMemory did in fact stop the warnings, this may be yet
> another issue caused by ccabd0efb05e (the job queue change)...

Noted.  I'll try to get the user to test this out.
Comment 3 Gerrit Notification Bot 2014-02-27 19:18:07 UTC
Change 113038 merged by jenkins-bot:
Moved job running via $wgJobRunRate to a special API

https://gerrit.wikimedia.org/r/113038

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links