#3139 auto-upgrade problems
( on solaris10, webmin 1.40, 1.41, 1.42, global zone)
when upgrading webmin from the webmin console, a few things happen that cause webmin and modules to break:
1) miniserv.conf is updated before file permissions are changed on the new webmin-$VERSION directory & the server fails to restart
2) installing into unique directories is a good idea in general, but could break modules which have paths hardcoded - it would be simpler to keep variables pointing at $DIR/webmin which does not change, and make that directory as a symlink to $DIR/webmin-$VERSION -- after passing a few checks and tests on the new version.
3) the 'module compatability' checking feature in online module updates always seems to require the latest version, even with modules that have no real dependency on the changes or updates in the "latest" version. This is problematic to require constant upgrading, especially when the software does not update itself correctly.
4) during the previous upgrade which had to be reverse-engineered, the PAM modules (and other important stuff) didn't get installed into the new folder.
..
overall, after upgrading webmin from the console 3 times, it has broken itself in various ways each time.
Logged In: YES
user_id=129364
Originator: NO
1) What error did the server fail to start with? I haven't seen this before ..
2) You can install into a fixed directory if you like - when you run setup.sh in the webmin-x.xx directory, it can be given an install dir like /usr/local/webmin as a parameter, to which all files are copied. Future upgrades will use that same directory.
This is the recommended install method in the docs.
3) I think the correct fix here is to get the automatic update working properly..
4) Are you referring to non-core modules that didn't get copied across?