Question

Photo of Matthew Meekins

0

Rock Cleanup job not running successfully

Our database was periodically getting extremely slow so we would restart the server and it would start working well. I then noticed in "Jobs Administration" that the Rock Cleanup job hadn't run successfully since the morning of 12/25/14. I'm including an image of the status message but it's too big to get the whole thing. It ends with, "Job threw and unhandled exception." Any ideas? Please let me know if I need to post more information. 

Screen Shot 2015-01-15 at 2.13.52 PM.png

  • Photo of Matthew Meekins

    1

    DJ, your post reminded me to update this. As I said, I did a complete reinstall of Rock and it didn't work right at first. But now, all the jobs are running successfully. I'm not sure if it was a server issue or what, but everything seems to be working now. I wish I knew if it was something I did, that fixed it but I have no idea. 

  • Photo of Matthew Meekins

    1

    Just a note that the "Rock Cleanup" job is still failing. It's not slowing down the system like it was before, but it still fails every time it runs. I had it turned off until 3.1 came and then turned it back on to see if it would run correctly. 

  • Photo of Mike Peterson

    0

    Is there more information about the error in Home > System Settings > Exception List?  Hopefully you'll find something in there on why it crashed.  Otherwise, my guess is that you got a database timeout error.

  • Photo of Matthew Meekins

    0

    I can't find anything about the failure in the exception list. I actually completely deleted and reinstalled all of Rock and the Cleanup Job still fails. I'm also not getting the failure until I update to 2.0. And the Location Services Job is failing. Any ideas?

    • DJ Grick

      I recently noticed my Rock Cleanup job is also not running. In fact it has not since 10/21/2014. There is not an exemption in the logs but it does show a long error (which cant be copied and pasted). I will have it e-mail me the error tonight and see if I can post mine here tomorrow.

  • Photo of Matthew Meekins

    0

    So, I'm getting the same issue again. Every morning Rock is almost entirely unresponsive until I restart the server. I feel like one of these system jobs is responsible, but I don't know how to figure that out. There's nothing in the exception list that relates to these events. 

    Screen Shot 2015-02-19 at 8.55.41 AM.png

    Screen Shot 2015-02-19 at 8.56.13 AM.png

    (continued)

    Screen Shot 2015-02-19 at 9.01.34 AM.png

  • Photo of Rock RMS

    0

    We have found an issue with the Process Workflows job locking resources and taking a considerable amount of time to run.  We have fixed this for the next update, but until then, you may want to consider scheduling that job to run less often.

    • Matthew Meekins

      Do you think it's the "Process Workflows" job that is making the "Calculate Person Duplicates" and "Rock Cleanup" jobs fail?

    • Rock RMS

      It's possible, especially since one of them is reporting a timeout issue. Can you try changing the Process Workflow job so that id doesn't run for an evening and see if that helps the other jobs run successfully.

    • Matthew Meekins

      I turned off the Process Workflows job for a few days and it does now allow the "Calculate Person Duplicates" job to run. However, "Rock Cleanup" is still failing. And when it fails our server gets bogged down by 100% and we can't do anything and we have to restart the server. I assume it's not a big deal to turn off "Rock Cleanup" for now so that doesn't happen, but I'm sure there's a reason for that job.


      TLDR: Turning off "Process Workflows" didn't fix the main problem.

  • Photo of DJ Grick

    0

    CleanupJob.png

    Here is what we are getting now for our Rock Cleanup job (Version 3.2). I checked in the app code directory for the .dll file but the only file type in that directory is .cs. 

    I recently setup a sandbox and the Clean up job is running correctly on that install but also does not have a .dll file in the App_Code directory.