Apache segmentation fault

[webfeatus]

I am receiving regular errors:
Received From: loft2234->/var/log/httpd/error_log
Rule: 30104 fired (level 12) -> "Apache segmentation fault."
[Fri Feb 18 03:13:41 2011] [notice] child pid 25761 exit signal Segmentation fault (11)

I can see related issues but nothing below seems to relate to my particular situation:
http://www.atomicorp.com/forum/viewtopic.php?f=1&t=4724
http://www.atomicorp.com/forum/viewtopi ... =12&t=4570
http://www.atomicorp.com/forum/viewtopi ... =12&t=4698

I believe that the issue started after a yum ioncube update but I cannot find any more information about the error from the logs.

I have this link which I think may be related to my problem:
http://forum.parallels.com/pda/index.php/t-85988.html

I have no idea what my next step is.
Can anyone help?

[biggles]

Well, my problem was definitely connected to zend, so my suggestions is trying without it...

[webfeatus]

I cannot simply disable ioncube as some clients require it.

I found that ioncube was disabled after yum update:
Feb 09 01:05:49 Erased: php5-ioncube-loader
Feb 09 01:05:31 Installed: 1:php-ioncube-loader-4.0.5-1.el5.art.x86_64

The problem seemed to be that this file was missing.
/etc/php.d/ioncube.ini

So I added this line to that file:
zend_extension=/usr/lib64/php/ioncube/ioncube_loader_lin_5.2.so

The program which required ioncube began to work but the segfaults started.

[faris]

The segfaults may be caused by something else (like mine), but in the meantime I'd look to make sure that you are loading the most recent ioncube_loader_lin_5.2.so

I do not use the RPMs for ioncube/Zend - I download the latest version directly and copy the appropriate .so files to the right place in order to make sure everything is happening correctly.

So it might be worth double-checking you don't have more than one ioncube_loader_lin_5.2.so stored in your filesystem and if you do then make sure you are loading the correct one, just in case this is the cause of the problem.

[webfeatus]

Although I still have not solved the segfault issue, can I digress to the previous step which actually initiated the problem: "yum update"

Since using ASL for 3 years now, I find a regular occurrance:
1. System is operating perfectly.
2. Run Yum update.
3. Spend months working out how the update destroyed my system.

I perform "yum update" only because it is recommended by ASL, and occassionally, very occassionally, there are necessary updates required for ASL to operate effectively. Other than those particular files, to be honest, I could care less; because, you see, my system is working perfectly - at that point.

I have no idea about configuring the yum repository file therefore I use standard defaults like atomic, centos, etc. And I run yum update as an automatic function.

I don't even know how to select from the files that are "ready to update" and only update the preferred ones, individually and manually.

Let alone knowing how to make a distinction as to what I should or shouldn't download.

And even if I could make a distinction and only download "required" files, then ASL would tell me that my system needs updating - into eternity; because I had not downloaded the updates recommended by my yum respository configuration.

(hear me screaming, at this stage)

After my system is adversly affected by an update; ioncube, sql, centos files, or whatever - ASL support and this forum tend to inform me "Oh, you shouldn't have updated that OR I never use the RPM's for that."

I am not a professional server administrator.
I am only a bloke who wants reliable server security.
I have no idea of what future hassles I am creating for myself when I automatically install by running yum update the way that I do.
Is there any advice for someone like me?

[biggles]

My advise would be to stay on a bit older platforms, like CentOS 4.X. Normally new functionality releases aren't released for these older platforms. Then you can happily stay on an older platform. But you wont benefit from newer releases...

Myself, I try to check out what actually is updated before I complete a yum update. Are there any key components that are updated (mysql, php, apache for example)? Have I read anything about them on the forums (for example I read all new posts at this forum, which usually keeps me in the clear)? I also keep a test environment set up where I can try the updates before running them in production (using virtual server on a VMware platform, this doesn't even cost me any money, just some time now and then...). The main reason behind this is that I feel that old releases often aren't supported anymore. And sooner or later some of my customers will need the new functionality offered and then I'm forced to update.

I'm sure there are pro's here that have better advise, but with this plan I am keeping my head above the water, both regarding security, availability and keeping up to date.

PS Really isn't fair blaming Atomic. You have definitely actively chosen to update to PHP 5 by enabling the Atomic repos. If you just want ASL, only enable the ASL repos...

[scott]

Get vmware/kvm/parallels/whatever an set up test environment. I cannot recommend this step enough. Your ASL license supports not one, but two extra uses just for this kind of development and testing. Take advantage of it

[webfeatus]

I feel that a smart and simple, immediate solution to my current dilema is that I list my current repos here and maybe someone may be kind enough to advise.

I know that the yum update reads a configuration file that contains the repos (and I know that I have looked at it before) but can someone please tell me what the file is and where it is?

Then I will post the contents here and see what happens.

[biggles]

Out of the top of my head, the files in /etc/yum.conf.d/

[Imaging]

I feel that a smart and simple, immediate solution to my current dilema is that I list my current repos here and maybe someone may be kind enough to advise.

I know that the yum update reads a configuration file that contains the repos (and I know that I have looked at it before) but can someone please tell me what the file is and where it is?

Then I will post the contents here and see what happens.

Your repo files are likely in:

/etc/yum.repos.d/

[biggles]

Your repo files are likely in:

/etc/yum.repos.d/

Thanks! I know my head wasn't in it's right mind!

[webfeatus]

PHP Version: 5.2.17
MYSQL Version: 5.1.55-log
Webserver Version: Apache
Linux Distro: CentOS release 5.5 (Final)
Kernel: 2.6.32.28-1.art.x86_64
Platform: x86_64
Plesk 9.5.2
Located in Germany.

/etc/yum.repos.d
-rw-r--r-- 1 root root 442 Jul 16 2010 asl.repo
-rw-r--r-- 1 root root 1337 Aug 19 2010 atomic.repo
-rw-r--r-- 1 root root 2245 Apr 25 2010 CentOS-Base.repo
-rw-r--r-- 1 root root 2347 Mar 31 2009 CentOS-Base.repo.old
-rw-r--r-- 1 root root 626 Apr 25 2010 CentOS-Media.repo
-rw-r--r-- 1 root root 227 Mar 31 2009 intergenia.repo
-rw-r--r-- 1 root root 250 Sep 22 06:02 plesk.repo

[webfeatus]

Anyone want to suggest anything regarding this list of repos?

[webfeatus]

Oh well, I guess no assistence will be forthcominmg regarding this.
This is the only option for me i.e.help with sensible repos regarding my lack of expertise with yum upgrade.
The testing server environment option is simply beyond my experience.

If this lack of input from the experienced forum members is not forthcoming, I must return to my bottom line that the ASL Program is simply beyongd my capabilities. A deflating personal realisation after the 3 years of effort that I have invested so far. Exasperated, I state that I have concientiouisly tried my best and there has been NO lack of endeavour on my part!

Don't forget that if you want to focus your development endeavours to include the "layman" customer - this will be a basic focus of paramount importanace. Note your recent cPanel endeavours combined with effective cross-marketing features. Or is your program only for the wise and experienced?

Is there a recommended set repos for yum update that safeguard and minimise the issues outlined in this ticket?

[biggles]

Only using asl repo, not atomic repo gets you what you want... (And of course, the standard Centos repos).

I really don't understand why a test environment is beyond you capabilities. Setting one up isn't harder then setting up your current environment. You can even do it on your local desktop, just firing it up and testing out updates before installing them, when you need it.