Just in case, someone still think about this topic.
For the lack of other ideas - I resolved the issue by tearing my config
file templates apart and putting them back together from the working
deployed parts. Diffing the old (broken config) and new working one
produces identity, so do access logs.
I would suspect that there are conditionals in those jinja2 templates that
is making things different.
On Mon, Jan 7, 2019, 6:28 PM Bill Barry On Tue, Jan 8, 2019 at 2:02 AM Bill Barry wrote:
>
> >
> >
> > On Mon, Jan 7, 2019 at 9:52 PM Tomas Kuchta <
> tomas.kuchta.li...@gmail.com>
> > wrote:
On Tue, Jan 8, 2019 at 2:02 AM Bill Barry wrote:
>
>
> On Mon, Jan 7, 2019 at 9:52 PM Tomas Kuchta
> wrote:
>
>> The problem is 99.9% in the Apache config - the same application runs
>> on one server not the other. No matter which way I synchronize the code,
>> it
>> executes in one place, n
On Mon, Jan 7, 2019 at 9:52 PM Tomas Kuchta
wrote:
> The problem is 99.9% in the Apache config - the same application runs
> on one server not the other. No matter which way I synchronize the code, it
> executes in one place, not the other.
>
>
> The only difference are Apache config files
On 1/7/19 11:12 AM, Tomas Kuchta wrote:
Hi,
I am having difficulty to debug why CGI scripts are not executed by
Apache2, again.
Can someone recommend some iteligent, algorithmical and converging way to
debug this?
There is nothing visible in the logs with CGIs, no error messages, no
config e
The problem is 99.9% in the Apache config - the same application runs
on one server not the other. No matter which way I synchronize the code, it
executes in one place, not the other.
The only difference are Apache config files, produced mostly with Jinja
templates and search and replace with
On Jan 7, 2019, at 3:30 PM, Paul Heinlein wrote:
>
> On Mon, 7 Jan 2019, Tomas Kuchta wrote:
>
>> Yes, the file serving part works, and is observable in the logs. There is
>> good visibility on client side with curl or browsers. When Apache executes
>> it, I get the output html/json/ When it
On Mon, 7 Jan 2019, Tomas Kuchta wrote:
Yes, the file serving part works, and is observable in the logs. There is
good visibility on client side with curl or browsers. When Apache executes
it, I get the output html/json/ When it doesn't work, I get to download
the code.
I usually build coup
Yes, the file serving part works, and is observable in the logs. There is
good visibility on client side with curl or browsers. When Apache executes
it, I get the output html/json/ When it doesn't work, I get to download
the code.
I usually build couple of identical machines and synchronize th
On Mon, Jan 7, 2019 at 7:12 PM Tomas Kuchta
wrote:
> Hi,
>
> I am having difficulty to debug why CGI scripts are not executed by
> Apache2, again.
>
> Can someone recommend some iteligent, algorithmical and converging way to
> debug this?
>
> There is nothing visible in the logs with CGIs, no err
I'm a big fan of strace.
On Mon, Jan 7, 2019 at 11:14 AM Tomas Kuchta
wrote:
> Hi,
>
> I am having difficulty to debug why CGI scripts are not executed by
> Apache2, again.
>
> Can someone recommend some iteligent, algorithmical and converging way to
> debug this?
>
> There is nothing visible in
Hi,
I am having difficulty to debug why CGI scripts are not executed by
Apache2, again.
Can someone recommend some iteligent, algorithmical and converging way to
debug this?
There is nothing visible in the logs with CGIs, no error messages, no
config errors, no obvious file ownership, permission
12 matches
Mail list logo
