patched apache and now PSA keeps shutting down overnight

[one1step1]

I am a proud new user of a VPS with Plesk 8.1. I have a few domain names that I wanted to be aliased. For example, my main domain is thinkmac.net and I wanted my other domains to point to it.

My linux friend wasn't familiar with vhosts or plesk and modified my: /etc/httpd/conf.d/zz010_psa_httpd.conf file.

He simply added this line to the end of it:
Include /var/www/vhosts/thinkmac.net/conf/httpd.include.patched

The 'patched' file it references the file he modded, and it doesn't look for the previous "httpd.include" anymore.
This new file contains all of the previous info, plus the new domain aliases he entered.

My hosting provider says they won't fix my problem, since that file shouldn't be modded. My friend told me tough, change it back if I need it fixed. So now, I am between a rock and a hard place, and now my site is active, and it shuts down everynight. When I come in about 6am, the site is unreachable, and when I login to Plesk/Virtuozzo, it says PSA is not available, and I have to restart it. When I restart it, I then need to go start httpd, since it isn't starting automatically.

Any ideas? I can provide the files if someone would be willing to help.
I am wondering if this is the problem or not. Are there any logs or errors I should be looking at/for?

Thanks so much.

 

[one1step1]

Now it appears to be shutting down during the day. happened two times today.

 

[breun]

Why not just use Plesk 8's domain alias feature?

 

[one1step1]

I added the domains in Plesk in the Domain Alias feature, but it didn't seem to be working. I added them, restarted, etc, but didn't seem to work at all.

 

[breun]

You changed back your apache config?

 

[one1step1]

Yes, I decided to change it back and take a chance. It's better than having it not run at all. It hasn't shut down since.

I change the include file to point back to the original httpd.include, and then I ran this command:
/usr/local/psa/admin/sbin/websrvmng -a -v

However, I am having a different kind of trouble. Virtuozzo is running, but when I login to it, it says 'TOP->Service Unavailable'

It is running, however, when I try to use it for something like 'Maintenance' I get this message"Service is not available now, probably your Plesk is misconfigured.
Contact Your provider for details.

Internal Plesk error occurred: Incorect value in request: direct=top."

Any ideas of where to look for a problem? A particular log file, etc?

 

[one1step1]

It is happening again. The server seems to be going down erratically overnight it appears. This is with everything back the way that it was originally.

Here is the problem. Virtuozzo is running, but when I login to it, it says 'TOP->Service Unavailable' It is running, however, when I try to use it for something like 'Maintenance' I get this message"Service is not available now, probably your Plesk is misconfigured. Contact Your provider for details. Internal Plesk error occurred: Incorect value in request: direct=top."

Then, sometime overnight, the whole thing shuts down, and I end up having to choose to 'restart' the service.
See images 3,4, & 5

All of the websites on my vps go down. And when I start the service again (see image 4), I have to manually restart httpd (see image 5, and you will see it is down, and I have to manually restart it).

Here is what is happening:

Problem 1

Problem 2

Problem 3

Problem 4

Problem 5

Anybody have anything they can throw out for me to look into?

 

[breun]

I don't run Virtuozzo, but maybe there are some logs you could have a look at? Maybe even the httpd logs?