i was on the phone with Servermatrix for an hour... they have no idea how to fix it.

has anyone had this problem with Plesk?

First of all we need to see what might be causing apache to not start.
Here's the first thing to try (assuming you have redhat linux or some variant)
ssh into the server as root and give the command "service httpd start" This command should attempt to start apache and give you an error message if it doesn't start. Please post any error messages you get. :)

tail -f the apache error log and try to start apache see what it says

The reason it probably stopped working after reboot was you actually already had a config file problem, but since it only reloads when you restart apache... it started not loading after you rebooted.

I'd suggest doing what thelinuxguy suggests -- check the error log.

Originally posted by VagrantHost
i was on the phone with Servermatrix for an hour... they have no idea how to fix it.

has anyone had this problem with Plesk?
Wow, great support. Doesn't take a genius to solve something simple like that. SM techs must really have their heads up their .....

Originally posted by NexDog
Wow, great support. Doesn't take a genius to solve something simple like that. SM techs must really have their heads up their .....

Do you know what's wrong or what SM tried? It could be something more complicated than it seems at first. It's a bit rash to degrade another person based off something you have no first hand knowledge of.

i had a third party company look into it for me. the 127.0.0.1 was commented out in /etc/hosts... which he uncommented and apache started fine.

now, i have a major DNS issue that popped up out of nowhere. i had about 35 sites switched over, propagated and working on the new server... now, after we got apache up and running, only about 2 of those sites are working.
http://dnsreport.com/tools/dnsreport.ch?domain=komamusic.com
this site was working fine earlier yesterday.

again, on the phone with servermatrix for an hour at 3am... couldn't find any issues. bumped it up to "level 2".

*praying that i don't lose any clients over this*

Thats just sad, their techs dont know anything!

Originally posted by VagrantHost
i*praying that i don't lose any clients over this*
Well, for the kind of service you are providing, you deserve to lose all your clients until you get real.

Originally posted by NexDog
Well, for the kind of service you are providing, you deserve to lose all your clients until you get real.

How about sticking on-topic instead of flaming that guy ?

He's trying to learn how to be a host via WHT. While this place is a great resource on the industry as a whole, I find it strange that someone would try and resolve technical matters here. The thread starter has posted numerous threads in the last few weeks about plesk, dns, apache etc problems. There is only one solution and that is to hire someone that will fix issues and teach him some basics. Clients are paying him money and they deserve some kind of service.

This is a good example of how not to start a hosting company or jump from reseller to dedicated. I don't mean to flame but his clients deserve more. Providing shoddy service just adds to the bad name of the industry. Sorry.

And yet you initially blamed SM ;)