Not sure if this should be in thisforum or the feature requests.

We have several file triggers which look for the presence of a file in order to fire the job/task.

Following a reboot all of these become inactive causing jobs to then not run, pls could this be resolved as it is causing jobs to be missed.


Thank you.


Graham

Are you watchine local or remote folders? Can you plese send the log to support@visualcron.com.

---

Ditto. I'm having the same exact problem. Seems like a relatively minor thing, but it is causing alot of headache. A quick fix would be GREATLY appreciated! I'm sending the server log.

Edit: I think it *might* have something to do with using the UNC path, and not an absolute or relative drive-letter path. I could be wrong, though.

Thanks,

Mike

The log file you sent seems to concern that you restart a remote computer (not local). Am I right? VisualCron will try to reconnect but it can't try forever. There are rules how long and how often of course. You can adjust these reconnect settings in the file trigger. By default, it is configured for a short downtime.

---

Henrik,

So the error reconnect interval is how long it will try before it deactivates itself? I thought it was how long in between each try. Which one is it?

Thanks,

Mike

It tries 3 times, with the interval you specify.

---

Ahhh.. got it. Thanks for clearing that up. Maybe the number of tries should also be a parameter? With the option to "try forever".

Thanks again, Henrik.

Try forever is not good because then you loose control at the client. But I agree that we could add the try x times as a parameter. Should not be a big thing to add.

---

As a temporary work-around for the file triggers becoming inactive, has anyone found a way, or can think of a way, to create a job/task that checks for certain triggers being inactive, and activates them? I can't seem to find anything in the existing task types to do this. Any help would be greatly appreciated!!

Thanks in advance,
Mike

I would extend the retry interval. The default values are quite short if you loose a connection. You do that in the file trigger properties. Also, check the logs and compare to the event viewer - perhaps you are experiencing something special during that time.

---

It appears that "on error reconnect attempts" will not accept a value larger than three, when saved. Is this still in the works, or is this as far as it will go? (I have already extended the reconnect interval, but would much prefer being able to also extend the number of reconnect attempts.)

In the case of an extended outage, and there is no way to avoid having the triggers inactivated, it would also be very nice to have a job control job (or some other means) to be able to go through and reactivate all the triggers after the outage is over.

What exactly is the status of this issue ? We have 4.9.3 installed and this problem occurs each time a remote server being monitored by a file trigger gets restarted. We have to go and manually reactivate all the triggers (lots of work).

We have tried increasing the retry count to 10 with a 500 second delay and it still does not work, even though the remote server is available within that delay.

I could post a log if that would help.

Any ideas ?

Thanks.

A log file would be great. You can send it to support@visualcron.com

---

We found some issues and we have tested this a lot more. Fixes has been made in version 4.9.8. which can be downloaded here:

http://www.visualcron.com/forum/default.aspx?g=posts&t=163 

---