[horde] Proxy errors to downstream Horde server

Simon Wilson simon at simonandkate.net
Mon Jun 10 21:31:11 UTC 2013


>>>> Citeren Simon Wilson <simon at simonandkate.net>:
>>>>
>>>>> A quick config change to the proxypass timeout with  
>>>>> "connectiontimeout 300 timeout 300" makes no discernable  
>>>>> difference, so even with 5 minutes timeout I am still getting  
>>>>> just as many of the 502s.
>>>>>
>>>>> How long should the ping process take? and how do I identify  
>>>>> when it starts finished in the device log?
>>>>
>>>> It can take up to $conf[activesync][ping][heartbeatmax] seconds  
>>>> (which can be 59 minutes or 3540 seconds max). Usually, it will  
>>>> be lower though (depending on the client), with a minimum of  
>>>> $conf[activesync][ping][heartbeatmin] seconds.
>>>>
>>>>> From what I can see a pid is held from the auth request at the  
>>>>> start of a PING through to that pid disappearing from the logs  
>>>>> for between 2 and 4 minutes.
>>>>
>>>> That shouldn't happen.
>>>>
>>>>> Or is there something else that it continues to do that needs to  
>>>>> be kept alive for the PING request?
>>>>
>>>> Yes. It keeps monitoring the folders every  
>>>> $conf[activesync][ping][waitinterval] seconds for changes and if  
>>>> it finds any, will report that back to the client. The client in  
>>>> turn will run a SYNC then. After that (or in the absence of  
>>>> changes) the device will initiate a new PING and all starts over  
>>>> again. So generally, for any ActiveSync device that is active,  
>>>> you'll see a process running on your server with a connection  
>>>> open to your IMAP server.
>>>
>>>
>>> Thanks (again) :) Arjen.
>>>
>>> So my max is set to 2700 - should I have connectiontimeout /  
>>> timeout on the proxy set to that?
>>
>> I would say, at *least* that. You definitly don't want your proxy  
>> to take the initiative to terminate a connection, before your  
>> client does.
>>
>>> And any impact on resources on the proxy server, holding processes  
>>> for that long?
>>
>> That largely depends on the number of connections your proxy can  
>> handle. It will need to keep two connections open per client (one  
>> to the client, one to the server). If that is going to be a  
>> problem, largely depends on the size of your userbase (the number  
>> of simultaneous connections it should proxy) and whatever other  
>> activities are running on that box. Unless you have thousands of  
>> users, I wouldn't worry about it.
>
>
> Would be great if one of you two could add a section to the wiki  
> with this type of configuration information?  
> http://wiki.horde.org/ActiveSync
>
>
> -- 
> mike
>

I'll do so later today.

Happy to say that overnight with the proxy set to a 3000 timeout there  
have been NO proxy errors :-D

So it looks like with the help of this list I have cracked these  
errors. I am seeing slower device log accumulation as a result, so  
hoping that it will provide a small device battery life improvement as  
well.

Thanks Arjen and Mike.

Simon.



--
Simon Wilson
M: 0400 12 11 16
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-keys
Size: 1339 bytes
Desc: PGP Public Key
URL: <http://lists.horde.org/archives/horde/attachments/20130610/6d80703c/attachment-0002.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: PGP Digital Signature
URL: <http://lists.horde.org/archives/horde/attachments/20130610/6d80703c/attachment-0003.bin>


More information about the horde mailing list