Out of 4 v3 servers 2 now have cron job problems, I open a ticket and get blamed for removing the cron jobs (yea right), does anyone else have cron job problems?

That was me who "blamed" you (not really, just made a factual observation ) and I personally looked at your server.

To clarify: I didn't say that you removed the Centova Cast cron jobs.

I said the cron daemon itself was missing from your server.  eg: Not only was cron not running, it wasn't even *installed* on the machine.  The whole package was gone.

There is absolutely no possible way, beyond any shadow of a doubt, that cron could have been removed by Centova Cast... Centova Cast cannot uninstall entire packages from your server.

The only way this could be *remotely* related to Centova Cast is if somehow yum on your server went totally berserk when calculating your package dependencies, and as a result, when the installer invoked yum to install Centova Cast's required packages, yum (for some unexplainable reason) decided to uninstall the cron package.  That is extremely unlikely as cron is considered an essential service, but even if it happened, it would be a pretty big stretch to blame it on Centova Cast if yum, the standard package manager for your OS, went haywire.

As you know, I have no problem acknowledging and taking responsibility for bugs -- you've made a ton of very valuable bug reports here on the forums --  but, I mean, credit where credit is due... this is not a CC issue.

Sorry I had always just thought everything was included with the v3 package (other than mysql), this was a brand new installation with CentOS 6.2 - 32-BIT, I guess I didn't fully understand, but the solution was simple ..

{quote}
yum install vixie-cron crontabs
/sbin/chkconfig crond on
/sbin/service crond start
{/quote}

Sorry I had always just thought everything was included with the v3 package (other than mysql),
...
yum install vixie-cron crontabs

The above is precisely why we do not attempt to install it.  There are a variety of different cron packages available for CentOS, and the one you chose above is not the default -- the default is 'cronie'.

If we try to install cronie (or any other cron package) as part of the installation, then every user who has installed a different cron package in advance will have it uninstalled and replace with cronie.

It's unfortunate that (as I've just found out) the CentOS minimal package does not include cron, but as I've found while reading about it, the 'minimal' package is not the 'server' package -- it is intended to be minimal and not include anything but the bare minimum you need to boot with networking and package management.

Also FYI, Centova Cast does explicitly list cron as a system requirement.

So how do we fix these cron job errors from accurring, every post i read about cron job error, i run in ssh its good for like 8 - 12 hrs then it comes right back up......


Out of my 9 Centova v3 servers i got 3 that are popping errors.

I run the debug and no warnings come up

Whats the next step to fix this.

Kris

I just did not have cron daemon installed, it had nothing to do with Centova

yum install vixie-cron crontabs
/sbin/chkconfig crond on
/sbin/service crond start

ok what about debian install of that.