New configuration files for the Apache web server were not created due to the errors

[GigaBlast]

I am not happy after waking up to finding a dead server. The update broke apache! It the busiest time of year. i am running adwords at £400 per day. What the heck is going on?

New configuration files for the Apache web server were not created due to the errors
New configuration files for the Apache web server were not created due to the errors in configuration templates: mkdir: cannot create directory `/var/www/vhosts/domain.com/conf/vhost.conf:/system/img.domain.com/conf': No such file or directory mktemp: failed to create file via template `/var/www/vhosts/domain.com/conf/vhost.conf:/system/img.domain.com/conf/13863349090.87530800_httpd.conf.XXXXXX': No such file or directory Can not create temporary file . The error message containing the detailed error descriptions was sent to you by e-mail. Please resolve the issues and click here to generate broken configuration files once again or here to generate all configuration files.

Luckily the generate all configuration files brought the site back online.

My prior forum thread hasn't been resolved either.

 

[abdi]

My prior forum thread hasn't been resolved either.

Which one?

 

[GigaBlast]

Hi Abdi,

the last post >> http://forum.parallels.com/showthre...riction-in-effect-on-Cron-Jobs-on-VPS-123-reg
Which might have led to this problem "server configurations not created due"..
Meanwhile I need to find out how to stop further updates so i don't have to wake up at 3am to fix a dead apache.

 

[Nikolay.]

GigaBlast, you should have listened to Faris Raouf. He's a wise man

But umm....do not edit /etc/psa/psa.conf! I'm not sure why you did that? You must not touch that file. Here be dragons.

Revert all of your random changes, especially in psa.conf, then call:

# plesk sbin packagemng -sdf; plesk sbin httpdmng --reconfigure-all

Oh, and as you can see, update is not to blame by itself. If anything, it was only a catalyst for the problem to show up earlier.

 

[abdi]

Meanwhile I need to find out how to stop further updates so i don't have to wake up at 3am to fix a dead apache.

I agree with you on this, especially on a production server (Overtime plesk has proven to be UN-predictable, you really do not want to run updates without your eyes watching)

Anyhow, you can easily disable automatic updates through your control panel, Tools and Settings -> Updates / Upgrades settings ..

 

[GigaBlast]

thanks for your answers guys. I shouldn't even be in here wasting my time on server configs. in the past with cpanel it just worked. all these posts because i get cron jobs to run. Crazy the amount of weeks i've spent researching. fiddling with dragons... i only did what Indas parallels product expert told me i needed to do Nicolay. Its all undone except the file and directory i created 'var/www/vhosts/domain.com/conf/vhost.conf' - do i need this conf folder?

I've seen your ssh commands. thank you for your time! but feel now isn't the time to break anything which i can't fix... things are running at the moment. Updates are off.

Back to the issue. why am i having such a problem removing my VPS open base directory restrictions for the cron scheduler and for ssh commands? it works if i visit the url and run the trigger script.