Erro in pushing a blueprint - socket.error: [Errno 104] Connection reset by peer

850 views
Skip to first unread message

Rob Morin

unread,
Jan 17, 2012, 12:00:16 PM1/17/12
to bluepri...@googlegroups.com
Hello all , my first post here , so be gentle. :)

I installed blueprint just fine(by source) and created my first blueprint, no problem.... However i go to push the blueprint to the server and i get these errors on the put put.

[root@Web02 log]# blueprint-push Web2.blueprint

# [blueprint] storing source tarballs - this may take a while

Traceback (most recent call last):
  File "/usr/local/bin/blueprint-push", line 36, in <module>
    url = blueprint.io.push(server, secret, b)
  File "/usr/lib/python2.6/site-packages/blueprint/io/__init__.py", line 85, in push
    server=server)
  File "/usr/lib/python2.6/site-packages/blueprint/io/http.py", line 54, in put
    return _request('PUT', path, body, headers, server)
  File "/usr/lib/python2.6/site-packages/blueprint/io/http.py", line 29, in _request
    raise e
socket.error: [Errno 104] Connection reset by peer

This is on a RedHat 6.2 instance at AWS..

[root@Web02 log]# cat /etc/redhat-release
Red Hat Enterprise Linux Server release 6.2 (Santiago)

[root@Web02 log]# uname -a
Linux ip-10-6-62-66 2.6.32-220.2.1.el6.x86_64 #1 SMP Tue Dec 13 16:21:34 EST 2011 x86_64 x86_64 x86_64 GNU/Linux

git-1.7.1-2.el6_0.1.x86_64
python-2.6.6-29.el6.x86_64

/var/log/messages logs show..

Jan 17 10:56:59 ip-10-6-xx-xx python2.6: abrt: detected unhandled Python exception in /usr/local/bin/blueprint-push
Jan 17 10:58:15 ip-10-6-xx-xx abrtd: New client connected
Jan 17 10:58:23 ip-10-6-xx-xx abrt-server[2219]: Message is too long, aborting

Any suggestions??

Thanks!


Any ideas, i was so excited to get this going, and now i am stuck....



Richard Crowley

unread,
Jan 26, 2012, 1:27:34 AM1/26/12
to bluepri...@googlegroups.com

Hi Rob,

First off, I'm sorry for the delay in my reply.

My best guess from looking at access logs is that your blueprint
contains a tarball that's beyond the service's 64 MB limit. This is
easy to blow past if you're not careful of what's in /usr/local.

Run `blueprint show -S foo` (where `foo` is your blueprint's name) and
see how large the tarball(s) in foo/ are.

Run `blueprint show-sources foo` to list the files being included and
put lines like this in /etc/blueprintignore to fine-tune it:

source:/usr/local/foo/bar
source:/usr/local/baz

I hope that helps,

Richard

kv

unread,
Mar 20, 2012, 7:47:41 AM3/20/12
to bluepri...@googlegroups.com
Richard,

I'm running this on a Ubuntu AMI on Amazon EC2. Just normal system utilities are installed.
The tarball size is a whopping 415 MB.
Excluding packages as you have suggested does not seem to be practical as it would quickly become messy.

There's no documentation of how to increase the accepted request body size for gunicorn either.
Any suggestions?

- KV

Reply all
Reply to author
Forward
0 new messages