Re: SOLVED: Re: [gentoo-user] Progress made, not done yet Re: All of a sudden, no apache2. No clue why.
On 2010-08-05 9:25 PM, Kevin O'Gorman kogor...@gmail.com wrote: On Thu, Aug 5, 2010 at 10:29 AM, Kevin O'Gorman kogor...@gmail.com mailto:kogor...@gmail.com wrote: I may have found the root of the problem: examine the following output of an eix query on apache, and note that the cgi stuff seems to be turned off in the installed version. So, apparently you don't read the postinstall messages when installing updates? Here is the postinst message for this latest apache update: LOG: postinst Attention: cgi and cgid modules are now handled via APACHE2_MODULES flags make sure to enable those in order to compile them. In general, you should use 'cgi' with non-multithreaded MPMs (such as prefork) and 'cgid' with multithreaded ones (such as worker) It can really save you a lot of hassle if you read these... ;)
SOLVED: Re: [gentoo-user] Progress made, not done yet Re: All of a sudden, no apache2. No clue why.
On Thu, Aug 5, 2010 at 10:29 AM, Kevin O'Gorman kogor...@gmail.com wrote: I may have found the root of the problem: examine the following output of an eix query on apache, and note that the cgi stuff seems to be turned off in the installed version. [snip snip] The installed version seems to have CGI turned off completely (notice - in installed version). I cannot find any reason either in /etc/portage/package.use nor in /usr/portage/profiles or its subdirectories. Is there someplace else to look? Well, I took the easy way out, and added those two options to /etc/portage/package.use for apache: www-servers/apache threads -ldap doc apache2_modules_cgi apache2_modules_cgid After a recompile and restart, my CGI scripts are running again. -- Kevin O'Gorman, PhD
[gentoo-user] Progress made, not done yet Re: All of a sudden, no apache2. No clue why.
On Fri, Jul 30, 2010 at 9:12 AM, Kyle Bader kyle.ba...@gmail.com wrote: * Starting apache2 ... (98)Address already in use: make_sock: could not bind to address 64.166.164.49:80 no listening sockets available, shutting down Unable to open logs [ Strace will probably reveal which log file can't be opened, something like this will probably do the trick: strace /path/to/apache2 -D module list -d /path/to/apache2dir It took some bash tracing to fill out that command, but once that was done, it was obvious that the server was doing exactly what had been suggested above: trying to listen (bind(2) call) on 0.0.0.0:80 as well as my.host:80. I had not touched my configs in ages, so I guess some default snuck in there somehow; I suspect something to do with virtual hosts (which I do not need), but it was easy to find and fix. Now it comes up and serves my pages. However, my configs contain a few ScriptAlias directories, which are full of python programs. They are not being executed, but served up in source code form, even though they have an initial shebang and remain executable by all. So there must be some new thing to do besides defining a ScriptAlias directory. Anybody know what it is? -- Kevin O'Gorman, PhD
