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 their config/content. Still, when one machine in the pair is stubbornly refusing to run some stuff, it takes a lot of diffing, renaming, rebuilding, ... What makes Apache to choose to execute some files and not the others, is the $M question. On Mon, Jan 7, 2019, 11:34 AM Bill Barry <b...@billbarry.org wrote: > On Mon, Jan 7, 2019 at 7:12 PM Tomas Kuchta <tomas.kuchta.li...@gmail.com> > 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 errors, no obvious file ownership, permission issues. > > > > I am standing up the servers using Ansible, one like the other, > repeatably. > > Still, some servers work, some do not. Most of the time, the script > execute > > fine upon provisionning, some times the do not. When they do not run, it > > takes days of almost random rebuilds to resolve. Some times .cgi works, > > sometimes .py/php does not. Often helloWorld.cgi runs but not some other > > random.cgi. Usually, what I want/need does not run. I am sick of sinking > > days in this unproductive trial and error... > > > > Any sensible and calm advice? > > > > Thanks, Tomas > > > > Can you confirm that Apache is receiving the request? If not is it an > upstream DNS/networking problem? > > Bill > _______________________________________________ > PLUG mailing list > PLUG@pdxlinux.org > http://lists.pdxlinux.org/mailman/listinfo/plug > _______________________________________________ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug