Submitted by fuerst on Mon, 04/26/2010 - 14:11
When restoring a backed up alias subserver I get this error:
Checking restored PHP execution mode ..
Error: No <Directory> section found for mod_fcgid directives
Error
-----
No <Directory> section found for mod_fcgid directives
-----
Restore halts after that error.
Alias server usually don't have a option in their Apache conf file so I guess this is the reason for the error.
You may download this 2 backup files which you can use to reproduce the error:
http://fuerstnet.de/kram/redirect.test-fuerstnet.de.tar.gz http://fuerstnet.de/kram/test-fuerstnet.de.tar.gz
redirect.test-fuerstnet.de.tar.gz is the one producing the error.
If possible: I would appreciate a quick + dirty fix very much because I'm currently in the process of server migration.
Thanks in advance! Bernhard
Status:
Active
Comments
Submitted by fuerst on Mon, 04/26/2010 - 14:37 Comment #1
(add subscription)
Submitted by fuerst on Mon, 04/26/2010 - 16:17 Comment #2
Quick fix is to change lines 197 to 199 in /usr/share/webmin/virtual-server/php-lib.pl from
$dirstr || &error("No <Directory> section found ",
"for mod_fcgid directives");
push(@phpconfs, $dirstr);
to
# $dirstr || &error("No <Directory> section found ",
# "for mod_fcgid directives");
$dirstr && push(@phpconfs, $dirstr);
Submitted by JamieCameron on Mon, 04/26/2010 - 16:38 Comment #3
That's an odd error, as the code that checks the PHP execution mode isn't run for alias domains at all.
Was the domain redirect.test-fuerstnet.de perhaps already in existance on the target system, but as some type other than an alias domain?
On my test system, both backup files restored just fine.
Submitted by fuerst on Mon, 04/26/2010 - 17:04 Comment #4
redirect.test-fuerstnet.de already was in existance on the target system. With the same configuration though. I actually got the error on other alias domains too.
Submitted by JamieCameron on Mon, 04/26/2010 - 18:06 Comment #5
If you delete redirect.test-fuerstnet.de and then re-restore it, do you get the same error message?
Submitted by fuerst on Mon, 04/26/2010 - 19:02 Comment #6
Yes, same error. I deleted the whole test-fuerstnet.de server and restored it using this command:
virtualmin restore-domain --no-reuid --all-features --source /backup/umzug --domain test-fuerstnet.de --domain redirect.test-fuerstnet.de
.Output is attached.
Submitted by JamieCameron on Mon, 04/26/2010 - 23:19 Comment #7
Odd, on my systems this works just fine!
Which Virtualmin version are you running there?
Submitted by fuerst on Tue, 04/27/2010 - 05:02 Comment #8
It's 3.77 pro. Do you need access to the box?
Submitted by JamieCameron on Tue, 04/27/2010 - 11:59 Comment #9
Yes, that would be really useful.. you can either use our remote support access feature, or email me at jcameron@virtualmin.com
Submitted by JamieCameron on Wed, 04/28/2010 - 00:28 Comment #10
Ok, I see the cause now .. this is a Virtualmin bug, but it is only triggered when you have an alias domain configured to use a Redirect to the destination domain. I have patched the code on your system to handle this case, and will include the fix in Virtualmin versions 3.79 and later..
Submitted by Issues on Sun, 05/16/2010 - 01:53 Comment #11
Automatically closed -- issue fixed for 2 weeks with no activity.
Submitted by iann@fuelforce.com on Fri, 01/13/2012 - 19:27 Comment #12
Running Virtualmin 3.89 we ran into this issue attempting to migrate from one server to another. All our restore files failed with the message Restore error: No section found for mod_fcgid directives. Your suggestion to comment out lines in /usr/share/webmin/virtual-server/php-lib.pl did the trick
Here are the lines we commented out in the 3.89 version of the file: 222 #$dirstr || &error("No <Directory> section found ", 223 #"for mod_fcgid directives"); 224 #push(@phpconfs, $dirstr);
Submitted by JamieCameron on Fri, 01/13/2012 - 23:39 Comment #13
iann - was the domain this problem occurred for an alias, or a top-level virtual server?
Submitted by iann@fuelforce.com on Mon, 01/23/2012 - 14:52 Comment #14
They were all top level virtual servers.
Submitted by JamieCameron on Mon, 01/23/2012 - 15:37 Comment #15
If you validate one of these domains with a command like :
virtualmin validate-domain --domain example.com --all-features
does it report any errors?
Submitted by iann@fuelforce.com on Fri, 01/27/2012 - 15:50 Comment #16
Every virtual server returns the same error:
Apache website : Missing Apache <Directory> block for HTML directory /usr/local/fuelserve/accounts/<virtual server name>/public_html
Where <virtual server name> is the name of the virtual server.
Submitted by JamieCameron on Fri, 01/27/2012 - 18:23 Comment #17
Could you post the full <virtualhost> block from your Apache config file for one of these domains?