Last modified: 2011-12-01 18:46:36 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T11365, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 9365 - segfault on /index.php after installation
segfault on /index.php after installation
Status: RESOLVED INVALID
Product: MediaWiki
Classification: Unclassified
User blocking (Other open bugs)
1.9.x
PC Linux
: Highest blocker (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-03-22 04:51 UTC by Sven
Modified: 2011-12-01 18:46 UTC (History)
2 users (show)

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


Attachments

Description Sven 2007-03-22 04:51:08 UTC
- installation went OK
- remove /config
- hit /[installedpath]/

apache error logs:
[Wed Mar 21 21:36:52 2007] [notice] child pid 31905 exit signal Segmentation
fault (11)

traced it to this call:
        includes/Wiki.php, line 74
        $ret = Title::newMainPage();

following the methods to
        includes/GlobalFunctions.php, line 420
        $message = $wgMessageCache->get( $key, $useDB, $forContent );
        where values are "mainpage", 1, 1
Comment 1 Jason Spiro 2007-03-22 09:34:00 UTC
Thank you for your bug report and for your troubleshooting work.

NOTE: I am not a developer or even a bug triager, I am just some guy. But still,
I suspect this is not a MediaWiki bug.  If you could please provide us with more
information:

1. What is your:

- Apache version
- PHP version
- Operating system and version

2. How often has this segfault happened?

3. Have you done anything with your /wiki/ directory since the crash happened,
or do you still have the directory?

4. Did you get any weird messages during the installation?
Comment 2 Brion Vibber 2007-03-22 14:19:21 UTC
Check also for presence of various PHP or Zend extensions.
Some may have compatibility or stability issues.
Comment 3 Sven 2007-03-22 16:30:31 UTC
Jason, Brion - thanks for the shout, and here's the add'l info. 

1.
Apache 2.2.4
PHP 5.2.1
REHL (2.6.9-34.EL) on a dell x86
eAccellerator 0.9.5

2.
every request to the mediawiki = seg fault.
Other PHP apps running fine

3. I installed into /mediawiki - directory untouched except for removal of /config

4. Not weird errors - install was point-click and done.

php.ini section:
extension="eaccelerator.so"
  eaccelerator.shm_size="50"
  eaccelerator.cache_dir="/tmp/eaccelerator"
  eaccelerator.enable="1"
  eaccelerator.optimizer="1"
  eaccelerator.check_mtime="1"
  eaccelerator.debug="0"
  eaccelerator.filter=""
  eaccelerator.shm_max="0"
  eaccelerator.shm_ttl="0"
  eaccelerator.shm_prune_period="0"
  eaccelerator.allowed_admin_path = "/usr/local/apache2/htdocs/eacc.php"

php config
'./configure' '--with-apxs2=/usr/local/apache2/bin/apxs' '--disable-cli'
'--disable-cgi' '--with-config-file-path=/etc' '--with-zlib' '--enable-calendar'
'--with-curl' '--enable-exif' '--enable-ftp' '--with-gd' '--enable-mbstring'
'--enable-zip' '--enable-zend-multibyte' '--with-magickwand=/usr' '--with-mysql'
'--with-mysql-libs=/usr/lib/mysql' '--with-mysql-headers=/usr/include/mysql'
'--enable-soap'

eAccel config
./configure --with-eaccelerator-disassembler --with-eaccelerator-info --enab
le-eaccelerator=shared --with-php-config=/usr/local/bin/php-config

apache config
./configure --enable-modules=most --enable-mods-shared=all --enable-so
Comment 4 Brion Vibber 2007-03-22 17:46:47 UTC
eAccelerator 0.9.5 has multiple known problems with PHP 5.2.x... try removing that.
You may have to build 0.9.6 prereleases from source control, or try APC or another
alternative.
Comment 5 Sven 2007-03-22 18:53:21 UTC
remove eAccel 0.9.5 and use APC (latest)

issue resolved - not a MediaWiki issue

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


Navigation
Links