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.



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.

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

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

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?

Were you able to reproduce this on Ubuntu?


No, for me it works perfectly ..

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?

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..

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

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?

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

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?

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.

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

Services - PHP Configuration - Resource Limits

That is probably the issue?

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

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).

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

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?)

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