This is probably the wrong place to ask the question, but I'm hoping someone can point me in the right direction.
My perl (v 5.24) intranet site (approx. 175 users) is running apache2 on Debian. Every few weeks, the perl borks out but is fine after reloading apache. The apache error log gives the error:
[:error] [pid 33013:tid 139730578532096] Attempt to reload IO/Handle.p
+m aborted.\n
Compilation failed in require at /usr/local/lib/x86_64-linux-gnu/perl/
+5.24.1/IO/Socket.pm line 12.\n
BEGIN failed--compilation aborted at /usr/local/lib/x86_64-linux-gnu/p
+erl/5.24.1/IO/Socket.pm line 12.\n
Compilation failed in require at /usr/local/share/perl/5.24.1/Net/LDAP
+.pm line 9.\n
BEGIN failed--compilation aborted at /usr/local/share/perl/5.24.1/Net/
+LDAP.pm line 9.\n
Compilation failed in require at /var/www/html/perl/modules/Intranet/D
+ocTracker.pm line 5.\n
BEGIN failed--compilation aborted at /var/www/html/perl/modules/Intran
+et/DocTracker.pm line 5.\n
Compilation failed in require at /usr/share/perl/5.24/base.pm line 136
+.\n
\t...propagated at /usr/share/perl/5.24/base.pm line 158.\n
BEGIN failed--compilation aborted at /var/www/html/perl/intranet/user/
+doctracker.pl line 8.\n
The filenames change, but it's always the same basic error message. Reloading apache smacks the server back into line and everything is rosy again. ....Until a few weeks later when this happens again. I currently have 11+G of memory. Apache was using 3.xxG before restarting it this morning when it went down to 1.75G.
Any ideas why perl is failing?