These forums are locked and archived, but all topics have been migrated to the new forum. You can search for this topic on the new forum: Search for Upgrading to Hardy... on the new forum.
Web Hosting and Cloud Computing Control Panels
Going from dapper to hardy? Hmmm...it should be OK, but you'll need to plan for some additional downtime (on top of the upgrade time) to insure all of the Virtualmin-provided packages get updated, as well. You'll probably need to update the Virtualmin source manually for that to point to the hardy repo rather than dappy.
Anyway, both OS versions are supported by both Webmin and Virtualmin, and we provide packages for both. So, the differences should be relatively minor, and problems will be small. Let us know if any issues show up, and we'll help you get them resolved (but again, plan for things to break--OS upgrades pretty much always break stuff, and even if Virtualmin stuff goes completely without a hitch, I kinda doubt the OS upgrade will).
--
Check out the forum guidelines!
OK, thank you for the info.
Would it be more advisable to upgrade Dapper to Edgy then to Feisty then Gutsy then Hardy?
I was under the impression (though I don't know exactly why, I seem to recall reading it somewhere) that the upgrade between LTS versions was extensively tested, since this is always the version in use in mission critical environments. So, I'm guessing it'll be safer to go from LTS to LTS than to go from LTS to non-LTS to non-LTS to non-LTS to LTS. But, what do I know? I've not done a lot of Ubuntu upgrades.
--
Check out the forum guidelines!
Well the upgrade went smooth enough (6.06LTS to 8.04LTS), I had a few saslauthd problems but when have I not had them...
I had to add the following to the saslauthd startup script:
# Global variables
NAME=saslauthd
DESC="SASL Authentication Daemon"
DEFAULTS=/etc/default/saslauthd
PWDIR=/var/spool/postfix/var/run/saslauthd
PIDFILE="/var/spool/postfix/var/run/${NAME}/saslauthd.pid"
and the following in "/etc/default/saslauthd"
#PARAMS="-m /var/spool/postfix/var/run/saslauthd -r" <--commented out
OPTIONS="-m ${PWDIR}" <-- added
I changed the Virtualmin source to hardy once the upgrade was complete and the updates were installed fine.
so far everything look OK.
Thank you for the advice.
Well the upgrade went smooth enough (6.06LTS to 8.04LTS), I had a few saslauthd problems but when have I not had them...
I had to add the following to the saslauthd startup script:
# Global variables
NAME=saslauthd
DESC="SASL Authentication Daemon"
DEFAULTS=/etc/default/saslauthd
PWDIR=/var/spool/postfix/var/run/saslauthd
PIDFILE="/var/spool/postfix/var/run/${NAME}/saslauthd.pid"
and the following in "/etc/default/saslauthd"
#PARAMS="-m /var/spool/postfix/var/run/saslauthd -r" <--commented out
OPTIONS="-m ${PWDIR}" <-- added
I changed the Virtualmin source to hardy once the upgrade was complete and the updates were installed fine.
so far everything look OK.
Thank you for the advice.
Well the upgrade went smooth enough (6.06LTS to 8.04LTS), I had a few saslauthd problems but when have I not had them...
I had to add the following to the saslauthd startup script:
# Global variables
NAME=saslauthd
DESC="SASL Authentication Daemon"
DEFAULTS=/etc/default/saslauthd
PWDIR=/var/spool/postfix/var/run/saslauthd
PIDFILE="/var/spool/postfix/var/run/${NAME}/saslauthd.pid"
and the following in "/etc/default/saslauthd"
#PARAMS="-m /var/spool/postfix/var/run/saslauthd -r" <--commented out
OPTIONS="-m ${PWDIR}" <-- added
I changed the Virtualmin source to hardy once the upgrade was complete and the updates were installed fine.
so far everything look OK.
Thank you for the advice.
Thanks for the followup, I'm sure that will help other folks.
I'm glad to hear it's working now though!
-Eric
Sweet! Sounds like Ubuntu did pretty well on the upgrade process (Debian is also historically really good on this front, better than CentOS/RHEL, for sure).
--
Check out the forum guidelines!