Yes, it was the Secure Linux preventing the use of the port. I wonder if the error message should be broadened to include the possibility that security policies are not allowing it's use, rather than just assuming that the port is not available because it's already in use. I added the port to the security policy with this command: # semanage port -a -t http_port_t -p tcp 280 I had already added the port to the firewall [root@web1e conf]# firewall-cmd --info-zone=public public (active) target: default ... services: dhcpv6-client https http ssh ports: 9100/tcp 9101/tcp ... 280/tcp ... Jeffrey Cauhape – IT Professional III – Linux and Solaris Administrator Nevada Department of Employment, Training and Rehabilitation (775) 684-3804 (office) jpcauhape@xxxxxxxxxxx -----Original Message----- From: Jeff Cauhape [mailto:jpcauhape@xxxxxxxxxxx] Sent: Monday, February 4, 2019 8:29 AM To: users@xxxxxxxxxxxxxxxx Subject: RE: Stupid question time - VirtualHost Luca, Thanks for the suggestion. It looks like we may have stumbled over the Secure Linux policy settings. I'll know more later this morning. I'll post a follow up when I figure it out. Thanks, Jeffrey Cauhape – IT Professional III – Linux and Solaris Administrator Nevada Department of Employment, Training and Rehabilitation (775) 684-3804 (office) jpcauhape@xxxxxxxxxxx -----Original Message----- From: Luca Toscano [mailto:toscano.luca@xxxxxxxxx] Sent: Saturday, February 2, 2019 11:29 AM To: users@xxxxxxxxxxxxxxxx Subject: Re: Stupid question time - VirtualHost Hi Jeff! Il giorno ven 1 feb 2019 alle ore 16:02 Jeff Cauhape <jpcauhape@xxxxxxxxxxx> ha scritto: > > My usage of Apache has been pretty plain vanilla, and now I am > required to > > add a virtual host to a system, and I’m wondering what doing wrong. My > hunch > > is that it’s obvious to others. > > > > I am using Apache 2.4.6 as reported by httpd -v > > > > In my httpd.conf file I have: > > … > > Listen web1e.detr.nv:80 > > Listen web1e.detr.nv:280 > > … > > and > > <VirtualHost _default_:280> > > ServerName survey.nvdetr.org > > UseCanonicalName Off > > DocumentRoot "/var/www/html/survey/" > > ScriptAlias /cgi-bin/ "/var/www/cig-bin/survey/cgi-bin/" > > … > > </VirtualHost> > > > > Question: Isn’t it true that I must have a Listen directive for each VirtualHost? > > > > However, if I try to start the apache server configured like this I > get an error message that > > the port 8090 (or any other number I choose) is already in use and not > available. This causes > > apache to fail to start. > > > > # lsof -I :280 > > > > and > > > > # netstat -ltnp > > > > Do not show the port in use by anything. I can change the port number > to anything I choose > > and the results are the same. This suggests to me that the problem is in apache config somewhere. > > > > If I comment out the Listen director for the VirtualHost, I don’t get > the error, but I don’t see any > > process listening on the port either. > > > > Ideas? Suggestions? Did you check https://httpd.apache.org/docs/2.4/vhosts/examples.html ? There are useful examples in there, it should clarify all doubts. Hope that helps! Luca --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx B KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKCB [ X ܚX KK[XZ[ \ \ ][ X ܚX P \X K ܙ B ܈Y][ۘ[ [X[ K[XZ[ \ \ Z[ \X K ܙ B --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|