I configured cron in Drupal 7 for every 1 hour to delete "watchdog" table data. However, it is not working fine as expected when done automatically, even though it is working fine manually. What could be the problem with cron running automatically for specified intervals of time? Please, kindly help me with any alternate options, if possible.
Good morning.
Maybe one of your installed modules has a bad implementation of hook_cron(). An error in this hook would provoke the whole cron process to fail. You can use Cron Debug module to check which of the modules is failing during the cron execution. After that, you may consider disabling the module, or checking what is going wrong and fixing it.
Hope it helps.
Related
I have had a user report an issue where between midnight and 1am, some of my app's functions don't work correctly.
To recreate these issues, I would either need to just wait til midnight to fix them, or somehow emulate the time so the app thinks it's midnight. Is there a way I can do this without changing my Windows system time, or preferably without using a VM? My current technologies are
Windows 10
React 17.0.1
Webpack 5.9.0
I am open to using more npm packages if required. Any suggestions would be helpful
I have answered my own question here. There is a chrome extension here https://chrome.google.com/webstore/detail/change-timezone-time-shif/nbofeaabhknfdcpoddmfckpokmncimpj/related?hl=en that will quickly change your timezone in a current browser session. Hope someone else finds this useful
I have 5 Cloud Tasks queues that have been working for the past few weeks. Today they have simply stopped firing off tasks.
The tasks are still placed into the queue without issue however the queue metrics are all zeroed out. The queue is located in us-central1.
The queue is not paused, the app-engine application is not disabled, and my billing account is up to date.
The only error I see on the Cloud Task Dashboard is "Could not load queue stats. Try to refresh later."
Any ideas on what's going on? I've applied for a Google support account but it looks like it will take 5 days to get that.
There was an incident on march 24 affecting the Cloud Scheduler service in the us-central1 region, impacting Cloud Tasks and Cron jobs.
This was documented by Google there: https://status.cloud.google.com/incident/cloud-tasks/21001 (although they were still listing the service as fully functional more than one hour after the issue had started...)
Same issue for me. Status page says it's working fine but none of my task are moving. When I click now nothing happens and there are not logs of it attempting to run on my server.
I suspect it's most likely a google problem, I have the same situation right now.
I have been bug hunting the last hour, but there seems nothing wrong. If multiple people are affected, it's probably not your fault.
Just wait and hope for the best.
Does anybody know if there is Jenkins plugin that detects stuck jobs and e.g. sends an email?
I know that I can abort the build after n minutes (via the Binding configuration). My actual problem is that I've to check 60 projects and reconfigure each of them ...
Thx
Build-timeout Plugin gives the option to stop build that answer specific configuration. for example if the build takes more than T minutes or if the build takes 3 times more than an average successful build.
Is that what you meant ?
I am having a hard time trying to get tests that run fine on Chrome to run in a stable manner on IE.
I have followed the required configuration steps on Selenium's own documentation for IEDriver and I have the 32bit version of IEDriver also installed. I found the steps needed to setup the protected zones and add the registry key was all I needed to get IE to launch and for the tests to begin.
When running the tests I am often seeing intermittent time out related errors like so:
A Jasmine spec timed out. Resetting the WebDriver Control Flow.
I have seen some talk of just increasing timeout settings in the protractor config but this just feels like a magic number approach to me.
I am unsure what else to try right now, so thought I'd ask here to see what others may have done to help them past such issues.
One thing I did come across in a post elsewhere was how Chrome is more 'forgiving' with promises and that to get them to behave with IE, chaining then() callbacks on promises helped. This doesnt make sense to me, since from what I have read about the webdriver control flow chaining like so shouldnt be required.
Can anyone out there share their experiences with testing against IEDriver and if they have ever hit these intermittent timeouts, how have you been able to resolve these?
Thanks
You can have a look at this Post: This more about getting IE to work but maybe som e of the capability setting will help and also you need to configure your IE
How to fix the slow sendkeys on IE 11 with Selenium Webdriver 3.0.0?.
For me it became more stable, when i use Windows 10 IE, but I don't think it's relevant version with Windows 7 IE. I had simular problems on Windows 7 IE version, after a few runs my tests started slow down, and sometimes i get the same error as described. But it was half a year ago, i don't now about current versions, may be it's more stable.
Recently I've started using limited staging on my Google App Engine project. The data is still shared between all versions, but behaviour (especially user facing behaviour) is different.
Naturally when I implement something incredibly new it only runs on the latest version of my code and I don't feel like it should be backported to the older versions.
Some of this new functionality requires cron jobs to be run periodically, but I'm hitting a problem. I have to run a cron job to call the latest code, but this is what Google's documentation has to say about the issue:
Cron requests are always sent to the default version of the application.
The default version is the oldest because the first versions of the client code that went out to users weren't future proof and don't know how to select which API version to call.
So my question is, how can I get around this limitation and make a cron job that will call the latest rather than the default version of the application?
You can now specify a version using the target tag.
<target>version-2</target>
You can't change the cron jobs to run on a different version then the default.
Depending on how much time your cron job takes to run you could change your cron job script to to do a URLFetch to "http://latest.appname.appspot.com/cron_job_endpoint".
If you're cron job takes longer then 10 minutes to run, then I would design it in a way that you can chain the different tasks using task queues.