comment on

What I'm trying to figure is what element of that would cause the script to fail in cron on one server but not the other. My feeling is that it's the database client.

The error message is supposed to tell you that :)

No error message? Adjust cron error reporting, check your mail, ...

Still no error message? Increase verbosity (maybe use Carp::Always; or twiddle some logging levels or $DEBUG++/$VERBOSE++, whatever you're using

Still no error message? Maybe redirect errors to a logfile ?

Once you have an error message, you can check the usual (everything, sanity check), $PATH/$LD_LIBRARY_PATH..., chroot jail,selinux, permissions and password typos, shebang ... its a checklist, error message usually tells you what to check

Like the deep links from Re: Cron revisited/Re^2: Perl Module Not Working In Crontab explain, and here they are:

In reply to Re^4: Cron revisited by Anonymous Monk
in thread Cron revisited by tweetiepooh

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


No such thing as a small change
	PerlMonks