I have further news on my question - it's probably not
Apache-related. At this time the issue appears to be NFS file
locking. The NFS server where the files are stored was also
upgraded and the mount options on the web servers were changed
slightly. Too many upgrades and changes all at once. Not the way
I usually operate.
Dave Hall Binghamton University firstname.lastname@example.org 607-760-2328 (Cell) 607-777-4641 (Office)
I have a Perl-CGI-based website that's been running on Debian/Apache since at last Squeeze. The transition from Apache 2.2 to Apache 2.4 caused my organization some considerable heartache so we're just finally getting to Buster.
Some of the Perl CGI scripts for this site, running with suexec, manipulate a small set of files/directories in a specific user directory. I had adjusted the site to run on Jessie-backports on one server and used it that way for about a year and the file manipulation was working fine - just like it always did.
Now that I have migrated to stretech-backports, the CGI-scripts that manipulate the user files have stopped working - they just hang until I get a 504 error. The Apache config and the site content were not changed in the course of the upgrade. Since both Jessie and Stretch run the same major release of Apache (2.4) I'm perplexed as to what might have caused this.
My question: Is there anything that changed between these two Apache versions or between these two Debian/Linux versions - a security related policy change or a capability set change - that could inhibit this kind of file I/O? And if there is, how do I re-enable this capability?