Board index FlightGear Support Compiling

cloning data error: RPC failed; curl 56 GnuTLS recv error (-

Building FlightGear from source, and in the need for help?

cloning data error: RPC failed; curl 56 GnuTLS recv error (-

Postby powoflight » Thu Apr 30, 2020 8:20 am

Good Morning

Once again problem with downloading last next: DATA.
SIMGEAR & FGFS are OK

1) I have updated fgmeta
======================================================
Updating download_and_compile.sh
======================================================
in directory cd ~/flightgear/fgmeta
git clone https://git.code.sf.net/p/flightgear/fgmeta && git pull

2) /home/me/flightgear/fgmeta/download_and_compile.sh DATA

Code: Select all
****************************************
**************** DATA ******************
****************************************
Fetching DATA with 'git clone https://git.code.sf.net/p/flightgeaSIMGEAR FGFSr/fgdata'
Cloning into '.'...
remote: Enumerating objects: 71510, done.
remote: Counting objects: 100% (71510/71510), done.
remote: Compressing objects: 100% (28688/28688), done.
error: RPC failed; curl 56 GnuTLS recv error (-110): The TLS connection was non-properly terminated.
fatal: The remote end hung up unexpectedly
fatal: early EOF
fatal: index-pack failed

I tried many times till yesterday in the afternoon
git config --global http.postBuffer 1048576000
as described in : viewtopic.php?t=34146&p=331505#p338481
but no success.

I have UBUNTU 18.04.4 LTS
I can remember in November 2019 i had a lot problems concerning DATA too. I think it worked only one time.

What can i do?
Should i change in download_and_compile.sh
The sequence https:// with the sequence git://
Code: Select all
PROGNAME=$(basename "$0")
FGVERSION="release/$(git ls-remote --heads https://git.code.sf.net/p/flightgear/flightgear|grep '\/release\/'|cut -f4 -d'/'|sort -t . -k 1,1n -k2,2n -k3,3n|tail -1)"

see: viewtopic.php?t=34146&p=331505#p331670

But in this case i get problems with git clone fgmeta!

What is your recommandation?
powoflight
 
Posts: 212
Joined: Fri Mar 25, 2016 11:04 am
Location: LOWW
Callsign: OE-POW
Version: 2020.4
OS: win7 Ubuntu 18.04

Re: cloning data error: RPC failed; curl 56 GnuTLS recv erro

Postby powoflight » Thu Apr 30, 2020 9:05 am

So i find a solution.

I download the fgdata / next from the Mirror: https://gitlab.com/flightgear/fgdata
successfully.

Decompress and copy it in
/home/bb/flightgear/next202004/install/flightgear/fgdata

Have done a short check and it looks like it worked :D .
powoflight
 
Posts: 212
Joined: Fri Mar 25, 2016 11:04 am
Location: LOWW
Callsign: OE-POW
Version: 2020.4
OS: win7 Ubuntu 18.04

Re: cloning data error: RPC failed; curl 56 GnuTLS recv erro

Postby rominet » Tue Jun 16, 2020 3:36 pm

