Thread: Apache issues with Glype

I found it, this is what they said.

08-May-2009 07:18

WARNING for Debian users. Just to drive you completely crazy Debian does its own form of session management and will completely ignore all alterations to the values who do within your PHP script.

Debian sets up a <crontab /etc/cron.d/php5> which deletes all files, including those in subdirectories, which exceed the gc_maxlifetime specified in the <php.ini> file only.

That is, on Debian (and likely variants like Ubuntu) modifying the session expiration settings (like gc_maxlifetime) does *NOTHING*. You *HAVE* to modify the global <php.ini>. Not even a <.htaccess> file will help you.

PHP: Session Functions - Manual

Ah thanks for looking that up - but that doesn't explain why it would hang while setting the lock on the session file. This just talks about how the sessions are cleaned up...

This is interesting no one else is having problems like this.

Originally Posted by nux

This is interesting no one else is having problems like this.

Maby its because everyone else is using CentOS. :0

This happened to me on the Debian system and also the Gentoo system. The info you posted above doesn't describe the issue I'm having with sessions.

I noticed your Glype session is named "s=" on your site unblockspace.net (from your sig), in Glype its actually "t=" at least from the version that the original owner had set out, downloading the copy of glype from the glype website, it is in fact now named "s" for some reason...

I think the new owner has been modifying the script.. Who knows what else has been changed. I would be suspicious if your problem is being caused by something the new owner did to it.

Yea, I noticed the default theme changed for the older 0.x.x.x version. wtf

The default and basic or minimal or whatever it was called themes are gone and have been replaced with a fruity "glype" theme.

You mean the theme with the red and green circular logo? That was always like that, its not something new. Only the 1.x versions had the default and minimal theme folders.

I've setup a testing environment on the following operating systems and have been able to reproduce the issue:
Centos 5.3
Debian 4
Debian 5

And I am now setting up FreeBSD to try it on. I'm beginning to think this isn't just an issue I'm having.

Does anyone else monitor server-status on their servers, and/or apache children count?

I've done some more testing... with PHProxy I was getting 7 requests per second to apache with an average of about 50 requests being processed. Than ran fine for over an hour.

Then I added in Glype. I was still getting 7 requests per second but after an hour there were over 300 requests being processed. I also noticed in my Apache log there are a few undefined variables in Glype that keep getting recorded.

I still haven't been able to find a solution yet. I might do some testing on a local server and see if I can fix Glype.

Originally Posted by Nathan

I've done some more testing... with PHProxy I was getting 7 requests per second to apache with an average of about 50 requests being processed. Than ran fine for over an hour.

Then I added in Glype. I was still getting 7 requests per second but after an hour there were over 300 requests being processed. I also noticed in my Apache log there are a few undefined variables in Glype that keep getting recorded.

I still haven't been able to find a solution yet. I might do some testing on a local server and see if I can fix Glype.

What were the errors?


Nux have you tried putting

PHP Code:

exit; 


At the end of Browse.php? That might stop run away processes.