search

mietek / haskell-on-heroku

Buildpack for deploying Haskell apps
BSD 3-Clause "New" or "Revised" License
131 stars 16 forks source link

Halcyon download failing with 503 error #38

Closed iand675 closed 9 years ago

iand675 commented 9 years ago

When I use the hello-yesod example project, I get the following console output:

-----> Fetching custom git buildpack... done
-----> Haskell app detected

-----> Deploying with Haskell on Heroku
       BUILDPACK_URL:                            https://github.com/mietek/haskell-on-heroku

-----> Installing buildpack... done, fff7dba
-----> Installing Halcyon... done, 09001ce
-----> Installing bashmenot... done, 0016251
-----> Archiving app source
       Creating buildpack-app-source.tar.gz... done, 4.0KB
-----> Deploying environment
       GHC version:                              7.8.3
       Cabal version:                            1.20.0.3
       Cabal repository:                         Hackage
       External storage:                         public

-----> Restoring GHC directory
       Downloading https://halcyon.global.ssl.fastly.net/linux-ubuntu-14.04-x86_64/halcyon-ghc-7.8.3.tar.gz... 503 (service unavailable)
   *** WARNING: Cannot build GHC directory
   *** WARNING: Cannot deploy environment

-----> Buildpack deployed

-----> To build the app, use a one-off PX dyno:
       $ heroku run --size=PX build

       Next, deploy the app:
       $ git commit --amend -C HEAD
       $ git push -f heroku HEAD:master

-----> Discovering process types
       Procfile declares types -> (none)

-----> Compressing... done, 917K
-----> Launching... done, v4
       https://immense-dusk-5793.herokuapp.com/ deployed to Heroku

To git@heroku.com:immense-dusk-5793.git
 * [new branch]      master -> master

You'll notice that downloading Halcyon fails in the 'Restoring GHC directory' step. It looks like it's an SSL handshake issue, AFAICT.

mietek commented 9 years ago

Thanks for the report. Note Halcyon is already installed (line 8); the problem is a failure to download the GHC directory archive.

Just pushed https://github.com/mietek/halcyon/commit/5e1667dcde33e88ee339b0fdb917daae4ef448eb, switching back to using S3/CloudFront directly for public storage. Let me know if this helps.

mietek commented 9 years ago

Resolved.

mietek commented 9 years ago

The SSL handshake timeout in Fastly’s configuration has been increased, and as of https://github.com/mietek/halcyon/commit/4324f14c6020abe6b5b5f5c5f293dde2138fee33, Halcyon is back to using Fastly.