Based on trying to understand what’s wrong, from other threads I gather that the install for some reason didn’t replace my apache after upgrading to Virtualmin Pro:
If so, anything needs to be done after that? and just wondering why the upgrade didn’t do this?
From what I can tell this should be fine… it’s the equivalent of what I did (except apt/debian in my case) to address the issue when I had it. After doing so everything was fine, no additional steps were necessary.
however…apache is already there I guess, so got the response ‘nothing to do’.
what I did was change the document root in the httpd.conf file in two places from /var/www/html to /home and restarted apache
Got the following response:
[code:1]Failed to apply changes :
[Sun Dec 23 02:45:39 2007] [error] [client 127.0.0.1] Directory index forbidden by Options directive: /var/www/html/
[Sun Dec 23 05:09:21 2007] [notice] caught SIGTERM, shutting down
[Sun Dec 23 05:09:23 2007] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Sun Dec 23 05:09:23 2007] [notice] Digest: generating secret for digest authentication …
[Sun Dec 23 05:09:23 2007] [notice] Digest: done[/code:1]
suexec -V still shows -D AP_DOC_ROOT="/var/www" and asking a .cgi to execute in a virtual domain still reflects from error log of suexec: command not in docroot
The document root in ‘Apache webserver’ is showing as /home under the default server and when I restarted apache again, there were no errors.
Now…how do I change the document root to reflect as /home in suexec
OK…reverted back to square one from a backup, so everything is back to where it was, that is: -D AP_DOC_ROOT="/var/www"
In the meantime, had also tried to load mod_fcgid without any success. Got to the stage of correcting the MAKEFILE to the correct top_dir path but when I asked to make I got:
Makefile:13: /etc/httpd/build/special.mk: No such file or directory
make: *** No rule to make target `/etc/httpd/build/special.mk’. Stop.
So…obviously my upgrade to Pro didn’t pick up certain aspects that it had to. Once again if I may…
1. How do I change the suexec docroot to /home in a centos-release-5-1.0.el5.centos.1 httpd-2.2.3-11.el5.centos environment that I understand is required, and should have been so by default with an upgrade.
2. How do I load mod_fcgid module that I understand is required, and should have been so by default with an upgrade.
Should replace your Apache with a righteous build. We hope. If it doesn’t, let me know why it refuses and I try to help you resolgve it.
SuExec is the one binary you cannot screw around with–it is a security package with extreme prejudice about anything out of the ordinary. Modifying it is effectively saying, "someone has done something nasty and intends to use suexec for evil rather than good".
mod_fcgid is also easy to get:
yum install mod_fcgid
If it fails, let me know the error. It sounds like the upgrade from GPL isn’t working correctly, as it should have fixed both of these things automatically.
Yeah…having fun…good learning process!! Appreciate your guidance.
[code:1][root@host ~]# yum update httpd
Loading "installonlyn" plugin
Setting up Update Process
Setting up repositories
rpmforge 100% |=========================| 1.1 kB 00:00
base 100% |=========================| 1.1 kB 00:00
updates 100% |=========================| 951 B 00:00
addons 100% |=========================| 951 B 00:00
extras 100% |=========================| 1.1 kB 00:00
Reading repository metadata in from local files
Could not find update match for httpd
No Packages marked for Update/Obsoletion
[root@host ~]# yum install mod_fcgid
Loading "installonlyn" plugin
Setting up Install Process
Setting up repositories
Reading repository metadata in from local files
Parsing package install arguments
Nothing to do[/code:1]
Had actually tried that sometime before with the same results.
If it fails, let me know the error. It sounds like the upgrade from GPL isn't working correctly, as it should have fixed both of these things automatically.
Didn’t have time to pursue this thread, but now have some time to get this right.
If it fails, let me know the error. It sounds like the upgrade from GPL isn't working correctly, as it should have fixed both of these things automatically.
Is there another method to request for support? Mail sent to support [at] virtualmin.com does not respond.
The compare page states:-
Unlimited premium support via email and issue tracker for all Virtualmin Professional customers, with usual response time under 24 hours.
Anyone knows which email address is being refered to above?
You don’t have Virtualmin repositories there at all. Howd’d that happen? (You’ve also got a non-OS repository “rpmforge” that is almost certainly going to cause problems.)
So, you upgraded to Pro via the “Upgrade” option within Virtualmin, right? Were there any errors during the upgrade? This doesn’t look like anything actually happened with the upgrade, as everything ought to be coming in from our yum repository. How about sending me server details via email, and I’ll drop in on this box and see if I can figure out what went wrong.
Is there another method to request for support? Mail sent to support [at] virtualmin.com does not respond.
I meant here in this thread. But, I managed to miss the message where you actually posted the results.
The ticket tracker is always the better method. Email is just for folks are aren’t comfortable with the ticket tracker for some reason…but I’ve removed it as a suggestion, as it’s become impossible for me to keep up with all of the support email I get now. With the ticket tracker, it’ll be seen by both me and Jamie, and we’ll be hiring an extra support person in the next month or two to help out. Tickets will always be the most likely to get some sort of response quickly. Email gets further and further backed up, as our customer base grows and Joe fails to scale (support@ is just me, in case I hadn’t made that clear–without dumping those messages into a ticket tracker, there’d be no way to keep up with which ones had been answered and by whom, so it’s a one man operation).
