We have jobs set up to download files from our partner's ftp sites. We have the job set up to retry on job failure. It is set up to wait 3600 seconds (1 hour) and retry three times. However, on job failure the job retries multiple times. we have the job set up to email our programming support people on job failure. We received 204 emails within an hour. I have checked the job log and it has tried over and over again instead of waiting 3600 seconds. What can we do to correct this?

How this job is scheduled?

: We have jobs set up to download files from our partner's ftp sites. We have
: the job set up to retry on job failure. It is set up to wait 3600 seconds
: (1 hour) and retry three times. However, on job failure the job retries
: multiple times. we have the job set up to email our programming support
: people on job failure. We received 204 emails within an hour. I have
: checked the job log and it has tried over and over again instead of
: waiting 3600 seconds. What can we do to correct this?

: How this job is scheduled?
It is set to run Mondays at 1:00 pm.
to send an email message on job error.
to restart the job if it fails.
restart in 3600 seconds retries 3.

Which 24x7 version are you running?

: It is set to run Mondays at 1:00 pm.
: to send an email message on job error.
: to restart the job if it fails.
: restart in 3600 seconds retries 3.

: Which 24x7 version are you running?
3.4.0

Please upgrade to a more recent version. I believe this issue has been fixed.

PS. The upgrade is free. Here is the download link
http://www.24x7automation.com/download/247upg.exe

: 3.4.0

I've got the same problem with version 3.4.11
Is it likely to have been fixed with the 3.4.12 version?

: Please upgrade to a more recent version. I believe this issue has been fixed.

: PS. The upgrade is free. Here is the download link
: http://www.24x7automation.com/download/247upg.exe

Sorry I wanted to paste http://www.softtreetech.com/cgi_bin/config.cgi?review=2510

: I've got the same problem with version 3.4.11
: Is it likely to have been fixed with the 3.4.12 version?

There was a job configuration issue causing quick retries which was fixed in 3.4.2 or 3.4.3.

Because Dennis did not post a new message since 8/19/2003, after it was suggested to him to upgrade, I assume his problem has been fixed. Otherwise, why didn't he post then?

Maybe you are experiencing a similar in nature but not exactly the same problem. Please let us know more about your job setup and design so we can start helping you.

By the way, take a look at http://www.softtreetech.com/cgi_bin/config.cgi?review=4344
In that message thread we were discussing a workaround for the retry issues.

: I've got the same problem with version 3.4.11
: Is it likely to have been fixed with the 3.4.12 version?

The job is set to run at 7:30 PM. Retry once after 300 seconds.
I see it is a different type of problem though.
When I try the same job settings with:

RaiseError("test")

as the jal script it works fine.

When I change the script to:

Dim listing, string
FTPDir( "1.2.3.4", "anonymous", "24x7@", "/*.*", listing )

the job runs once. When it retries the second time
it gets in a loop and adds the job to the queue +-50 times
and then starts to run each job.
That is of course when it cannot connect to the Ftp "1.2.3.4"

: There was a job configuration issue causing quick retries which was fixed in
: 3.4.2 or 3.4.3.

: Because Dennis did not post a new message since 8/19/2003, after it was
: suggested to him to upgrade, I assume his problem has been fixed.
: Otherwise, why didn't he post then?

: Maybe you are experiencing a similar in nature but not exactly the same
: problem. Please let us know more about your job setup and design so we can
: start helping you.

: By the way, take a look at
: http://www.softtreetech.com/cgi_bin/config.cgi?review=4344
: In that message thread we were discussing a workaround for the retry issues.

Because you have FTPDir, I assume you also have a loop in your script to process returned file list. Could it be that the problem is caused by that loop logic? Is the job setup to ignore errors?

Please try the following

...[your other code here]...
Dim ErrorMessage, String
OnErrorGoto ERROR_HANDLER

FTPDir( "1.2.3.4", "anonymous", "24x7@", "/*.*", listing )
...[your other code here]...

Exit

