I have seen in other posts that if you set up a file event trigger and it keeps getting shut down that you need to change the reconnect interval. What is a resonable setting for this? We have had this issue for a while now and we have our jobs set to

reconnect attempts = 5
reconnect interval = 120 (seconds).

Do we need to go up to 10 attempts?

Robert

One other thing, When we look at the log for the job, we get the following error

Error watching directory, err: Object reference not set to an instance of an object.

Are you wathing a Samba share or Windows folder?

---

yes, we have Use polling (Samba compatible) checked

Yes, but I just want to confirm that this is a Samba share you are monitoring as well - not windows.

---

Correct, we are watching our ftp server which is a Samba share

Could you post a screenshot of your settings?

---

Here are the two pages of the settings.

Thanks, forgot these questions:

1. do you have a lot of file triggers?
2. do you see any pattern in when or after how long this occurs?

---

3. Has the remote server been restarted when this happens?

To your original question. The values should match a restart time so VisualCron will try to connect during downtime.

What concerns us is the error that does not mean anything and should be handled better.

---

we have 52 jobs set up. 20 of those are file triggers. In the past we have had impersonation errors. We changed the login for the VC service. Then today we are getting the "Object reference not set to an instance of an object". Always a well descriptive error message.

I am trying to look for a history of the job logs, but seem to only see the most current one through the GUI. Do you guys keep any kind of job log history that I can browse to see the history of our file trigger errors?

Robert

No Job history yet (only log files). We are currently reviewing how that Job history should work.

1. do you believe that this error was caused by recent change of VC service login?
2. do you only receive errors on some of your triggers?
3. does the triggers start working properly after enabling them?
4. can you reproduce the problem in any way?

---

I just spoke with my Infrastructure team and they say that server never gets restarted. It is a Linux server

Answers to your questions.

1. do you believe that this error was caused by recent change of VC service login?
- I don't know. They have been running good for awhile and then just failed today. They seem to run good for awhile and then just fail one day. We re-enable them and then they run for awhile and then fail again. I am going to have our support team start keeping a log of when they fail, what job they fail on, and what the error message was.

2. do you only receive errors on some of your triggers?
- Yes all of them got the Object reference error this time.

3. does the triggers start working properly after enabling them?
- Yes

4. can you reproduce the problem in any way?
- No, we just know to re-enable the triggers and then they run for awhile and then quit.

What is interesting is answer 2. where you say that you get the same errors on all of them. Since each Trigger is run in a separate thread in VisualCron they should not affect each other. This indicates that something is happening at network or server level when this happens.

We will continue investigation from here by adding more debugging. Please come back with results from your side.

---

Update on this. We had 5 jobs have their file triggers disabled with the following error

Error watching directory, err: Object reference not set to an instance of an object., Could not UpdateFileTrigger in Trigger: '<file trigger name>', ex: Object reference not set to an instance of an object.

Do you see any reconnection attempts in the log?

---

Here is a screen shot of the log of one of the jobs

It is hard for us to say what the problem is but VisualCron gets the errors that are in the screenshot. Perhaps there is a problem with the device, you are restarting it or something with the network.

---