Re: Unable to determine error source

2011-02-15 Thread Mike Blezien
- Original Message - From: "Rob Dixon" To: Cc: "Mike Blezien" Sent: Monday, February 14, 2011 10:29 PM Subject: Re: Unable to determine error source On 14/02/2011 16:10, Mike Blezien wrote: I have a script that has been generating a strange error that I ca

Re: Unable to determine error source

2011-02-14 Thread Rob Dixon
On 14/02/2011 16:10, Mike Blezien wrote: I have a script that has been generating a strange error that I can't seem to find the source. In the script, at the top, we have the following to help trouble shoot it if any errors: #!/usr/bin/perl BEGIN { open (STDERR, ">./scriptname_error.log"); } I

Re: Unable to determine error source

2011-02-14 Thread Shawn H Corey
On 11-02-14 11:10 AM, Mike Blezien wrote: Invalid offset: And that's it. Normally it will indicate the line#, date, detailed error, etc., like in the apache error_log file. but this is all it shows. This is a cron script also. "Invalid offset" is not a Perl error message. Try scanning your

Unable to determine error source

2011-02-14 Thread Mike Blezien
Hello, I have a script that has been generating a strange error that I can't seem to find the source. In the script, at the top, we have the following to help trouble shoot it if any errors: #!/usr/bin/perl BEGIN { open (STDERR, ">./scriptname_error.log"); } In the error_log file it generates