ERROR_HANDLER:
GetLastError( ErrorMessage )
OnErrorStop
RaiseError( ErrorMessage )

Please let me know if that does not help.

: The job is set to run at 7:30 PM. Retry once after 300 seconds.
: I see it is a different type of problem though.
: When I try the same job settings with: RaiseError("test")

: as the jal script it works fine.

: When I change the script to: Dim listing, string
: FTPDir( "1.2.3.4", "anonymous", "24x7@",
: "/*.*", listing )

: the job runs once. When it retries the second time
: it gets in a loop and adds the job to the queue +-50 times
: and then starts to run each job.
: That is of course when it cannot connect to the Ftp "1.2.3.4"

I tried modifying the script as suggested but it
didn't make any difference.

There is a loop to process the listing but the loop
works fine if I use Run Now to run the job.
Only when the job retries is it giving me a problem.
It couldn't be the logic since after reducing the
script to only the two lines Dim...FtpDir it still
Queues the job repeatedly.

The job isn't set up to ignore errors.

: Because you have FTPDir, I assume you also have a loop in your script to
: process returned file list. Could it be that the problem is caused by that
: loop logic? Is the job setup to ignore errors?

: Please try the following

: ...[your other code here]...
: Dim ErrorMessage, String
: OnErrorGoto ERROR_HANDLER

: FTPDir( "1.2.3.4", "anonymous", "24x7@",
: "/*.*", listing )
: ...[your other code here]...

: Exit

: ERROR_HANDLER: GetLastError( ErrorMessage )
: OnErrorStop
: RaiseError( ErrorMessage )

: Please let me know if that does not help.

I cannot reproduce this issue. Let start from beginning.

1. The job is setup to retry 3 times with a 1 hour wait. Which means in the worst case the job will run 4 times.

2. How this job is scheduled to run?
If you have 3 hours window for all retries you cannot setup this job to run with a less than 3 hour and 1 minute time interval between normal runs?

3. How long does it take for the job to fail? I mean how long does it take for FTPDir to connect to your FTP server and then fail?

4. Are there other FTP jobs?

5. Are there other jobs that rigger your FTPDir job explicitly if they do not find some dependencies created by FTPDir?

6. Have you tried upgrading to a more recent version?

: I tried modifying the script as suggested but it
: didn't make any difference.

: There is a loop to process the listing but the loop
: works fine if I use Run Now to run the job.
: Only when the job retries is it giving me a problem.
: It couldn't be the logic since after reducing the
: script to only the two lines Dim...FtpDir it still
: Queues the job repeatedly.

: The job isn't set up to ignore errors.

I have tried upgrading to version 3.4.12.
Maybe you
could try run this test job
http://www.das.co.za/data/retry_test.dat
and see if you don't get the same problem?

There are no inter-dependent jobs or other ftp
jobs running at the same time.

: I cannot reproduce this issue. Let start from beginning.

: 1. The job is setup to retry 3 times with a 1 hour wait. Which means in the
: worst case the job will run 4 times.

: 2. How this job is scheduled to run?
: If you have 3 hours window for all retries you cannot setup this job to run
: with a less than 3 hour and 1 minute time interval between normal runs?

: 3. How long does it take for the job to fail? I mean how long does it take
: for FTPDir to connect to your FTP server and then fail?

: 4. Are there other FTP jobs?

: 5. Are there other jobs that rigger your FTPDir job explicitly if they do not
: find some dependencies created by FTPDir?

: 6. Have you tried upgrading to a more recent version?

Ok, I now can reproduce it and agree that something weird is going on.
I will continue looking into this and get back to you as soon as I have any explanation for this effect or a good workaround.

By the way, I also tried to set this job to run asynchronous and it didn't event attempt to retry after first failure.

: I have tried upgrading to version 3.4.12.
: Maybe you
: could try run this test job
: http://www.das.co.za/data/retry_test.dat
: and see if you don't get the same problem?

: There are no inter-dependent jobs or other ftp
: jobs running at the same time.