Hi guys, I have discovered that if I handle a user profile adding a new website, mail, ftp, etc.. the apache connection is reset. Try this scenario: 1. A cron job executes a huge operation 2. Any user change some configuration in his ISPConfig panel 3. The apache service has been reset and the Cron job stopped any glue? thanks
Hi Till, which is the problem? I have read the link, but what kind of information do you need? regards
From the post: "Please provide the following information when you make a new thread, this helps us to solve your problem. - Linux Distribution and version used on your server. - ISPConfig version" and "Debug instructions for the ISPConfig server process are in the FAQ: http://www.faqforge.com/linux/debugging-ispconfig-3-server-actions-in-case-of-a-failure/ Follow the instructions and post the output in your thread."
About which kind of cronjob are you talking, a url cron? When apache settings are changed, apache has to be reloaded or restarted depending of the change that has been made, otherwise apache wont use the new settings. If you wnat to ensure that your cron job is not affected, run it as shell cron and not url cron.
Hi Till, I am talking about a custom cron. The execution of this cron is truncated when ispconfig restart the apache. This cron export/import data from a database using a php script. It is a huge operation that requires about 30 minutes. If in this 30 minutes someone try to change something in the admin ispconfig panel, the cron is deleted. thanks
hello vaio, you cannot avoid that. Apache has to be restarted on changes in website settings in ispconfig as Till already said. Anyway.. I would never recommend to use cron-jobs via URL calls that run such a long time. Change it to a command line script or you will never be able to solve this problem.
So if a user change its configuration all the day and press the save button the apache will be restarted every time?
That depends on what he changes. If it is apache-related then yes, a reload/restart is done about once per minute. If you want to reduce the impact you have to change the setting in "server config" not to make a apache test on restart - this reduces it but you will not be able to avoid reloads/restarts on changes.
