Gnutls error in the pull function debian 11

curl: (56) GnuTLS recv error (-54): Error in the pull function. #1707

I did this

I expected the following

no error, wiki.en.zip file saved.

curl/libcurl version

operating system

notes

wget works. date is correct.

The text was updated successfully, but these errors were encountered:

Is this reproducible with just curl? It could be a temporary network problem.

It looks like a temporary network problem. Using that same packaged version in Ubuntu 16 I downloaded 20% in about an hour and the speed was all over the place. It is far too slow for me to complete the whole thing.

Try adding -v to the command and see if that tells something more. If the transfer ends before the 9877MB are transferred (it showed me Content-Length: 10356881301 ), it really should output an error.

Like @jay, I cannot reproduce a problem with this URL, although I built the current git master and ran the command line tool using GnuTLS/3.5.14. I got the whole file downloaded (in my first and only attempt to get the whole thing) in 11m03, at about a 14.8 megabytes/second transfer rate on average.

I tried from another machine with curl 7.47.0 (i586-pc-linux-gnu) libcurl/7.47.0 GnuTLS/3.5.5 and it also managed to download the first part of the file just fine. I didn’t bother to wait for the whole file there.

@bagder Thank you for the tests and details. Here is what happens:

Part of the file has been saved

But not completely, since the whole file is 10356881301B ,

That seems to be an error detected by and returned from a GnuTLS function. I’ve googled around for it a bit but it didn’t give me any clear answers. I think it hints to a problem with that GnuTLS version, possibly in combination with something in your network/environment that makes it trigger for you. It’s hard to know better without a way to reproduce it.

@bagder agreed, there is no evidence that is nothing than a network/env problem, so closing this.

Источник

I tried to reboot the iPhone but it didn’t work. The pair command worked.

I already have the latest ifuse

Ubuntu 16.04, iPhone 5, iOS 10.1.1

The text was updated successfully, but these errors were encountered:

Getting the same. Linux Mint 18, 4.4.0-21 kernel, same version of ifuse as reported above, iPhone 6s, iOS 10.1.1.

This is probably the same as #413?

It would seem so, @borisovg. I note there is supposed to be a bug fix in the code base for that, but the latest release is 1.2.0 from Jan. 28, 2015 (which is what I am running), so I presume I will have to clone and build the lib myself to get the patch. Will queue it up for when I get some free time.

Aaaaannnd. cloned, rebuilt (took some dependency installs, but I got there) and installed, and same error.

Make sure to remove invalidly generated pairing records by deleting the appropriate files or call idevicepair unpair for the affected devices.
Also, mind that usbmuxd might be linked against an older version of libimobiledevice that might still be on the system, thus generating invalid pairing records all over again.

I can confirm that building libimobiledevice and usbmuxd make it work for me (as tested with ideviceinfo ) but I had to remove the relevant Debian packages first.

Are there any plans for a release soon — I doubt we will get a new package in Debian without it. And with the freeze for the upcoming stable coming up very soon it would be great to get this fix into it!

@nikias I did do an unpair and re-pair after I rebuilt the lib. @borisovg I wanted to try removing the existing packages first, but under Mint everything and its dog has this lib as a dependency and it was warning it was going to uninstall Cinnamon(!) and a whole bunch of other packages (see screenshot).

I am sure I can more «surgically» remove the libs with apt, so will try that tonight, hopefully.

@dullroar I feel your pain — I also had to drop gvfs-backends which I’m not happy about. But the alternative is not being able to get at my phone’s photos and videos. 🙁

The real solution is for a release to be published and packaged by Debian, which should in turn filter down to Mint and Ubuntu.

Hello everybody, I have just made a gist to install libimobile and openssl which (for me) fixed the issue with the lockdownd error.

@samrocketman I only ended up rebuilding libimobiledevice plus its pre-reqs (I’ve slept since then and don’t recall everything I had to build to get it to work).

I have moved on, given that the real problem I was trying to solve was getting some images and videos off the iPhone that I ended up unfortunately having to delete, since not even sending them to iCloud or sharing via email or messaging from the phone itself worked for them, and neither did syncing with iTunes on Windows. In all cases the images/videos ended up being not accessible, even to Apple products/iOS itself, even though I could see their thumbnails on the phone. In most cases I had already gotten the images off the phone before the problem showed up by using Dropbox, but in a few cases I just lost them. Sigh,

