Displaying 20 results from an estimated 28 matches for "gf_auth".
Did you mean:
do_auth
2008 Sep 15
1
Errors on mounting (but works)
....12:1023
2008-09-15 15:04:42 D [tcp-server.c:257:gf_transport_fini] server:
destroying transport object for 192.168.10.12:1023 (fd=63)
2008-09-15 15:04:42 D [tcp-server.c:145:tcp_server_notify] server:
Registering socket (63) for new transport object of 192.168.10.12
2008-09-15 15:04:42 D [ip.c:120:gf_auth] mapreduce1: allowed = "*", received
ip addr = "192.168.10.12"
2008-09-15 15:04:42 D [server-protocol.c:5667:mop_setvolume] server:
accepted client from 192.168.10.12:1022
2008-09-15 15:04:42 D [tcp-server.c:145:tcp_server_notify] server:
Registering socket (66) for new transpor...
2018 Jan 14
0
Volume can not write to data if this volume quota limits capacity and mount itself volume on arm64（aarch64） architecture
...bvolumes (up=7, mask=7, remaining=0, good=5, bad=2)" repeated 6 times between [2018-02-02 12:24:19.680348] and [2018-02-02 12:24:19.694499]
[root at f08n25bricks]# tail -n 100 data-gluster-1045fe63-bf09-42f5-986b-ce2d3d63def0-test_vol.log
[2018-02-02 11:23:28.615522] I [login.c:81:gf_auth] 0-auth/login: allowed user names: ff3d40c1-1ef1-4eb3-a448-19ec3cb60f16
[2018-02-02 11:23:28.615573] I [MSGID: 115029] [server-handshake.c:690:server_setvolume] 0-test_vol-server: accepted client from f08n33-90322-2018/01/14-06:17:22:557038-test_vol-client-1-0-0 (version: 3.7.20)
[2018-02-02 11:23:...
2010 Mar 15
1
Glusterfs 3.0.X crashed on Fedora 11
...2010-03-14 22:46:48] N [afr.c:2627:notify] rep15: Subvolume 'cbrick32' came back up; going online.
[2010-03-14 22:46:48] N [client-protocol.c:6246:client_setvolume_cbk] cbrick40: Connected to 192.168.1.159:6996, attached to remote volume 'brick8'.
[2010-03-14 22:46:48] D [addr.c:190:gf_auth] brick3: allowed = "*", received addr = "192.168.1.155"
[2010-03-14 22:46:48] N [server-protocol.c:5852:mop_setvolume] server: accepted client from 192.168.1.155:998
[2010-03-14 22:46:48] D [dht-diskusage.c:71:dht_du_info_cbk] dist: on subvolume 'rep1': avail_percent is:...
2018 Jan 19
2
geo-replication command rsync returned with 3
...ing EOF.
[2018-01-19 14:23:27.163053] I [syncdutils(agent):220:finalize] <top>:
exiting.
[2018-01-19 14:23:28.61029] I [monitor(monitor):344:monitor] Monitor:
worker(/brick1/mvol1) died in startup phase
/var/log/glusterfs/bricks/brick1-mvol1.log
[2018-01-19 14:23:18.264649] I [login.c:81:gf_auth] 0-auth/login:
allowed user names: 2bc51718-940f-4a9c-9106-eb8404b95622
[2018-01-19 14:23:18.264689] I [MSGID: 115029]
[server-handshake.c:690:server_setvolume] 0-mvol1-server: accepted
client from
gl-master-04-8871-2018/01/19-14:23:18:129523-mvol1-client-0-0-0
(version: 3.7.18)
[2018-01-19 14...
2013 Sep 16
1
Gluster 3.4 QEMU and Permission Denied Errors
...lled.
I have a single volume on gluster called vmdata that contains my qcow2
formated image created like this:
qemu-img create -f qcow2 gluster://localhost/vmdata/test1.qcow 8G
I'm able to boot my created virtual machine but in the logs I see this:
[2013-09-16 15:16:04.471205] E [addr.c:152:gf_auth] 0-auth/addr:
client is bound to port 46021 which is not privileged
[2013-09-16 15:16:04.471277] I
[server-handshake.c:567:server_setvolume] 0-vmdata-server: accepted
client from gluster1.local-1061-2013/09/16-15:16:04:441166-vmdata-client-1-0
(version: 3.4.0)[2013-09-16 15:16:04.488000] I
[server-...
2018 Feb 28
1
Intermittent mount disconnect due to socket poller error
...VOL-server: Shutting down connection
CLIENT-30688-2018/02/28-03:11:39:784734-VOL-client-1-0-0
[2018-02-28 19:40:58.351350] I [addr.c:55:compare_addr_and_update]
0-/glusterfs/uploads-brick2/data: allowed = "*", received addr = "CLIENT"
[2018-02-28 19:40:58.351684] I [login.c:34:gf_auth] 0-auth/login:
connecting user name: CLIENT
SERVER1:/var/log/glusterfs/bricks/VOL-brick1.log
[2018-02-28 19:35:58.509713] W [socket.c:593:__socket_rwv]
0-tcp.VOL-server: writev on CLIENT:49150 failed (No data available)
[2018-02-28 19:35:58.509839] E [socket.c:2632:socket_poller]
0-tcp.VOL-serv...
2018 Jan 19
0
geo-replication command rsync returned with 3
...3053] I [syncdutils(agent):220:finalize] <top>:
>exiting.
>[2018-01-19 14:23:28.61029] I [monitor(monitor):344:monitor] Monitor:
>worker(/brick1/mvol1) died in startup phase
>
>
>/var/log/glusterfs/bricks/brick1-mvol1.log
>
>[2018-01-19 14:23:18.264649] I [login.c:81:gf_auth] 0-auth/login:
>allowed user names: 2bc51718-940f-4a9c-9106-eb8404b95622
>[2018-01-19 14:23:18.264689] I [MSGID: 115029]
>[server-handshake.c:690:server_setvolume] 0-mvol1-server: accepted
>client from
>gl-master-04-8871-2018/01/19-14:23:18:129523-mvol1-client-0-0-0
>(version...
2018 Mar 07
0
Intermittent mount disconnect due to socket poller error
...2018/02/28-03:11:39:784734-VOL-client-1-0-0
>> ??? [2018-02-28 19:40:58.351350] I [addr.c:55:compare_addr_and_update]
>> ??? 0-/glusterfs/uploads-brick2/data: allowed = "*", received addr =
>> ??? "CLIENT"
>> ??? [2018-02-28 19:40:58.351684] I [login.c:34:gf_auth] 0-auth/login:
>> ??? connecting user name: CLIENT
>>
>> ??? SERVER1:/var/log/glusterfs/bricks/VOL-brick1.log
>> ??? [2018-02-28 19:35:58.509713] W [socket.c:593:__socket_rwv]
>> ??? 0-tcp.VOL-server: writev on CLIENT:49150 failed (No data available)
>> ??? [2018...
2008 Dec 18
3
Feedback and Questions on afr+unify
...ife easier for new
adopters.
- One of my servers is behind a router with NAT enabled and this
caused problems. I kept getting errors of this kind when trying to
connect from the NATed client (10.24.1.4) to the other one. The logfile
gave me the following:
2008-12-18 00:25:40 E [addr.c:117:gf_auth] auth/addr: client is bound to
port 59327 which is not privilaged
2008-12-18 00:25:40 E [authenticate.c:193:gf_authenticate] auth: no
authentication module is interested in accepting remote-client
10.24.1.4:59327
2008-12-18 00:25:40 E [server-protocol.c:6842:mop_setvolume] server:
Cannot authen...
2018 Jan 18
0
issues after botched update
...376:afr_local_discovery_cbk] 0-home-replicate-0:
selecting local read_child home-client-0
[2018-01-18 08:38:39.039054] I [addr.c:55:compare_addr_and_update]
0-/data/home/brick1: allowed = "*", received addr = "*.*.*.*"
[2018-01-18 08:38:39.040813] I [login.c:76:gf_auth] 0-auth/login:
allowed user names: 2d225def-3f34-472a-b8e4-c183acafc151
[2018-01-18 08:38:39.040853] I [MSGID: 115029]
[server-handshake.c:793:server_setvolume] 0-home-server: accepted
client from
gluster00.cluster.local-21570-2018/01/18-08:38:38:940331-home-client-0-0-0
(ve...
2023 Feb 23
1
Big problems after update to 9.6
...d_submit_reply] 0-glusterd: Reply submission
failed
And in the brick log:
[2023-02-23 20:22:56.717721 +0000] I [addr.c:54:compare_addr_and_update]
0-/nodirectwritedata/gluster/gvol0: allowed = "*", received addr =
"10.20.20.11"
[2023-02-23 20:22:56.717817 +0000] I [login.c:110:gf_auth] 0-auth/login:
allowed user names: a26c7de4-1236-4e0a-944a-cb82de7f7f0e
[2023-02-23 20:22:56.717840 +0000] I [MSGID: 115029]
[server-handshake.c:561:server_setvolume] 0-gvol0-server: accepted client
from
CTX_ID:46b23c19-5114-4a20-9306-9ea6faf02d51-GRAPH_ID:0-PID:35568-HOST:br.m5voip.com-PC_NAME:gvo...
2018 Feb 13
2
Failed to get quota limits
...md-volume.c:1674:cli_cmd_quota_handle_list_all] 0-cli: Failed to get quota limits for 16ac4cde-a5d4-451f-adcc-422a542fea24
[2018-02-13 08:16:14.092980] I [input.c:31:cli_batch] 0-: Exiting with: 0
*** /var/log/glusterfs/bricks/data-myvolume-brick.log ***
[2018-02-13 08:16:13.948065] I [addr.c:182:gf_auth] 0-/data/myvolume/brick: allowed = "*", received addr = "127.0.0.1"
[2018-02-13 08:16:13.948105] I [login.c:76:gf_auth] 0-auth/login: allowed user names: bea3e634-e174-4bb3-a1d6-25b09d03b536
[2018-02-13 08:16:13.948125] I [MSGID: 115029] [server-handshake.c:695:server_setvolume]...
2018 Feb 13
0
Failed to get quota limits
...ndle_list_all] 0-cli: Failed to get
> quota limits for 16ac4cde-a5d4-451f-adcc-422a542fea24
> [2018-02-13 08:16:14.092980] I [input.c:31:cli_batch] 0-: Exiting with: 0
>
>
> *** /var/log/glusterfs/bricks/data-myvolume-brick.log ***
>
> [2018-02-13 08:16:13.948065] I [addr.c:182:gf_auth] 0-/data/myvolume/brick:
> allowed = "*", received addr = "127.0.0.1"
> [2018-02-13 08:16:13.948105] I [login.c:76:gf_auth] 0-auth/login: allowed
> user names: bea3e634-e174-4bb3-a1d6-25b09d03b536
> [2018-02-13 08:16:13.948125] I [MSGID: 115029]
> [server-handshak...
2018 Feb 13
2
Failed to get quota limits
...gt;> quota limits for 16ac4cde-a5d4-451f-adcc-422a542fea24
>>>>> [2018-02-13 08:16:14.092980] I [input.c:31:cli_batch] 0-: Exiting with: 0
>>>>> *** /var/log/glusterfs/bricks/data-myvolume-brick.log ***
>>>>> [2018-02-13 08:16:13.948065] I [addr.c:182:gf_auth] 0-/data/myvolume/brick:
>>>>> allowed = "*", received addr = "127.0.0.1"
>>>>> [2018-02-13 08:16:13.948105] I [login.c:76:gf_auth] 0-auth/login: allowed
>>>>> user names: bea3e634-e174-4bb3-a1d6-25b09d03b536
>>>>> [201...
2018 Feb 13
2
Failed to get quota limits
...16ac4cde-a5d4-451f-adcc-422a542fea24
>>>>>>> [2018-02-13 08:16:14.092980] I [input.c:31:cli_batch] 0-: Exiting with: 0
>>>>>>> *** /var/log/glusterfs/bricks/data-myvolume-brick.log ***
>>>>>>> [2018-02-13 08:16:13.948065] I [addr.c:182:gf_auth] 0-/data/myvolume/brick:
>>>>>>> allowed = "*", received addr = "127.0.0.1"
>>>>>>> [2018-02-13 08:16:13.948105] I [login.c:76:gf_auth] 0-auth/login: allowed
>>>>>>> user names: bea3e634-e174-4bb3-a1d6-25b09d03b536
&...
2018 Feb 13
0
Failed to get quota limits
...a limits for 16ac4cde-a5d4-451f-adcc-422a542fea24
>>>>>> [2018-02-13 08:16:14.092980] I [input.c:31:cli_batch] 0-: Exiting with: 0
>>>>>> *** /var/log/glusterfs/bricks/data-myvolume-brick.log ***
>>>>>> [2018-02-13 08:16:13.948065] I [addr.c:182:gf_auth] 0-/data/myvolume/brick:
>>>>>> allowed = "*", received addr = "127.0.0.1"
>>>>>> [2018-02-13 08:16:13.948105] I [login.c:76:gf_auth] 0-auth/login: allowed
>>>>>> user names: bea3e634-e174-4bb3-a1d6-25b09d03b536
>>>&...
2023 Feb 24
1
Big problems after update to 9.6
...d_submit_reply] 0-glusterd: Reply submission failed
And in the brick log:
[2023-02-23 20:22:56.717721 +0000] I [addr.c:54:compare_addr_and_update] 0-/nodirectwritedata/gluster/gvol0: allowed = "*", received addr = "10.20.20.11"
[2023-02-23 20:22:56.717817 +0000] I [login.c:110:gf_auth] 0-auth/login: allowed user names: a26c7de4-1236-4e0a-944a-cb82de7f7f0e
[2023-02-23 20:22:56.717840 +0000] I [MSGID: 115029] [server-handshake.c:561:server_setvolume] 0-gvol0-server: accepted client from CTX_ID:46b23c19-5114-4a20-9306-9ea6faf02d51-GRAPH_ID:0-PID:35568-HOST:br.m5voip.com-PC_NAME:gvo...
2018 Feb 13
0
Failed to get quota limits
...d4-451f-adcc-422a542fea24
>>>>>>>> [2018-02-13 08:16:14.092980] I [input.c:31:cli_batch] 0-: Exiting with: 0
>>>>>>>> *** /var/log/glusterfs/bricks/data-myvolume-brick.log ***
>>>>>>>> [2018-02-13 08:16:13.948065] I [addr.c:182:gf_auth] 0-/data/myvolume/brick:
>>>>>>>> allowed = "*", received addr = "127.0.0.1"
>>>>>>>> [2018-02-13 08:16:13.948105] I [login.c:76:gf_auth] 0-auth/login: allowed
>>>>>>>> user names: bea3e634-e174-4bb3-a1d6-25...
2018 Feb 12
0
Failed to get quota limits
Hi,
Can you provide more information like, the volume configuration, quota.conf
file and the log files.
On Sat, Feb 10, 2018 at 1:05 AM, mabi <mabi at protonmail.ch> wrote:
> Hello,
>
> I am running GlusterFS 3.10.7 and just noticed by doing a "gluster volume
quota <volname> list" that my quotas on that volume are broken. The command
returns no output and no errors
2018 Feb 23
2
Failed to get quota limits
...-422a542fea24
>>>>>>>>> [2018-02-13 08:16:14.092980] I [input.c:31:cli_batch] 0-: Exiting with: 0
>>>>>>>>> *** /var/log/glusterfs/bricks/data-myvolume-brick.log ***
>>>>>>>>> [2018-02-13 08:16:13.948065] I [addr.c:182:gf_auth] 0-/data/myvolume/brick:
>>>>>>>>> allowed = "*", received addr = "127.0.0.1"
>>>>>>>>> [2018-02-13 08:16:13.948105] I [login.c:76:gf_auth] 0-auth/login: allowed
>>>>>>>>> user names: bea3e634-e174-...