Hello, this is done automatically for you if you use the latest version of download_and_compile.sh (use option --non-interactive if you don't want the script to stop in the middle asking for your consent). See here and here.
rominet
 
Posts: 605
Joined: Sat Nov 01, 2014 2:33 pm
Callsign: F-KATS
Version: Git next
OS: Debian GNU/Linux

Re: cloning data error: RPC failed; curl 56 GnuTLS recv erro

Postby powoflight » Mon Oct 19, 2020 11:50 am

Once again : error: RPC failed; curl 56 GnuTLS recv error (-110): The TLS connection was non-properly terminated.

I have update fgmeta : cd ~/flightgear/fgmeta && git pull
Code: Select all
remote: Enumerating objects: 172, done.
remote: Counting objects: 100% (164/164), done.
remote: Compressing objects: 100% (135/135), done.
remote: Total 137 (delta 72), reused 0 (delta 0)
Receiving objects: 100% (137/137), 21.16 KiB | 10.58 MiB/s, done.
Resolving deltas: 100% (72/72), completed with 11 local objects.
From https://git.code.sf.net/p/flightgear/fgmeta
   e78b239..90f951a  next             -> origin/next
   12fce0f..88cc782  release/2018.3   -> origin/release/2018.3
   e61f4cb..71f48ae  release/2020.2   -> origin/release/2020.2
 * [new branch]      release/2020.3   -> origin/release/2020.3
 * [new tag]         version/2018.3.6 -> version/2018.3.6
Updating e78b239..90f951a
Fast-forward
 .gitignore                                     |  2 ++
 FlightGear.iss                                 | 60 +-----------------------------------------------------------
 build_appimage.sh                              |  7 +++++--
 build_release_windows.bat                      | 56 +++++++-------------------------------------------------
 catalog/stable-2020-catalog/catalog.config.xml | 34 ++++++++++++++++++++++++++++++++++
 catalog/stable-2020-catalog/template.xml       | 13 +++++++++++++
 catalog/stable-2020-catalog/zip-excludes.lst   |  5 +++++
 catalog/update_catalogs.sh                     | 55 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
 download_and_compile.sh                        |  2 +-
 fgaddon/aircraft_updates.py                    | 81 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 fgaddon/find_md5file.py                        | 25 +++++++++++++++++++++++++
 post_upload.py                                 | 13 ++++++++++++-
 sync_to_SF_frs.sh                              | 29 +++++++++++++++++++++++++++++
 version                                        |  2 +-
 14 files changed, 271 insertions(+), 113 deletions(-)
 mode change 100644 => 100755 build_appimage.sh
 create mode 100644 catalog/stable-2020-catalog/catalog.config.xml
 create mode 100644 catalog/stable-2020-catalog/template.xml
 create mode 100644 catalog/stable-2020-catalog/zip-excludes.lst
 create mode 100755 catalog/update_catalogs.sh
 create mode 100755 fgaddon/aircraft_updates.py
 create mode 100755 fgaddon/find_md5file.py
 create mode 100755 sync_to_SF_frs.sh


and
bern@FG-Ubuntu:~/flightgear/Next202010$ /home/bern/flightgear/fgmeta/download_and_compile.sh -j4 --non-interactive


Code: Select all
****************************************
**************** DATA ******************
****************************************
Starting special initialization routine for the DATA component...
Fetching FGData with 'git clone https://gitlab.com/flightgear/fgdata.git'
Cloning into '.'...
remote: Enumerating objects: 984, done.
remote: Counting objects: 100% (984/984), done.
remote: Compressing objects: 100% (528/528), done.
error: RPC failed; curl 56 GnuTLS recv error (-110): The TLS connection was non-properly terminated.
fatal: The remote end hung up unexpectedly
fatal: early EOF
fatal: index-pack failed
powoflight
 
Posts: 212
Joined: Fri Mar 25, 2016 11:04 am
Location: LOWW
Callsign: OE-POW
Version: 2020.4
OS: win7 Ubuntu 18.04

Re: cloning data error: RPC failed; curl 56 GnuTLS recv erro

Postby rominet » Mon Oct 19, 2020 12:23 pm

Gah... I've never seen this myself from GitLab, but you are the second person to report it, AFAIK (I have libcurl4-openssl-dev installed on my system and not libcurl4-gnutls-dev, but I believe the chances that this detail matters here are slim). The first person who reported this apparently had an unstable connection and was able to successfully clone FGData the second time.

My suggestion: either retry once, or use the SSH method for cloning FGData. There are a few more manual steps, but the wiki explains them in great detail, therefore unless your connection is really unstable, I think you should manage to get FGData this way.
rominet
 
Posts: 605
Joined: Sat Nov 01, 2014 2:33 pm
Callsign: F-KATS
Version: Git next
OS: Debian GNU/Linux

Re: cloning data error: RPC failed; curl 56 GnuTLS recv erro

Postby ludomotico » Mon Oct 19, 2020 12:28 pm

Gitlab and sourceforce set bandwidth limits for unauthenticated connections. These limits are not always enforced, I guess it depends on the current server load. Two options:

- Use the SSH method to authenticate yourself in GitLab. Authenticated connections have typically higher limits, and you'll be able to download FgFdata completely even faster.
- If you can't or won't authenticate in GitLab, try again, and again, and again, and you'll be able to download FgData, eventually.
User avatar
ludomotico
 
Posts: 1269
Joined: Tue Apr 24, 2012 2:01 pm
Version: nightly
OS: Windows 10

Re: cloning data error: RPC failed; curl 56 GnuTLS recv erro

Postby rominet » Mon Oct 19, 2020 12:47 pm

Thanks for this additional info, ludomotico. For the SSH method, I suggest (as in the wiki page) to download directly from SourceForge: the master repository is there; this way, there won't be any need to change the Git remote afterwards. That being said, changing the remote to point to the master repository on SourceForge is as easy as running the following command once the clone operation has succeeded:
Code: Select all
(cd /path/to/fgdata && \
git remote set-url origin https://git.code.sf.net/p/flightgear/fgdata)
rominet
 
Posts: 605
Joined: Sat Nov 01, 2014 2:33 pm
Callsign: F-KATS
Version: Git next
OS: Debian GNU/Linux

Re: cloning data error: RPC failed; curl 56 GnuTLS recv erro

Postby powoflight » Mon Oct 19, 2020 2:52 pm

Thanks for your hints
1) @rominet
The first person who reported this apparently had an unstable connection and was able to successfully clone FGData the second time.

Download speed is about 28 M/bits .. Think, this should be ok.

2) @ludomotico
Gitlab and sourceforce set bandwidth limits for unauthenticated connections.

