Error: Can’t locate Search/Xapian.pm in @INC (you may need to install the Search::Xapian module) (@INC contains: /path/to/something /etc/perl /usr/local/lib/perl/5.18.2 /usr/local/share/perl/5.18.2 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.18 /usr/share/perl/5.18 /usr/local/lib/site_perl .) at (eval 143) line 2. BEGIN failed–compilation aborted at (eval 143) line 2.
Can’t locate Sort/Naturally.pm in @INC (you may need to install the Sort::Naturally module) (@INC contains: /path/to/something /etc/perl /usr/local/lib/perl/5.18.2 /usr/local/share/perl/5.18.2 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.18 /usr/share/perl/5.18 /usr/local/lib/site_perl .) at (eval 145) line 2. BEGIN failed–compilation aborted at (eval 145) line 2.
To reduce disk writes or silence access logs on a local lab server, update your Apache configuration in /etc/apache2/ (note that Ubuntu/Debian Apache 2.4 uses conf-available/ and 000-default.conf instead of legacy conf.d/ and default):
1. Disable the global vhost access log config:
sudo a2disconf other-vhosts-access-log
2. Inside your VirtualHost files (/etc/apache2/sites-available/000-default.conf and default-ssl.conf), comment out CustomLog:
Operational Warning: You can silence errors with ErrorLog /dev/null on disposable test VMs, but in staging or production keep ErrorLog active (or raise LogLevel warn) so crashes, permission failures, and TLS errors remain diagnosable.
If you lose your Amazon EC2 SSH key and can’t log in to your instance, this isn’t a big problem as long as your instance is EBS-based and uses an Elastic IP.
1. Upload your new SSH key, or use one generated by AWS.
2. Create an AMI of your instance.
3. Launch a new instance from your AMI and select the new SSH key.
4. Log in to your instance with the default user (ubuntu or ec2-user, depending on your original AMI).
5. Reassign the Elastic IP to the new instance.
6. Turn off the old instance and terminate it.
Modern Alternatives (No Instance Replacement Required): Today you can usually regain access without cloning an AMI by connecting via AWS Systems Manager Session Manager, pushing a temporary key through EC2 Instance Connect, or stopping the instance to attach its root EBS volume to a temporary rescue VM and updating ~/.ssh/authorized_keys directly.