similar to: Execution Expired when running a script

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, I''m using a webservice in my application. How can I make it so that my application will only try to connect to the webservice for a certain period of time and then give up? Right now my code is using a begin-rescue-else but sometimes I get a "execution expired" error if the webservice is not available or takes too long to respond. Thanks, Peter begin service =

Hey there! All my clients have gone "out of sync" are have the following line in the puppet.out log file... err: Could not send report: Error 400 on SERVER: execution expired The clients appear to not be updating either... I have restarted the Puppet Master to no avail... Any help appreciated! -- You received this message because you are subscribed to the Google Groups

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/.

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''ve been constantly getting in the recent days: Timeout::Error (execution expired): /usr/lib/ruby/1.8/timeout.rb:54:in `new'' /usr/lib/ruby/1.8/net/protocol.rb:206:in `old_open'' /usr/lib/ruby/1.8/timeout.rb:56:in `timeout'' /usr/lib/ruby/1.8/timeout.rb:76:in `timeout'' This has started one or two days ago, and never before. It is

Hi Guys, I am trying to executed sign client to server, I give the command to client #puppetd --test -d -v debug: /File[/var/lib/puppet/ssl/private_keys]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/var/lib/puppet/ssl/certs]: Autorequiring File[/var/lib/puppet/ssl] debug: Finishing transaction 23595599384520 err: Could not request certificate: execution expired Exiting; failed to

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''

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''

Hi everyone, I recently ran into an issue where my puppetmaster can''t run puppet on itself. It errors out with the following: Error: Could not retrieve catalog from remote server: execution expired Warning: Not using cache on failed catalog Error: Could not retrieve catalog; skipping run I''m running Puppet 3 with passanger and puppetdb (hsql). I''ve tried restarting

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

Hello, I have a program that takes blog urls that our customers enter into their profiles. In some cases they enter bad feeds (IE html pages instead of atom or rss), and it throws these two errors: execution expired and bad URI errors in the view. I need to find a graceful way to handle both. Preferably, if I could find a way to throw an error message for the execution expired

Almost 4-5% of the total number of nodes are not receiving catalog from the master on an hourly run. We have about 250 nodes. The nodes that are receiving this error are rather random. The hourly cron happens almost at the same time. Is there any configuration changes for Puppet that can be done to avoid this ? Puppet (err): Could not retrieve catalog from remote server: execution expired

On Fri, 2023-10-27 at 10:44 +0200, Kees van Vloten wrote: > Hi Andrew, > > > Op 27-10-2023 om 02:22 schreef Andrew > Bartlett: > > > > > > > I'm sorry to say that from here you really need to work > > closely with a Samba developer (eg via a commercial support > > provider) or do a deep

Hi Andrew, Op 27-10-2023 om 02:22 schreef Andrew Bartlett: > I'm sorry to say that from here you really need to work closely with a > Samba developer (eg via a commercial support provider) or do a deep > dive into debugging yourself. > > Ideally if you have time, do a git bisect between the last known > working version and the first failing one. ?That may find the >

Hi I just installed EA 9 Trial version. I can't get running it further than splash screen. At this point EA says the evaluation period has expired! But this couldn't be true since EA was downloaded and installed today. However the screen offers 2 buttons "Continue Trial" or "Buy". If I choose "Buy" nothing happens at all. Otherwise the application will

[.. most data for the archives ..] I've got several windows 2000 machines and a samba 2.2.12 on solaris 7. for years only one of the windows machines has ever needed to connect to the samba server. just a couple of days ago, it was necessary for a second machine to connect to the samba server. Whenever the second machine tried to load the network share, windows came back with its "The

https://bugzilla.samba.org/show_bug.cgi?id=6061 Summary: [FMR]: Add an option to only delete files once they expire Product: rsync Version: 3.0.4 Platform: x86 OS/Version: Linux Status: NEW Severity: enhancement Priority: P3 Component: core AssignedTo: wayned@samba.org

I am running Debian 'woody' with Samba 3.0.2 and am having a sparatic problem on my network. Some users will suddenly lose their connections to the samba shares and when trying to log in to the system again will get an error that windows cannot locate their roaming profile - "Semaphore time period has expired". It seems that if they wait for about 15 minutes they can then

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