OpenVZ Forum: Support » Incorrect Crontab times set

Home » General » Support » Incorrect Crontab times set (Incorrect Crontab times set on container creation)

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Incorrect Crontab times set [message #45107]

Mon, 30 January 2012 19:56

samix
Messages: 3
Registered: January 2012

Junior Member

Hey,

I made a template of a openvz container using the document here wiki.openvz.org/Creating_a_CentOS_5.0_Template

When I created VM's using this template all the cron times changed and each container had a different cron time than the image as well as different from each other.

Cron file in the image

cat /tmp/50/etc/cron.d/atop
# start atop daily at midnight
0 0 * * * root /etc/cron.daily/atop

And now the same file in the container that were created using this template

container 111
# start atop daily at midnight
32 1 * * * root /etc/atop/atop.daily
container 112
# start atop daily at midnight
6 3 * * * root /etc/atop/atop.daily
container 113
# start atop daily at midnight
40 1 * * * root /etc/atop/atop.daily
container 114
# start atop daily at midnight
18 1 * * * root /etc/atop/atop.daily
container 115
# start atop daily at midnight
9 2 * * * root /etc/atop/atop.daily
container 116
# start atop daily at midnight
25 1 * * * root /etc/atop/atop.daily
container 117
# start atop daily at midnight
43 2 * * * root /etc/atop/atop.daily
container 118
# start atop daily at midnight
29 1 * * * root /etc/atop/atop.daily

Is this a know problem ? a bug ? Any ideas what can I do to rectify this, because now I am wondering that many other files may have also changed just like this and I will come to know only when something breaks..

Regards,
samix

Report message to a moderator

Re: Incorrect Crontab times set [message #45126 is a reply to message #45107]

Tue, 31 January 2012 13:24

samix
Messages: 3
Registered: January 2012

Junior Member

I figured out, this is because of the postcreate.sh script, but I think this is wrong, and that this feature should be optional and not mandatory.

I have a setup where we run completely identical servers and the cron times need to be same on all of them, apart from other stuff.

Normally we create our own image and then using puppet create other containers, due to the postcreate.sh script, the cron times in the newly created containers change and we have to again manually set the cron times on all the containers, which defeats the entire purpose of creating a custom image and automated deploy.

I think openvz designers should consider this and make this feature optional.

Report message to a moderator

Re: Incorrect Crontab times set [message #45127 is a reply to message #45107]

Tue, 31 January 2012 14:25

Ales
Messages: 330
Registered: May 2009

Senior Member

I suggest opening a bugreport with the request for the added functionality.

I believe this is a wanted feature in general. If you look at it from the perspective of server load, distributing cron times makes sense. So most HN admins wouldn't want cron to be run at exactly the same time on all the VMs. But having a switch to disable this for cases such as yours also makes sense, IMHO.

Report message to a moderator

Re: Incorrect Crontab times set [message #45128 is a reply to message #45127]

Tue, 31 January 2012 14:49

samix
Messages: 3
Registered: January 2012

Junior Member

Yes, in case of VPS based hosting this would be a very good feature, thank's for you input, I have raised a bug report here bugzilla.openvz.org/show_bug.cgi?id=2174

Report message to a moderator

Previous Topic:	Disturb VMs in two HDD
Next Topic:	mounting ext3 image inside VE

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Sun Aug 02 04:14:10 GMT 2026

Total time taken to generate the page: 1.06396 seconds