I've installed the required Perl modules, but the Server Readiness Tool tells me I haven'tOur handy Server Readiness Tool can be used prior to purchasing our web based room booking and resource scheduling software to quickly assess whether or not your server is ready to run a self-hosted edition of MIDAS.
As part of the checks the Server Readiness Tool performs, it will verify the existence of Perl modules which MIDAS requires in order to function. If any of these required modules are not found, the tool will inform you and provide guidance on how to install missing Perl modules.
Once you've installed any missing Perl modules, you can then run the Server Readiness Tool again, and all being well all tests will pass and your server will be ready to install and run MIDAS!
If however when you run the Server Readiness Tool again after installing missing modules, you're informed that required modules are still missing, then it's likely due to the fact that modules you've installed have not been installed to a valid location on your server.
When looking for modules, Perl searches in the locations specified within either the @INC environmental variable (under Linux), or "Path" environmental variable (under Windows). If the modules cannot be found in one of folders (or their sub folders) contained within @INC/Path, then the Server Readiness Tool will report that the modules are missing.
You'll therefore need to ensure that any Perl modules you're installing are installed to a location reference within @INC/Path system variable.
|To view the contents of the "Path" environmental variable on Windows:||To view the contents of the "@INC" environmental variable on Linux:|
|To locate where a Perl module has been installed on Windows:||To locate where a Perl module has been installed on a Linux server:|
You can then compare the location on the Perl module with the locations specified in @INC/Path.
Here's an illustrative example on Linux:
# find / -name Eksblowfish
In the above example an instance of the Crypt::Eksblowfish module was found at /usr/local/lib64/perl5/Crypt/Eksblowfish, which is covered by the @INC path /usr/lib64/perl5, and so the Server Readiness Tool will be able to locate this module.
If the location where your Perl modules are installed is not encompassed within one of the @INC/Path locations, this will be the reason for module not found errors/warnings when running the Server Readiness Tool.
You'd either need to modify the @INC/Path environmental variable to point to the location where your Perl modules are installed, or more preferably install Perl modules to a location already present in @INC/Path
← Return to Knowledgebase