If your install of Apache is failing like this, chances are that there's something seriously wrong with it. I suggest you completely reinstall Apache from the ground up.
You should do this even if your server works perfectly, since the latest version of Apache is 2.0.54 and your server is quite vulnerable if you don't upgrade.
-----Original Message----- From: mediawiki-l-bounces@Wikimedia.org [mailto:mediawiki-l- bounces@Wikimedia.org] On Behalf Of Jason Lixfeld Sent: Friday, July 22, 2005 10:00 AM To: MediaWiki announcements and site admin list Subject: [Mediawiki-l] Apache Seg Fault when attempting to save any
edit
Keep seeing these in my apache logs after editing any page. Needless to say the browser disconnects and cannot complete the request so the edit never takes.
==> access_log <== 192.168.100.190 - - [22/Jul/2005:12:40:33 -0400] "GET / HTTP/1.1" 301
28
192.168.100.190 - - [22/Jul/2005:12:40:33 -0400] "GET /index.php/ Main_Page HTTP/1.1" 304 28 192.168.100.190 - - [22/Jul/2005:12:40:40 -0400] "GET /index.php? title=Main_Page&action=edit HTTP/1.1" 200 3004
==> error.log <== [Fri Jul 22 12:40:53 2005] [notice] child pid 26551 exit signal Segmentation fault (11)
I'm running (not sure if the perl stuff matters, but I'll include it anyway):
php4-4.3.11_1 perl-5.8.6_2 mod_perl2-2.0.1,2 bsdpan-libwww-perl-5.803 apache-2.0.50_1 mediawiki-1.4.6
Anyone seen this or know how to possibly troubleshoot it? _______________________________________________ MediaWiki-l mailing list MediaWiki-l@Wikimedia.org http://mail.wikipedia.org/mailman/listinfo/mediawiki-l
Well, I upgraded to 2.0.54 with no joy. Still get the seg faults. Anyone seen any issue with PHP or the like causing these issues? A permissions problem, perhaps?
On 22-Jul-05, at 3:35 PM, Zain Memon wrote:
If your install of Apache is failing like this, chances are that there's something seriously wrong with it. I suggest you completely reinstall Apache from the ground up.
You should do this even if your server works perfectly, since the latest version of Apache is 2.0.54 and your server is quite vulnerable if you don't upgrade.
-----Original Message----- From: mediawiki-l-bounces@Wikimedia.org [mailto:mediawiki-l- bounces@Wikimedia.org] On Behalf Of Jason Lixfeld Sent: Friday, July 22, 2005 10:00 AM To: MediaWiki announcements and site admin list Subject: [Mediawiki-l] Apache Seg Fault when attempting to save any
edit
Keep seeing these in my apache logs after editing any page. Needless to say the browser disconnects and cannot complete the request so the edit never takes.
==> access_log <== 192.168.100.190 - - [22/Jul/2005:12:40:33 -0400] "GET / HTTP/1.1" 301
28
192.168.100.190 - - [22/Jul/2005:12:40:33 -0400] "GET /index.php/ Main_Page HTTP/1.1" 304 28 192.168.100.190 - - [22/Jul/2005:12:40:40 -0400] "GET /index.php? title=Main_Page&action=edit HTTP/1.1" 200 3004
==> error.log <== [Fri Jul 22 12:40:53 2005] [notice] child pid 26551 exit signal Segmentation fault (11)
I'm running (not sure if the perl stuff matters, but I'll include it anyway):
php4-4.3.11_1 perl-5.8.6_2 mod_perl2-2.0.1,2 bsdpan-libwww-perl-5.803 apache-2.0.50_1 mediawiki-1.4.6
Anyone seen this or know how to possibly troubleshoot it? _______________________________________________ MediaWiki-l mailing list MediaWiki-l@Wikimedia.org http://mail.wikipedia.org/mailman/listinfo/mediawiki-l
MediaWiki-l mailing list MediaWiki-l@Wikimedia.org http://mail.wikipedia.org/mailman/listinfo/mediawiki-l
Jason Lixfeld wrote:
Well, I upgraded to 2.0.54 with no joy. Still get the seg faults. Anyone seen any issue with PHP or the like causing these issues? A permissions problem, perhaps?
Segmentation faults are always due to one of: * Software bugs * Hardware failure
Since PHP programs cannot access memory directly, segmentation faults due to software bugs must be problems with: * The PHP interpreter itself * some PHP extension or library call * the web server * the operating system
Common hardware failures that can cause segmentation faults include: * Overheating * Bad memory
Note that PHP recommends that Apache 2 be used in prefork mode rather than threaded mode, as some PHP extensions may not be thread-safe.
-- brion vibber (brion @ pobox.com)
Fixed it. Upgraded apache to 2.0.54, upgraded PHP to 4.4 and upgraded all related php modules to 4.4.
On 24-Jul-05, at 11:33 AM, Brion Vibber wrote:
Jason Lixfeld wrote:
Well, I upgraded to 2.0.54 with no joy. Still get the seg faults. Anyone seen any issue with PHP or the like causing these issues? A permissions problem, perhaps?
Segmentation faults are always due to one of:
- Software bugs
- Hardware failure
Since PHP programs cannot access memory directly, segmentation faults due to software bugs must be problems with:
- The PHP interpreter itself
- some PHP extension or library call
- the web server
- the operating system
Common hardware failures that can cause segmentation faults include:
- Overheating
- Bad memory
Note that PHP recommends that Apache 2 be used in prefork mode rather than threaded mode, as some PHP extensions may not be thread-safe.
-- brion vibber (brion @ pobox.com) _______________________________________________ MediaWiki-l mailing list MediaWiki-l@Wikimedia.org http://mail.wikipedia.org/mailman/listinfo/mediawiki-l
On 7/24/05, Jason Lixfeld jason+lists.mediawiki@lixfeld.ca wrote:
Well, I upgraded to 2.0.54 with no joy. Still get the seg faults. Anyone seen any issue with PHP or the like causing these issues? A permissions problem, perhaps?
You can try running it with strace and see if you can determine when it dies.
mediawiki-l@lists.wikimedia.org