----- Original Message -----
From: "xrx" <xrx-ml(a)xrx.me>
Sent: Sunday, September 2, 2012 7:59:54 AM
Subject: Re: [Users] Installing Host - action is taking longer than allowed
On 09/01/12 01:09, Alon Bar-Lev wrote:
> ----- Original Message -----
>> From: "Mohsen Saeedi"<mohsen.saeedi(a)gmail.com>
>> To: users(a)ovirt.org
>> Sent: Friday, August 31, 2012 11:57:59 PM
>> Subject: [Users] Installing Host - action is taking longer than
>> allowed by configuration
>> The required action is taking longer than allowed by
>> I know the reason for it. i have very slow connection. I think
>> clean yum metadata and try to get metadata again. but my internet
>> connection is very slow (about 64Kb/s) and takes a lot of time
>> finish. how can i increase the allowed time by configuration or
>> change on postgresql database.?
> You can set the SSHInactivityTimoutSeconds within vdc_options
> # psql -d engine -U postgres -c "update vdc_options set
> option_value = 600 where option_name =
Is having a hard-coded timeout really a good idea? I have had the
problem; surely there must be a better way of implementing this than
timeout (which is essentially guessing how fast everyone's internet
connection/machine would be)?
Meanwhile perhaps the timeout should be changed to a very large
and maybe even a mention of where the log is kept
(/tmp/vds_bootstrap...) so the user can see the progress.
You are correct.
While rewriting the SSH implementation in master, I added two separate timeouts: soft
timeout, hard timeout.
- Soft timeout is a timeout since last communication activity.
- Hard timeout is a timeout of the complete process.
Soft timeout is not currently used, but in near future I will also make use of it. It will
enable to extend the hard timeout to much larger value.