[users@httpd] Re: 0 length robot.txt

On 06 Oct 2018, at 17:59, Filipe Cifali wrote: > It's described on the CustomLog docs: > https://httpd.apache.org/docs/current/mod/mod_log_config.html#customlog > > "The second argument specifies what will be written to the log file. It can > specify either a ***nickname*** defined by a previou

Re: [users@httpd] Re: 0 length robot.txt

It's described on the CustomLog docs: https://httpd.apache.org/docs/current/mod/mod_log_config.html#customlog "The second argument specifies what will be written to the log file. It can specify either a ***nickname*** defined by a previous LogFormat

[users@httpd] Re: 0 length robot.txt

On 03 Oct 2018, at 17:11, @lbutlr wrote: > It’ been over 4 hours now (almost 5) and the site is still responding > perfectly. Well, I am more confused. I changed the log from common to debug and the site has been fine for days now. - CustomLog /home/user/logs/XXX.access_log combined + Custo

[users@httpd] Re: 0 length robot.txt

On 04 Oct 2018, at 13:20, Filipe Cifali wrote: > And the docs, this project is open source, we can change (or rather, propose > changes) to documentation anytime we want. Sure, but first you have to figure out the multiple layers of complexity in the current docs. -- Boy, it sure would be ni

Re: [users@httpd] Re: 0 length robot.txt

It's a bit strange to say that considering there is a page covering the changes from 2.2 to 2.4: https://httpd.apache.org/docs/2.4/upgrading.html And the docs, this project is open source, we can change (or rather, propose changes) to documentation anytime we want. On Thu, Oct 4, 2018 at 3:54 PM

[users@httpd] Re: 0 length robot.txt

On 04 Oct 2018, at 11:50, Filipe Cifali wrote: > You want to use a CustomLog for virtualhost config to gather the most info > you can from the request: > > https://httpd.apache.org/docs/current/mod/mod_log_config.html#customlog Ugh. That is a terrible bit of documentation written by and for peo

Re: [users@httpd] Re: 0 length robot.txt

You want to use a CustomLog for virtualhost config to gather the most info you can from the request: https://httpd.apache.org/docs/current/mod/mod_log_config.html#customlog Also, read the *Context* so you know where you can use them: https://httpd.apache.org/docs/2.4/mod/core.html#LogLevel On

[users@httpd] Re: 0 length robot.txt

On 03 Oct 2018, at 18:27, Filipe Cifali wrote: > you can for example turn log level to debug and access the site, tailing the > logs should provide some information about what is breaking. Is it possible to set the log level just for a virtual host? I thought that was a server-wide setting. I t

Re: [users@httpd] Re: 0 length robot.txt

Lewis, you can for example turn log level to debug and access the site, tailing the logs should provide some information about what is breaking. Also, why you have a ProxyPass on a virtualhost that doesn't run anything PHP? Create a template without the config and use it. On Wed, Oct 3, 2018 at 8

[users@httpd] Re: 0 length robot.txt

On 03 Oct 2018, at 12:27, @lbutlr wrote: > There is exactly one line in the site configuration that, when commented, > makes the site work again. Though, possibly only for a little while. I’ll > have to check more in 3-4 hours. There is no other proxy logic at all. It’ been over 4 hours now (al

[users@httpd] Re: 0 length robot.txt

On 03 Oct 2018, at 12:07, Filipe Cifali wrote: > you can check what virtualhost is being served via apache2ctl like this: $ > apache2ctl -S > $ apache2ctl -h provides this info: > -S : a synonym for -t -D DUMP_VHOSTS -D DUMP_RUN_CFG Yes that is all fine, and the site was loadin

Re: [users@httpd] Re: 0 length robot.txt

Hi Kremels, you can check what virtualhost is being served via apache2ctl like this: $ apache2ctl -S $ apache2ctl -h provides this info: -S : a synonym for -t -D DUMP_VHOSTS -D DUMP_RUN_CFG After checking that the right vhost is being served, start removing proxy logic and just

[users@httpd] Re: 0 length robot.txt

On 03 Oct 2018, at 11:39, @lbutlr wrote: > Removing that file made the site load properly. Well, it did for about 3h25 minutes, in fact. Just after posting the message, the site went back to showing only “File Not Found” I’m at a loss. The only other issue I see is in the main http-error log