This repository was archived by the owner on Jan 16, 2025. It is now read-only.
This repository was archived by the owner on Jan 16, 2025. It is now read-only.
Running brew update fails with SSL error #46590
Closed
Description
This issue has only started occurring in the past month or two, and I can't figure out what's causing it.
When I run brew update, about 60% of the time, it will fail with an SSLRead() return error -9806. Other times, it will successfully complete the update.
brew config
HOMEBREW_VERSION: 0.9.5
ORIGIN: https://github.com/Homebrew/homebrew
HEAD: 5171f2a0b280fa8675f23f67ba85b99810d1cc44
Last commit: 26 hours ago
HOMEBREW_PREFIX: /usr/local
HOMEBREW_REPOSITORY: /usr/local
HOMEBREW_CELLAR: /usr/local/Cellar
HOMEBREW_BOTTLE_DOMAIN: https://homebrew.bintray.com
CPU: quad-core 64-bit haswell
OS X: 10.10.5-x86_64
Xcode: 7.1.1
CLT: 7.1.0.0.1.1444952191
Clang: 7.0 build 700
X11: 2.7.8 => /opt/X11
System Ruby: 2.0.0-p481
Perl: /usr/bin/perl
Python: /usr/local/bin/python => /usr/local/Cellar/python/2.7.10_2/Frameworks/Python.framework/Versions/2.7/bin/python2.7
Ruby: /usr/bin/ruby => /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/bin/ruby
Java: 1.8.0_60, 1.8.0_31brew doctor
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry and just ignore them. Thanks!
Warning: Unbrewed header files were found in /usr/local/include.
If you didn't put them there on purpose they could cause problems when
building Homebrew formulae, and may need to be deleted.
Unexpected header files:
/usr/local/include/python3.5m/greenlet/greenlet.h
Warning: You have unlinked kegs in your Cellar
Leaving kegs unlinked can lead to build-trouble and cause brews that depend on
those kegs to fail to run properly once built. Run `brew link` on these:
vim
Warning: Your Homebrew is outdated.
You haven't updated for at least 24 hours. This is a long time in brewland!
To update Homebrew, run `brew update`.Regardless of the value of GIT_SSL_NO_VERIFY, the same error occurs. Here is the output of running the brew update --verbose command itself:
brew update --verbose
==> git symbolic-ref --short HEAD 2>/dev/null
master
==> git rev-parse -q --verify HEAD
5171f2a0b280fa8675f23f67ba85b99810d1cc44
git config core.autocrlf false
git pull --ff --no-rebase origin refs/heads/master:refs/remotes/origin/master
fatal: unable to access 'https://github.com/Homebrew/homebrew/': SSLRead() return error -9806
Error: Failure while executing: git pull --ff --no-rebase origin refs/heads/master:refs/remotes/origin/masterMetadata
Metadata
Assignees
Labels
No labels
Type
Projects
Milestone
Relationships
Development
No branches or pull requests
Participants
Activity
DomT4 commentedon Dec 2, 2015
~/.gitconfig?sslCAinfovariable set in your~/.gitconfig?SSL_CERT_FILEenv set?gitare you using? Ours or the system's?blackrobot commentedon Dec 2, 2015
@DomT4 There aren't any proxy settings, or
sslCAinfochanges as far as I can tell, but I've posted the full file here in case I'm missing something: https://gist.github.com/blackrobot/3b1c43fefd103e1ab20dIt is not set.
I'm using the Homebrew version of
git. I've also tried installingcurlwithopenssl, and re-installinggitwith the--with-brewed-curland--with-brewed-opensslflags.DomT4 commentedon Dec 2, 2015
Can't see anything in the
.gitconfigthat would change anything significant to being able to pull. Can you trybrew rm gitand then runbrew updateagain? Will help us narrow it down a bit further.blackrobot commentedon Dec 2, 2015
After removing
git, I still get anSSLRead()error, but with a new error code:36. I'm not sure if it's relevant, but it took just under 10 minutes from entering thebrew updatecommand to receiving the error. I didn't time the previous runs, but they seemed to stall for about the same amount of time.MikeMcQuaid commentedon Dec 4, 2015
What country are you in, out of interest? Can you manually
git clone https://github.com/Homebrew/homebrew/? How aboutgit://github.com/Homebrew/homebrew/?blackrobot commentedon Dec 4, 2015
🇺🇸 USA, in Brooklyn New York.
I can manually clone both, and I've never had issues using git and github directly with my own projects. But, right now
brew updateis behaving normally–as it does intermittently. Later today, I'll trybrew updateagain, and if it fails, I'll immediately try thegit cloneoperations again.MikeMcQuaid commentedon Dec 4, 2015
Sounds like it could be a random connectivity/ISP issue. Not much more we can do to help debug here, sorry. Might be better reaching out to GitHub Support in future.