NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
dj_ad
Jun 09, 2013Aspirant
Apache won't start after successful upgrade to 4.2.23
Hi !
My apache server won't start since i successfully upgraded from 4.2.22 to 4.2.23...
I have a socket error can anyone help me please, i have no more access to frontend, to backups, to plexmedia server...
Here is the commande line i'm trying to use to start apache
apache-ssl -f /etc/frontview/apache/httpd.conf -k start
and here is the error i get
apache-ssl: Could not reliably determine the server's fully qualified domain name, using 192.168.2.200 for ServerName
(98)Address already in use: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
Any help would be welcome !
Thanks a lot
My apache server won't start since i successfully upgraded from 4.2.22 to 4.2.23...
I have a socket error can anyone help me please, i have no more access to frontend, to backups, to plexmedia server...
Here is the commande line i'm trying to use to start apache
apache-ssl -f /etc/frontview/apache/httpd.conf -k start
and here is the error i get
apache-ssl: Could not reliably determine the server's fully qualified domain name, using 192.168.2.200 for ServerName
(98)Address already in use: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
Any help would be welcome !
Thanks a lot
24 Replies
Replies have been turned off for this discussion
- dj_adAspirantI'm trying to figure out why is apache trying to bind a socket to 0.0.0.0.0 but have no clue, i'm looking at configurations files from addons, httpd.conf....
- dj_adAspirantok i've added ServerName 127.0.0.1 at the end of http.conf to suppress the message
apache-ssl: Could not reliably determine the server's fully qualified domain name, using 192.168.2.200 for ServerName
I've put # in front of the line Include /etc/frontview/apache/Virtual.conf to suppress all virtual domains
i've put # in front of the line Include /etc/frontview/apache/addons/*.conf to prevent addons from loading
but i still get the error
httpd not running, trying to start
(98)Address already in use: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
i think it is a system related error, other process bind socket and there is a conflict...
does anybody know how i can list which process uses which port ? - mdgm-ntgrNETGEAR Employee Retired
- dj_adAspirantTo identify the process using the port i ran command
netstat -lnp | grep '0.0.0.0:80'
but i get not output...
Any clue anyone ? - dj_adAspirantI killed all the proccesses returned by the command
netstat -tulpn
i checked nothing was mapped to sockets...
when i try to start apache i have the same error... :oops: - dj_adAspiranti forced usage of ipv4 instead of ipv6 by changing
Listen 80
Listen 443
to
Listen 0.0.0.0:80
Listen 0.0.0.0:443
but still getting the same error - mdgm-ntgrNETGEAR Employee RetiredHave you tried stopping your add-ons one by one to see if any of them are the problem?
- dj_adAspirantHummm no i didn't try to kill addons one by one, i thought that forbidding their loads within the httpd.conf was enough...
ok i'm gonna try this thanks a lot for your help... i appreciate a lot ! - dj_adAspirantstopped all addons manually... between each stop tried to start apache, still the same error...
i'm lost : ( - mdgm-ntgrNETGEAR Employee RetiredIf there are any addons you no longer need execute the remove script in /etc/frontview/addons
Perhaps also try Re-installing other add-ons you wish to keep and check you have an up to date version installed.
Revert your apache config back to what it was before.
What files are in /etc/frontview/apache/addons ?
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!