The Artima Developer Community
Sponsored Link

Ruby Buzz Forum
Today's conundrum: failure, yet success

0 replies on 1 page.

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 0 replies on 1 page
Daniel Berger

Posts: 1383
Nickname: djberg96
Registered: Sep, 2004

Daniel Berger is a Ruby Programmer who also dabbles in C and Perl
Today's conundrum: failure, yet success Posted: May 18, 2006 2:39 PM
Reply to this message Reply

This post originated from an RSS feed registered with Ruby Buzz by Daniel Berger.
Original Post: Today's conundrum: failure, yet success
Feed Title: Testing 1,2,3...
Feed URL: http://djberg96.livejournal.com/data/rss
Feed Description: A blog on Ruby and other stuff.
Latest Ruby Buzz Posts
Latest Ruby Buzz Posts by Daniel Berger
Latest Posts From Testing 1,2,3...

Advertisement
I was seeing some odd behavior from one of my automated reports. The log file would show a failure, then show that the job had finished successfully. Checking the archive it seemed everything had worked properly. All files that were supposed to be generated were, in fact, generated and placed where they were supposed to be placed.

So, why was the log showing an error? Turns out I had duplicate entries for the same job in the crontab. One job would start, then the second one. The second one would fail, log the error, and die while the first would go on its happy way and complete successfully.

Whoops!

Read: Today's conundrum: failure, yet success

Topic: Rails Featured in Dr. Dobbs Previous Topic   Next Topic Topic: Ruby on Rails featured in Dr. Dobbs

Sponsored Links



Google
  Web Artima.com   

Copyright © 1996-2019 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use