suexec command configured to /var/www

3 posts / 0 new
Last post
#1 Sun, 04/12/2009 - 10:24
mrwilder

suexec command configured to /var/www

Virtualmin gives this error when I try checking the configuration.

The Suexec command on your system is configured to only run scripts under /var/www, but the Virtualmin base directory is /home. CGI and PHP scripts run as domain owners will not be executed.

Okay, I admit I've seen posts about this thread everywhere, but all the topics seem to be way above my head. The one that DOES seem to be a useful set of instructions is, uh, written in German and I can't follow it closely enough to be confident.

Oddly, this is my second box with webmin/virtualmin. I installed one a few weeks ago and everything went so smooth I decided to build another one... this one has been all problems although I'm following similar procedures.

Does anyone have a clear explanation of what I'm supposed to do?

I'm fine with rebuilding suexec, uh... but, am I supposed to rebuild apache with different arguments? Sorry couldn't follow all the threads. For example, most of the time Joe says that disabling suexec in Virtualmin would work.

However, the path to do that is not evident on my machine, eg., there's no System->Settings->Templates path (or whatever it was) that I see.

By the way, this virtualmin appears to be a "module" in webmin, but on the machine that actually works, it's a separate thing than webmin, apparently. It has it's own entire menu on that machine (?)<br><br>Post edited by: mrwilder, at: 2009/04/12 11:18

Sun, 04/12/2009 - 16:54
andreychek

Well, perhaps before we go down the path to how to fix it, maybe we can explore the path of how the problem occurs in the first place :-)

Aside from the rare bug, that problem you're seeing exclusively occurs when Virtualmin is installed without using the wonderful install.sh utility.

The install.sh tool handles all the aspects of the installation -- it pulls down all the prerequisites, it configures Apache, Postfix, SpamAssassin, ClamAV, BIND, amongst others.

The install.sh makes sure that the Apache packages on your system have the correct suexec.

So my question for you is -- if you didn't install using the install.sh script, is that an option?

Are you in a position where you can start over with a fresh distro install? If so, I'd highly recommend using the install.sh script -- the GPL version is available here:

http://software.virtualmin.com/gpl/scripts/install.sh

On the other hand, if you have a live system now, then the install.sh program will likely break it, so that wouldn't be a good idea. If that's the case, then we can work on tweaking your setup to fix suexec.
-Eric

Sun, 04/12/2009 - 18:05
Joe
Joe's picture

<div class='quote'>Oddly, this is my second box with webmin/virtualmin. I installed one a few weeks ago and everything went so smooth I decided to build another one... this one has been all problems although I'm following similar procedures.</div>

Definitely not similar procedures. You clearly used install.sh for the first install, and didn't use install.sh for the second. That would explain the &quot;Virtualmin is a module&quot; behavior, as well as the &quot;suexec points to /var/www&quot; behavior. And that's just scratching the surface of all of the things that don't get configured when you don't use install.sh.

Installing with install.sh is expected to go smoothly on any freshly installed grade A supported OS...installing manually is expected to go very unsmoothly, requiring hours of effort and reading lots and lots of documentation. I suggest only really serious hard core UNIX experts attempt the manual installation.

--

Check out the forum guidelines!

Topic locked