The failure suggests that the port snapd is trying to bind to is already
in use. But snapd has been modified to use a new port everytime. I am
looking into this.
On 07/25/2016 02:23 PM, Nithya Balachandran wrote:
More failures:
https://build.gluster.org/job/rackspace-regression-2GB-triggered/22452/console
I see these messages in the snapd.log:
[2016-07-22 05:31:52.482282] I
[rpcsvc.c:2199:rpcsvc_set_outstanding_rpc_limit] 0-rpc-service:
Configured rpc.outstanding-rpc-limit with value 64
[2016-07-22 05:31:52.482352] W [MSGID: 101002]
[options.c:954:xl_opt_validate] 0-patchy-server: option 'listen-port'
is deprecated, preferred is 'transport.socket.listen-port', continuing
with correction
[2016-07-22 05:31:52.482436] E [socket.c:771:__socket_server_bind]
0-tcp.patchy-server: binding to failed: Address already in use
[2016-07-22 05:31:52.482447] E [socket.c:774:__socket_server_bind]
0-tcp.patchy-server: Port is already in use
[2016-07-22 05:31:52.482459] W [rpcsvc.c:1630:rpcsvc_create_listener]
0-rpc-service: listening on transport failed
[2016-07-22 05:31:52.482469] W [MSGID: 115045] [server.c:1061:init]
0-patchy-server: creation of listener failed
[2016-07-22 05:31:52.482481] E [MSGID: 101019]
[xlator.c:433:xlator_init] 0-patchy-server: Initialization of volume
'patchy-server' failed, review your volfile again
[2016-07-22 05:31:52.482491] E [MSGID: 101066]
[graph.c:324:glusterfs_graph_init] 0-patchy-server: initializing
translator failed
[2016-07-22 05:31:52.482499] E [MSGID: 101176]
[graph.c:670:glusterfs_graph_activate] 0-graph: init failed
On Mon, Jul 25, 2016 at 12:00 PM, Ashish Pandey <[email protected]
<mailto:[email protected]>> wrote:
Hi,
Following test has failed 3 times in last two days -
./tests/bugs/snapshot/bug-1316437.t
https://build.gluster.org/job/rackspace-regression-2GB-triggered/22445/consoleFull
https://build.gluster.org/job/rackspace-regression-2GB-triggered/22445/consoleFull
https://build.gluster.org/job/rackspace-regression-2GB-triggered/22470/consoleFull
Please take a look at it and check if it spurious failure or not.
Ashish
_______________________________________________
Gluster-devel mailing list
[email protected] <mailto:[email protected]>
http://www.gluster.org/mailman/listinfo/gluster-devel
_______________________________________________
Gluster-devel mailing list
[email protected]
http://www.gluster.org/mailman/listinfo/gluster-devel
