# Socket errors when using igem

**URL:** <https://www.ruby-forum.com/t/socket-errors-when-using-igem/178205>\
**Category:** IronRuby\
**Created:** [October 30, 2009, 7:17pm UTC](https://www.ruby-forum.com/t/socket-errors-when-using-igem/178205 "2009-10-30T19:17:26Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![confundido](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/90ced4/32.png) [@confundido](https://www.ruby-forum.com/u/confundido)\
**Post date:** [October 30, 2009, 7:17pm UTC](https://www.ruby-forum.com/t/socket-errors-when-using-igem/178205/1 "2009-10-30T19:17:26Z")

</div>

Does anyone else get a lot of socket errors when using igem? I often  
have to run igem a few times to get a successful install.

---

<div class="post-metadata">

**Author:** ![confundido](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/90ced4/32.png) [@confundido](https://www.ruby-forum.com/u/confundido)\
**Post date:** [October 31, 2009, 12:33am UTC](https://www.ruby-forum.com/t/socket-errors-when-using-igem/178205/2 "2009-10-31T00:33:03Z")

</div>

Nathan, I’ve never gotten that, though I have gotten timeouts of some  
sort in the past.  
I’m sure you’ve tried this already, but grab the same gem using just  
“gem” vs. “igem”  
Are you getting the result more from 1 particular gem source?  
What are the exact errors you’re getting? Thanks

Best Regards,  
Kevin

On Fri, Oct 30, 2009 at 12:05 PM, Nathan Stults

---

<div class="post-metadata">

**Author:** ![confundido](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/90ced4/32.png) [@confundido](https://www.ruby-forum.com/u/confundido)\
**Post date:** [October 31, 2009, 12:45am UTC](https://www.ruby-forum.com/t/socket-errors-when-using-igem/178205/3 "2009-10-31T00:45:22Z")

</div>

Kevin, it usually works OK with gem - and I believe I get these socket  
errors only with gemcutter. That is my impression anyway, but I will  
keep a closer eye on it. I can usually get always get the gem down after  
a few tries, and it doesn’t seem to be more prevalent on big gems or  
anything, seems pretty random. You know, I’m not sure I’ve added  
gemcutter to my ruby install, just my IR install - so maybe I would get  
these with gem as well? I’ll be more observant about when and under what  
conditions I get the error. If nobody else is experiencing this,  
however, it’s probably an issue between my network and the gem  
repository.