[support] I think, problem solved?
Roger
arelem at bigpond.com
Tue Feb 26 06:04:38 UTC 2013
I hope you can remember, I'd love to know more.
There's a subset to that issue in that apache opens new instances of
https, I don't know the correct term but after each failure it opens yet
another.
To overcome that I have " sudo service httpd stop && sudo service httpd
start" so that it refreshes from new. This reduces problems somewhat.
ps aux | grep httpd
root 4940 0.0 1.0 540912 20968 ? Ss 13:33 0:00
/usr/sbin/httpd -DFOREGROUND
apache 4942 0.1 3.4 555524 71444 ? S 13:33 0:12
/usr/sbin/httpd -DFOREGROUND
apache 4945 0.0 3.2 562280 67500 ? S 13:33 0:04
/usr/sbin/httpd -DFOREGROUND
apache 4946 0.0 2.6 547160 53484 ? S 13:33 0:05
/usr/sbin/httpd -DFOREGROUND
apache 5086 0.0 2.6 548720 54332 ? S 13:34 0:05
/usr/sbin/httpd -DFOREGROUND
apache 5101 0.1 2.6 547472 55052 ? S 13:34 0:14
/usr/sbin/httpd -DFOREGROUND
apache 5137 0.0 2.9 552872 60740 ? S 13:36 0:04
/usr/sbin/httpd -DFOREGROUND
apache 5138 0.0 2.9 554448 60776 ? S 13:36 0:07
/usr/sbin/httpd -DFOREGROUND
apache 5232 0.0 2.5 547836 52560 ? S 13:42 0:03
/usr/sbin/httpd -DFOREGROUND
apache 5324 0.0 2.6 547384 54244 ? S 13:50 0:06
/usr/sbin/httpd -DFOREGROUND
apache 5450 0.0 2.4 548136 50416 ? S 13:59 0:05
/usr/sbin/httpd -DFOREGROUND
I can have 20+ of these.
Thanks Don
Cheers
Roger
> Interesting. I had to increase that on a problem a while back. Now if
> i could remember what was causing it.
> I also had to decrease the connection timeout, it was using up all the
> connections.
>
> Guess I'd better add it to my debug checklist. thanks.
> -Don-
>
> On 2/25/2013 9:13 PM, Roger wrote:
>> Drupal 7 Content Types - Edit showing WSOD
>> After a little testing this morning the problem might, might be solved,
>> at least temporarily.
>> Today I was getting the Error 324 (net::ERR_EMPTY_RESPONSE): The server
>> closed the connection without sending any data.
>> Turns out it may not be a browser, php.ini setting nor a Drupal setting
>> but my.cnf setting.
>>
>> I changed max_allowed_packet=32M to max_allowed_packet=64M and now I
>> can edit all content types, no error messages, all good so far.
>> I have no idea why but it works.
>> I need to test this in the other installations for a few days to be more
>> sure.
>>
>> I still get the: Fatal error: Allowed memory size of 67108864 bytes
>> exhausted (tried to allocate 2458767 bytes) in
>> /var/www/html/myfile/modules/user/user.admin.inc on line 787 now for
>> permissions. But this seems to be a bug in php 5.
>>
>> Cheers
>> Roger
>
>
More information about the support
mailing list