similar to: Timeout::Error (execution expired)

Hi! I''m on debian. Sending a mail from Rails times out: Timeout::Error (execution expired): /usr/local/lib/ruby/1.8/timeout.rb:54:in `new'' /usr/local/lib/ruby/1.8/net/protocol.rb:206:in `old_open'' /usr/local/lib/ruby/1.8/timeout.rb:56:in `timeout'' /usr/local/lib/ruby/1.8/timeout.rb:76:in `timeout''

I''m writing a functional test to see if an email was generated from a particular action. The action of course sends an email at some point..but the test says it times out. config.action_mailer.delivery_method is set to :test in config/environments/test.rb, not sure why it would be ignoring that. If I take out my email config from environment.rb, the test runs fine. Here''s the

I have a long running task in my Rails app that I plan to run via cron when deployed. The problem is that I''m getting an expiration error when trying to test it out. Is there a way to change this timeout? The trace is included. The system is connecting to Flickr, which takes some time. Timeout::Error (execution expired): /usr/lib/ruby/1.8/timeout.rb:42:in `new''

Where are the memory leaks and what is the way to fix them? I''m working on a game that was fairly stable in terms the memory consumption and it was staying at around 200MB. Recently it has gone crazy, and unless I restart it, it goes straight up to 350-400+MB after 30 minutes-1hour. I am using Apache 1.3+fcgi in production mode. Also the dispatch.fcgi processes take a really high toll

i get his error when using ActionMailer: /usr/local/lib/ruby/1.8/timeout.rb:54:in `new'' /usr/local/lib/ruby/1.8/net/protocol.rb:206:in `old_open'' /usr/local/lib/ruby/1.8/timeout.rb:56:in `timeout'' /usr/local/lib/ruby/1.8/timeout.rb:76:in `timeout'' /usr/local/lib/ruby/1.8/net/protocol.rb:206:in `old_open'' /usr/local/lib/ruby/1.8/net/smtp.rb:393:in

RoR aficionados, I''ve configured ActionMailer for SMTP delivery of emails, and have configured "config/environment.rb" accordingly, including the address of our (external, but fully operational - checked and double-checked :-) SMTP server. Sending out emails from my Windows development laptop works without a hitch, but on a Linux staging server using the exact same source

Hi All, I encountered with following error when i try to send e-mail in production mode. Errno::ECONNREFUSED (Connection refused - connect(2)): /usr/lib/ruby/1.8/net/protocol.rb:206:in `initialize'' /usr/lib/ruby/1.8/net/protocol.rb:206:in `new'' /usr/lib/ruby/1.8/net/protocol.rb:206:in `old_open'' /usr/lib/ruby/1.8/timeout.rb:62:in `timeout''

When I deploy my rails 2.2.2 app to bluehost, I''m having trouble with the ActionMailer SMTP settings. When I attempt to send emails through Rails/SMTP, I get the following error message: getaddrinfo: Name or service not known google says that this means there''s an error negotiating with the mail server. Here are the settings I''m using for SMTP delivery:

One of my actions runs for 2 minutes. In development mode it runs and completes. In production mode it quits out with a timeout error: "Timeout::Error (execution expired):" Any ideas how i can stop this? Thanks Chris -- Posted via http://www.ruby-forum.com/.

There are cases when I have to create the same record 100 times. Is there a faster way than: 100.times{Obj.create(@params[:obj])} ? Bogdan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://wrath.rubyonrails.org/pipermail/rails/attachments/20060226/75d1e099/attachment.html

Hi all, My current conf splits 188 clients execution in one hour, and puppet runs as a cron job. My server (2cpu 2 GB RAM) runs with mongrel (with 8 puppetmasterd) and this conf works fine. We''d like puppet to run clients all at same time (force a change, i.e.), so we''re testing several things. (Previous conf do not support massive execution). First and most important, is

After my action has run for about 2 minutes i always get a timeout. It doesn''t happen with WEBRICK. As far as i can see there is nothing wrong with the code "execution expired RAILS_ROOT: config/.. Application Trace | Framework Trace | Full Trace /opt/tools/lib/ruby/1.8/timeout.rb:54:in `clone_attributes''

I am getting sporadic socket error in actionmailer class. Anyone has solution for this? On refresh the mail is send properly. It does not happen everytime. SocketError in Solution#create_zone getaddrinfo: no address associated with hostname. RAILS_ROOT: C:/DOCUME~1/JONFER~1/LOCALS~1/Temp/tar2rubyscript.d.1424.1/zdc/config/.. Application Trace | Framework Trace | Full Trace

Does it make sense to use the @session to store some values instead of accessing the db on each request? I am trying to optimize the most accessed area, a page that every visitor would access hundreds of times daily. Thanks, Bogdan -------------- next part -------------- An HTML attachment was scrubbed... URL:

I have moved my project to a dedicated server and I am getting a very annoying behaviour. I am able to view the site just fine when using the ip. The name is properly resolved on my computer, however I am getting "Bad Gateway The proxy server received an invalid response from an upstream server." This is simply random. The site works for several minutes, then i get this message for some

Assuming you have Person that has_many :messages, what will it happen if it has 10000 messages? Will rails attempt to initialize @person.messages with 10000 rows from database? If that is the case, is combining finder_sql and counter_sql the common practice to avoid this? Bogdan _______________________________________________ Rails mailing list

1 hour spent and I can''t got explanation why I have "execution expired" when I trying to test this web service: Pointed to: http://localhost:3000/news/list class NewsService < ActionWebService::Base web_service_api NewsApi def list [NewsTopic.new, NewsTopic.new] end end class NewsController < ApplicationController wsdl_service_name ''news''

No ideas? > -----Ursprüngliche Nachricht----- > Von: Bernd Adamowicz > Gesendet: Montag, 16. April 2012 13:32 > An: ''puppet-users@googlegroups.com'' > Betreff: Could not send report: Error 400 on SERVER: execution expired > > Hi all! > > One of my Puppet masters has to compile some 3800 stored configurations > which takes a very long time to

hi, After a "samba-tool drs showrepl" I saw that there had been an error in the replication of ForestDnsZones. I ran a "samba-tool drs replicate dc2 dc3 DC=ForestDnsZones,DC=campus,DC=sertao,DC=ifrs,DC=edu,DC=br -d10" and the error below occurred. ERROR(<class 'samba.drs_utils.drsException'>): DsReplicaSync failed - drsException: DsReplicaSync failed

Hi, I have a puppet infrastructure running 2.6.14 under Passenger with about 30 nodes. I''m just spinning up a new Cent 6.3, puppet 2.7.19 master. Right now I have the master built and configured using the same configuration as my 2.6.14 setup, with a few tweaks for the new version. Puppet on the master built itself fine. I have puppetd stopped on the master. I tried pointing one