search for: _gf_msg_internal

...06487] [glusterd-handler.c:1242:__glusterd_handle_cli_probe] > 0-glusterd: Received CLI probe req 192.168.1.17 24007 > > [2017-06-18 07:04:17.853237] D [MSGID: 0] [common-utils.c:3361:gf_is_local_addr] > 0-management: 192.168.1.17 > > [2017-06-18 07:04:17.854093] D [logging.c:1952:_gf_msg_internal] > 0-logging-infra: Buffer overflow of a buffer whose size limit is 5. About > to flush least recently used log message to disk > > The message "D [MSGID: 0] [common-utils.c:3361:gf_is_local_addr] > 0-management: 192.168.1.17 " repeated 2 times between [2017-06-18 > 07:0...

...8 07:04:17.853162] I [MSGID: 106487] [glusterd-handler.c:1242:__glusterd_handle_cli_probe] 0-glusterd: Received CLI probe req 192.168.1.17 24007 [2017-06-18 07:04:17.853237] D [MSGID: 0] [common-utils.c:3361:gf_is_local_addr] 0-management: 192.168.1.17 [2017-06-18 07:04:17.854093] D [logging.c:1952:_gf_msg_internal] 0-logging-infra: Buffer overflow of a buffer whose size limit is 5. About to flush least recently used log message to disk The message "D [MSGID: 0] [common-utils.c:3361:gf_is_local_addr] 0-management: 192.168.1.17 " repeated 2 times between [2017-06-18 07:04:17.853237] and [2017-06-18 0...

....c:1242:__glusterd_handle_cli_probe] 0-glusterd: >> Received CLI probe req 192.168.1.17 24007 >> >> [2017-06-18 07:04:17.853237] D [MSGID: 0] [common-utils.c:3361:gf_is_local_addr] >> 0-management: 192.168.1.17 >> >> [2017-06-18 07:04:17.854093] D [logging.c:1952:_gf_msg_internal] >> 0-logging-infra: Buffer overflow of a buffer whose size limit is 5. About >> to flush least recently used log message to disk >> >> The message "D [MSGID: 0] [common-utils.c:3361:gf_is_local_addr] >> 0-management: 192.168.1.17 " repeated 2 times between [...

...8 07:04:17.853162] I [MSGID: 106487] [glusterd-handler.c:1242:__glusterd_handle_cli_probe] 0-glusterd: Received CLI probe req 192.168.1.17 24007 [2017-06-18 07:04:17.853237] D [MSGID: 0] [common-utils.c:3361:gf_is_local_addr] 0-management: 192.168.1.17 [2017-06-18 07:04:17.854093] D [logging.c:1952:_gf_msg_internal] 0-logging-infra: Buffer overflow of a buffer whose size limit is 5. About to flush least recently used log message to disk The message "D [MSGID: 0] [common-utils.c:3361:gf_is_local_addr] 0-management: 192.168.1.17 " repeated 2 times between [2017-06-18 07:04:17.853237] and [2017-06-18 0...

Could you please send me the output of command "sysctl net.ipv4.ip_local_reserved_ports". Apart from output of command please send the logs to look into the issue. Thanks Gaurav On Thu, Jun 15, 2017 at 4:28 PM, Atin Mukherjee <amukherj at redhat.com> wrote: > +Gaurav, he is the author of the patch, can you please comment here? > > > On Thu, Jun 15, 2017 at 3:28

...date_cbk] 0-video-backup-dht: revalidate lookup of /path returned with op_ret 0 [Invalid argument] [2017-12-21 16:36:37.172352] D [fuse-helpers.c:650:fuse_ignore_xattr_set] 0-glusterfs-fuse: allowing setxattr: key [glusterfs.gfid.heal], client pid [0] [2017-12-21 16:36:37.172457] D [logging.c:1953:_gf_msg_internal] 0-logging-infra: Buffer overflow of a buffer whose size limit is 5. About to flush least recently used log message to disk The message "D [MSGID: 0] [dht-common.c:997:dht_revalidate_cbk] 0-video-backup-dht: revalidate lookup of /path returned with op_ret 0 [Invalid argument]" repeated 8...

...sterd_store_create_peer_dir] 0-glusterd: Returning with 0 [2017-04-03 22:20:24.728550] D [MSGID: 0] [store.c:421:gf_store_handle_new] 0-: Returning 0 [2017-04-03 22:20:24.728679] D [MSGID: 0] [store.c:375:gf_store_save_value] 0-management: returning: 0 [2017-04-03 22:20:24.728720] D [logging.c:1952:_gf_msg_internal] 0-logging-infra: Buffer overflow of a buffer whose size limit is 5. About to flush least recently used log message to disk The message "D [MSGID: 0] [store.c:375:gf_store_save_value] 0-management: returning: 0" repeated 2 times between [2017-04-03 22:20:24.728679] and [2017-04-03 22:20:2...

I have a ~600tb distributed gluster volume that I want to start using geo replication on. The current volume is on 6 100tb bricks on 2 servers My plan is: 1) copy each of the bricks to a new arrays on the servers locally 2) move the new arrays to the new servers 3) create the volume on the new servers using the arrays 4) fix the layout on the new volume 5) start georeplication (which should be