On 08/02/2012 05:35 PM, Lars Kellogg-Stedman wrote:
> On Thu, Aug 02, 2012 at 12:33:13PM -0400, Lars Kellogg-Stedman wrote:
>>> Looks like a typo.
>>> Could you try this.
>>
>> FYI: The same typo appears to exist in notify_qpid.py.
>
> Err, that is, glance/notifier/notify_qpid.py, in case it wasn'
On Thu, Aug 02, 2012 at 12:33:13PM -0400, Lars Kellogg-Stedman wrote:
> > Looks like a typo.
> > Could you try this.
>
> FYI: The same typo appears to exist in notify_qpid.py.
Err, that is, glance/notifier/notify_qpid.py, in case it wasn't
obvious...
--
Lars Kellogg-Stedman|
Senior Tech
Registering service heartbeat into the subsystem might alleviate the need
to restart certain items . This subsystem is the one that monitors what
services are up and running .
Ravi.
On Sun, Jul 29, 2012 at 9:58 PM, Lars Kellogg-Stedman wrote:
> On Sun, Jul 29, 2012 at 09:49:25PM -0400, Lars Ke
On Sun, Jul 29, 2012 at 09:49:25PM -0400, Lars Kellogg-Stedman wrote:
> And indeed, if I run a packet trace on this connection, I can verify
> that packets are only showing up at five-minute intervals.
Horrors! It may be that nova-volume didn't get restarted when I
restarted everything else. Aft
On Mon, Jul 30, 2012 at 01:41:20AM +0100, Pádraig Brady wrote:
> Perhaps there is another issue with the scheduling of this?
That's likely. While I verified that the patch successfully fixed our
connection timeout issue, I didn't look closely to see exactly where
the behavior changed...and the con
On 07/29/2012 07:14 PM, Lars Kellogg-Stedman wrote:
>> Looks like a typo.
>> Could you try this.
>
> That seems better...although while the documentation says that
> qpid_heartbeat is "Seconds between heartbeat messages" [1], observed
> behavior suggests that it is actually *minutes* between messa
> Looks like a typo.
> Could you try this.
That seems better...although while the documentation says that
qpid_heartbeat is "Seconds between heartbeat messages" [1], observed
behavior suggests that it is actually *minutes* between messages.
[1]:
http://docs.openstack.org/essex/openstack-compute/
On 07/29/2012 03:24 AM, Lars Kellogg-Stedman wrote:
> Our environment has connection-tracking firewalls that drop idle
> connections after an hour. There is a connection between nova-compute
> and our qpidd server that appears to be idle for long periods of time.
>
> When the firewall drops this
Our environment has connection-tracking firewalls that drop idle
connections after an hour. There is a connection between nova-compute
and our qpidd server that appears to be idle for long periods of time.
When the firewall drops this connection, the participating hosts are
unaware of that fact a
9 matches
Mail list logo