This ppa work with iOS 10.1 and lower https://launchpad.net/

martin-salbaba/+archive/ubuntu/ppa+libimobiledevice but not with iOS 10.2 ;-( then you are back to the errors. Try it on LinuxMint 18.1 Hope someone can fix it.

© 2023 GitHub, Inc.

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Источник

TLS gnutls_handshake() failed: Error in pull function when using proxy server from client machine. #1920

Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see https://kubernetes.io/docs/tasks/debug-application-cluster/troubleshooting/.):

What keywords did you search in NGINX Ingress controller issues before filing this one? (If you have found any duplicates, you should instead reply there.):

Is this a BUG REPORT or FEATURE REQUEST? (choose one):

NGINX Ingress controller version:

«name»: «nginx-ingress-controller»,
«image»: «quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0»,
«args»: [
«/nginx-ingress-controller»,
«—default-backend-service=$(POD_NAMESPACE)/default-http-backend»,
«—configmap=$(POD_NAMESPACE)/nginx-configuration»,
«—tcp-services-configmap=$(POD_NAMESPACE)/tcp-services»,
«—udp-services-configmap=$(POD_NAMESPACE)/udp-services»,
«—annotations-prefix=nginx.ingress.kubernetes.io»

Environment:

• Cloud provider or hardware configuration: None — Bare-Metal
• OS (e.g. from /etc/os-release): Ubuntu 16.04
• Kernel (e.g. uname -a ): Linux nginx 4.4.0-104-generic

Add configuration and annotation for port_in_redirect #127 -Ubuntu SMP Mon Dec 11 12:16:42 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

What happened: Ingress SSL connections do not work properly when using a proxy server on client machine attempting connections.

Standard http-server -S -C tls.crt -K tls.key -p 443 running on the exposed machine allows the connection through and works just fine.

But when using the nginx-ingress-controller the ssl connection does not establish. To clarify TLS works perfectly in chrome, firefox, iPhone, MacBook, etc. etc. Google crawls the site just fine using the SSL ports etc. But when routed through a proxy server the connection succeeds but there is an error message.

curl -v response below.

HTTP/1.1 200 Connection Established
Proxy replied OK to CONNECT request
ALPN, offering http/1.1
gnutls_handshake() failed: Error in the pull function.
Closing connection 0
curl: (35) gnutls_handshake() failed: Error in the pull function.

When I disabled the nginx-ingress-controller by setting the port to 8080 and 6443 and running the http-server command above and bound to 443 it works just fine.

What you expected to happen:
SSL to work

How to reproduce it (as minimally and precisely as possible):
route traffic through a http proxy server and you will see the error.

Anything else we need to know:
Zscalar is the proxy being used.

The text was updated successfully, but these errors were encountered:

Источник

setup_env failed on Debian8/9 with error «GnuTLS: Error in the pull function»

Bug Description

$ git clone https:/ /github. com/openstack/ refstack- client
$ cd refstack-clent
$./setup_env failed at:
Resolving github.com (github.com). 13.229.188.59, 52.74.223.119, 13.250.177.223
Connecting to github.com (github. com)|13. 229.188. 59|:443. .. connected.
HTTP request sent, awaiting response. 302 Found
Location: https:/ /codeload. github. com/pypa/ virtualenv/ tar.gz/ 15.0.3 [following]
—2018-05-30 11:48:33— https:/ /codeload. github. com/pypa/ virtualenv/ tar.gz/ 15.0.3
Resolving codeload.github.com (codeload. github. com). 13.229.189.0, 13.250.162.133, 54.251.140.56
Connecting to codeload.github.com (codeload. github. com)|13. 229.189. 0|:443. .. connected.
GnuTLS: Error in the pull function.
Unable to establish SSL connection.
+ tar xvfz 15.0.3.tar.gz
tar (child): 15.0.3.tar.gz: Cannot open: No such file or directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error is not recoverable: exiting now
+ rm 15.0.3.tar.gz
rm: cannot remove ‘15.0.3.tar.gz’: No such file or directory

verified on debian 8 and debian 9, both have this issue.

Источник

curl: (56) GnuTLS recv error (-54): Error in the pull function #8343

Failure link

Optional info

Failure output (captured from console output)

The text was updated successfully, but these errors were encountered:

File is clearly present as other pipelines have successfully retrieved and used the same binary download. I found this doing a google search, might be how we have git compiled if it was indeed compiled from source and not via package manager.

Failure happened on ub16-390-6 (or ub16-390-2) once the updated machines configuration is posted.

Updated: AdoptOpenJDK playbook shows we compile from source git v2.15. I believe this only occurs in a faillure/retry situation.

similar #7900 ?
We saw similar errors recently internally on the zlinux Fyre machines. Hasn’t been seen since the network for those instances was fixed, at least not that I am aware.

This is happening quite often and interfering with proper testing and promoting acceptance builds.

re: git
This is curl-ing the file from Artifactory. Nothing to do with Git.

Could be how we’re compiling curl

Although, looking at the zlinux machines, seems they aren’t using playbook curl since version doesn’t match

Not sure what to do. Could remove the -s from the curl and/or add -v temporarily. Could build our own retry & delay since the error seems to change after the build-in retry kicks in.

Источник

@artygus I have to be honest that I’m almost a dummy user at this point and really don’t understand the reason that the author recommend this «custom» installation.

But now I fixed the problem installing some extra dependencies that I found in this post from askubuntu. I’ll leave bellow all the dependencies installed and all steps that took me at this point:

First I separated the packages in a directory to avoid extra problems

$ mkdir -p ~/projects/ios-debug
$ cd ~/projects/ios-debug

Then installed a bunch of dependencies as listed in askubuntu post mentioned above.
Obs: Please tell me if there are some useless/unnecessary deps installed
Obs2: I know there are some deps listed bellow that are already installed in OS, but I was desperate 😂
Obs3: I know that I could install all in one command, just put in this way to make easier to read

$ sudo apt install -y libusbmuxd-dev
$ sudo apt install -y libplist-dev
$ sudo apt install -y libplist++-dev
$ sudo apt install -y libgnutls-dev
$ sudo apt install -y libssl-dev
$ sudo apt install -y usbmuxd
$ sudo apt install -y make
$ sudo apt install -y automake
$ sudo apt install -y autoconf
$ sudo apt install -y libtool
$ sudo apt install -y pkg-config
$ sudo apt install -y gcc
$ sudo apt install -y libusb-dev
$ sudo apt install -y libusb-1.0-0-dev
$ sudo apt install -y libimobiledevice-dev

After this, I installed the libimobiledevice via github:

$ git clone https://github.com/libimobiledevice/libimobiledevice.git
$ cd libimobiledevice
$ ./autogen.sh
$ make
$ sudo make install
$ cd ../ # Back to the ~/projects/ios-debug dir

After I tried to install ios-webkit-debug-proxy from master branch and get the same error from here:

$ git clone https://github.com/google/ios-webkit-debug-proxy.git
$ cd ios-webkit-debug-proxy
$ ./autogen.sh
$ make 
/bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I..  -I../include   -I/usr/local/include -I/usr/include/libxml2 -I/usr/include/libxml2 -g -O2 -Wall -Werror -MT webinspector.lo -MD -MP -MF .deps/webinspector.Tpo -c -o webinspector.lo webinspector.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I../include -I/usr/local/include -I/usr/include/libxml2 -I/usr/include/libxml2 -g -O2 -Wall -Werror -MT webinspector.lo -MD -MP -MF .deps/webinspector.Tpo -c webinspector.c  -fPIC -DPIC -o .libs/webinspector.o
webinspector.c:57:11: error: conflicting types for ‘idevice_connection_get_fd’
 wi_status idevice_connection_get_fd(idevice_connection_t connection,
           ^
In file included from /usr/local/include/libimobiledevice/installation_proxy.h:33:0,
                 from webinspector.c:18:
/usr/local/include/libimobiledevice/libimobiledevice.h:250:17: note: previous declaration of ‘idevice_connection_get_fd’ was here
 idevice_error_t idevice_connection_get_fd(idevice_connection_t connection, int 
                 ^

So I moved to branch libimobiledevice_idevice_connection and now get success on running de debug proxy!

$ git checkout libimobiledevice_idevice_connection
$ ./autogen.sh
$ make
$ sudo make install

$ ios-webkit-debug-proxy
Listening devices on :9221
Connected :9222 to Julio's iPhone.......

I hope this could help and thank you so much for your help @artygus !