Shidb / Apache Segmentation Fault

[Cantor, Scott]

On 11/16/14, 8:26 AM, "Aleix Dorca Josa" <adorca at uda.ad> wrote:
>
>We have two servers using a load sharing scheme. These use Debian Wheezy, 
>Apache, Moodle, GlusterFS to sync the data folder and the Shibd module to 
>handle the authentication.

Aside from everything about that being unsupported by me, any kind of 
distributed file sharing of any sort is a complete non-starter so it would 
have to reproduced without that complication.

I'm not aware that Moodle uses the SP session at all after login, so it 
doesn't seem like any clustering of the SP is needed at all. Maybe I'm 
mistaken about that.

>The problem is: every Sunday at 7:00 (more or less, just after the whole 
>cron stuff) Apache starts logging segmentation faults (11) whenever a 
>user tries to log in.
>
>I know you'll say that I have some weird cron job on Sundays, but no, 
>nothing at all. Maybe a memory problem? Seems obvious, but the system has 
>plenty to spare. I could even add more if necessary.

I would guess that the cron jobs are destroying needed files somewhere.

>The problem is only solved if I reboot the machine. Some times TWO 
>reboots are necessary and I can't find anything at all on the logs that 
>points me to solving the problem.
>Restarting the services Apache, Shibd or GlusterFS has no effect at all. 
>This strikes me as odd too.

It means the problem is with your system, I think, or how you've wired all 
this up. Whatever it is, it's below the layer of the SP software itself. 
Without a stack trace identifying the area of the fault, there's nothing 
else to go on.

>Previously I have found this:

That means nothing other than Apache closed down.

-- Scott