Re: apache2 what is the standard way to enable modules?
Bob Proulx b...@proulx.com writes: a2enmod takes a simple name like cgi not a name with .load or .conf on the end like cgi.load. You want a2enmod cgi without the .load on the end. Yeah, I finally got that part. But still not seeing what is bad about what I did... after all it did allow the cgi scripts to start working: From a previous post: Thanks for the push... Tinkering with your suggestion lead me to read the `LoadModule' lines on the files in mods-available. The line in cgi.load: LoadModule cgi_module /usr/lib/apache2/modules/mod_cgi.so Looked the most promising, so I tried: a2enmod cgi.load But it told me my MPM(?) seemed to be threaded so it gave me `cgid.conf' and `cgid.load'... and away it went... cgi firing on all 8 cylinders. That last bit was sort of warning I guess and the it proceeded to create the needed symlinks only with cgid.* in there names. After that command above, cgi scripts commenced to working. Apparently the command figured out what needed to be done. So, anyway... now I know a better and more appropriate command to use. Thanks to all. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/8761geh1tu@reader.local.lan
Re: apache2 what is the standard way to enable modules?
On 23/09/14 at 10:02am, Harry Putnam wrote: Bob Proulx b...@proulx.com writes: a2enmod takes a simple name like cgi not a name with .load or .conf on the end like cgi.load. You want a2enmod cgi without the .load on the end. Yeah, I finally got that part. But still not seeing what is bad about what I did... after all it did allow the cgi scripts to start working: Played with this by myself and yes, a2enmod also works if you add .load to the module name. From a previous post: Thanks for the push... Tinkering with your suggestion lead me to read the `LoadModule' lines on the files in mods-available. The line in cgi.load: LoadModule cgi_module /usr/lib/apache2/modules/mod_cgi.so Looked the most promising, so I tried: a2enmod cgi.load But it told me my MPM(?) seemed to be threaded so it gave me `cgid.conf' and `cgid.load'... and away it went... cgi firing on all 8 cylinders. That last bit was sort of warning I guess and the it proceeded to create the needed symlinks only with cgid.* in there names. After that command above, cgi scripts commenced to working. Apparently the command figured out what needed to be done. So, anyway... now I know a better and more appropriate command to use. -- « Nunc est bibendum, nunc pede libero pulsanda tellus » -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140923141125.gb19...@gmail.com
Re: apache2 what is the standard way to enable modules?
2014-09-20 7:48 GMT+02:00 Bob Proulx b...@proulx.com: Harry Putnam wrote: Raffaele Morelli writes: Is that what you are warning about? Nope, my warning was to use `a2enmod cgi` instead of `a2enmod cgi.load` (which is wrong) OK, thanks. But once again you've failed to explain the nature of the wrongness. Can you define what the nature of this wrongness is? Will bad things happen...? Seems like I missed this, apologize a2enmod takes a simple name like cgi not a name with .load or .conf on the end like cgi.load. You want a2enmod cgi without the .load on the end. Bob That.
Re: apache2 what is the standard way to enable modules?
Harry Putnam wrote: Raffaele Morelli writes: Is that what you are warning about? Nope, my warning was to use `a2enmod cgi` instead of `a2enmod cgi.load` (which is wrong) OK, thanks. But once again you've failed to explain the nature of the wrongness. Can you define what the nature of this wrongness is? Will bad things happen...? a2enmod takes a simple name like cgi not a name with .load or .conf on the end like cgi.load. You want a2enmod cgi without the .load on the end. Bob signature.asc Description: Digital signature
Re: apache2 what is the standard way to enable modules?
Raffaele Morelli raffaele.more...@gmail.com writes: Is that what you are warning about? Nope, my warning was to use `a2enmod cgi` instead of `a2enmod cgi.load` (which is wrong) OK, thanks. But once again you've failed to explain the nature of the wrongness. Can you define what the nature of this wrongness is? Will bad things happen...? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/8761glyeni@reader.local.lan
Re: apache2 what is the standard way to enable modules?
On 11/09/14 at 03:04pm, Harry Putnam wrote: Raffaele Morelli raffaele.more...@gmail.com writes: [...] Thanks for the push... Tinkering with your suggestion lead me to read the `LoadModule' lines on the files in mods-available. The line in cgi.load: LoadModule cgi_module /usr/lib/apache2/modules/mod_cgi.so Looked the most promising, so I tried: a2enmod cgi.load But it told me my MPM(?) seemed to be threaded so it gave me `cgid.conf' and `cgid.load'... and away it went... cgi firing on all 8 cylinders. beware that a2enmod doesn't require extension eg. a2enmod cgi.load won't work cause the module is 'cgi', symlink is created for both .conf and .load in /etc/apache2/mods-enabled/ hint: enable bash completion, a2enmod completes available module I'm not sure what you are getting at. Do you mean it won't work period or that only scripts with ext cgi will work? As reported further back in the thread: a2enmod cgi.load Gave me: cgid.conf - ../mods-available/cgid.conf cgid.load - ../mods-available/cgid.load Now my `script.cgi' work. But I had a few from a long ago previous setup without cgi extension... so just to test I tried this: cp test.cgi test Then opened `test.cgi' with a browser... it works opened `test' and it does not work. Is that what you are warning about? Nope, my warning was to use `a2enmod cgi` instead of `a2enmod cgi.load` (which is wrong) Can anyone tell me how to allow scripts without cgi extension to work? Create symlinks to the ones with extensions. -- « Nunc est bibendum, nunc pede libero pulsanda tellus » -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140912070017.gc4...@gmail.com
Re: apache2 what is the standard way to enable modules?
Raffaele Morelli raffaele.more...@gmail.com writes: [...] Thanks for the push... Tinkering with your suggestion lead me to read the `LoadModule' lines on the files in mods-available. The line in cgi.load: LoadModule cgi_module /usr/lib/apache2/modules/mod_cgi.so Looked the most promising, so I tried: a2enmod cgi.load But it told me my MPM(?) seemed to be threaded so it gave me `cgid.conf' and `cgid.load'... and away it went... cgi firing on all 8 cylinders. beware that a2enmod doesn't require extension eg. a2enmod cgi.load won't work cause the module is 'cgi', symlink is created for both .conf and .load in /etc/apache2/mods-enabled/ hint: enable bash completion, a2enmod completes available module I'm not sure what you are getting at. Do you mean it won't work period or that only scripts with ext cgi will work? As reported further back in the thread: a2enmod cgi.load Gave me: cgid.conf - ../mods-available/cgid.conf cgid.load - ../mods-available/cgid.load Now my `script.cgi' work. But I had a few from a long ago previous setup without cgi extension... so just to test I tried this: cp test.cgi test Then opened `test.cgi' with a browser... it works opened `test' and it does not work. Is that what you are warning about? Can anyone tell me how to allow scripts without cgi extension to work? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/877g1anfmg@reader.local.lan
Re: apache2 what is the standard way to enable modules?
On Wed, 03 Sep 2014 20:55:19 -0400 Harry Putnam rea...@newsguy.com wrote: what is the name of cgi module? That would be very useful for the `a2enmod' cmd. And for something real simple like making sure it is installed. I see several files in [...]/mods-available with the string `cgi' in them. None of those show up in [...]/mods-enabled. a2enmod is just for that: creating a symlink from mods-available to mods-enabled (usually needs a restart). You could: cd mods-available grep filename /var/lib/dpkg/info/*ist which will return the name of the pkg containing this module.list; if it doesn't talk by itself, check what your pkg manager description says about it. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140904030750.4aee33d7@msi.defcon1
Re: apache2 what is the standard way to enable modules?
On 9/3/2014 8:55 PM, Harry Putnam wrote:
googling to learn how to enable modules in apache2-2.4.10-1+b1
I'm getting a little too much input to really see what to do.
what is the name of cgi module? That would be very useful for the
`a2enmod' cmd. And for something real simple like making sure it is
installed.
Which language is the script written in? There are multiple CGI modules
because there are multiple languages which can use it.
I see several files in [...]/mods-available with the string `cgi' in
them. None of those show up in [...]/mods-enabled.
apache2 -M is supposed to dump all modules but instead dumps a bunch
of guff that says nothing at all about modules. And none of the
complaints appear to be a problem for apache2 since it starts and
restarts with no errors even when logging is set to `debug'. (see
first blurb below)
Using apachetcl -t to show all loaded mods (amongst several other
things) seems not to do that (see the last blurb below)
--- --- ---=--- --- ---
apache2 -M
[Wed Sep 03 20:12:14.669980 2014] [core:warn] [pid 6481] AH00111: Config
variable ${APACHE_LOCK_DIR} is not defined
[Wed Sep 03 20:12:14.671468 2014] [core:warn] [pid 6481] AH00111: Config
variable ${APACHE_PID_FILE} is not defined
[Wed Sep 03 20:12:14.672347 2014] [core:warn] [pid 6481] AH00111: Config
variable ${APACHE_RUN_USER} is not defined
[Wed Sep 03 20:12:14.673177 2014] [core:warn] [pid 6481] AH00111: Config
variable ${APACHE_RUN_GROUP} is not defined
[Wed Sep 03 20:12:14.674001 2014] [core:warn] [pid 6481] AH00111: Config
variable ${APACHE_LOG_DIR} is not defined
[Wed Sep 03 20:12:14.677377 2014] [core:warn] [pid 6481:tid 3074520896]
AH00111: Config variable ${APACHE_LOG_DIR} is not defined
[Wed Sep 03 20:12:14.678458 2014] [core:warn] [pid 6481:tid 3074520896]
AH00111: Config variable ${APACHE_LOG_DIR} is not defined
[Wed Sep 03 20:12:14.679343 2014] [core:warn] [pid 6481:tid 3074520896]
AH00111: Config variable ${APACHE_LOG_DIR} is not defined
AH00526: Syntax error on line 74 of /etc/apache2/apache2.conf:
Invalid Mutex directory in argument file:${APACHE_LOCK_DIR}
--- --- ---=--- --- ---
sudo apachectl -t
[Wed Sep 03 20:46:48.376425 2014] [core:trace3] [pid 6933:tid 3074139968]
core.c(3051): Setting LogLevel for all modules to trace4
Syntax OK
Not loading a module is not an error - although you should fix the error
in line 74. Attempting to load a non-existent module would be an error.
Jerry
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/5407cc1b.9000...@attglobal.net
Re: apache2 what is the standard way to enable modules?
B lazyvi...@gmx.com writes: On Wed, 03 Sep 2014 20:55:19 -0400 Harry Putnam rea...@newsguy.com wrote: what is the name of cgi module? That would be very useful for the `a2enmod' cmd. And for something real simple like making sure it is installed. I see several files in [...]/mods-available with the string `cgi' in them. None of those show up in [...]/mods-enabled. a2enmod is just for that: creating a symlink from mods-available to mods-enabled (usually needs a restart). You could: cd mods-available grep filename /var/lib/dpkg/info/*ist which will return the name of the pkg containing this module.list; if it doesn't talk by itself, check what your pkg manager description says about it. Thanks for the push... Tinkering with your suggestion lead me to read the `LoadModule' lines on the files in mods-available. The line in cgi.load: LoadModule cgi_module /usr/lib/apache2/modules/mod_cgi.so Looked the most promising, so I tried: a2enmod cgi.load But it told me my MPM(?) seemed to be threaded so it gave me `cgid.conf' and `cgid.load'... and away it went... cgi firing on all 8 cylinders. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87tx4odt54@reader.local.lan
Re: apache2 what is the standard way to enable modules?
Jerry Stuckle jstuc...@attglobal.net writes: Not loading a module is not an error - although you should fix the error in line 74. Attempting to load a non-existent module would be an error. Just one thing about that... I have the log level jacked up to trace4 and when I restart apache2, that error does not show up anywhere... nothing at all to be concerned with. in error or access.log. If you notice, that same command (apache2 -M) also reported that the log file was not defined and yet logs are appearing where they are supposed to. I'm thinking there is something a little shaky about calling apache2 -M like that, and that there is really no syntax error at all. You may note the last line of apachectl -t reports `Syntax OK' -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87ppfcdsqu@reader.local.lan
Re: apache2 what is the standard way to enable modules?
On Wed, 03 Sep 2014 22:19:35 -0400 Harry Putnam rea...@newsguy.com wrote: cgi firing on all 8 cylinders. Comparing to nginx, I'd say: firing on 2 cyl/8 ;) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140904042905.5c5e5e2f@msi.defcon1
Re: apache2 what is the standard way to enable modules?
B lazyvi...@gmx.com writes: On Wed, 03 Sep 2014 22:19:35 -0400 Harry Putnam rea...@newsguy.com wrote: cgi firing on all 8 cylinders. Comparing to nginx, I'd say: firing on 2 cyl/8 ;) Oh oh, you'll have to explain that one... it went right over my head. Just not clever enough to follow your wit. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87lhq0dsjw@reader.local.lan
Re: apache2 what is the standard way to enable modules?
On Wed, 03 Sep 2014 22:32:19 -0400 Harry Putnam rea...@newsguy.com wrote: Oh oh, you'll have to explain that one... it went right over my head. Just not clever enough to follow your wit. Not that nginx is way faster than apache, but it copes much better with a huge number of connections. The main (huge) difference and advantage is the way nginx handles memory that is awfully much better: ~2MB w/ 1,000 connections @ a rate of 50 conn./s, not any error, up to 12 php5-fpm running together (~2.5 MB each for my front page); which is not bad for a celeron 2.00GHz and 628MB of RAM. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140904050249.5a0892e9@msi.defcon1
Re: apache2 what is the standard way to enable modules?
Harry Putnam rea...@newsguy.com writes: googling to learn how to enable modules in apache2-2.4.10-1+b1 I'm getting a little too much input to really see what to do. what is the name of cgi module? That would be very useful for the `a2enmod' cmd. And for something real simple like making sure it is installed. The modules you have available are in /etc/apache2/mods-available/ To enable one, create a symbolic link from one the module and its configuration in /etc/apache2/mods-enabled. I've got cgi enabled on my system with babs:511$ pwd /etc/apache2 babs:512$ ls -l mods-enabled/*cgi* lrwxrwxrwx 1 root root 26 Sep 26 2013 mods-enabled/cgi.load - ../mods-available/cgi.load babs:513$ I see several files in [...]/mods-available with the string `cgi' in them. None of those show up in [...]/mods-enabled. Right -- the way you enable them is to create the symbolic link. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1bmwaggiy3@pfeifferfamily.net
Re: apache2 what is the standard way to enable modules?
2014-09-04 4:19 GMT+02:00 Harry Putnam rea...@newsguy.com: B lazyvi...@gmx.com writes: On Wed, 03 Sep 2014 20:55:19 -0400 Harry Putnam rea...@newsguy.com wrote: what is the name of cgi module? That would be very useful for the `a2enmod' cmd. And for something real simple like making sure it is installed. I see several files in [...]/mods-available with the string `cgi' in them. None of those show up in [...]/mods-enabled. a2enmod is just for that: creating a symlink from mods-available to mods-enabled (usually needs a restart). You could: cd mods-available grep filename /var/lib/dpkg/info/*ist which will return the name of the pkg containing this module.list; if it doesn't talk by itself, check what your pkg manager description says about it. Thanks for the push... Tinkering with your suggestion lead me to read the `LoadModule' lines on the files in mods-available. The line in cgi.load: LoadModule cgi_module /usr/lib/apache2/modules/mod_cgi.so Looked the most promising, so I tried: a2enmod cgi.load But it told me my MPM(?) seemed to be threaded so it gave me `cgid.conf' and `cgid.load'... and away it went... cgi firing on all 8 cylinders. beware that a2enmod doesn't require extension eg. a2enmod cgi.load won't work cause the module is 'cgi', symlink is created for both .conf and .load in /etc/apache2/mods-enabled/ hint: enable bash completion, a2enmod completes available module
