Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
The OS is Fedora 9. The network is working. I'm using Firefox over it. I can ping 192.168.1.100 from other machines. However I can't get Apache to start and it seems to be finding a conflict on port 80.
[~]$service httpd start
Starting httpd: (13)Permission denied: make_sock: could not bind to address 192.168.1.100:80
no listening sockets available, shutting down
[~]$service httpd restart
Stopping httpd: [FAILED]
Starting httpd: (13)Permission denied: make_sock: could not bind to address 192.168.1.100:80
no listening sockets available, shutting down
be root, or configure (or disable) selinux correctly. you're getting permissions issues, not conflicts.
SELinux is disabled. I was SU when the commands were issued. What further did you mean when you said "be root".
From the SELinux config file:
# This file controls the state of SELinux on the system.
# SELINUX= can take one of these three values:
# enforcing - SELinux security policy is enforced.
# permissive - SELinux prints warnings instead of enforcing.
# disabled - No SELinux policy is loaded.
SELINUX=disabled
SELinux is disabled. I was SU when the commands were issued. What further did you mean when you said "be root".
From the SELinux config file:
# This file controls the state of SELinux on the system.
# SELINUX= can take one of these three values:
# enforcing - SELinux security policy is enforced.
# permissive - SELinux prints warnings instead of enforcing.
# disabled - No SELinux policy is loaded.
SELINUX=disabled
command whoami will let you know who you are
netstat -lnp | grep :80 - will list all of another soft listening port 80
and 'su -' will make you a superuser(=root)
regards.
command whoami will let you know who you are
netstat -lnp | grep :80 - will list all of another soft listening port 80
and 'su -' will make you a superuser(=root)
regards.
[/]$whoami
root
I tried the netstat command. I don't think it found anything:
[/]$netstat -lnp | grep :80
[/]$
What do you think?
I was SU in the listings of the previous posts. Samba is working now. Everything is running well on this system except Apache. Too bad that's the only thing I need to work.
[/]$service httpd restart
Stopping httpd: [FAILED]
Starting httpd: (98)Address already in use: make_sock: could not bind to address 192.168.1.100:80
no listening sockets available, shutting down
well that's a different error to what you originally posted, so something was different, and if you run netstat i'm sure you'll see the process on the port then. Also chekc the output of dmesg to see if there's anything nasty popping up in there. That's certainly where you'd see the SElinux errors (although you said it's disabled of course)
well that's a different error to what you originally posted, so something was different, and if you run netstat i'm sure you'll see the process on the port then. Also chekc the output of dmesg to see if there's anything nasty popping up in there. That's certainly where you'd see the SElinux errors (although you said it's disabled of course)
[/]$service httpd restart
Stopping httpd: [FAILED]
Starting httpd: (98)Address already in use: make_sock: could not bind to address 192.168.1.100:80
no listening sockets available, shutting down
I tried to start httpd in telinit 2 and then again in telinit 1 and it still comes up with the same problem, "make_sock: could not bind to address 192.168.1.100:80 no listening sockets available, shutting down"
In the httpd.conf file I changed the specified port from :80 to :8015 and in that case Apache started up just fine.
I removed the Apache server using the System->Admin->Add/Remove Software
rebooted and then reinstalled the software and I'm right back to the same problem.
[/]$service httpd restart
Stopping httpd: [FAILED]
Starting httpd: (98)Address already in use: make_sock: could not bind to address 192.168.1.100:80
no listening sockets available, shutting down
I tried to start httpd in telinit 2 and then again in telinit 1 and it still comes up with the same problem, "make_sock: could not bind to address 192.168.1.100:80 no listening sockets available, shutting down"
In the httpd.conf file I changed the specified port from :80 to :8015 and in that case Apache started up just fine.
I removed the Apache server using the System->Admin->Add/Remove Software
rebooted and then reinstalled the software and I'm right back to the same problem.
What does /var/log/messages tell you? What do the apache logs tell you?
Try this...in one window perform:
Code:
root@host# tail -f /var/log/messages
And on another window do:
Code:
root@host# service httpd stop
root@host# service httpd start
If that dosen't tell you anything...do the same but with the apache error logs...
either way...post the outcome.
If it works on port 8015 but NOT on 80; that means that something else is using that port...in which case netstat should tell you what is listening on that port...
What does /var/log/messages tell you? What do the apache logs tell you?
Try this...in one window perform:
Code:
root@host# tail -f /var/log/messages
And on another window do:
Code:
root@host# service httpd stop
root@host# service httpd start
If that dosen't tell you anything...do the same but with the apache error logs...
either way...post the outcome.
If it works on port 8015 but NOT on 80; that means that something else is using that port...in which case netstat should tell you what is listening on that port...
-C
In the first window after having run the second window:
Code:
[/]$tail -f /var/log/messages
Jan 3 17:23:34 linuxserver gconfd (root-2788): Resolved address "xml:readwrite:/root/.gconf" to a writable configuration source at position 1
Jan 3 17:23:34 linuxserver gconfd (root-2788): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 2
Jan 3 17:26:04 linuxserver gconfd (root-2788): GConf server is not in use, shutting down.
Jan 3 17:26:04 linuxserver gconfd (root-2788): Exiting
Jan 3 17:26:32 linuxserver gconfd (root-2878): starting (version 2.22.0), pid 2878 user 'root'
Jan 3 17:26:32 linuxserver gconfd (root-2878): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0
Jan 3 17:26:32 linuxserver gconfd (root-2878): Resolved address "xml:readwrite:/root/.gconf" to a writable configuration source at position 1
Jan 3 17:26:32 linuxserver gconfd (root-2878): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 2
Jan 3 17:29:02 linuxserver gconfd (root-2878): GConf server is not in use, shutting down.
Jan 3 17:29:02 linuxserver gconfd (root-2878): Exiting
In the second window
Code:
[/]$service httpd stop
Stopping httpd: [FAILED]
[/]$service httpd start
Starting httpd: (98)Address already in use: make_sock: could not bind to address 192.168.1.100:80
no listening sockets available, shutting down
Unable to open logs
[FAILED]
[/]$
apache starts by root but than usually switches to user "apache"
check this setting in your htttp.conf, maybe something wrong with it
ps aux | grep http[d] - will exactly show you the user from which apache is working
apache starts by root but than usually switches to user "apache"
check this setting in your htttp.conf, maybe something wrong with it
ps aux | grep http[d] - will exactly show you the user from which apache is working
Here is the output:
Code:
[/]$service httpd restart
Stopping httpd: [FAILED]
Starting httpd: (98)Address already in use: make_sock: could not bind to address 192.168.1.100:80
no listening sockets available, shutting down
Unable to open logs
[FAILED]
[/]$ps aux | grep http
root 11760 0.0 0.0 4120 692 pts/1 S+ 12:10 0:00 grep http
[/]$ps aux | grep httpd
root 11762 0.0 0.0 4120 692 pts/1 S+ 12:11 0:00 grep httpd
[/]$
Thanks for all the suggestions and help. What I've decided to do is to start over on this install. I'm reloading from the distribution disk currently. I hope I can report back to you that all is working.
A friend of mine who is a Linux pro -- having spent most of his life working on Linux systems -- spent a number of hours with me on this problem. He has now given up on my psychotic system. He thinks there is a flaw somewhere that will take longer to find than it would take to reload it.
After reloading to OS from the distribution disks, Apache is now working. I guess we will never know what was wrong. The good news is I can move on with my life now. Thanks.
After reloading to OS from the distribution disks, Apache is now working. I guess we will never know what was wrong. The good news is I can move on with my life now. Thanks.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
