Re: [gentoo-user] Dead apache (cannot listen)
heres my default vhost Listen 80 NameVirtualHost *:80 IfDefine HIVE VirtualHost *:80 ServerAdmin [EMAIL PROTECTED] ServerName hive.silan DocumentRoot /var/www/hive.silan/htdocs Directory /var/www/hive.silan/htdocs Options Indexes FollowSymLinks AllowOverride All Order allow,deny Allow from all /Directory Alias /icons /var/www/hive.silan/icons Directory /var/www/hive.silan/icons Options None AllowOverride none Order allow,deny Allow from all /Directory IfModule alias_module ScriptAlias /cgi-bin/ /var/www/hive.silan/cgi-bin/ /IfModule Directory /var/www/hive.silan/cgi-bin AllowOverride None Options None Order allow,deny Allow from all /Directory /VirtualHost /IfDefine -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Dead apache (cannot listen)
Thanks for top-posting :o) This is still a bit mysterious for me. I've tried to do what you said, but apache still fails to start because it cannot open a listening port. Here's what I've figured out about what I have: /etc/conf.c/apache2 contains APACHE2_OPTS=-D DEFAULT_VHOST -D INFO -D LANGUAGE -D MANUAL -D SSL -D SSL_DEFAULT_VHOST -D USERDIR to which I contributed only USERDIR -- the other stuff came with the ebuild. Maybe I should drop the SSL stuff since my server has no https stuff (It does have htaccess and htpasswd stuff, but I think that's different). In any event, removing the SSL stuff does not change the problem. Everything else in that file is commented out, which I take to mean that default values are used. Among the defaults is #CONFIGFILE=/etc/apache2/httpd.conf and that file contains Include /etc/apache2/vhosts.d/*.conf And /etc/apache2/vhosts.d/ includes 00_default_ssl_vhost.confand 00_default_vhost.conf My 00_default_vhost.conf: === start 00_default_vhost.conf == # If your host doesn't have a registered DNS name, enter its IP address here. # #ServerName www.example.com:80 ServerName www.kosmanor.com:80 #KOSMANOR changes #Listen 80 Listen 64.166.164.49:80 Listen localhost:80 # DocumentRoot: The directory out of which you will serve your # documents. By default, all requests are taken from this directory, but # symbolic links and aliases may be used to point to other locations. # # If you change this to something that isn't under /var/www then suexec # will no longer work. DocumentRoot /var/www/localhost/htdocs # This should be changed to whatever you set DocumentRoot to. Directory /var/www/localhost/htdocs # Possible values for the Options directive are None, All, # or any combination of: # Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews # # Note that MultiViews must be named *explicitly* --- Options All # doesn't give it to you. # # The Options directive is both complicated and important. Please see # http://httpd.apache.org/docs/2.2/mod/core.html#options # for more information. Options Indexes FollowSymLinks # AllowOverride controls what directives may be placed in .htaccess files. # It can be All, None, or any combination of the keywords: # Options FileInfo AuthConfig Limit AllowOverride All # Controls who can get stuff from this server. Order allow,deny Allow from all /Directory IfModule alias_module # Redirect: Allows you to tell clients about documents that used to # exist in your server's namespace, but do not anymore. The client # will make a new request for the document at its new location. # Example: # Redirect permanent /foo http://www.example.com/bar # Alias: Maps web paths into filesystem paths and is used to # access content that does not live under the DocumentRoot. # Example: # Alias /webpath /full/filesystem/path # # If you include a trailing / on /webpath then the server will # require it to be present in the URL. You will also likely # need to provide a Directory section to allow access to # the filesystem path. # ScriptAlias: This controls which directories contain server scripts. # ScriptAliases are essentially the same as Aliases, except that # documents in the target directory are treated as applications and # run by the server when requested rather than as documents sent to the # client. The same rules about trailing / apply to ScriptAlias # directives as to Alias. ScriptAlias /cgi-bin/ /var/www/localhost/cgi-bin/ /IfModule # /var/www/localhost/cgi-bin should be changed to whatever your ScriptAliased # CGI directory exists, if you have that configured. Directory /var/www/localhost/cgi-bin AllowOverride None Options None Order allow,deny Allow from all /Directory # vim: ts=4 filetype=apache === end 00_default_vhost.conf == On 9/6/07, Alexander Reitzel [EMAIL PROTECTED] wrote: you should look at your vhost configs. take an example of the current default_vhost config and make sure to keep the -D DEFAULT_VHOST in /etc/conf.d/apache2 Ive had the same problem with one of my servers and after using the default thiggie it worked fine. Am Freitag, 7. September 2007 03:08:43 schrieb Kevin O'Gorman: Somewhere in the update to 2.2.4-r12, listening got lost. I tried to follow instructions, but apparently failed. Here's what happens (minus a MaxClients warning that doesn't look like a show-stopper): treat init.d # ./apache2 start * Starting apache2 ... (98)Address already in use: make_sock: could not bind to address 64.166.164.49:80 no listening
Re: [gentoo-user] Dead apache (cannot listen)
Kevin O'Gorman skrev: My 00_default_vhost.conf: === start 00_default_vhost.conf == # If your host doesn't have a registered DNS name, enter its IP address here. # #ServerName www.example.com:80 http://www.example.com:80 ServerName www.kosmanor.com:80 http://www.kosmanor.com:80 #KOSMANOR changes #Listen 80 Listen 64.166.164.49:80 http://64.166.164.49:80 Listen localhost:80 Thats not a vhost configuration, so it's a bit confusing why your trying to use Gentoo's default vhost config file and making non vhost configs and I bet it isn't liking the missing: NameVirtualHost *:80 (You will have to check the apache2 doc for the VirtualIP version of NameVirtualHost) VirtualHost *:80 If you want to make a non vhost configuration, then do so from the ground up, don't mix vhost and non vhost unless you want a mess. The reason you get :80 already bound, is because your configuration bind twice to the same IP. It's Apache itself that bind twice and bails on the second attempt. Not having used this configuration layout in years, I would guess ServerName is the one creating the listening socket, maybe because it's placed before Listen. smime.p7s Description: S/MIME Cryptographic Signature
Re: [gentoo-user] Dead apache (cannot listen)
On 9/7/07, Steen Eugen Poulsen [EMAIL PROTECTED] wrote: Kevin O'Gorman skrev: My 00_default_vhost.conf: === start 00_default_vhost.conf == # If your host doesn't have a registered DNS name, enter its IP address here. # #ServerName www.example.com:80 http://www.example.com:80 ServerName www.kosmanor.com:80 http://www.kosmanor.com:80 #KOSMANOR changes #Listen 80 Listen 64.166.164.49:80 http://64.166.164.49:80 Listen localhost:80 Thats not a vhost configuration, so it's a bit confusing why your trying to use Gentoo's default vhost config file and making non vhost configs and I bet it isn't liking the missing: NameVirtualHost *:80 (You will have to check the apache2 doc for the VirtualIP version of NameVirtualHost) VirtualHost *:80 If you want to make a non vhost configuration, then do so from the ground up, don't mix vhost and non vhost unless you want a mess. The reason you get :80 already bound, is because your configuration bind twice to the same IP. It's Apache itself that bind twice and bails on the second attempt. Not having used this configuration layout in years, I would guess ServerName is the one creating the listening socket, maybe because it's placed before Listen. A workaround has been found (see below). As may be obvious by now, I don't understand much about configuring apache. I just used what dropped in when I installed Gentoo around 2003, and tried to adapt as time and updates came along. My needs are fairly simple: a basic server on a single IP plus localhost, using the default port 80. Static and CGI pages only, no secure applications. Users (only me, actually) have a page in public_html. I intend to use mod_python eventually, or write my own module, but that's for later. I have not a clue how to build a configuration from the ground up, and I'm hoping to not have to learn. Since it would be a singleton excercise, I would just forget it anyway in the midst of many other things that claim my attention. Workaround: In any event, making ServerName come after Listen, or commenting it out completely, do not change the symptoms at all. However, commenting out all Listen lines does allow apache to start. It seems you're right and apache is colliding with itself, but I don't know why, as I don't see any other Listen directives. This is at best a stopgap because apache's now listening promiscuously, which I do not like at all. I'm hoping for more help, but my fallback is to save my config files, unmerge apache completely, re-emerge it and see if the default configuration can be made to work right. That might turn out to be a lot of work, for which read a lot of time. -- Kevin O'Gorman, PhD
Re: [gentoo-user] Dead apache (cannot listen)
Mystery solved. As expected: my bad. Details at the bottom On 9/7/07, Kevin O'Gorman [EMAIL PROTECTED] wrote: On 9/7/07, Steen Eugen Poulsen [EMAIL PROTECTED] wrote: Kevin O'Gorman skrev: My 00_default_vhost.conf: === start 00_default_vhost.conf == # If your host doesn't have a registered DNS name, enter its IP address here. # #ServerName www.example.com:80 http://www.example.com:80 ServerName www.kosmanor.com:80 http://www.kosmanor.com:80 #KOSMANOR changes #Listen 80 Listen 64.166.164.49:80 http://64.166.164.49:80 Listen localhost:80 Thats not a vhost configuration, so it's a bit confusing why your trying to use Gentoo's default vhost config file and making non vhost configs and I bet it isn't liking the missing: NameVirtualHost *:80 (You will have to check the apache2 doc for the VirtualIP version of NameVirtualHost) VirtualHost *:80 If you want to make a non vhost configuration, then do so from the ground up, don't mix vhost and non vhost unless you want a mess. The reason you get :80 already bound, is because your configuration bind twice to the same IP. It's Apache itself that bind twice and bails on the second attempt. Not having used this configuration layout in years, I would guess ServerName is the one creating the listening socket, maybe because it's placed before Listen. A workaround has been found (see below). As may be obvious by now, I don't understand much about configuring apache. I just used what dropped in when I installed Gentoo around 2003, and tried to adapt as time and updates came along. My needs are fairly simple: a basic server on a single IP plus localhost, using the default port 80. Static and CGI pages only, no secure applications. Users (only me, actually) have a page in public_html. I intend to use mod_python eventually, or write my own module, but that's for later. I have not a clue how to build a configuration from the ground up, and I'm hoping to not have to learn. Since it would be a singleton excercise, I would just forget it anyway in the midst of many other things that claim my attention. Workaround: In any event, making ServerName come after Listen, or commenting it out completely, do not change the symptoms at all. However, commenting out all Listen lines does allow apache to start. It seems you're right and apache is colliding with itself, but I don't know why, as I don't see any other Listen directives. This is at best a stopgap because apache's now listening promiscuously, which I do not like at all. I'm hoping for more help, but my fallback is to save my config files, unmerge apache completely, re-emerge it and see if the default configuration can be made to work right. That might turn out to be a lot of work, for which read a lot of time. I was sure I checked for duplicate Listen directives, but I missed one. Fixing that allowed apache to start. As pennance, I hunted down all my tailorings and put them in a single include file. In the process I wound up eliminating a bunch of other duplications. Hopefully things will be more sane soon. But not right away -- but I'll start another thread for that. ++ kevin -- Kevin O'Gorman, PhD
Re: [gentoo-user] Dead apache (cannot listen)
you should look at your vhost configs. take an example of the current default_vhost config and make sure to keep the -D DEFAULT_VHOST in /etc/conf.d/apache2 Ive had the same problem with one of my servers and after using the default thiggie it worked fine. Am Freitag, 7. September 2007 03:08:43 schrieb Kevin O'Gorman: Somewhere in the update to 2.2.4-r12, listening got lost. I tried to follow instructions, but apparently failed. Here's what happens (minus a MaxClients warning that doesn't look like a show-stopper): treat init.d # ./apache2 start * 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 [ !! ] treat init.d # So it got my instructions to listen, but failed. Looking at 'netstat --inet -l' does not show any listeners or open sockets on port 80. What else should I look at? -- [EMAIL PROTECTED] mailing list
