On Wed, Nov 11, 2009 at 6:34 PM, Philip Wigg wrote:
>> (99)Cannot assign requested address: make_sock: could not bind to
>> address 213.49.146.24:8080
>> no listening sockets available, shutting down
>> Unable to open logs
>>
>> What could be the trouble?
>
> The server must actually have 213.49.1
On Nov 11, 2009, at 07:48 , Siju George wrote:
# apache2ctl start
apache2: Could not reliably determine the server's fully qualified
domain name, using 127.0.1.1 for ServerName
(99)Cannot assign requested address: make_sock: could not bind to
address 213.49.146.24:8080
no listening sockets avai
> (99)Cannot assign requested address: make_sock: could not bind to
> address 213.49.146.24:8080
> no listening sockets available, shutting down
> Unable to open logs
>
> What could be the trouble?
The server must actually have 213.49.146.24 as it's IP address. Is
that the case here? It's no good
You need the ServerName statement.
On Wed, Nov 11, 2009 at 11:48 PM, Siju George wrote:
> HI I have the following ports.conf
>
>
>
> NameVirtualHost *:80
> Listen 80
>
>
># SSL name based virtual hosts are not yet supported, therefore no
># NameVirtualHost statement here
>Listen 443
HI I have the following ports.conf
NameVirtualHost *:80
Listen 80
# SSL name based virtual hosts are not yet supported, therefore no
# NameVirtualHost statement here
Listen 443
Listen 213.49.146.24:8080
I have this in sites-enabled
ServerAdmin webmas...@localhost
