IPCCommTimeout

Submitted by helpmin on Fri, 07/13/2012 - 13:33

I am not sure whether i remember correctly, but didn't you add a feature (before 3.92) that would also change the IPCCommTimeout when you change the php timeout limit?

If yes, then there could be a bug, because I still have to manually change the IPCCommTimeout value.

Status: 
Active

Comments

Submitted by JamieCameron on Fri, 07/13/2012 - 20:28

Yes, Virtualmin should set IPCCommTimeout to match the PHP timeout automatically.

Is this not happening for you in some or all of your virtual hosts?

If so, try going to Limits and Validation -> Validate Virtual Servers, and running a full validation of the domains you are seeing problems with. I'd be interested to know if that reports any errors.

Submitted by helpmin on Sat, 07/14/2012 - 02:40

correct, this is not happening, when I change the Maximum execution time

All features validate ok (except for the ssl warning because of SNI)

Submitted by JamieCameron on Sat, 07/14/2012 - 13:03

By any chance is it happening for the non-SSL virtualhost, but not for the SSL virtualhost?

Or does it fail for both of them?

Submitted by helpmin on Tue, 08/07/2012 - 16:42

Were you able to reproduce this on Ubuntu?

:-)

Submitted by JamieCameron on Tue, 08/07/2012 - 16:55

No, for me it works perfectly ..

Submitted by helpmin on Tue, 08/07/2012 - 16:58

Is there anything I could debug? (I am not a perl expert, but if you tell me where to look I might be able to find something).

I also suspect that you only checked the pro version, right? what happens if you try GPL?

Submitted by JamieCameron on Tue, 08/07/2012 - 19:25

The code is the same in the GPL and pro versions, at least for the parts of Virtualmin that handle PHP.

The only thing I can think of to debug this further would be if I could login to your system myself and see what is happening inside Virtualmin. Let me know if that is possible..

Submitted by helpmin on Wed, 08/08/2012 - 04:06

Unfortunately only on my laptop. I am planning to move my server from centos to ubuntu. So I am still testing locally :-)

Submitted by JamieCameron on Wed, 08/08/2012 - 15:38

Oh well .. I'm not sure what else can be done to debug this then.

By the way, I assume the domain is set to fcgi execution mode for PHP, at Server Configuration -> Website Options?

Submitted by helpmin on Sat, 08/11/2012 - 12:54

ok, understand i will get back to you on this.

Submitted by helpmin on Fri, 03/07/2014 - 23:16

Hi :-)

I have a server now, where you could test this.

Debian 7.4 with VM 4.06 gpl. Everything installed from scratch

Where should I send the password?

Submitted by JamieCameron on Sat, 03/08/2014 - 17:19

Thanks, got it. And I did a test in which I adjusted the max PHP execution time (at Server Configuration -> Website Options), and the IPCCommTimeout was increased to match correctly.

Submitted by helpmin on Sat, 03/08/2014 - 17:25

Ah, ok. Now I understand, I have always changed the time with menu:

Services - PHP Configuration - Resource Limits

That is probably the issue?

Submitted by JamieCameron on Sat, 03/08/2014 - 23:53

Yes, that explains it - that setting effects PHP only.

Submitted by helpmin on Sun, 03/09/2014 - 17:09

Ok, well, maybe it would make sense to update IPCCommTimeout from there as well?

The owner of the virtualserver typically doesn't have access to website options, but is allowed to change the timeout via PHP configurationand then configure website + edit directives & configure website for ssl + edit directives. (assuming the owner knows the dependency in the first place).

Submitted by JamieCameron on Sun, 03/09/2014 - 18:57

You can grant the domain owner permissions to use the Website Options page though, on the Edit Owner Limits page.

Submitted by helpmin on Sun, 03/09/2014 - 19:07

That is true, but then the user would have access to all the other features of that website options page, right? (maybe not a good idea, probably for the same reason it is not enabled by default?)

Submitted by JamieCameron on Sun, 03/09/2014 - 22:54

True, but all of those options are safe - the domain owner can only effect their own domains.