From: Seb <sp...@gm...> - 2013-07-20 22:52:59
|
Hi, Since the last Apache 2.2 upgrade in Debian, I cannot see where to configure the userdir module. It used to be in "Document Options" of the Default Server as "User WWW directory". Now this option is no longer there. FWIW, here are the contents of the relevant module config: ---<--------------------cut here---------------start------------------->--- <IfModule mod_userdir.c> UserDir public_html UserDir disabled root <Directory /home/*/public_html> AllowOverride FileInfo AuthConfig Limit Indexes Options MultiViews Indexes SymLinksIfOwnerMatch IncludesNoExec <Limit GET POST OPTIONS> Require all granted </Limit> <LimitExcept GET POST OPTIONS> Require all denied </LimitExcept> </Directory> </IfModule> # vim: syntax=apache ts=4 sw=4 sts=4 sr noet ---<--------------------cut here---------------end--------------------->--- Any tips on how to configure this in Webmin 1.630 appreciated. Cheers, -- Seb |
From: Jamie C. <jca...@we...> - 2013-07-21 02:20:25
|
On 20/Jul/2013 08:11 Seb <sp...@gm...> wrote .. > Hi, > > Since the last Apache 2.2 upgrade in Debian, I cannot see where to > configure the userdir module. It used to be in "Document Options" of > the Default Server as "User WWW directory". Now this option is no > longer there. FWIW, here are the contents of the relevant module > config: > > ---<--------------------cut here---------------start------------------->--- > <IfModule mod_userdir.c> > UserDir public_html > UserDir disabled root > > <Directory /home/*/public_html> > AllowOverride FileInfo AuthConfig Limit Indexes > Options MultiViews Indexes SymLinksIfOwnerMatch IncludesNoExec > <Limit GET POST OPTIONS> > Require all granted > </Limit> > <LimitExcept GET POST OPTIONS> > Require all denied > </LimitExcept> > </Directory> > </IfModule> > > # vim: syntax=apache ts=4 sw=4 sts=4 sr noet > ---<--------------------cut here---------------end--------------------->--- > > Any tips on how to configure this in Webmin 1.630 appreciated. Those options still appear on my system. Perhaps Webmin thinks that mod_userdir isn't enabled? You can check by grepping for userdir in /etc/webmin/apache/site - Jamie |
From: Seb <sp...@gm...> - 2013-07-21 04:24:27
|
On Sat, 20 Jul 2013 19:20:17 -0700 (PDT), "Jamie Cameron" <jca...@we...> wrote: > On 20/Jul/2013 08:11 Seb <sp...@gm...> wrote .. >> Hi, >> Since the last Apache 2.2 upgrade in Debian, I cannot see where to >> configure the userdir module. It used to be in "Document Options" of >> the Default Server as "User WWW directory". Now this option is no >> longer there. FWIW, here are the contents of the relevant module >> config: >> ---<--------------------cut >> here---------------start------------------->--- <IfModule >> mod_userdir.c> UserDir public_html UserDir disabled root >> <Directory /home/*/public_html> AllowOverride FileInfo AuthConfig >> Limit Indexes Options MultiViews Indexes SymLinksIfOwnerMatch >> IncludesNoExec <Limit GET POST OPTIONS> Require all granted </Limit> >> <LimitExcept GET POST OPTIONS> Require all denied </LimitExcept> >> </Directory> </IfModule> >> # vim: syntax=apache ts=4 sw=4 sts=4 sr noet >> ---<--------------------cut >> here---------------end--------------------->--- >> Any tips on how to configure this in Webmin 1.630 appreciated. > Those options still appear on my system. Perhaps Webmin thinks that > mod_userdir isn't enabled? You can check by grepping for userdir in > /etc/webmin/apache/site Interesting, something seems hosed then with my Webmin (Debian): ╭───── [ sudo cat /etc/webmin/apache/site ] │ modules=core/2.44 mod_log_config/2.44 │ webmin=1.630 │ path=/usr/sbin/apache2 │ size=614432 ╰───── And yet, I see several modules as enabled (as I have done so) under Global Configuration -> Configure Apache modules. Should I toggle these modules in that section? Thanks, -- Seb |
From: Andrey R. <anr...@fr...> - 2013-07-21 20:20:04
|
Greetings, Webmin users list! >> On 20/Jul/2013 08:11 Seb <sp...@gm...> wrote .. >>> Hi, >>> Since the last Apache 2.2 upgrade in Debian, I cannot see where to >>> configure the userdir module. It used to be in "Document Options" of >>> the Default Server as "User WWW directory". Now this option is no >>> longer there. FWIW, here are the contents of the relevant module >>> config: >>> ---<--------------------cut >>> here---------------start------------------->--- <IfModule >>> mod_userdir.c> UserDir public_html UserDir disabled root >>> <Directory /home/*/public_html> AllowOverride FileInfo AuthConfig >>> Limit Indexes Options MultiViews Indexes SymLinksIfOwnerMatch >>> IncludesNoExec <Limit GET POST OPTIONS> Require all granted </Limit> >>> <LimitExcept GET POST OPTIONS> Require all denied </LimitExcept> >>> </Directory> </IfModule> >>> # vim: syntax=apache ts=4 sw=4 sts=4 sr noet >>> ---<--------------------cut >>> here---------------end--------------------->--- >>> Any tips on how to configure this in Webmin 1.630 appreciated. >> Those options still appear on my system. Perhaps Webmin thinks that >> mod_userdir isn't enabled? You can check by grepping for userdir in >> /etc/webmin/apache/site > Interesting, something seems hosed then with my Webmin (Debian): > ?----- [ sudo cat /etc/webmin/apache/site ] > ¦ modules=core/2.44 mod_log_config/2.44 > ¦ webmin=1.630 > ¦ path=/usr/sbin/apache2 > ¦ size=614432 > ?----- > And yet, I see several modules as enabled (as I have done so) under > Global Configuration -> Configure Apache modules. Should I toggle these > modules in that section? apache2ctl -M ? -- WBR, Andrey Repin (anr...@fr...) 21.07.2013, <23:20> Sorry for my terrible english... |
From: Seb <sp...@gm...> - 2013-07-21 04:30:13
|
On Sat, 20 Jul 2013 23:24:09 -0500, Seb <sp...@gm...> wrote: [...] > And yet, I see several modules as enabled (as I have done so) under > Global Configuration -> Configure Apache modules. Should I toggle > these modules in that section? I just toggled only userdir off/on, to no avail... -- Seb |
From: Seb <sp...@gm...> - 2013-07-21 22:24:51
|
On Sun, 21 Jul 2013 23:20:51 +0400, Andrey Repin <anr...@fr...> wrote: [...] > apache2ctl -M ? Everything is as I expect: ╭───── [ sudo apache2ctl -M ] │ Loaded Modules: │ core_module (static) │ so_module (static) │ watchdog_module (static) │ http_module (static) │ log_config_module (static) │ logio_module (static) │ version_module (static) │ unixd_module (static) │ unixd_module (static) │ access_compat_module (shared) │ alias_module (shared) │ auth_basic_module (shared) │ authn_core_module (shared) │ authn_file_module (shared) │ authz_core_module (shared) │ authz_groupfile_module (shared) │ authz_host_module (shared) │ authz_user_module (shared) │ autoindex_module (shared) │ cgi_module (shared) │ dav_module (shared) │ deflate_module (shared) │ dir_module (shared) │ env_module (shared) │ filter_module (shared) │ mime_module (shared) │ mpm_prefork_module (shared) │ negotiation_module (shared) │ reqtimeout_module (shared) │ rewrite_module (shared) │ setenvif_module (shared) │ status_module (shared) │ userdir_module (shared) ╰───── As Jamie suggests, Webmin seems to think userdir is not enabled. Thanks, -- Seb |
From: Jamie C. <jca...@we...> - 2013-07-22 07:43:41
|
How about if you run httpd -l ? That's the command Webmin uses to get the list of modules, combined with any LoadModule lines in your Apache config. On 21/Jul/2013 15:24 Seb <sp...@gm...> wrote .. > On Sun, 21 Jul 2013 23:20:51 +0400, > Andrey Repin <anr...@fr...> wrote: > > [...] > > > apache2ctl -M ? > > Everything is as I expect: > > ╭───── [ sudo apache2ctl -M ] > │ Loaded Modules: > │ core_module (static) > │ so_module (static) > │ watchdog_module (static) > │ http_module (static) > │ log_config_module (static) > │ logio_module (static) > │ version_module (static) > │ unixd_module (static) > │ unixd_module (static) > │ access_compat_module (shared) > │ alias_module (shared) > │ auth_basic_module (shared) > │ authn_core_module (shared) > │ authn_file_module (shared) > │ authz_core_module (shared) > │ authz_groupfile_module (shared) > │ authz_host_module (shared) > │ authz_user_module (shared) > │ autoindex_module (shared) > │ cgi_module (shared) > │ dav_module (shared) > │ deflate_module (shared) > │ dir_module (shared) > │ env_module (shared) > │ filter_module (shared) > │ mime_module (shared) > │ mpm_prefork_module (shared) > │ negotiation_module (shared) > │ reqtimeout_module (shared) > │ rewrite_module (shared) > │ setenvif_module (shared) > │ status_module (shared) > │ userdir_module (shared) > ╰───── > > As Jamie suggests, Webmin seems to think userdir is not enabled. > > Thanks, > > -- > Seb > > > ------------------------------------------------------------------------------ > See everything from the browser to the database with AppDynamics > Get end-to-end visibility with application monitoring from AppDynamics > Isolate bottlenecks and diagnose root cause in seconds. > Start your free trial of AppDynamics Pro today! > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > - > Forwarded by the Webmin mailing list at web...@li... > To remove yourself from this list, go to > http://lists.sourceforge.net/lists/listinfo/webadmin-list |
From: Seb <sp...@gm...> - 2013-07-22 13:02:10
|
On Mon, 22 Jul 2013 00:43:31 -0700 (PDT), "Jamie Cameron" <jca...@we...> wrote: > How about if you run httpd -l ? That's the command Webmin uses to get > the list of modules, combined with any LoadModule lines in your Apache > config. That command doesn't exist in my system (Debian sid). Should I install the package that provides it? Thanks, -- Seb |
From: Jamie C. <jca...@we...> - 2013-07-22 14:15:31
|
Are you sure the httpd command doesn't exist anywhere on your system? You can find it with : find / -type f -name httpd On Jul 22, 2013, at 9:01 PM, Seb <sp...@gm...> wrote: > On Mon, 22 Jul 2013 00:43:31 -0700 (PDT), > "Jamie Cameron" <jca...@we...> wrote: > >> How about if you run httpd -l ? That's the command Webmin uses to get >> the list of modules, combined with any LoadModule lines in your Apache >> config. > > That command doesn't exist in my system (Debian sid). Should I install > the package that provides it? > > Thanks, > > -- > Seb > > > ------------------------------------------------------------------------------ > See everything from the browser to the database with AppDynamics > Get end-to-end visibility with application monitoring from AppDynamics > Isolate bottlenecks and diagnose root cause in seconds. > Start your free trial of AppDynamics Pro today! > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > - > Forwarded by the Webmin mailing list at web...@li... > To remove yourself from this list, go to > http://lists.sourceforge.net/lists/listinfo/webadmin-list > |
From: Kormos 'M. G. <mo...@kt...> - 2013-07-22 14:46:42
|
httpd is the RedHat name for Apache. Debian and derivatives use the name apache2. Try apache2 -l Morc. On 22/07/2013 16:15, Jamie Cameron wrote: > Are you sure the httpd command doesn't exist anywhere on your system? You can find it with : > > find / -type f -name httpd > > On Jul 22, 2013, at 9:01 PM, Seb <sp...@gm...> wrote: > >> On Mon, 22 Jul 2013 00:43:31 -0700 (PDT), >> "Jamie Cameron" <jca...@we...> wrote: >> >>> How about if you run httpd -l ? That's the command Webmin uses to get >>> the list of modules, combined with any LoadModule lines in your Apache >>> config. >> That command doesn't exist in my system (Debian sid). Should I install >> the package that provides it? >> >> Thanks, >> >> -- >> Seb >> >> >> ------------------------------------------------------------------------------ >> See everything from the browser to the database with AppDynamics >> Get end-to-end visibility with application monitoring from AppDynamics >> Isolate bottlenecks and diagnose root cause in seconds. >> Start your free trial of AppDynamics Pro today! >> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk >> - >> Forwarded by the Webmin mailing list at web...@li... >> To remove yourself from this list, go to >> http://lists.sourceforge.net/lists/listinfo/webadmin-list >> > ------------------------------------------------------------------------------ > See everything from the browser to the database with AppDynamics > Get end-to-end visibility with application monitoring from AppDynamics > Isolate bottlenecks and diagnose root cause in seconds. > Start your free trial of AppDynamics Pro today! > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > - > Forwarded by the Webmin mailing list at web...@li... > To remove yourself from this list, go to > http://lists.sourceforge.net/lists/listinfo/webadmin-list |
From: Seb <sp...@gm...> - 2013-07-22 17:19:28
|
On Mon, 22 Jul 2013 16:27:34 +0200, Kormos 'Morc' Gábor <mo...@kt...> wrote: > httpd is the RedHat name for Apache. Debian and derivatives use the > name apache2. Try apache2 -l Thank you Gábor, indeed here seems to be the problem: ╭───── [ sudo apache2 -l ] │ Compiled in modules: │ core.c │ mod_so.c │ mod_watchdog.c │ http_core.c │ mod_log_config.c │ mod_logio.c │ mod_version.c │ mod_unixd.c │ mod_unixd.c ╰───── What is going on? I bet I missed doing something during the update to the Debian Apache2 packages. -- Seb |
From: Kormos 'M. G. <mo...@kt...> - 2013-07-22 17:39:39
|
Hi Seb, On 22/07/2013 19:19, Seb wrote: > On Mon, 22 Jul 2013 16:27:34 +0200, > Kormos 'Morc' Gábor <mo...@kt...> wrote: > >> httpd is the RedHat name for Apache. Debian and derivatives use the >> name apache2. Try apache2 -l > Thank you Gábor, indeed here seems to be the problem: > > ╭───── [ sudo apache2 -l ] > │ Compiled in modules: > │ core.c > │ mod_so.c > │ mod_watchdog.c > │ http_core.c > │ mod_log_config.c > │ mod_logio.c > │ mod_version.c > │ mod_unixd.c > │ mod_unixd.c > ╰───── > > What is going on? I bet I missed doing something during the update to > the Debian Apache2 packages. I'm on Ubuntu, not sure if it's the same on Debian, but only some core modules are compiled into Apache2 and most are loaded. -l only shows compiled in modules. As root execute "source /etc/apache2/envvars" then execute "apache2 -t -D DUMP_MODULES" to get a list of modules which are configured to load. I think this will not list modules which could be loaded successfully, only which are configured to load, but if Apache2 runs fine I think this list is comprehensive. Since you use Sid it is possible that the update package broke your previous install. I don't recall if a package update/upgrade resets the enabled modules or not, so that could explain why userdir is not loaded any more. If userdir is not loaded you can enable it with "a2enmod userdir" executed as root, and then restart Apache to have it available. Morc. |
From: Seb <sp...@gm...> - 2013-07-22 19:28:07
|
On Mon, 22 Jul 2013 19:39:24 +0200, Kormos 'Morc' Gábor <mo...@kt...> wrote: [...] > I'm on Ubuntu, not sure if it's the same on Debian, but only some > core modules are compiled into Apache2 and most are loaded. -l only > shows compiled in modules. As root execute "source > /etc/apache2/envvars" then execute "apache2 -t -D DUMP_MODULES" to get > a list of modules which are configured to load. I think this will not > list modules which could be loaded successfully, only which are > configured to load, but if Apache2 runs fine I think this list is > comprehensive. Since you use Sid it is possible that the update > package broke your previous install. I don't recall if a package > update/upgrade resets the enabled modules or not, so that could > explain why userdir is not loaded any more. If userdir is not loaded > you can enable it with "a2enmod userdir" executed as root, and then > restart Apache to have it available. But I'm confused, 'apache2ctl -l' reports userdir and many other modules as loaded, as in my earlier post, and 'a2enmod userdir' tells me that "Module userdir already enabled". So userdir is certainly loaded, but somehow Webmin doesn't know about it. -- Seb |
From: Kormos 'M. G. <mo...@kt...> - 2013-07-22 19:36:39
|
Sorry, I only subscribed to see when a new version is out and saw your trouble with not finding httpd... I can't help you with Webmin problems really. Morc. On 22/07/2013 21:27, Seb wrote: > On Mon, 22 Jul 2013 19:39:24 +0200, > Kormos 'Morc' Gábor <mo...@kt...> wrote: > > [...] > >> I'm on Ubuntu, not sure if it's the same on Debian, but only some >> core modules are compiled into Apache2 and most are loaded. -l only >> shows compiled in modules. As root execute "source >> /etc/apache2/envvars" then execute "apache2 -t -D DUMP_MODULES" to get >> a list of modules which are configured to load. I think this will not >> list modules which could be loaded successfully, only which are >> configured to load, but if Apache2 runs fine I think this list is >> comprehensive. Since you use Sid it is possible that the update >> package broke your previous install. I don't recall if a package >> update/upgrade resets the enabled modules or not, so that could >> explain why userdir is not loaded any more. If userdir is not loaded >> you can enable it with "a2enmod userdir" executed as root, and then >> restart Apache to have it available. > But I'm confused, 'apache2ctl -l' reports userdir and many other modules > as loaded, as in my earlier post, and 'a2enmod userdir' tells me that > "Module userdir already enabled". So userdir is certainly loaded, but > somehow Webmin doesn't know about it. > > |
From: Jamie C. <jca...@we...> - 2013-07-23 04:18:08
|
On 22/Jul/2013 12:27 Seb <sp...@gm...> wrote .. > On Mon, 22 Jul 2013 19:39:24 +0200, > Kormos 'Morc' Gábor <mo...@kt...> wrote: > > [...] > > > I'm on Ubuntu, not sure if it's the same on Debian, but only some > > core modules are compiled into Apache2 and most are loaded. -l only > > shows compiled in modules. As root execute "source > > /etc/apache2/envvars" then execute "apache2 -t -D DUMP_MODULES" to get > > a list of modules which are configured to load. I think this will not > > list modules which could be loaded successfully, only which are > > configured to load, but if Apache2 runs fine I think this list is > > comprehensive. Since you use Sid it is possible that the update > > package broke your previous install. I don't recall if a package > > update/upgrade resets the enabled modules or not, so that could > > explain why userdir is not loaded any more. If userdir is not loaded > > you can enable it with "a2enmod userdir" executed as root, and then > > restart Apache to have it available. > > But I'm confused, 'apache2ctl -l' reports userdir and many other modules > as loaded, as in my earlier post, and 'a2enmod userdir' tells me that > "Module userdir already enabled". So userdir is certainly loaded, but > somehow Webmin doesn't know about it. Currently, Webmin doesn't use the apache2ctl -l command to find modules, as some older Apache releases don't support that flag. Instead it looks at the core modules (as shown by apache2 -l) , and also at any LoadModule lines in your Apache config file. Does your Apache config contain any LoadModule entries, and if so is there one for the userdir module? - Jamie |
From: Seb <sp...@gm...> - 2013-07-23 16:12:29
|
On Mon, 22 Jul 2013 21:18:00 -0700 (PDT), "Jamie Cameron" <jca...@we...> wrote: [...] > Currently, Webmin doesn't use the apache2ctl -l command to find > modules, as some older Apache releases don't support that > flag. Instead it looks at the core modules (as shown by apache2 -l) , > and also at any LoadModule lines in your Apache config file. > Does your Apache config contain any LoadModule entries, and if so is > there one for the userdir module? Thanks, I get it now: ╭───── [ sudo apache2 -l ] │ Compiled in modules: │ core.c │ mod_so.c │ mod_watchdog.c │ http_core.c │ mod_log_config.c │ mod_logio.c │ mod_version.c │ mod_unixd.c │ mod_unixd.c ╰───── and /etc/apache2/apache2.conf doesn't contain any LoadModule entries. Following the hints at the top: ╭───── [ head -n48 /etc/apache2/apache2.conf ] │ # This is the main Apache server configuration file. It contains the │ # configuration directives that give the server its instructions. │ # See http://httpd.apache.org/docs/2.4/ for detailed information about │ # the directives and /usr/share/doc/apache2/README.Debian about Debian specific │ # hints. │ # │ # │ # Summary of how the Apache 2 configuration works in Debian: │ # The Apache 2 web server configuration in Debian is quite different to │ # upstream's suggested way to configure the web server. This is because Debian's │ # default Apache2 installation attempts to make adding and removing modules, │ # virtual hosts, and extra configuration directives as flexible as possible, in │ # order to make automating the changes and administering the server as easy as │ # possible. │ │ # It is split into several files forming the configuration hierarchy outlined │ # below, all located in the /etc/apache2/ directory: │ # │ # /etc/apache2/ │ # |-- apache2.conf │ # | `-- ports.conf │ # |-- mods-enabled │ # | |-- *.load │ # | `-- *.conf │ # |-- conf-enabled │ # | `-- *.conf │ # `-- sites-enabled │ # `-- *.conf │ # │ # │ # * apache2.conf is the main configuration file (this file). It puts the pieces │ # together by including all remaining configuration files when starting up the │ # web server. │ # │ # * ports.conf is always included from the main configuration file. It is │ # supposed to determine listening ports for incoming connections which can be │ # customized anytime. │ # │ # * Configuration files in the mods-enabled/, conf-enabled/ and sites-enabled/ │ # directories contain particular configuration snippets which manage modules, │ # global configuration fragments, or virtual host configurations, │ # respectively. │ # │ # They are activated by symlinking available configuration files from their │ # respective *-available/ counterparts. These should be managed by using our │ # helpers a2enmod/a2dismod, a2ensite/a2dissite and a2enconf/a2disconf. See │ # their respective man pages for detailed information. │ # ╰───── and: ╭───── [ README.Debian.gz (lines: 40 - 56) ] │ Files and Directories in '/etc/apache2': │ --------------------------------------- │ │ apache2.conf │ │ This is the main configuration file. It does not include any │ actual configuration we expect to be adapted on your site, so │ where possible please do not touch it. This file is the │ foundation stone of the Apache configuration in Debian and should │ be up to date after upgrades to make sure all configuration pieces │ are properly included. │ │ If you want to extend the global configuration, you can customize │ the Apache web server by including configuration files through the │ conf-available mechanism. To change listening ports and socket │ configuration use ports.conf (see below). ╰───── So I guess that in order to have Apache2 play nice with Webmin we do need to go against the recommendation and touch /etc/apache2/apache2.conf. However, I'm afraid this would break the way Apache2 works and may break with every upgrade because of the structure in place (notice *.load and *.conf files for each module). What do you think? Thanks, -- Seb |
From: Andrey R. <anr...@fr...> - 2013-07-24 01:35:19
|
Greetings, Webmin users list! >> Currently, Webmin doesn't use the apache2ctl -l command to find >> modules, as some older Apache releases don't support that >> flag. Instead it looks at the core modules (as shown by apache2 -l) , >> and also at any LoadModule lines in your Apache config file. >> Does your Apache config contain any LoadModule entries, and if so is >> there one for the userdir module? > Thanks, I get it now: > ?----- [ sudo apache2 -l ] > ¦ Compiled in modules: > ¦ core.c > ¦ mod_so.c > ¦ mod_watchdog.c > ¦ http_core.c > ¦ mod_log_config.c > ¦ mod_logio.c > ¦ mod_version.c > ¦ mod_unixd.c > ¦ mod_unixd.c > ?----- > and /etc/apache2/apache2.conf doesn't contain any LoadModule entries. > Following the hints at the top: > ?----- [ head -n48 /etc/apache2/apache2.conf ] > ¦ # This is the main Apache server configuration file. It contains the > ¦ # configuration directives that give the server its instructions. > ¦ # See http://httpd.apache.org/docs/2.4/ for detailed information about > ¦ # the directives and /usr/share/doc/apache2/README.Debian about Debian specific > ¦ # hints. > ¦ # > ¦ # > ¦ # Summary of how the Apache 2 configuration works in Debian: > ¦ # The Apache 2 web server configuration in Debian is quite different to > ¦ # upstream's suggested way to configure the web server. This is because Debian's > ¦ # default Apache2 installation attempts to make adding and removing modules, > ¦ # virtual hosts, and extra configuration directives as flexible as possible, in > ¦ # order to make automating the changes and administering the server as easy as > ¦ # possible. > ¦ > ¦ # It is split into several files forming the configuration hierarchy outlined > ¦ # below, all located in the /etc/apache2/ directory: > ¦ # > ¦ # /etc/apache2/ > ¦ # |-- apache2.conf > ¦ # | `-- ports.conf > ¦ # |-- mods-enabled > ¦ # | |-- *.load > ¦ # | `-- *.conf > ¦ # |-- conf-enabled > ¦ # | `-- *.conf > ¦ # `-- sites-enabled > ¦ # `-- *.conf > ¦ # > ¦ # > ¦ # * apache2.conf is the main configuration file (this file). It puts the pieces > ¦ # together by including all remaining configuration files when starting up the > ¦ # web server. > ¦ # > ¦ # * ports.conf is always included from the main configuration file. It is > ¦ # supposed to determine listening ports for incoming connections which can be > ¦ # customized anytime. > ¦ # > ¦ # * Configuration files in the mods-enabled/, conf-enabled/ and sites-enabled/ > ¦ # directories contain particular configuration snippets which manage modules, > ¦ # global configuration fragments, or virtual host configurations, > ¦ # respectively. > ¦ # > ¦ # They are activated by symlinking available configuration files from their > ¦ # respective *-available/ counterparts. These should be managed by using our > ¦ # helpers a2enmod/a2dismod, a2ensite/a2dissite and a2enconf/a2disconf. See > ¦ # their respective man pages for detailed information. > ¦ # > ?----- > and: > ?----- [ README.Debian.gz (lines: 40 - 56) ] > ¦ Files and Directories in '/etc/apache2': > ¦ --------------------------------------- > ¦ > ¦ apache2.conf > ¦ > ¦ This is the main configuration file. It does not include any > ¦ actual configuration we expect to be adapted on your site, so > ¦ where possible please do not touch it. This file is the > ¦ foundation stone of the Apache configuration in Debian and should > ¦ be up to date after upgrades to make sure all configuration pieces > ¦ are properly included. > ¦ > ¦ If you want to extend the global configuration, you can customize > ¦ the Apache web server by including configuration files through the > ¦ conf-available mechanism. To change listening ports and socket > ¦ configuration use ports.conf (see below). > ?----- > So I guess that in order to have Apache2 play nice with Webmin we do > need to go against the recommendation and touch > /etc/apache2/apache2.conf. However, I'm afraid this would break the way > Apache2 works and may break with every upgrade because of the structure > in place (notice *.load and *.conf files for each module). What do you > think? If you ask me, Webmin should not rely on the contents of any file, where it is not necessary. In this case, you have a straightforward way to ask Apache HTTPD server itself, which module is configured to load at startup. -- WBR, Andrey Repin (anr...@fr...) 24.07.2013, <05:18> Sorry for my terrible english... |
From: Jamie C. <jca...@we...> - 2013-07-24 02:22:35
|
Agreed - in the next Webmin release, it will use apache2ctl -M to get the list of modules, rather than looking at the config file. On Jul 24, 2013, at 11:20 AM, Andrey Repin <anr...@fr...> wrote: > Greetings, Webmin users list! > >>> Currently, Webmin doesn't use the apache2ctl -l command to find >>> modules, as some older Apache releases don't support that >>> flag. Instead it looks at the core modules (as shown by apache2 -l) , >>> and also at any LoadModule lines in your Apache config file. > >>> Does your Apache config contain any LoadModule entries, and if so is >>> there one for the userdir module? > >> Thanks, I get it now: > >> ?----- [ sudo apache2 -l ] >> ¦ Compiled in modules: >> ¦ core.c >> ¦ mod_so.c >> ¦ mod_watchdog.c >> ¦ http_core.c >> ¦ mod_log_config.c >> ¦ mod_logio.c >> ¦ mod_version.c >> ¦ mod_unixd.c >> ¦ mod_unixd.c >> ?----- > >> and /etc/apache2/apache2.conf doesn't contain any LoadModule entries. >> Following the hints at the top: > >> ?----- [ head -n48 /etc/apache2/apache2.conf ] >> ¦ # This is the main Apache server configuration file. It contains the >> ¦ # configuration directives that give the server its instructions. >> ¦ # See http://httpd.apache.org/docs/2.4/ for detailed information about >> ¦ # the directives and /usr/share/doc/apache2/README.Debian about Debian specific >> ¦ # hints. >> ¦ # >> ¦ # >> ¦ # Summary of how the Apache 2 configuration works in Debian: >> ¦ # The Apache 2 web server configuration in Debian is quite different to >> ¦ # upstream's suggested way to configure the web server. This is because Debian's >> ¦ # default Apache2 installation attempts to make adding and removing modules, >> ¦ # virtual hosts, and extra configuration directives as flexible as possible, in >> ¦ # order to make automating the changes and administering the server as easy as >> ¦ # possible. >> ¦ >> ¦ # It is split into several files forming the configuration hierarchy outlined >> ¦ # below, all located in the /etc/apache2/ directory: >> ¦ # >> ¦ # /etc/apache2/ >> ¦ # |-- apache2.conf >> ¦ # | `-- ports.conf >> ¦ # |-- mods-enabled >> ¦ # | |-- *.load >> ¦ # | `-- *.conf >> ¦ # |-- conf-enabled >> ¦ # | `-- *.conf >> ¦ # `-- sites-enabled >> ¦ # `-- *.conf >> ¦ # >> ¦ # >> ¦ # * apache2.conf is the main configuration file (this file). It puts the pieces >> ¦ # together by including all remaining configuration files when starting up the >> ¦ # web server. >> ¦ # >> ¦ # * ports.conf is always included from the main configuration file. It is >> ¦ # supposed to determine listening ports for incoming connections which can be >> ¦ # customized anytime. >> ¦ # >> ¦ # * Configuration files in the mods-enabled/, conf-enabled/ and sites-enabled/ >> ¦ # directories contain particular configuration snippets which manage modules, >> ¦ # global configuration fragments, or virtual host configurations, >> ¦ # respectively. >> ¦ # >> ¦ # They are activated by symlinking available configuration files from their >> ¦ # respective *-available/ counterparts. These should be managed by using our >> ¦ # helpers a2enmod/a2dismod, a2ensite/a2dissite and a2enconf/a2disconf. See >> ¦ # their respective man pages for detailed information. >> ¦ # >> ?----- > >> and: > >> ?----- [ README.Debian.gz (lines: 40 - 56) ] >> ¦ Files and Directories in '/etc/apache2': >> ¦ --------------------------------------- >> ¦ >> ¦ apache2.conf >> ¦ >> ¦ This is the main configuration file. It does not include any >> ¦ actual configuration we expect to be adapted on your site, so >> ¦ where possible please do not touch it. This file is the >> ¦ foundation stone of the Apache configuration in Debian and should >> ¦ be up to date after upgrades to make sure all configuration pieces >> ¦ are properly included. >> ¦ >> ¦ If you want to extend the global configuration, you can customize >> ¦ the Apache web server by including configuration files through the >> ¦ conf-available mechanism. To change listening ports and socket >> ¦ configuration use ports.conf (see below). >> ?----- > >> So I guess that in order to have Apache2 play nice with Webmin we do >> need to go against the recommendation and touch >> /etc/apache2/apache2.conf. However, I'm afraid this would break the way >> Apache2 works and may break with every upgrade because of the structure >> in place (notice *.load and *.conf files for each module). What do you >> think? > > If you ask me, Webmin should not rely on the contents of any file, where it is > not necessary. > In this case, you have a straightforward way to ask Apache HTTPD server > itself, which module is configured to load at startup. > > > -- > WBR, > Andrey Repin (anr...@fr...) 24.07.2013, <05:18> > > Sorry for my terrible english... > ------------------------------------------------------------------------------ > See everything from the browser to the database with AppDynamics > Get end-to-end visibility with application monitoring from AppDynamics > Isolate bottlenecks and diagnose root cause in seconds. > Start your free trial of AppDynamics Pro today! > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > - > Forwarded by the Webmin mailing list at web...@li... > To remove yourself from this list, go to > http://lists.sourceforge.net/lists/listinfo/webadmin-list |