Hi guys, I have a multiserver setup that use the mirror feature of ispconfig. I'm a bit confused by cron job that get replicated accross all members of the mirror set (typically I have a bunch of 3 servers 1 master, 2 clones) This cause obviously my cron job to be runned multiple times ... Is this by design or a bug. If per design I can't quite understand the motivation for doing such... Regards,
This is by design, as a mirror setup means that every config step gets processed on both servers and ispconfig can not decide whch cronjob has to be run on both servers and which cronjob shall be run on one server only. If you do not want that cronjobs get added on the mirror server, then disable the 2 cron server plugins on the mirror by deleting their symlinks in the plugins-enabled folder.
To be perfectly frank with you I can't imagine a scenario where you'd like cron to be replicated. I tend to think that this is a per physical server action we want to drive here... I hate having to patch code on some but not all server. I have a farm of 12 servers, only part are mirrors and this approach is mistake prone. The actual design make thing impossible in the following scenario: - One may like to cron his DOCROOT space via cron rsync - One (has I do) has db replication + doc root replication and implement load-balanced service accross mirrored nodes - cron webservice based action need to be runned only once - One may need to run some housekeeping on a per physical server based ( statistics coonsolidation / backup export ... I wonder how many of us are using mirror setup and if any has cron on top. IMHO crons should not been replicated, it is the matter of the system admin to do such on his own ...
There is n code that needs to be patched. disabling and enabling plugins for a server is a normal administrative task, it does not mean to patch anything. So if you dont need a certain plugin, you should disable its, thats what the plugin enabling mechanism is made for.
I ended-up making symbolic link /etc/cron.d/ispc_webx => /dev/null on all but the prime node. This address the *disabling* of cron on a node/web better granularity than full on/off per plugins removal. This does nothing however to permit different crons on one mirror than on others. one mirror is fenced on a different network and need to do things differently. I is actually adressed per non ipconfig driven crons at a cost of not integrated in the supervisor.
