A client of mine is running Virtualmin Pro, has installed a number of scripts for client websites and it appears some of those clients have manually upgraded some of the scripts.
As part of a routine role, I now proactively upgrade scripts to ensure that security patches are installed across the board.
In doing this, I keep coming up against Virtualmin thinking there are scripts which can be upgraded, but because the client has upgraded the script outside Virtualmin, when I click "Upgrade Now" I get the error "Failed to upgrade scripts : None of the selected servers have scripts installed that can be upgraded to the selected version".
Is there a way to "clean up" Virtualmin or "resync" it so that it does not provide false positives in the list of upgradable scripts?
I think it'd be nice in a future release to have a button called "Clean Up / Resync" which would cause Virtualmin to check if each of the "known" installs are in sync with what Virtualmin last knew about them, and either reflect the upgrades in the dropdown box or remove them if they have been upgraded outside the Script Installer system.
*** alternatively, or in addition a background task could be run from time to time to do this automatically. ***
In the meantime, what's the best way to accomplish this safely without breaking things?
-Peter
Comments
Submitted by JamieCameron on Sat, 03/01/2014 - 11:50 Comment #1
Detection of manual upgrades should actually happen automatically for some scripts, at least the ones where Virtualmin knows how to read the version number out of the install. Which specific scripts were you seeing this problem with?
Alternately, you can force Virtualmin to think think that it has already done the upgrade by editing files under the
/etc/webmin/virtual-server/scriptlogdirectory. Each domain has a dir based on it's unique numeric ID, and inside that dir there is a text file for each script.Jamie,
Attached are 3 screenshots:
"upgrade-scripts.png" - shows "Joomla 1.6.6" which can allegedly be upgraded.
"upgrade-scripts-submit.png" - shows what happens when I click "Upgrade Now" button.
"script-summary.png" - shows that Virtualmin is detecting the version of many scripts including one that is newer than Virtualmin has available.
The problem lies in what is depicted in the first two screenshots.
-Peter
Submitted by JamieCameron on Sun, 03/02/2014 - 14:29 Comment #3
The problem here is that Joomla doesn't support upgrading from 1.5.x to 1.6.x. So the message shown on upgrade-scripts-submit.png is actually correct.