NOTE: As of 02-06-2024, version 7.13.28 has been promoted to n the Release channel, and these steps are no longer needed
Due to an upstream change with Imunify, their deploy.sh script is missing the information to create the ‘lib’ directory. This results in a generic error in the GUI, with the following in ~iworx/var/log/iworx.log:
ERROR: /usr/local/interworx/plugins/imunifyav/Plugin/Imunifyav.php(409): include(/home/interworx/plugins/imunifyav/lib/index.php): failed to open stream: No such file or directory : /nodeworx/imunifyav/open
Because this exact issue has come up a few times in the past year, where changes to the deploy.sh script resulted in the required directory not being created, we are making a change on our end so that the lib directory exists by default. So far, every time this issue has arisen, as long as the directory exists, it is populated with the required files, so, in theory, this should prevent the same issue from coming up again, in the future.
That change will be in the next Beta version of InterWorx (7.13.28), which, barring any surprises, should be out this week. As long as there are no blocking bugs reported against that version, it will then take about three weeks to be promoted through the normal process to the Release channel.
I will update this post when that occurs, which should be in the beginning of Feb.
In the meantime, there is a very easy fix:
- Uninstall imunify
- Create the lib directory and chown to the correct permissions
chown iworx:iworx /home/interworx/plugins/imunifyav/lib
- Reinstall Imunify
~iworx/bin/imunify.pex --install --version av
~iworx/bin/imunify.pex --install --version im360
If, after taking the above steps, there are still errors viewing Imunify in the GUI, please submit a support ticket to https://support.interworx.com/ and we’ll take a look for you.
Friendly Neighborhood InterWorx Support Manager