Please note that VisualCron support is not actively monitoring this community forum. Please use our contact page for contacting the VisualCron support directly.


keithdavis
2009-06-24T19:54:32Z
This is a tough one, and it's happened twice now. The last one went as follows. I set up a job on VC a long time ago. I thought it was working, not sure now. I added an email notification from VC and from the application that the job is running. The job fires off a VB .NET app that is just a web browser and passes a command line argument, where PHP runs a function.

The tests beforehand on the PHP function worked fine. I did not run the VC job manually to test (it would cause problems for my users.) Last night at 2:03, VC emailed me that the job ran. However, the PHP class did not send me an email. This morning, I fired the job manually, by selecting it in VC and clicking Run Job. This time I got two emails, one from VC and one from my PHP code. So I set the trigger to go off in 2 minutes, logged out and it worked. Tried it several times, and it worked.

This is the second time I have had this happen. Last week, another job, same app, different function in the same PHP code. Same problem, same solution. Ran the VC job once manually, and now it works fine.

Here is the relevant log from last night:

6/24/2009 2:03:00 AM Info Job started: MYSQL Table Cleanup - Daily
6/24/2009 2:03:00 AM Debug Job (1966) was added to processlist: MYSQL Table Cleanup - Daily
6/24/2009 2:03:00 AM Debug Running Email Notification: 'Job Start'
6/24/2009 2:03:00 AM Debug Task (531) was added to processlist: Run Daily Reports Application with MYSQLTableCleanup_Daily
6/24/2009 2:03:00 AM Info Task started: Run Daily Reports Application with MYSQLTableCleanup_Daily (531)
6/24/2009 2:03:00 AM Debug Process status - retrieving process id (531)
6/24/2009 2:04:04 AM Debug Process status - has left WaitForExit (529)
6/24/2009 2:04:04 AM Debug Process status - OutPut captured (529)
6/24/2009 2:04:04 AM Debug Process status - trying to retrieve exit code
6/24/2009 2:04:04 AM Debug Process status - ExitCode fetched (529)
6/24/2009 2:04:04 AM Debug Process status - ProcessHandles closed (529)
6/24/2009 2:04:04 AM Debug Ending timeout timer (529)
6/24/2009 2:04:04 AM Debug Ending output readers (529)
6/24/2009 2:04:04 AM Debug Closing desktop handles (529)
6/24/2009 2:04:04 AM Debug Process status - About to raise TaskCompleted (529)
6/24/2009 2:04:04 AM Info Task completed: Run Backup for SystemState Daily Copy to File (529)
6/24/2009 2:04:04 AM Debug Setting previous task in TaskProcessCompleted: Run Backup for SystemState Daily Copy to File (bc06a789-24a3-4359-b138-fdcf5be2d0d2) in job: SystemState Daily Copy to File
6/24/2009 2:04:04 AM Debug Process status - About to SendTaskProcess (529)
6/24/2009 2:04:04 AM Debug Process status - About to RemoveTaskProcess (529)
6/24/2009 2:04:04 AM Debug Task (529) was removed from processlist: Run Backup for SystemState Daily Copy to File
6/24/2009 2:04:04 AM Debug Job (1964) was removed from processlist: SystemState Daily Copy to File
6/24/2009 2:04:04 AM Debug Next execution (2) for job 'SystemState Daily Copy to File' is: 6/25/2009 2:00:11 AM
6/24/2009 2:04:04 AM Info Job completed: SystemState Daily Copy to File
6/24/2009 2:04:23 AM Debug Saving Jobs
6/24/2009 2:04:43 AM Debug Process status - has left WaitForExit (531)
6/24/2009 2:04:43 AM Debug Process status - OutPut captured (531)
6/24/2009 2:04:43 AM Debug Process status - trying to retrieve exit code
6/24/2009 2:04:43 AM Debug Process status - ExitCode fetched (531)
6/24/2009 2:04:43 AM Debug Process status - ProcessHandles closed (531)
6/24/2009 2:04:43 AM Debug Ending timeout timer (531)
6/24/2009 2:04:43 AM Debug Ending output readers (531)
6/24/2009 2:04:43 AM Debug Closing desktop handles (531)
6/24/2009 2:04:43 AM Debug Process status - About to raise TaskCompleted (531)
6/24/2009 2:04:43 AM Info Task completed: Run Daily Reports Application with MYSQLTableCleanup_Daily (531)
6/24/2009 2:04:43 AM Debug Setting previous task in TaskProcessCompleted: Run Daily Reports Application with MYSQLTableCleanup_Daily (767724b5-51bd-4e57-b0b7-e7f8cc16df86) in job: MYSQL Table Cleanup - Daily
6/24/2009 2:04:43 AM Debug Process status - About to SendTaskProcess (531)
6/24/2009 2:04:43 AM Debug Process status - About to RemoveTaskProcess (531)
6/24/2009 2:04:43 AM Debug Task (531) was removed from processlist: Run Daily Reports Application with MYSQLTableCleanup_Daily
6/24/2009 2:04:43 AM Debug Job (1966) was removed from processlist: MYSQL Table Cleanup - Daily
6/24/2009 2:04:43 AM Debug Next execution (2) for job 'MYSQL Table Cleanup - Daily' is: 6/25/2009 2:03:00 AM
6/24/2009 2:04:43 AM Info Job completed: MYSQL Table Cleanup - Daily
6/24/2009 2:05:23 AM Debug Saving Jobs
Sponsor
Forum information
Support
2009-06-24T23:32:57Z
I think we need to combine this with logs from your php-script. Perhaps there is something in the event log?
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
keithdavis
2009-06-25T00:16:48Z
Nothing in the event log. What do you want? My PHP script?
Support
2009-06-25T01:08:27Z
I am not sure I want it 😁

But perhaps you can add some debugging to see how far it goes and what fails?
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
keithdavis
2009-06-25T16:33:26Z
I will if it happens again. However, it seems odd to me that the same code works fine every time after I run it manually once.
keithdavis
2009-06-25T17:26:33Z
Actually, we capture all PHP errors and they are sent to us automatically. The only way it could be a code problem is with the VB app that contains it and that app is extremely simply, and runs about 50 jobs a day without issue.

If the code was run, we would have gotten something.
Support
2009-06-25T18:11:25Z
I would write to a log file at the first line. Then you know if it is aborted or not.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
Scroll to Top