Preview not working after virtual server creation

6 posts / 0 new
Last post
#1 Fri, 03/20/2009 - 14:07
synergos

Preview not working after virtual server creation

Whenever I create a new Virtual Server and try to preview the site I get the following error, until I reboot the server, then the preview works as expected. I tried restarting Apache without the reboot, but no joy.

Any suggestions?

-Jeff

Error: template '/home/homeiqsystems/public_html/index.html' not found

Fri, 03/20/2009 - 14:23
Joe
Joe's picture

That's an odd error. I don't think Virtualmin has anything that would respond that way. What's in the Apache error log for this virtual server when you see this error?

--

Check out the forum guidelines!

Fri, 03/20/2009 - 14:55
synergos

Error log is empty. Perhaps this is not a Virtualmin related error?

It may be WebDNA, now that I think of it. WebDNA calls pages templates. Perhaps it has some thing to do with the order in which the Apache directives are processed, since the new Virtual Server gets appended to the bottom of the http.conf and the include for webdna.conf is above the Virtual Host settings.

Is it possible that Apache would load the directives differently when restarted as opposed to a server reboot?

-Jeff

Fri, 03/20/2009 - 21:16 (Reply to #3)
Joe
Joe's picture

<div class='quote'>Is it possible that Apache would load the directives differently when restarted as opposed to a server reboot?</div>

No, but if WebDNA has an independent process...it wouldn't be restated during a graceful reload of Apache (which is what Virtualmin does under most circumstances). If it's entirely separate, then it would definitely need a restart.

You can do that using a post creation script. These are configured in the Module Config in the &quot;Actions upon server and user creation&quot;.

--

Check out the forum guidelines!

Sat, 03/21/2009 - 11:26 (Reply to #4)
synergos

Thanks Joe. I'll do it.

-Jeff

Fri, 03/20/2009 - 15:32
synergos

Definitely a WebDNA problem. I restarted WebDNA, and the error went away. It still may have something to do with the way the Virtual Host directives are loaded after an update to httpd.conf.

-Jeff

Topic locked