Sunday, May 26, 2013

SetCronJob automatically corrects cron URL

Hello there,

I often receive message from users reporting their cronjobs are failing and they don't know why. I checked their cronjobs execution logs (hit the View logs icon) and found that their URLs just redirects to another "version" of themselves:
- Redirection from www to non-www version or vice versa e.g. from
http://example.com/cron.php
to
http://www.example.com/cron.php
- Redirection from http:// to https:// version or vice versa e.g. from
http://example.com/cron.php
to
https://example.com/cron.php
- Redirection to URL with trailing slash (after directory name) e.g. from
http://example.com/cron
to
http://example.com/cron/
(in this case, the index file e.g. index.php is the actual cron script).
- Some combination of redirections above.

For your convenience, SetCronJob will now automatically correct your cronjob URL (after first execution) so it's no longer a problem now.

Hope this helps.

P/S: We're improving our service now, so there will be more upgrade coming soon ;-)

Best regards,
Nguyen An Thuan.

Sunday, April 14, 2013

SetCronJob DNS cache

A DNS cache contains entries that translate Internet domain names to IP addresses, for example matching setcronjob.com with 50.116.9.254.

Besides system’s DNS cache, SetCronJob has its own DNS cache that each entry’s TTL (time-to-live) is 1 day. Once a domain name is resolved to an IP address, it’ll be kept at SetCronJob’s DNS cache for one day.

At the moment, our service has around 100,000 cronjobs, and active cronjobs are executing 1,300,000 times a day.  Thanks to our DNS cache, the cron processors just need to resolve 8,500 domain names a day instead of 1.3 million times a day, and that’s saving much server resources.

In case your domain name changes its IP address, the DNS cache may not be updated as soon as expected; it’ll cause a glitch in the cron execution.  There are two cases:
  • If the cron fails i.e. the old IP address doesn’t respond appropriately with the current request, SetCronJob will refresh the cache entry, trying to get the new IP address.
  • If the cron is still fine, the IP address will be updated next day. To force SetCronJob refresh any DNS cache for any domain name, just Edit then Save one cronjob with that domain name. 
If there’s something unclear, feel free to comment below, or email me.

Best regards,
Nguyen An Thuan.

Thursday, August 23, 2012

SetCronJob new layout

Hello everyone,

We have recently improved SetCronJob with many updates:

Improved Control Panel

SetCronJob's simple Control Panel now has new button set, clearer layout, and beautiful icons.
AJAX is supported thoroughly, which lets you create, edit, disable, enable, delete cronjobs quickly and easily.

You can also sort cronjobs order by ID, name, URL and points.

Automatically Billing

Premium Users with Silver and Gold accounts can subscribe to our PayPal account and get your account automatically billed every year.
You can easily upgrade and downgrade you account to another plan, and we'll magically calculated remained credits for you.

Better error message notification

We now have per-input and whole-page eye-catching error messages, so you will find out what's causing the problem very quickly.

More features

- You can request us to keep you logged in (Remember Me), so you won't need to to log in again (on the same computer).
- Users with Gold Account can archive more cronjob execution results (up to 50 results).
- Simpler sign up process that helps you sign up in less than 10 seconds!

And more features are coming soon, as we're working on this new version now :-)

If you have any question, feedback or suggestion, just share with us.

Friday, August 3, 2012

Server Status on Aug 03, 2012

Our web server (Apache) encountered a Segmentation fault error, and was inaccessible in 3h 22m.
When we found the problem, we restart the web server, and SetCronJob backs online now.

Because it was the problem with Apache only, while the whole server was online, all of your cronjobs were being executed correctly during web server downtime.

We fixed it and make sure it won't happen again.

Sorry for the inconvenience caused.

Our apologies for the trouble,
SetCronJob.

Wednesday, May 23, 2012

Batch CronJob Operations

Hello there,

SetCronJob now supports Batch CronJob Operations, including Delete, Disable multiple cronjobs at once.


To do this, simply click on the the cronjobs' row (the row will then be marked as selected, and the checkbox at beginning of row is checked), then select desired operation.

You can also check the first checkbox at header row (before ID column), this will select/unselect all cronjobs at once.

More batch operations will be added if necessary.

If you have any suggestion, just let us know :-)