[Gluster-users] Errors when downloading from download.gluster.org
Looks like there are some issues with the download.gluster.org server: $ sudo apt-get install glusterfs-client Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: glusterfs-common The following NEW packages will be installed: glusterfs-client glusterfs-common 0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. Need to get 9,258 kB of archives. After this operation, 23.1 MB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 https://download.gluster.org/pub/gluster/glusterfs/9/LATEST/Debian/stretch/amd64/apt stretch/main amd64 glusterfs-common amd64 9.5-1 [6,215 kB] Err:1 https://download.gluster.org/pub/gluster/glusterfs/9/LATEST/Debian/stretch/amd64/apt stretch/main amd64 glusterfs-common amd64 9.5-1 GnuTLS recv error (-9): A TLS packet with unexpected length was received. Get:2 https://download.gluster.org/pub/gluster/glusterfs/9/LATEST/Debian/stretch/amd64/apt stretch/main amd64 glusterfs-client amd64 9.5-1 [3,043 kB] Err:2 https://download.gluster.org/pub/gluster/glusterfs/9/LATEST/Debian/stretch/amd64/apt stretch/main amd64 glusterfs-client amd64 9.5-1 GnuTLS recv error (-9): A TLS packet with unexpected length was received. E: Failed to fetch https://download.gluster.org/pub/gluster/glusterfs/9/LATEST/Debian/stretch/amd64/apt/pool/main/g/glusterfs/glusterfs-common_9.5-1_amd64.deb GnuTLS recv error (-9): A TLS packet with unexpected length was received. E: Failed to fetch https://download.gluster.org/pub/gluster/glusterfs/9/LATEST/Debian/stretch/amd64/apt/pool/main/g/glusterfs/glusterfs-client_9.5-1_amd64.deb GnuTLS recv error (-9): A TLS packet with unexpected length was received. E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?" $ curl " https://download.gluster.org/pub/gluster/glusterfs/9/LATEST/Debian/stretch/amd64/apt/pool/main/g/glusterfs/glusterfs-common_9.5-1_amd64.deb; > glusterfs-common_9.5-1_amd64.deb % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 0 6069k0 324080 0 30573 0 0:03:23 0:00:01 0:03:22 30602 curl: (18) transfer closed with 6182684 bytes remaining to read $ wget " https://download.gluster.org/pub/gluster/glusterfs/9/LATEST/Debian/stretch/amd64/apt/pool/main/g/glusterfs/glusterfs-common_9.5-1_amd64.deb; > glusterfs-common_9.5-1_amd64.deb --2022-06-07 15:17:34-- https://download.gluster.org/pub/gluster/glusterfs/9/LATEST/Debian/stretch/amd64/apt/pool/main/g/glusterfs/glusterfs-common_9.5-1_amd64.deb Resolving download.gluster.org (download.gluster.org)... 8.43.85.185 Connecting to download.gluster.org (download.gluster.org)|8.43.85.185|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 6215092 (5.9M) Saving to: ‘glusterfs-common_9.5-1_amd64.deb.1’ glusterfs-common_9.5-1_amd64.deb.10%[ ] 31.65K --.-KB/sin 0.003s 2022-06-07 15:17:35 (9.62 MB/s) - Read error at byte 32408/6215092 (Error decoding the received TLS packet.). Retrying. --2022-06-07 15:17:36-- (try: 2) https://download.gluster.org/pub/gluster/glusterfs/9/LATEST/Debian/stretch/amd64/apt/pool/main/g/glusterfs/glusterfs-common_9.5-1_amd64.deb Connecting to download.gluster.org (download.gluster.org)|8.43.85.185|:443... connected. HTTP request sent, awaiting response... 206 Partial Content Length: 6215092 (5.9M), 6182684 (5.9M) remaining Saving to: ‘glusterfs-common_9.5-1_amd64.deb.1’ glusterfs-common_9.5-1_amd64.deb.11%[ ] 63.24K --.-KB/sin 0.005s 2022-06-07 15:17:37 (5.75 MB/s) - Read error at byte 64759/6215092 (Error decoding the received TLS packet.). Retrying. --2022-06-07 15:17:39-- (try: 3) https://download.gluster.org/pub/gluster/glusterfs/9/LATEST/Debian/stretch/amd64/apt/pool/main/g/glusterfs/glusterfs-common_9.5-1_amd64.deb Connecting to download.gluster.org (download.gluster.org)|8.43.85.185|:443... connected. HTTP request sent, awaiting response... 206 Partial Content Length: 6215092 (5.9M), 6150333 (5.9M) remaining Saving to: ‘glusterfs-common_9.5-1_amd64.deb.1’ glusterfs-common_9.5-1_amd64.deb.11%[> ] 94.83K --.-KB/sin 0s 2022-06-07 15:17:40 (62.7 MB/s) - Read error at byte 97110/6215092 (Error decoding the received TLS packet.). Retrying. ...etc Community Meeting Calendar: Schedule - Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC Bridge: https://meet.google.com/cpu-eiue-hvk Gluster-users mailing list Gluster-users@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-users
Re: [Gluster-users] transport endpoint not connected on just 2 files
Hi, Thanks - sorry for the late reply - I was suddenly swamped with other work then it was a UK holiday. I've tried rsync -A -X with the volume stopped, then restarted it. Will see whether it heals. Cheers, Kingsley. On Mon, 2022-05-30 at 18:41 +, Strahil Nikolov wrote: > Make a backup from all bricks. Based on the info 2 of the bricks have > the same copy while brickC has another copy (gfid mismatch). > > I would use mtime to identify the latest version and use that, but I > have no clue what kind of application you have. > > Usually, It's not recommended to manipulate bricks directly, but in > this case it might be necessary. The simplest way is to move the file > on brick C (the only one that is different) away, but if you need > exactly that one, you can rsync/scp it to the other 2 bricks. > > > Best Regards, > Strahil Nikolov > > > On Fri, May 27, 2022 at 11:45, Kingsley Tart > > wrote: > > Hi, thanks. > > > > OK that's interesting. Picking one of the files, on bricks A and B > > I see this (and all of the values are identical between bricks A > > and B): > > > > trusted.afr.dirty=0x > > trusted.afr.gw-runqueues-client-2=0x00010002 > > trusted.gfid=0xa40bb83ff3784ae09c997d272296a7a9 > > trusted.gfid2path.06eddbe9be9c7c75=0x30323665396561652d613661662d34 > > 6365642d623863632d626135303739646364372f677733 > > trusted.glusterfs.mdata=0x01628ec577000 > > 0007168bb628ec576628ec57600 > > 00 > > > > and on brick C I see this: > > > > trusted.gfid=0xd73992aee03e4021824b1baced973df3 > > trusted.gfid2path.06eddbe9be9c7c75=0x30323665396561652d613661662d34 > > 6365642d623863632d626135303739646364372f677733 > > trusted.glusterfs.mdata=0x01628ec523000 > > 030136ca0628ec523628ec52300 > > 00 > > > > So brick C is missing the trusted.afr attributes and the > > trusted.gfid and mdata differ. > > > > What do I need to do to fix this? > > > > Cheers, > > Kingsley. > > > > On Fri, 2022-05-27 at 03:59 +, Strahil Nikolov wrote: > > > Check the file attributes on all bricks: > > > > > > getfattr -d -e hex -m. /data/brick/gw-runqueues/ > > > > > > > > > Best Regards, > > > Strahil Nikolov > > > > > > > On Thu, May 26, 2022 at 16:05, Kingsley Tart > > > > wrote: > > > > Hi, > > > > > > > > I've got a strange issue where on all clients I've tested on > > > > (tested on > > > > 4) I have "transport endpoint is not connected" on two files in > > > > a > > > > directory, whereas other files can be read fine. > > > > > > > > Any ideas? > > > > > > > > On one of the servers (all same version): > > > > > > > > # gluster --version > > > > glusterfs 9.1 > > > > > > > > On one of the clients (same thing with all of them) - problem > > > > with > > > > files "gw3" and "gw11": > > > > > > > > [root@gw6 btl]# cd /mnt/runqueues/runners/ > > > > [root@gw6 runners]# ls -la > > > > ls: cannot access gw11: Transport endpoint is not connected > > > > ls: cannot access gw3: Transport endpoint is not connected > > > > total 8 > > > > drwxr-xr-x 2 root root 4096 May 26 09:48 . > > > > drwxr-xr-x 13 root root 4096 Apr 12 2021 .. > > > > -rw-r--r-- 1 root root0 May 26 09:49 gw1 > > > > -rw-r--r-- 1 root root0 May 26 09:49 gw10 > > > > -? ? ?? ?? gw11 > > > > -rw-r--r-- 1 root root0 May 26 09:49 gw2 > > > > -? ? ?? ?? gw3 > > > > -rw-r--r-- 1 root root0 May 26 09:49 gw4 > > > > -rw-r--r-- 1 root root0 May 26 09:49 gw6 > > > > -rw-r--r-- 1 root root0 May 26 09:49 gw7 > > > > [root@gw6 runners]# cat * > > > > cat: gw11: Transport endpoint is not connected > > > > cat: gw3: Transport endpoint is not connected > > > > [root@gw6 runners]# > > > > > > > > > > > > Querying on a server shows those two problematic files: > > > > > > > > # gluster volume heal gw-runqueues info > > > > Brick gluster9a:/data/brick/gw-runqueues > > > > /runners > > > > /runners/gw11 > > > > /runners/gw3 > > > > Status: Connected > > > > Number of entries: 3 > > > > > > > > Brick gluster9b:/data/brick/gw-runqueues > > > > /runners > > > > /runners/gw11 > > > > /runners/gw3 > > > > Status: Connected > > > > Number of entries: 3 > > > > > > > > Brick gluster9c:/data/brick/gw-runqueues > > > > Status: Connected > > > > Number of entries: 0 > > > > > > > > > > > > However several hours later there's no obvious change. The > > > > servers have > > > > hardly any load and the volume is tiny. From a client: > > > > > > > > # find /mnt/runqueues | wc -l > > > > 35 > > > > > > > > > > > > glfsheal-gw-runqueues.log from server gluster9a: > > > > https://pastebin.com/7mPszBBM > > > > > > > > glfsheal-gw-runqueues.log from server gluster9b: > > > > https://pastebin.com/rxXs5Tcv > > > > > > > > > > > > Any pointers would be much appreciated! > > > > > > > > Cheers,
