IP/Port Virtual Hosts - Listen Directive - Lab 7.3. Create a New IP Virtual Host
Hello!
I went through the HTTP server chapter 7, and read from the slide "IP/Port Virtual Hosts" that it was necessary to ensure that all the IP addresses and ports would be defined in a Listen directive.
When I came to the "Lab 7.3. Create a New IP Virtual Host", I then created a Listen directive in my ipvhost.conf file as follows:
Listen 192.168.153.53:80 <VirtualHost 192.168.153.53:80> DocumentRoot /var/www/ipvhost/ ServerName ipvhost.example.com <Directory /var/www/ipvhost> Options Indexes FollowSymLinks AllowOverride None Require all granted </Directory> </VirtualHost>
However, if the Listen directive is declared, I can not start the apache2 service, and get the following error message:
● apache2.service - The Apache HTTP Server
Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Wed 2021-04-07 15:58:20 EEST; 6s ago
Docs: https://httpd.apache.org/docs/2.4/
Process: 505773 ExecStart=/usr/sbin/apachectl start (code=exited, status=1/FAILURE)
huhti 07 15:58:20 X230 systemd[1]: Starting The Apache HTTP Server...
huhti 07 15:58:20 X230 apachectl[505776]: AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 2001:2003:fbh3:6500:904a:6dpb:92bb:6f6c. Set the 'ServerName' directive globally to suppress this message
huhti 07 15:58:20 X230 apachectl[505776]: (99)Cannot assign requested address: AH00072: make_sock: could not bind to address 192.168.153.53:80
huhti 07 15:58:20 X230 apachectl[505776]: no listening sockets available, shutting down
huhti 07 15:58:20 X230 apachectl[505776]: AH00015: Unable to open logs
huhti 07 15:58:20 X230 apachectl[505773]: Action 'start' failed.
huhti 07 15:58:20 X230 apachectl[505773]: The Apache error log may have more information.
huhti 07 15:58:20 X230 systemd[1]: apache2.service: Control process exited, code=exited, status=1/FAILURE
huhti 07 15:58:20 X230 systemd[1]: apache2.service: Failed with result 'exit-code'.
huhti 07 15:58:20 X230 systemd[1]: Failed to start The Apache HTTP Server.
If I comment and disable the Listen directive, the apache2 service starts, and I can succesfully test my IPvhost ans the original host as indicated in the Lab solutions.
I am confused, why it seems to be required theoretically and does not work in practice? What to do to make the Listen directive function as it should?
My system:
Chassis: laptop
Operating System: Ubuntu 20.04.2 LTS
Kernel: Linux 5.8.0-44-generic
Architecture: x86-64
Thank you!
Lionel.
Comments
-
Hello Lionel,
Just to make sure, 192.168.153.53 is the second address you've added to your network adapter right ?
sudo ip addr add 192.168.153.53/24 dev eth0where eth0 is your network adapter
0 -
If that is the case, I think the issue is overlapping Listen directives (see https://httpd.apache.org/docs/2.4/bind.html)
By default Apache is listening on port 80 on all addresses and if you specify a new exact address I guess it's an overlap, because it already listens an all addresses...
If you change the default configuration in /etc/apache2/ports.conf to
Listen 192.168.153.X:80Where X is your network adapter address, your configuration would work
Otherwise no need to add Listen directive in ipvhost.conf file
1 -
Hi k0dard,
I confirm that 192.168.153.53 was the second address added to my network adapter.
I have removed the
Listendirective from theipvhost.confand placed it in the '/etc/apached2/ports.conf' defining there all the hosts and all is functioning alright now!Thank you! : )
-1 -
You're welcome
-1 -
Thank you for all the coments and assistance.
The lab assumes a default installation and part of the defaults for Ubuntu include a "listen 80" directive in the ports.conf file. It should be unnecessary to change or alter the default listen directive as it should listen for all ip addresses. Setting the address on on the listen directive will tell the server to only listen to the specified ip address.
Thank you for participating, Lee
0 -
Thank you Lee for the additional comments.
0
Categories
- All Categories
- 177 LFX Mentorship
- 177 LFX Mentorship: Linux Kernel
- 754 Linux Foundation IT Professional Programs
- 374 Cloud Engineer IT Professional Program
- 170 Advanced Cloud Engineer IT Professional Program
- 74 DevOps IT Professional Program - Discontinued
- 5 DevOps & GitOps IT Professional Program
- 100 Cloud Native Developer IT Professional Program
- 7.6K Training Courses & Learning Paths
- 2 AI & ML Training
- 1 Blockchain & Decentralized Identity Training
- 5 Cloud & Containers Training
- 1 Cybersecurity Training
- 2 DevOps & Site-Reliability Training
- 1 Linux Kernel Development Training
- 1 Networking Training
- 2 Open Source Best Practice Training
- 2 System Administration Training
- 1 System Engineering Training
- 1 Web & Application Development Training
- 794 Hardware
- 202 Drivers
- 68 I/O Devices
- 37 Monitors
- 95 Multimedia
- 173 Networking
- 91 Printers & Scanners
- 89 Storage
- 769 Linux Distributions
- 81 Debian
- 68 Fedora
- 22 Linux Mint
- 13 Mageia
- 24 openSUSE
- 150 Red Hat Enterprise
- 31 Slackware
- 13 SUSE Enterprise
- 356 Ubuntu
- 465 Linux System Administration
- 31 Cloud Computing
- 73 Command Line/Scripting
- Github systems admin projects
- 98 Linux Security
- 78 Network Management
- 101 System Management
- 46 Web Management
- 111 Mobile Computing
- 19 Android
- 77 Development
- 1.2K New to Linux
- 1K Getting Started with Linux
- 393 Off Topic
- 121 Introductions
- 182 Small Talk
- 29 Study Material
- 976 Programming and Development
- 310 Kernel Development
- 648 Software Development
- 990 Software
- 382 Applications
- 182 Command Line
- 5 Compiling/Installing
- 68 Games
- 317 Installation
- Archived
- 2 LFD140 Class Forum
- 1.4K LFS258 Class Forum
Upcoming Training
-
August 20, 2018
Kubernetes Administration (LFS458)
-
August 20, 2018
Linux System Administration (LFS301)
-
August 27, 2018
Open Source Virtualization (LFS462)
-
August 27, 2018
Linux Kernel Debugging and Security (LFD440)

