I had IPCCommTimeout declared in the Virtualhost and in the global
config. I was making changes to the global config and the Virtualhost
config was over riding it. Wish I had found it sooner ..
Thanks for the help.
On Wed, Nov 16, 2011 at 3:26 PM, Jeff Dyke wrote:
> I guess my question is mor
I did the same test again with the settings (mod_fcgid and php) as
given , then I reset the setting back to the defaults and there was
not change. This leaves the issue with mysql as it's the only resource
that is called by phpwiki.
I have noted that php-cgi spikes upto 90% cpu utilization for the
I guess my question is more about what that page is doing. Connecting
to a DB, a cache, LDAP and are those failing to return a valid
connection within the page/server connection timeout time. If you
turn down all of your timeouts does it occur in much shorter time then
currently?
On Tue, Nov 15
Hi Jeff.
I have gone through the php.ini and I have set all the values
insanely high. I have used phpinfo(); to check that it's reading the
correct file and it is.
phpinfo output:
PHP Version 5.3.3-1ubuntu9.6
System Linux nzhmlapp04 2.6.35-30-generic #60-Ubuntu SMP Mon Sep 19
20:42:44 UTC 2011
31 seconds is likely not a coincidence that its a default timeout to a
lot of things, core PHP included.
I know every little about PHPWiki, but suspect its trying to connect
to something and the default timeout it giving up after 30 seconds.
This is an interesting setting:
IPCCommTimeout 31
what
Hi.
I'm running Apache/2.2.16 (Ubuntu) , libapache2-mod-fcgid
1:2.3.5-2ubuntu0.1, php5-cgi 5.3.3-1ubuntu9.6. on Ubuntu 10.10 LTS,
in a Virtualmin LAMP stack. Each Virtualhost runs suexec, thus the
need for mod-fcgid so that each site is running under its own user
account.
I have a clean install o
