I am using 24x7 scheduler version 3.4.22. I have it running as a service. It looks once a minute for a semephot file. If it sees it, it deletes it and syncs a local directory with an FTP site.

Normally it runs fine, but if it sits for a long period (ie longer than a day or so) without a semephor file being created, it stops looking for it. When we do create a semephor file, it will not kick off the process. I must delete the semephor file, stop and start 24x7, then recreate the semephor file for it to work normally.

Is there any known issusesand/or fixes that address these symptoms?

This sounds like a problem with the network connection.

Create a debug job to copy a file from the same network share to the local computer and set it to run every minute. Let it run for a few days and then check at what time it stops running. Warning: Put this job int oa separate job queue so that when it will stop it will not block other jobs!

: I am using 24x7 scheduler version 3.4.22. I have it running as a service. It
: looks once a minute for a semephot file. If it sees it, it deletes it and
: syncs a local directory with an FTP site.

: Normally it runs fine, but if it sits for a long period (ie longer than a day
: or so) without a semephor file being created, it stops looking for it.
: When we do create a semephor file, it will not kick off the process. I
: must delete the semephor file, stop and start 24x7, then recreate the
: semephor file for it to work normally.

: Is there any known issusesand/or fixes that address these symptoms?

: This sounds like a problem with the network connection.

: Create a debug job to copy a file from the same network share to the local
: computer and set it to run every minute. Let it run for a few days and
: then check at what time it stops running. Warning: Put this job int oa
: separate job queue so that when it will stop it will not block other jobs!

Actually, this is running on an IIS box with Cold Fusion. A webpage creates the semephor file on the hard drive (local) where 24x7 is looking for it. It all happens on the same box. The semephor file is created properly, but 24x7 never seems to even look for it (after it's been dormant for a while per my original post).

I have combed the 24x7 log files, and have not seem it try to look. I have looked in the event viewer, and have not seen 24x7 throw any errors.

Did you check Windows NT Application Event Log for relevant messages?
Does it run other jobs while the semaphore file is present and ignored?

: Actually, this is running on an IIS box with Cold Fusion. A webpage creates
: the semephor file on the hard drive (local) where 24x7 is looking for it.
: It all happens on the same box. The semephor file is created properly, but
: 24x7 never seems to even look for it (after it's been dormant for a while
: per my original post).

: I have combed the 24x7 log files, and have not seem it try to look. I have
: looked in the event viewer, and have not seen 24x7 throw any errors.

: Did you check Windows NT Application Event Log for relevant messages?
: Does it run other jobs while the semaphore file is present and ignored?

Yes, I checked the event log as well as the 24x7 logs. I do not know if other jobs will run, as we use it exclusively for this type of task.

We sync several different dirs with FTP sites depending on the semephor file created. None of the semephor files are recognized when it starts acting up.

I will try to create a job that checks for a semephor file every 15 mins or so as a "keep alive" type job and have it log when it finds it, as suggested in your previous post.

I don't think this will shed any light, as you already know it will stop at some point.
I would like to suggest setting all jobs to run detached. This should free the queue. Also set different jobs to run in different queues to prevent them from blocking each other.

PS. The reason you don't see any errors in the log is that the logging is probably tuned off for these jobs, this is a default for frequently running jobs. If this is the case turn it on while you are troubleshooting the issue..

: Yes, I checked the event log as well as the 24x7 logs. I do not know if other
: jobs will run, as we use it exclusively for this type of task.

: We sync several different dirs with FTP sites depending on the semephor file
: created. None of the semephor files are recognized when it starts acting
: up.

: I will try to create a job that checks for a semephor file every 15 mins or
: so as a "keep alive" type job and have it log when it finds it,
: as suggested in your previous post.

: I don't think this will shed any light, as you already know it will stop at
: some point.
: I would like to suggest setting all jobs to run detached. This should free
: the queue. Also set different jobs to run in different queues to prevent
: them from blocking each other.

: PS. The reason you don't see any errors in the log is that the logging is
: probably tuned off for these jobs, this is a default for frequently
: running jobs. If this is the case turn it on while you are troubleshooting
: the issue..

I have upgraded my hardware and 24x7 since the last reply to this thread, but have not had any luck. Nothing in the 24x7 logs (I made sure logging was turned on) or windows event logs. The "Keep ALive" process I made checks for a file that is never deleted and writes the date/time to that file, so I can pin point when it happens, but no other info. I have all jobs running as detatched and in their own queues. It could go for days before acting up, but it never happens more than once in 24 hours. In other words, if it acts up and I restart 24x7, it will not happen again for atleast a day, usually not for a week or more.