Topic: error in capistrano deployment for media temple
every cap command i run, i get the following error
c:/ruby/lib/ruby/gems/1.8/gems/net-ssh-1.0.10/lib/net/ssh/transport/version-negotiator.rb:51:in `readline': end of file reached (EOFError)
You are not logged in. Please login or register.
Rails Forum - Ruby on Rails Help and Discussion Forum » Other Rails Programming » error in capistrano deployment for media temple
every cap command i run, i get the following error
c:/ruby/lib/ruby/gems/1.8/gems/net-ssh-1.0.10/lib/net/ssh/transport/version-negotiator.rb:51:in `readline': end of file reached (EOFError)
*update, i had an error in my set :domain statement.
*update, i had an error in my set :domain statement.
Does this mean you figured out the cause of the problem, or are you still stuck?
--Arman.
oh yeah, i got it working.
thanks.
did you register just to see if my problem was fixed?
that's pretty amazing either way.
I agree - good service from (mt) there ![]()
I had an gs account with (mt) for them for a while but PHP performance was too low for my liking and never got around to trying to Rails. But service was excellent (despite having to submit three cancellation requests
)
Hey Arman,
Maybe you can help out with this ticket I've had sitting out for over a week?
ID#: 221091
It's related to this thread:
http://railsforum.com/viewtopic.php?id=4505
I like the service at (mt) well enough, but I'm going to have to move over to Slicehost pretty soon. I've been bitten by 2 problems I consider to be shortcomings of Media Temple, and I'm not sure I'll stick around to take a 3rd.
Sidenote: Here's a Capistrano recipe that I've found to work pretty well: http://www.almosteffortless.com/2007/01 ia-temple/
Thanks!
Last edited by trevorturk (2007-04-11 00:36:57)
@smoothoperatah: Glad to hear your problem's been fixed! I did register just to see if you still needed some help. I'm sure I'll be using this forum again in the future anyway. ![]()
@trevorturk: Your ticket was answered on Monday by one of our main developers. From the details of the request, it appears that we paid special attention to your issue and got a developer involved to take a closer look. I'd rather not disclose the details of your issue here, but it definitely has not been a week since we've updated your request. I will see if there's anything else our developer can help you with.
Thanks!
--Arman.
Arman, thanks for your response. I didn't mean that nobody at MT had contacted me for a week - just that the issue I'm having has remained unsolved for that long.
Unfortunately, it seems that the issue I'm having is not going to be fixed on MT's side. I'm going to post to the Rails Deployment mailing list again with more detail to see if someone can help me over there.
I'm still suspicious that there is something wrong with the MT Apache configuration, but I do appreciate the developers taking the time to work with me.
Thanks again.