I've reverted [1] which brought the change allow-insecure to be on by default. The patch seems to have issues which will be addressed and merged later. The revert can be found at [2]. [1] http://review.gluster.org/11274 [2] http://review.gluster.org/11507 Please let me know if the regressions are still failing. regards, Raghavendra. ----- Original Message ----- > From: "Joseph Fernandes" <josferna@xxxxxxxxxx> > To: "Atin Mukherjee" <atin.mukherjee83@xxxxxxxxx> > Cc: "Gluster Devel" <gluster-devel@xxxxxxxxxxx> > Sent: Thursday, July 2, 2015 9:49:16 PM > Subject: Re: Failure in tests/basic/tier/bug-1214222-directories_miising_after_attach_tier.t > > Yep.. Thanks Guys. > > ----- Original Message ----- > From: "Atin Mukherjee" <atin.mukherjee83@xxxxxxxxx> > To: "Joseph Fernandes" <josferna@xxxxxxxxxx> > Cc: kparthas@xxxxxxxxxx, "Atin Mukherjee" <amukherj@xxxxxxxxxx>, "Gluster > Devel" <gluster-devel@xxxxxxxxxxx> > Sent: Thursday, July 2, 2015 9:45:01 PM > Subject: Re: Failure in > tests/basic/tier/bug-1214222-directories_miising_after_attach_tier.t > > Joe, > > Please refer to Prasanna's mail. He has uploaded a patch to solve it. > > -Atin > Sent from one plus one > On Jul 2, 2015 9:42 PM, "Joseph Fernandes" <josferna@xxxxxxxxxx> wrote: > > > Hi All, > > > > This is the same issue as the previous tiering regression failure. > > > > Volume brick not able to start brick because port is busy > > > > [2015-07-02 10:20:20.601372] [run.c:190:runner_log] (--> > > /build/install/lib/libglusterfs.so.0(_gf_log_callingfn+0x240)[0x7f05e080bc32] > > (--> /build/install/lib/libglusterfs.so.0(runner_log+0x192)[0x7f05e08754ce] > > (--> > > /build/install/lib/glusterfs/3.8dev/xlator/mgmt/glusterd.so(glusterd_volume_start_glusterfs+0xae7)[0x7f05d5c935d7] > > (--> > > /build/install/lib/glusterfs/3.8dev/xlator/mgmt/glusterd.so(glusterd_brick_start+0x151)[0x7f05d5c9d4e3] > > (--> > > /build/install/lib/glusterfs/3.8dev/xlator/mgmt/glusterd.so(glusterd_op_perform_add_bricks+0x8fe)[0x7f05d5d10661] > > ))))) 0-: Starting GlusterFS: /build/install/sbin/glusterfsd -s > > slave33.cloud.gluster.org --volfile-id > > patchy.slave33.cloud.gluster.org.d-backends-patchy5 -p > > /var/lib/glusterd/vols/patchy/run/slave33.cloud.gluster.org-d-backends-patchy5.pid > > -S /var/run/gluster/ca5f5a89aa3a24f0a54852590ab82ad5.socket --brick-name > > /d/backends/patchy5 -l /var/log/glusterfs/bricks/d-backends-patchy5.log > > --xlator-option *-posix.glusterd-uuid=da011de8-9103-4cf2-9f4b-03707d0019d0 > > --brick-port 49167 --xlator-option patchy-server.listen-port=49167 > > [2015-07-02 10:20:20.624297] I [MSGID: 106144] > > [glusterd-pmap.c:269:pmap_registry_remove] 0-pmap: removing brick (null) on > > port 49167 > > [2015-07-02 10:20:20.625315] E [MSGID: 106005] > > [glusterd-utils.c:4448:glusterd_brick_start] 0-management: Unable to start > > brick slave33.cloud.gluster.org:/d/backends/patchy5 > > [2015-07-02 10:20:20.625354] E [MSGID: 106074] > > [glusterd-brick-ops.c:2096:glusterd_op_add_brick] 0-glusterd: Unable to add > > bricks > > [2015-07-02 10:20:20.625368] E [MSGID: 106123] > > [glusterd-syncop.c:1416:gd_commit_op_phase] 0-management: Commit of > > operation 'Volume Add brick' failed on localhost > > > > > > Brick Log: > > > > [2015-07-02 10:20:20.608547] I [MSGID: 100030] [glusterfsd.c:2296:main] > > 0-/build/install/sbin/glusterfsd: Started running > > /build/install/sbin/glusterfsd version 3.8dev (args: > > /build/install/sbin/glusterfsd -s slave33.cloud.gluster.org --volfile-id > > patchy.slave33.cloud.gluster.org.d-backends-patchy5 -p > > /var/lib/glusterd/vols/patchy/run/slave33.cloud.gluster.org-d-backends-patchy5.pid > > -S /var/run/gluster/ca5f5a89aa3a24f0a54852590ab82ad5.socket --brick-name > > /d/backends/patchy5 -l /var/log/glusterfs/bricks/d-backends-patchy5.log > > --xlator-option *-posix.glusterd-uuid=da011de8-9103-4cf2-9f4b-03707d0019d0 > > --brick-port 49167 --xlator-option patchy-server.listen-port=49167) > > [2015-07-02 10:20:20.617113] I [MSGID: 101190] > > [event-epoll.c:627:event_dispatch_epoll_worker] 0-epoll: Started thread > > with index 1 > > [2015-07-02 10:20:20.623097] I [MSGID: 101173] > > [graph.c:268:gf_add_cmdline_options] 0-patchy-server: adding option > > 'listen-port' for volume 'patchy-server' with value '49167' > > [2015-07-02 10:20:20.623135] I [MSGID: 101173] > > [graph.c:268:gf_add_cmdline_options] 0-patchy-posix: adding option > > 'glusterd-uuid' for volume 'patchy-posix' with value > > 'da011de8-9103-4cf2-9f4b-03707d0019d0' > > [2015-07-02 10:20:20.623358] I [MSGID: 115034] > > [server.c:392:_check_for_auth_option] 0-/d/backends/patchy5: skip format > > check for non-addr auth option auth.login./d/backends/patchy5.allow > > [2015-07-02 10:20:20.623374] I [MSGID: 115034] > > [server.c:392:_check_for_auth_option] 0-/d/backends/patchy5: skip format > > check for non-addr auth option > > auth.login.96bcb872-559b-4f19-84ad-a735dc6068f6.password > > [2015-07-02 10:20:20.623568] I > > [rpcsvc.c:2210:rpcsvc_set_outstanding_rpc_limit] 0-rpc-service: Configured > > rpc.outstanding-rpc-limit with value 64 > > [2015-07-02 10:20:20.623633] W [MSGID: 101002] > > [options.c:952:xl_opt_validate] 0-patchy-server: option 'listen-port' is > > deprecated, preferred is 'transport.socket.listen-port', continuing with > > correction > > [2015-07-02 10:20:20.623707] E [socket.c:818:__socket_server_bind] > > 0-tcp.patchy-server: binding to failed: Address already in use > > [2015-07-02 10:20:20.623720] E [socket.c:821:__socket_server_bind] > > 0-tcp.patchy-server: Port is already in use > > [2015-07-02 10:20:20.623746] W [rpcsvc.c:1599:rpcsvc_transport_create] > > 0-rpc-service: listening on transport failed > > [2015-07-02 10:20:20.623758] W [MSGID: 115045] [server.c:998:init] > > 0-patchy-server: creation of listener failed > > [2015-07-02 10:20:20.623772] E [MSGID: 101019] [xlator.c:423:xlator_init] > > 0-patchy-server: Initialization of volume 'patchy-server' failed, review > > your volfile again > > [2015-07-02 10:20:20.623783] E [MSGID: 101066] > > [graph.c:323:glusterfs_graph_init] 0-patchy-server: initializing translator > > failed > > [2015-07-02 10:20:20.623792] E [MSGID: 101176] > > [graph.c:669:glusterfs_graph_activate] 0-graph: init failed > > [2015-07-02 10:20:20.624203] W [glusterfsd.c:1214:cleanup_and_exit] (--> > > 0-: received signum (0), shutting down > > > > > > Regards, > > Joe > > > > > > ----- Original Message ----- > > From: "Pranith Kumar Karampuri" <pkarampu@xxxxxxxxxx> > > To: "Dan Lambright" <dlambrig@xxxxxxxxxx> > > Cc: "Gluster Devel" <gluster-devel@xxxxxxxxxxx>, "Joseph Fernandes" < > > josferna@xxxxxxxxxx> > > Sent: Thursday, July 2, 2015 6:16:44 PM > > Subject: Re: Failure in > > tests/basic/tier/bug-1214222-directories_miising_after_attach_tier.t > > > > Thanks Dan!. > > > > Pranith > > > > On 07/02/2015 06:14 PM, Dan Lambright wrote: > > > I'll check on this. > > > > > > ----- Original Message ----- > > >> From: "Pranith Kumar Karampuri" <pkarampu@xxxxxxxxxx> > > >> To: "Gluster Devel" <gluster-devel@xxxxxxxxxxx>, "Joseph Fernandes" < > > josferna@xxxxxxxxxx> > > >> Sent: Thursday, July 2, 2015 5:40:34 AM > > >> Subject: Failure in > > tests/basic/tier/bug-1214222-directories_miising_after_attach_tier.t > > >> > > >> hi Joseph, > > >> Could you take a look at > > >> > > http://build.gluster.org/job/rackspace-regression-2GB-triggered/11842/consoleFull > > >> > > >> Pranith > > >> _______________________________________________ > > >> Gluster-devel mailing list > > >> Gluster-devel@xxxxxxxxxxx > > >> http://www.gluster.org/mailman/listinfo/gluster-devel > > >> > > > > > > _______________________________________________ > > Gluster-devel mailing list > > Gluster-devel@xxxxxxxxxxx > > http://www.gluster.org/mailman/listinfo/gluster-devel > > > > > _______________________________________________ > Gluster-devel mailing list > Gluster-devel@xxxxxxxxxxx > http://www.gluster.org/mailman/listinfo/gluster-devel > _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-devel
