Re: [users@httpd] Apache Will Not Start
Yes I do.
On Tue, Aug 28, 2018 at 9:51 PM Rose, John B wrote:
> Do you have a /var/run/httpd directory?
>
> Sent from my iPad
>
> On Aug 28, 2018, at 9:48 PM, Alex Nyamweya wrote:
>
> Hi,
>
> I am running an Apache server with CentOS 7 installed. I'm having issues
> starting apache using the command* systemctl status httpd.service *as I
> would get the following message:
>
> *Job for httpd.service failed because the control process exited with
> error code. See "systemctl status httpd.service" and "journalctl -xe" for
> details.*
>
> Here is the output of *systemctl status httpd*:
>
> httpd.service - The Apache HTTP Server
>Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; vendor
> preset: disabled)
>Active: failed (Result: exit-code) since Wed 2018-08-29 02:46:48 CEST;
> 42s ago
> Docs: man:httpd(8)
>man:apachectl(8)
> Process: 9599 ExecStop=/bin/kill -WINCH ${MAINPID} (code=exited,
> status=1/FAILURE)
> Process: 9597 ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND
> (code=exited, status=1/FAILURE)
> Main PID: 9597 (code=exited, status=1/FAILURE)
>
> Aug 29 02:46:48 [server-name] systemd[1]: Starting The Apache HTTP
> Server...
> Aug 29 02:46:48 [server-name] httpd[9597]: (98)Address already in use:
> AH00072: make_sock: could not bind to address [my-ip-address]:443
> Aug 29 02:46:48 [server-name] httpd[9597]: no listening sockets available,
> shutting down
> Aug 29 02:46:48 [server-name] httpd[9597]: AH00015: Unable to open logs
> Aug 29 02:46:48 [server-name] systemd[1]: httpd.service: main process
> exited, code=exited, status=1/FAILURE
> Aug 29 02:46:48 [server-name] kill[9599]: kill: cannot find process ""
> Aug 29 02:46:48 [server-name] systemd[1]: httpd.service: control process
> exited, code=exited status=1
> Aug 29 02:46:48 [server-name] systemd[1]: Failed to start The Apache HTTP
> Server.
> Aug 29 02:46:48 [server-name] systemd[1]: Unit httpd.service entered
> failed state.
> Aug 29 02:46:48 [server-name] systemd[1]: httpd.service failed.
>
> Here is what I tried so far. I tried checking if any process is running on
> port 443 using the command *netstat -an | grep 443*, but it showed
> nothing.
>
> I tried checking the httpd.conf and ssl.conf files and see if there is a *
> 'Listen 443'* on both but there isn't. It is only in ssl.conf.
>
> That's all I've tried so far but I'm open to any suggestions you may have.
>
>
Re: [users@httpd] Apache Will Not Start
Do you have a /var/run/httpd directory?
Sent from my iPad
On Aug 28, 2018, at 9:48 PM, Alex Nyamweya
mailto:animesoni...@gmail.com>> wrote:
Hi,
I am running an Apache server with CentOS 7 installed. I'm having issues
starting apache using the command systemctl status httpd.service as I would get
the following message:
Job for httpd.service failed because the control process exited with error
code. See "systemctl status httpd.service" and "journalctl -xe" for details.
Here is the output of systemctl status httpd:
httpd.service - The Apache HTTP Server
Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; vendor
preset: disabled)
Active: failed (Result: exit-code) since Wed 2018-08-29 02:46:48 CEST; 42s
ago
Docs: man:httpd(8)
man:apachectl(8)
Process: 9599 ExecStop=/bin/kill -WINCH ${MAINPID} (code=exited,
status=1/FAILURE)
Process: 9597 ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND (code=exited,
status=1/FAILURE)
Main PID: 9597 (code=exited, status=1/FAILURE)
Aug 29 02:46:48 [server-name] systemd[1]: Starting The Apache HTTP Server...
Aug 29 02:46:48 [server-name] httpd[9597]: (98)Address already in use: AH00072:
make_sock: could not bind to address [my-ip-address]:443
Aug 29 02:46:48 [server-name] httpd[9597]: no listening sockets available,
shutting down
Aug 29 02:46:48 [server-name] httpd[9597]: AH00015: Unable to open logs
Aug 29 02:46:48 [server-name] systemd[1]: httpd.service: main process exited,
code=exited, status=1/FAILURE
Aug 29 02:46:48 [server-name] kill[9599]: kill: cannot find process ""
Aug 29 02:46:48 [server-name] systemd[1]: httpd.service: control process
exited, code=exited status=1
Aug 29 02:46:48 [server-name] systemd[1]: Failed to start The Apache HTTP
Server.
Aug 29 02:46:48 [server-name] systemd[1]: Unit httpd.service entered failed
state.
Aug 29 02:46:48 [server-name] systemd[1]: httpd.service failed.
Here is what I tried so far. I tried checking if any process is running on port
443 using the command netstat -an | grep 443, but it showed nothing.
I tried checking the httpd.conf and ssl.conf files and see if there is a
'Listen 443' on both but there isn't. It is only in ssl.conf.
That's all I've tried so far but I'm open to any suggestions you may have.
[users@httpd] Apache Will Not Start
Hi,
I am running an Apache server with CentOS 7 installed. I'm having issues
starting apache using the command* systemctl status httpd.service *as I
would get the following message:
*Job for httpd.service failed because the control process exited with error
code. See "systemctl status httpd.service" and "journalctl -xe" for
details.*
Here is the output of *systemctl status httpd*:
httpd.service - The Apache HTTP Server
Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; vendor
preset: disabled)
Active: failed (Result: exit-code) since Wed 2018-08-29 02:46:48 CEST;
42s ago
Docs: man:httpd(8)
man:apachectl(8)
Process: 9599 ExecStop=/bin/kill -WINCH ${MAINPID} (code=exited,
status=1/FAILURE)
Process: 9597 ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND
(code=exited, status=1/FAILURE)
Main PID: 9597 (code=exited, status=1/FAILURE)
Aug 29 02:46:48 [server-name] systemd[1]: Starting The Apache HTTP Server...
Aug 29 02:46:48 [server-name] httpd[9597]: (98)Address already in use:
AH00072: make_sock: could not bind to address [my-ip-address]:443
Aug 29 02:46:48 [server-name] httpd[9597]: no listening sockets available,
shutting down
Aug 29 02:46:48 [server-name] httpd[9597]: AH00015: Unable to open logs
Aug 29 02:46:48 [server-name] systemd[1]: httpd.service: main process
exited, code=exited, status=1/FAILURE
Aug 29 02:46:48 [server-name] kill[9599]: kill: cannot find process ""
Aug 29 02:46:48 [server-name] systemd[1]: httpd.service: control process
exited, code=exited status=1
Aug 29 02:46:48 [server-name] systemd[1]: Failed to start The Apache HTTP
Server.
Aug 29 02:46:48 [server-name] systemd[1]: Unit httpd.service entered failed
state.
Aug 29 02:46:48 [server-name] systemd[1]: httpd.service failed.
Here is what I tried so far. I tried checking if any process is running on
port 443 using the command *netstat -an | grep 443*, but it showed nothing.
I tried checking the httpd.conf and ssl.conf files and see if there is
a *'Listen
443'* on both but there isn't. It is only in ssl.conf.
That's all I've tried so far but I'm open to any suggestions you may have.
[users@httpd] AW: Buffer in apache
Von: Christophe JAILLET Gesendet: Dienstag, 21. August 2018 21:54 An: Hemant Chaudhary ; d...@httpd.apache.org; users@httpd.apache.org Betreff: Re: Buffer in apache Le 21/08/2018 à 13:50, Hemant Chaudhary a écrit : Hi All, I want to use buffer of 512B in apache . I am using mod_proxy_http to send request to tomcat and have set ProxyIOBufferSize 512. But it is sending message to tomcat with size greater than 512B. How should I control apache in proxy so that it will send message and receive with max buffer size of 512B. Thanks Hemant Hi, for some reasons, mod_proxy_ajp has the folowing code ([1]) This means that value are silently forced between 8k (AJP_MSG_BUFFER_SZ) and 64k (AJP_MAX_BUFFER_SZ). I don't know why this is done this way and it looks spurious However, the code looks in line with apache 2.2 doc ([2]), but not with 2.4. ([3]) This looks to something that has not been completely updated in the 2.2 -> 2.4 process. Sounds like a useless limitation and mod_proxy_ajp should be aligned on the doc. IMHO, the test with AJP_MSG_BUFFER_SZ should be removed. (and also the one with AJP_MAX_BUFFER_SZ BTW) I cross-post to dev@ list for others feed-back. I think the code is correct and the documentation is wrong. mod_proxy_ajp has the assumption that it can send the whole request including all headers and possibly more request metadata in the first “buffer”. This will fail if this buffer is too small. Hence the 8k. Regards Rüdiger CJ [1]: http://svn.apache.org/viewvc/httpd/httpd/branches/2.4.x/modules/proxy/mod_proxy_ajp.c?diff_format=h&view=markup#l197 [2]: https://httpd.apache.org/docs/2.2/mod/mod_proxy.html#proxyiobuffersize [3]: https://httpd.apache.org/docs/2.4/mod/mod_proxy.html#proxyiobuffersize
Re: [users@httpd] Is HTTP Server affected by CVE-2018-11776 ?
Thanks Daniel
From: Daniel Gruno
Sent: Tuesday, August 28, 2018 3:07:23 PM
To: users@httpd.apache.org
Subject: Re: [users@httpd] Is HTTP Server affected by CVE-2018-11776 ?
On 08/28/2018 11:34 AM, Satish Chhatpar 02 wrote:
> Hi HTTP users, can anyone confirm if HTTP server any version is affected
> by CVE-2018-11776 ?
It is not. CVE-2018-11776 refers to Apache Struts, not the Apache HTTP
Server. Struts is a Java framework, and has no programmatic relation to
the HTTP Server other than being developed within the Apache Software
Foundation.
>
> ::DISCLAIMER::
>
>
> Confidentiality Notice from Dixons Carphone plc (registered in England &
> Wales No.07105905) of 1 Portal Way, London, W3 6RS ("Dixons Carphone").
> The information contained in this e-mail and any attachments may be
> legally privileged, proprietary and/or confidential. If you received
> this e-mail in error, please notify the sender by return, permanently
> delete the e-mail and destroy all hard copies immediately. No warranty
> is made as to the completeness or accuracy of the information contained
> in this e-mail. Opinions, conclusions and statements of intent in this
> e-mail are those of the sender and will not bind any Dixons Carphone
> group company (Dixons Carphone Group) unless confirmed by an authorised
> representative independently of this e-mail. We do not accept
> responsibility for viruses; you must scan for these. E-mails sent to and
> from Dixons Carphone Group are routinely monitored for record keeping,
> quality control, training purposes, to ensure regulatory compliance and
> to prevent viruses and unauthorised use of our computer systems. The
> Carphone Warehouse Limited (registered in England & Wales No.02142673)
> is a member of the Dixons Carphone Group and is authorised and regulated
> by the Financial Conduct Authority.
>
>
-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org
Re: [users@httpd] Is HTTP Server affected by CVE-2018-11776 ?
On 08/28/2018 11:34 AM, Satish Chhatpar 02 wrote:
Hi HTTP users, can anyone confirm if HTTP server any version is affected
by CVE-2018-11776 ?
It is not. CVE-2018-11776 refers to Apache Struts, not the Apache HTTP
Server. Struts is a Java framework, and has no programmatic relation to
the HTTP Server other than being developed within the Apache Software
Foundation.
::DISCLAIMER::
Confidentiality Notice from Dixons Carphone plc (registered in England &
Wales No.07105905) of 1 Portal Way, London, W3 6RS ("Dixons Carphone").
The information contained in this e-mail and any attachments may be
legally privileged, proprietary and/or confidential. If you received
this e-mail in error, please notify the sender by return, permanently
delete the e-mail and destroy all hard copies immediately. No warranty
is made as to the completeness or accuracy of the information contained
in this e-mail. Opinions, conclusions and statements of intent in this
e-mail are those of the sender and will not bind any Dixons Carphone
group company (Dixons Carphone Group) unless confirmed by an authorised
representative independently of this e-mail. We do not accept
responsibility for viruses; you must scan for these. E-mails sent to and
from Dixons Carphone Group are routinely monitored for record keeping,
quality control, training purposes, to ensure regulatory compliance and
to prevent viruses and unauthorised use of our computer systems. The
Carphone Warehouse Limited (registered in England & Wales No.02142673)
is a member of the Dixons Carphone Group and is authorised and regulated
by the Financial Conduct Authority.
-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org
[users@httpd] Is HTTP Server affected by CVE-2018-11776 ?
Hi HTTP users, can anyone confirm if HTTP server any version is affected by
CVE-2018-11776 ?
::DISCLAIMER::
Confidentiality Notice from Dixons Carphone plc (registered in England & Wales
No.07105905) of 1 Portal Way, London, W3 6RS ("Dixons Carphone"). The
information contained in this e-mail and any attachments may be legally
privileged, proprietary and/or confidential. If you received this e-mail in
error, please notify the sender by return, permanently delete the e-mail and
destroy all hard copies immediately. No warranty is made as to the completeness
or accuracy of the information contained in this e-mail. Opinions, conclusions
and statements of intent in this e-mail are those of the sender and will not
bind any Dixons Carphone group company (Dixons Carphone Group) unless confirmed
by an authorised representative independently of this e-mail. We do not accept
responsibility for viruses; you must scan for these. E-mails sent to and from
Dixons Carphone Group are routinely monitored for record keeping, quality
control, training purposes, to ensure regulatory compliance and to prevent
viruses and unauthorised use of our computer systems. The Carphone Warehouse
Limited (registered in England & Wales No.02142673) is a member of the Dixons
Carphone Group and is authorised and regulated by the Financial Conduct
Authority.