Looks to me logical. As you see beneath

3) I tried for testing download
~/flightgear/Next202010$ /home/bernhard/flightgear/fgmeta/download_and_compile.sh -j4 DATA

Now i am using :
From experience, cloning FGData from SourceForge using https does not work
(probably a problem at SourceForge), but updates do work. Thus, we propose to
clone FGData from GitLab and change the repository setup so that subsequent
updates are fetched from SourceForge. This should be quite safe, because
<https://gitlab.com/flightgear/fgdata> is an official mirror of FGData (it is
maintained by FlightGear developers).
Answer 'y' to proceed this way.
answer 'n', we'll *try* to clone FGData from SourceForge using https.
Answer 'q'if you want to quit.
What is your choice? [Y/n/q] y

Code: Select all
**************** DATA ******************
****************************************
From experience, cloning FGData from SourceForge using https does not work
(probably a problem at SourceForge), but updates do work. Thus, we propose to
clone FGData from GitLab and change the repository setup so that subsequent
updates are fetched from SourceForge. This should be quite safe, because
<https://gitlab.com/flightgear/fgdata> is an official mirror of FGData (it is
maintained by FlightGear developers).
Answer 'y' to proceed this way.
answer 'n', we'll *try* to clone FGData from SourceForge using https.
Answer 'q'if you want to quit.
What is your choice? [Y/n/q] y

Starting special initialization routine for the DATA component...
Fetching FGData with 'git clone https://gitlab.com/flightgear/fgdata.git'
Cloning into '.'...
remote: Enumerating objects: 984, done.
remote: Counting objects: 100% (984/984), done.
remote: Compressing objects: 100% (528/528), done.
remote: Total 74409 (delta 508), reused 874 (delta 432), pack-reused 73425
Receiving objects: 100% (74409/74409), 3.13 GiB | 3.02 MiB/s, done.
Resolving deltas: 100% (43676/43676), done.
warning: remote HEAD refers to nonexistent ref, unable to checkout.

Creating the 'next' local branch
Checking out files: 100% (12994/12994), done.
Branch 'next' set up to track remote branch 'next' from 'origin'.
Switched to a new branch 'next'
Setting FGData's 'origin' remote to https://git.code.sf.net/p/flightgear/fgdata
Updating FGData from https://git.code.sf.net/p/flightgear/fgdata
remote: Enumerating objects: 9, done.
remote: Counting objects: 100% (9/9), done.
remote: Compressing objects: 100% (5/5), done.
remote: Total 5 (delta 4), reused 0 (delta 0)
Unpacking objects: 100% (5/5), done.
From https://git.code.sf.net/p/flightgear/fgdata
   d99b62100..c7c280419  next       -> origin/next
 + 6a72c5a93...2198ccf55 topics/ui  -> origin/topics/ui  (forced update)
Updating d99b62100..c7c280419
Fast-forward
 Environment/environment.xml       |  1 -
 Environment/metarinterpolator.xml | 11 -----------
 2 files changed, 12 deletions(-)
Special initialization routine for the DATA component: done.
Already on 'next'
Your branch is up-to-date with 'origin/next'.
Already up-to-date.
Current branch next is up-to-date.
All optional package alternatives have found a matching package.

download_and_compile.sh has finished to work.

Looks good ...
powoflight
 
Posts: 212
Joined: Fri Mar 25, 2016 11:04 am
Location: LOWW
Callsign: OE-POW
Version: 2020.4
OS: win7 Ubuntu 18.04

Re: cloning data error: RPC failed; curl 56 GnuTLS recv erro

Postby rominet » Mon Oct 19, 2020 3:27 pm

Yes, it worked fine this time. For your 1), it's not a question of speed but of stability (but as ludomotico said, it may be the remote server that closed the connection the first time due to bandwidth limitations!).
rominet
 
Posts: 605
Joined: Sat Nov 01, 2014 2:33 pm
Callsign: F-KATS
Version: Git next
OS: Debian GNU/Linux


Return to Compiling

Who is online

Users browsing this forum: No registered users and 4 guests