Discussion in 'Plesk 9.x for Linux Suggestions and Feedback' started by danliker, Jan 24, 2010.
why does each plesk update takes hour's for the process ?
Usually it depends on quantity of mailboxes and domains.
that's right, but how can we reduce the dowtime, it is horrible! what do big companys with many domains/mailboxes on each server ?
Unfortunately mailsettings rebuilding and synchronization is absolutely necessary operation and it can't be disabled or something else. Therefore I can recommend you increase power of server's hardware, disabling and removing all unused domains/mailboxes, migrate some domains with mailboxes to other Plesk servers for decreasing quantity of mailboxes on server which should be upgraded and schedule upgrade downtime to night hours with corresponding customer's notification.
ok, but why is apache stopped during rebuilding and synchronization of mailboxes ?
How apache related packages can be upgraded without stopping httpd processes? And all vhosts configs should be rebuilded by websrvmng too.
don't you like to understand ? during the prozess of mail update and rebuilding and synchronization of mailboxes, why must apache be stopped in this moment ? i know that apache is restartet and websrvmng is running, but not on the SAME time ! as i see it is as fallow... - do some updates - stop apache - update mailsystem - rebuilding and synchronization of mailboxes - update apache things - start apache i think id sould be: - do some updates - update mailsystem - rebuilding and synchronization of mailboxes - stop apache - update apache things - start apache
I can assume that it is related to webmails because webmails have config dependences for mailsettings and for websettings too.
Respectfully I disagree. The Plesk update system is poorly structured if you ask me. Why does every single update need to rebuild the mail configuration and DNS configuration? I'm almost certain that EVERY release does not need to do this. It should be done where necessary. This is easy enough to do - you just set some DB flags or flags in a file then when processing the packages and running the post-install you do what you need to. Another issue I have is the fact that Plesk rebuilds this information SEVERAL times: We restart Apache as soon as we can and don't give a damn what Plesk is doing. We normally restart it as soon as we notice it's down and do so by running the websrvmng -a -v command to make sure Apache has the correct configuration. So in my dual processor, quad core Xeon servers with 24GB/32GB RAM and RAID 10 over SAS disks, what specs should I look at moving to? Because we don't run your "typical" hosting company boxes. Surely that's not a recommendation. :-/ How can't they? Replace binaries, rebuild config and then restart. The beauty of Linux is that you can replace an open/running file without any adverse affects.
Separate names with a comma.