Re: [lxc-users] lxd-client: frequent "Unable to connect to"

2016-01-26 Thread Tomasz Chmielewski

Entropy seems fine.

It looks as if communication in the bridge stops working sometimes, 
probably when there is no traffic in it for longer periods of time.



Tomasz Chmielewski
http://wpkg.org

On 2016-01-26 20:57, Jäkel wrote:

Dear Tomasz,

What's the output of

watch -n 1  cat /proc/sys/kernel/random/entropy_avail

around blocking or hanging times?


-Original Message-
From: lxc-users [mailto:lxc-users-boun...@lists.linuxcontainers.org] 
On Behalf Of Tomasz Chmielewski

Sent: Tuesday, January 26, 2016 10:58 AM
To: LXC users mailing-list
Subject: [lxc-users] lxd-client: frequent "Unable to connect to"

I'm using lxd-client in a lxd container.

Unfortunately, very frequently I'm getting "Unable to connect to" 
(after

several seconds of "hanging"), for example:

# lxc list
error: Get https://10.0.3.1:8443/1.0/containers?recursion=1: Unable to
connect to: 10.0.3.1:8443

I've checked with tcpdump on the host, and the packets are going both
ways.

At the same time when it happens (lxc list hangs, or any lxc commands
hang), "curl -k -v https://10.0.3.1:8443"; just works - i.e. returns:

{"type":"sync","status":"Success","status_code":200,"metadata":["/1.0"],"operation":""}



Do you have any ideas to debug this?

The same executed directly on the host always work fine.

___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users


___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users

Re: [lxc-users] lxd-client: frequent "Unable to connect to"

2016-01-26 Thread Jäkel , Guido
Dear Tomasz,

What's the output of

watch -n 1  cat /proc/sys/kernel/random/entropy_avail

around blocking or hanging times?

>-Original Message-
>From: lxc-users [mailto:lxc-users-boun...@lists.linuxcontainers.org] On Behalf 
>Of Tomasz Chmielewski
>Sent: Tuesday, January 26, 2016 10:58 AM
>To: LXC users mailing-list
>Subject: [lxc-users] lxd-client: frequent "Unable to connect to"
>
>I'm using lxd-client in a lxd container.
>
>Unfortunately, very frequently I'm getting "Unable to connect to" (after
>several seconds of "hanging"), for example:
>
># lxc list
>error: Get https://10.0.3.1:8443/1.0/containers?recursion=1: Unable to
>connect to: 10.0.3.1:8443
>
>I've checked with tcpdump on the host, and the packets are going both
>ways.
>
>At the same time when it happens (lxc list hangs, or any lxc commands
>hang), "curl -k -v https://10.0.3.1:8443"; just works - i.e. returns:
>
>{"type":"sync","status":"Success","status_code":200,"metadata":["/1.0"],"operation":""}
>
>
>
>Do you have any ideas to debug this?
>
>The same executed directly on the host always work fine.
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users

[lxc-users] lxd-client: frequent "Unable to connect to"

2016-01-26 Thread Tomasz Chmielewski

I'm using lxd-client in a lxd container.

Unfortunately, very frequently I'm getting "Unable to connect to" (after 
several seconds of "hanging"), for example:


# lxc list
error: Get https://10.0.3.1:8443/1.0/containers?recursion=1: Unable to 
connect to: 10.0.3.1:8443


I've checked with tcpdump on the host, and the packets are going both 
ways.


At the same time when it happens (lxc list hangs, or any lxc commands 
hang), "curl -k -v https://10.0.3.1:8443"; just works - i.e. returns:


{"type":"sync","status":"Success","status_code":200,"metadata":["/1.0"],"operation":""}



Do you have any ideas to debug this?

The same executed directly on the host always work fine.


Tomasz Chmielewski
http://wpkg.org
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users