xpra icon
Bug tracker and wiki

Opened 7 years ago

Closed 7 years ago

#124 closed defect (needinfo)

no new xpra sessions via winswitch

Reported by: pmarek Owned by: pmarek
Priority: blocker Milestone: 0.3
Component: server Version: 0.1.0
Keywords: Cc:

Description

On the server: xpra connection to xvfb seems to try IPv6, IPv4 and unix sockets...

while it gets an answer for IPv4, that is not sufficient?

This here is repeated several times:

16011 14:05:47.933487 socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 3
16011 14:05:47.933556 connect(3, {sa_family=AF_INET, sin_port=htons(6067), sin_addr=inet_addr("127.0.0.1")}, 16) = 0
16011 14:05:47.933631 getsockname(3, {sa_family=AF_INET, sin_port=htons(45529), sin_addr=inet_addr("127.0.0.1")}, [16]) = 0
16011 14:05:47.933702 close(3)          = 0
16011 14:05:47.933770 socket(PF_INET6, SOCK_DGRAM, IPPROTO_IP) = 3
16011 14:05:47.933839 connect(3, {sa_family=AF_INET6, sin6_port=htons(6067), inet_pton(AF_INET6, "::1", &sin6_addr), sin6_flowinfo=0, sin6_scope_id=0}, 28) = 0
16011 14:05:47.933918 getsockname(3, {sa_family=AF_INET6, sin6_port=htons(39133), inet_pton(AF_INET6, "::1", &sin6_addr), sin6_flowinfo=0, sin6_scope_id=0}, [28]) = 0
16011 14:05:47.933989 close(3)          = 0
16011 14:05:47.934061 socket(PF_INET6, SOCK_STREAM|SOCK_CLOEXEC, IPPROTO_TCP) = 3
16011 14:05:47.934131 setsockopt(3, SOL_TCP, TCP_NODELAY, [1], 4) = 0
16011 14:05:47.934200 setsockopt(3, SOL_SOCKET, SO_KEEPALIVE, [1], 4) = 0
16011 14:05:47.934267 connect(3, {sa_family=AF_INET6, sin6_port=htons(6067), inet_pton(AF_INET6, "::1", &sin6_addr), sin6_flowinfo=0, sin6_scope_id=0}, 28) = -1 ECONNREFUSED (Connec
16011 14:05:47.934368 close(3)          = 0
16011 14:05:47.934439 socket(PF_INET, SOCK_STREAM|SOCK_CLOEXEC, IPPROTO_TCP) = 3
16011 14:05:47.934509 setsockopt(3, SOL_TCP, TCP_NODELAY, [1], 4) = 0
16011 14:05:47.934577 setsockopt(3, SOL_SOCKET, SO_KEEPALIVE, [1], 4) = 0
16011 14:05:47.934644 connect(3, {sa_family=AF_INET, sin_port=htons(6067), sin_addr=inet_addr("127.0.0.1")}, 16) = -1 ECONNREFUSED (Connection refused)
16011 14:05:47.934758 close(3)          = 0
16011 14:05:47.934842 socket(PF_FILE, SOCK_STREAM|SOCK_CLOEXEC, 0) = 3
16011 14:05:47.934911 connect(3, {sa_family=AF_FILE, path=@"/tmp/.X11-unix/X67"}, 21) = -1 ECONNREFUSED (Connection refused)

Change History (3)

comment:1 Changed 7 years ago by Antoine Martin

Status: newaccepted

Do you get the same thing when using Xdummy, does the X11 server log anywhere why it is rejecting those connections?
It looks very suspicious, especially:

16011 14:05:47.934911 connect(3, {sa_family=AF_FILE, path=@"/tmp/.X11-unix/X67"}, 21) = -1 ECONNREFUSED (Connection refused)

Is this socket owned by the right user, umask, permissions or something?

Note, as this may well be relevant (just no sure how), that the default in xpra was changed to add -nolisten tcp in v0.2 (see #106 and r738), you may want to re-add that to the xpra command line to see if that helps. (if testing via winswitch, see xpra_xvfb_command=... in your .winswitch/server/server.conf)

comment:2 Changed 7 years ago by Antoine Martin

Owner: changed from Antoine Martin to pmarek
Status: acceptedassigned

comment:3 Changed 7 years ago by Antoine Martin

Resolution: needinfo
Status: assignedclosed

not heard back (2 months) - closing

Note: See TracTickets for help on using tickets.