OK, using my colleagues F19 PC, I was able to get an strace of remote-viewer.
grepping for setsockopt on the strace output shows
---
30548 setsockopt(10, SOL_SOCKET, SO_ATTACH_FILTER, "\10\0\0\0\0\0\0\0\20\204\26\363\377\177\0\0", 16) = 0
30548 setsockopt(10, SOL_SOCKET, SO_PASSCRED, [1], 4) = 0
30548 setsockopt(18, SOL_SOCKET, SO_ATTACH_FILTER, "\10\0\0\0\0\0\0\0\260\202\26\363\377\177\0\0", 16) = 0
30548 setsockopt(18, SOL_SOCKET, SO_PASSCRED, [1], 4) = 0
30548 setsockopt(9, SOL_SOCKET, SO_KEEPALIVE, [1], 4) = 0
30548 setsockopt(9, SOL_TCP, TCP_NODELAY, [1], 4) = 0
30548 setsockopt(9, SOL_SOCKET, SO_KEEPALIVE, [1], 4) = 0
30548 setsockopt(9, SOL_TCP, TCP_NODELAY, [1], 4) = 0
30548 setsockopt(22, SOL_SOCKET, SO_KEEPALIVE, [1], 4) = 0
30548 setsockopt(22, SOL_TCP, TCP_NODELAY, [1], 4) = 0
30548 setsockopt(22, SOL_SOCKET, SO_KEEPALIVE, [1], 4) = 0
30548 setsockopt(22, SOL_TCP, TCP_NODELAY, [1], 4) = 0
30548 setsockopt(25, SOL_SOCKET, SO_KEEPALIVE, [1], 4 <unfinished ...>
30548 <... setsockopt resumed> ) = 0
30548 setsockopt(25, SOL_TCP, TCP_NODELAY, [1], 4 <unfinished ...>
30548 <... setsockopt resumed> ) = 0
30548 setsockopt(25, SOL_SOCKET, SO_KEEPALIVE, [1], 4 <unfinished ...>
30548 <... setsockopt resumed> ) = 0
30548 setsockopt(25, SOL_TCP, TCP_NODELAY, [1], 4 <unfinished ...>
30548 <... setsockopt resumed> ) = 0
30548 setsockopt(24, SOL_SOCKET, SO_KEEPALIVE, [1], 4 <unfinished ...>
30548 <... setsockopt resumed> ) = 0
30548 setsockopt(24, SOL_TCP, TCP_NODELAY, [1], 4 <unfinished ...>
30548 <... setsockopt resumed> ) = 0
30548 setsockopt(25, SOL_SOCKET, SO_KEEPALIVE, [1], 4) = 0
30548 setsockopt(25, SOL_TCP, TCP_NODELAY, [1], 4) = 0
30548 setsockopt(30, SOL_SOCKET, SO_ATTACH_FILTER, "\10\0\0\0\0\0\0\0\300~\26\363\377\177\0\0", 16) = 0
30548 setsockopt(30, SOL_SOCKET, SO_PASSCRED, [1], 4) = 0
30548 setsockopt(27, SOL_SOCKET, SO_ATTACH_FILTER, "\10\0\0\0\0\0\0\0\340z\26\363\377\177\0\0", 16) = 0
30548 setsockopt(27, SOL_SOCKET, SO_PASSCRED, [1], 4) = 0
---
---
30548 setsockopt(10, SOL_SOCKET, SO_ATTACH_FILTER, "\10\0\0\0\0\0\0\0\20\204\26\363\377\177\0\0", 16) = 0
30548 setsockopt(10, SOL_SOCKET, SO_PASSCRED, [1], 4) = 0
30548 setsockopt(18, SOL_SOCKET, SO_ATTACH_FILTER, "\10\0\0\0\0\0\0\0\260\202\26\363\377\177\0\0", 16) = 0
30548 setsockopt(18, SOL_SOCKET, SO_PASSCRED, [1], 4) = 0
30548 setsockopt(9, SOL_SOCKET, SO_KEEPALIVE, [1], 4) = 0
30548 setsockopt(9, SOL_TCP, TCP_NODELAY, [1], 4) = 0
30548 setsockopt(9, SOL_SOCKET, SO_KEEPALIVE, [1], 4) = 0
30548 setsockopt(9, SOL_TCP, TCP_NODELAY, [1], 4) = 0
30548 setsockopt(22, SOL_SOCKET, SO_KEEPALIVE, [1], 4) = 0
30548 setsockopt(22, SOL_TCP, TCP_NODELAY, [1], 4) = 0
30548 setsockopt(22, SOL_SOCKET, SO_KEEPALIVE, [1], 4) = 0
30548 setsockopt(22, SOL_TCP, TCP_NODELAY, [1], 4) = 0
30548 setsockopt(25, SOL_SOCKET, SO_KEEPALIVE, [1], 4 <unfinished ...>
30548 <... setsockopt resumed> ) = 0
30548 setsockopt(25, SOL_TCP, TCP_NODELAY, [1], 4 <unfinished ...>
30548 <... setsockopt resumed> ) = 0
30548 setsockopt(25, SOL_SOCKET, SO_KEEPALIVE, [1], 4 <unfinished ...>
30548 <... setsockopt resumed> ) = 0
30548 setsockopt(25, SOL_TCP, TCP_NODELAY, [1], 4 <unfinished ...>
30548 <... setsockopt resumed> ) = 0
30548 setsockopt(24, SOL_SOCKET, SO_KEEPALIVE, [1], 4 <unfinished ...>
30548 <... setsockopt resumed> ) = 0
30548 setsockopt(24, SOL_TCP, TCP_NODELAY, [1], 4 <unfinished ...>
30548 <... setsockopt resumed> ) = 0
30548 setsockopt(25, SOL_SOCKET, SO_KEEPALIVE, [1], 4) = 0
30548 setsockopt(25, SOL_TCP, TCP_NODELAY, [1], 4) = 0
30548 setsockopt(30, SOL_SOCKET, SO_ATTACH_FILTER, "\10\0\0\0\0\0\0\0\300~\26\363\377\177\0\0", 16) = 0
30548 setsockopt(30, SOL_SOCKET, SO_PASSCRED, [1], 4) = 0
30548 setsockopt(27, SOL_SOCKET, SO_ATTACH_FILTER, "\10\0\0\0\0\0\0\0\340z\26\363\377\177\0\0", 16) = 0
30548 setsockopt(27, SOL_SOCKET, SO_PASSCRED, [1], 4) = 0
---
So remote-viewer is sending keep alives...
Back to wondering why, after 30 minutes of inactivity, the SPICE sessions become unusable in our environment.
CC
CC
On Wed, Sep 18, 2013 at 8:21 PM, Colin Coe <colin.coe@xxxxxxxxx> wrote:
I'll wait til Friday (not in the office tomorrow and working from home ATM) and try from my colleagues PC (F19) as that has virt-viewer 0.5.6Thanks--
On Wed, Sep 18, 2013 at 8:11 PM, Christophe Fergeau <cfergeau@xxxxxxxxxx> wrote:On Wed, Sep 18, 2013 at 08:01:10PM +0800, Colin Coe wrote:Ah hmm this is too old to be able to open the .vv file, support was added
> Yep, tried that and get error "Cannot determine the connection type from
> URI"
>
> remote-viewer -V
> remote-viewer version 0.5.4
in 0.5.5. I'd say you are missing some certificates for the SSL connection.
You can get the CA certificate from the IP of your RHEV/oVirt instance,
wget https://ovirt.example.com/ca.crt and then pass this to remote-viewer
using --spice-ca-file=ca.crt. You should also check if the .vv file defines
a host subject, and if so, pass it with --spice-host-subject.
Christophe
RHCE#805007969328369
--
RHCE#805007969328369
_______________________________________________ virt-tools-list mailing list virt-tools-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/virt-tools-list