Coldfusion neo-cron.xml has been modified - when it hasn't been - coldfusion

We've just upgraded from CF 9 to 9.0.1 (ColdFusion 9 Update 1). We're running on Windows Server 2008.
After the upgrade we noticed on our server that we were getting a lot of these messages in server.log:
"Information","scheduler-6","10/05/10","12:34:48",,"neo-cron.xml has been modified . Reloading the service coldfusion.scheduling.CronServiceImpl#c020a"
"Information","scheduler-5","10/05/10","14:54:50",,"neo-cron.xml has been modified . Reloading the service coldfusion.scheduling.CronServiceImpl#c020a"
"Information","scheduler-8","10/05/10","15:53:51",,"neo-cron.xml has been modified . Reloading the service coldfusion.scheduling.CronServiceImpl#c020a"
"Information","scheduler-19","10/05/10","16:57:52",,"neo-cron.xml has been modified . Reloading the service coldfusion.scheduling.CronServiceImpl#c020a"
"Information","scheduler-18","10/05/10","19:12:54",,"neo-cron.xml has been modified . Reloading the service coldfusion.scheduling.CronServiceImpl#c020a"
"Information","scheduler-4","10/05/10","21:32:56",,"neo-cron.xml has been modified . Reloading the service coldfusion.scheduling.CronServiceImpl#c020a"
"Information","scheduler-17","10/05/10","22:32:57",,"neo-cron.xml has been modified . Reloading the service coldfusion.scheduling.CronServiceImpl#c020a"
"Information","scheduler-7","10/06/10","02:15:00",,"neo-cron.xml has been modified . Reloading the service coldfusion.scheduling.CronServiceImpl#c020a"
"Information","scheduler-10","10/06/10","05:33:06",,"neo-cron.xml has been modified . Reloading the service coldfusion.scheduling.CronServiceImpl#c020a"
"Information","scheduler-0","10/06/10","06:50:08",,"neo-cron.xml has been modified . Reloading the service coldfusion.scheduling.CronServiceImpl#c020a"
"Information","scheduler-4","10/06/10","07:33:09",,"neo-cron.xml has been modified . Reloading the service coldfusion.scheduling.CronServiceImpl#c020a"
"Information","scheduler-15","10/06/10","08:40:10",,"neo-cron.xml has been modified . Reloading the service coldfusion.scheduling.CronServiceImpl#c020a"
We have not touched the neo-cron.xml file, but since the upgrade, every few hours CF thinks the file has been changed.
We probably would not have noticed this only for the fact that for a period between 2 of the reloads all our scheduled tasks were being executed twice! However, after another reload of neo-cron.xml the duplication stopped.
Has anyone else come across this issue?
Thanks in advance.
PS: Enable logging for scheduled tasks in CF admin is not enabled.

I'm not sure about the doubling up of tasks, but I also noticed that neo-cron.xml was constantly being modified.
Looks like they've added a new node to each task, last_run, which is updated after each execution of a task.

Related

AWS BeanStalk: Often restarts the service automatically

I have a super small C# .NET Framework web application that I run on AWS Beanstalk. It works fine, except for one peculiar thing:
AWS seems to restart the service with unregular interval. I can see this as I can see log prints that only happens on startup.
In this case I am using ServiceStack AppHostBase, which has a Configure method that should be executed only once, on startup. In this method, a log print is done, and this gets executed between every 15 min to 2 hours approximately, indicating that the service is restarted at those times:
No update of the build has been done at those times seen above.
The Beanstalk configuration looks like this:
I would like to know why it restarts and what I can do to stop it.

One or more services have started or stopped unexpectedly SPTimerService (SPTimerV4)

I have stop and restart services(Sharepoint Administration & Sharepoint Timer Service)
I cleaned the Configuration Cache by using mentioned steps.
Summary of the steps to clear the timer job:
Stop SharePoint Timer service on all servers in the farm.
Browse to C:\ProgramData\Microsoft\SharePoint\Config{GUID} where the {GUID} folder contains a bunch of XML files and NOT the files with a “.PERSITEDFILE” extension.
Delete all the XML files
Update the contents of the Cache.ini file to just say “1” (without quotes).
Restart the SharePoint Timer service on each server
Reanalyze the issue in Health Analyzer
Does anyone know why this keeps occurring and how I can stop it?
First of all try and check your ULS Logs and see if there is any error that arise.
Secondly try and maybe check the event viewer on your SharePoint server to see if any errors are shown and make sure you have enough disk space available.
and also you might want to check this :Clearing Timer Services
Let me know if you see any error post it here.
hope it helps.
Yotam.

Scheduled Task Never Runs unless I browse the URL manually

I have a particular scheduled task that CF claims runs every 2 minutes. However, it either doesn't run or complete since the database changes the task is supposed to perform do not occur after each run. However if I copy the exact same URL into a browser and run the script, it works 100% of the time.
I have no clue where to start debugging. There is no IP restriction on the page.
I can see in the CF Admin that it was last run at 2:06 for example and the next run will be at 2:08. I can also see it in the scheduler.log file.
We had updated our certs in IIS but didn't update our cacerts file. Once we did everything was great.
It was clear the process wasn't running when I added a line or two to email myself at the start of the task. The emails never came when the server ran the task but they did when I pinged the page. I changed the task to save the output to a log file and when I opened that up it just said "Connection Failure". This led me to some googling and some talk about certificates which made me remember that we just updated ours recently. Looking back at my emails with IT it did indeed happen on the same day that the last emails in the mailsent.log were sent from these scheduled tasks.

Multiple celery server but same redis broker executing task twice

When I inspect celery -A proj inspect active_queues I see two servers showing their queues they are listening to and they are pointing to same default queue name celery. Still the task issued by django app gets executed twice by both servers(Once by each celery server - so two times).
I can see the transport type is also direct - the default one.
On my local task gets executed once so I am sure that the task is called only once by my django app.
What can I be missing here?
Ok, i looked up the docs, i think you need to set celerybeat-scheduler in your settings.py which makes sure tasks are being scheduled by a single scheduler.
http://celery.readthedocs.org/en/latest/configuration.html#celerybeat-scheduler
On Redis you can set the current database for the application you are running, setting the database will separate the information to use different apps.
If you are using Django the configuration is
CELERY_BROKER_VHOST = {number of the database}
If you are not using Django i beleive the configuration is CELERY_REDIS_DB or redis_db depending on your celery version
For instance for your first application could be CELERY_BROKER_VHOST = 1
For the second application could be CELERY_BROKER_VHOST = 2
and for your local development could be CELERY_BROKER_VHOST = 99
http://docs.celeryproject.org/en/latest/userguide/configuration.html#id8

Scheduled Tasks not running - Coldfusion Server Administration

I have a series of scheduled tasks that all run at various times of the day. Since the migration from Coldfusion version 7 to 10, these tasks have stopped running.
When I check the box, that outputs the results to a file, I get a text file that says nothing more than "Connection Failure". I have tried everything imaginable regarding the username and password for the task. It makes no difference. When I run the CFM page in my browser, the
page works correctly and generates an email just like it should. I just
can't make it run as a scheduled event.
Is the scheduled task folder has any check for the session or anything? I mean is the scheduled task folder is accessible without login? Please try with removing all the redirect rules for the application. That might work.
For me the requests were timing out. I increased the timeout in the administrator and that solved it. Doing a cfhttp in a test file and dumping the results helped me troubleshoot it.