Skip to main content

Ubuntu 10.04LTS to 14.04LTS upgrade

Situation:
An old Ubuntu 10.04LTS server running on Rackspace First Generation Server
Running ISPConfig 3 as the main control panel
Wanted to upgrade to latest LTS as 10.04LTS support ends in April 2015.

Steps:
1. Backup using Image under RS mycloud control panel for recovery.
2. Get into SSH
3. apt-get install update-manager-core
4. apt-get update / apt-get upgrade - to update all packages
5. remove the sites-enabled in apache2 configurations (as apache 2.2 to 2.4 has some changes)
/etc/apache2/sites-enabled/
6. do-release-upgrade -d - this updates system from 10.04LTS to 12.04LTS - download was about 250M
7. setting a new MySQL password during the update / allow services to restart / other prompts: choose default values (i.e. keeping existing version of preferences, rather than using distro's default). Giving a new MySQL somehow reduced a lot of intermediate prompts for MySQL password settings.
8. at the end of upgrade, it prompts for deleting old packages (I chose "y" to save some space) and then reboot to finish. 10.04LTS to 12.04LTS took about 25 mins.
9. reboot into 12.04LTS, perform another do-release-upgrade -d
10. reboot into 14.04LTS
11. Execute an ISPConfig update:

cd /tmp
wget http://www.ispconfig.org/downloads/ISPConfig-3-stable.tar.gz
tar xvfz ISPConfig-3-stable.tar.gz
cd ispconfig3_install/install
php -q update.php

During the update, it should prompt for the MySQL password. Enter the new one as in Step 7.

12. login to ISPConfig -> Tools -> Resync -> Website -> Start. This will re-create the /sites-enabled based on ISPConfig website status and in correct format.

Comments

Post a Comment

Popular posts from this blog

ISPConfig / Pure-FTP / SSL (TLS) setup

ISPConfig comes with LetsEncrypt integrated in its panel for web domains. However, it does not automatically use the SSL cert for FTP service (PureFTP). This post describes the steps to enable the support. 1. We need an FQDN so that Lets Encrypt (LE) will be able to generate SSL under ISPConfig panel. 2. PureFTP TLS support requires a cert in .pem format which can be generated by leveraging the LE cert generated: cat /etc/letsencrypt/live/mydomain.com/privkey.pem /etc/letsencrypt/live/mydomain.com/fullchain.pem > /etc/ssl/private/pure-ftpd.pem 3. Restart PureFTP so that it will not use the new certificate 4. LE certificates need to be renewed regularly so it is necessary to create a cron job to keep the .pem file updated. Setup a crontab 0 6 * * * /etc/letsencrypt/certbot-auto -n renew --quiet --no-self-upgrade && cat /etc/letsencrypt/live/mydomain.com/privkey.pem /etc/letsencrypt/live/mydomain.com/fullchain.pem > /etc/ssl/private/pure-ftpd.pem && se
Post a Comment
Read more

ISPConfig 3 / Mail / Custom mail filter recipe

Recently trying to setup a mail re-direct (or a cc) to an external e-mail address. It is important to first determine if you are running courier or dovecot because the syntax is different. Under dovecot, it should be in sieve syntax. Therefore, under ISPConfig3 -> Email -> Email Mailbox -> Custom Rules, enter: redirect "mail@example.com"; Ensure it is double straight quotes and semi-colon at the end. Wait until the update is done (usually a few minutes) via the cron jobs of ISPConfig3 updating the /var/vmail/domain/username/.sieve
Post a Comment
Read more

Ubuntu 16.04 and ISPConfig 3.1 - stopping ClamAV

ClamAV requires quite a bit of resources to run in the background and this usually slows down the mail delivery. In the ISPConfig 3 (Under Perfect Server setup), clamAV is run within Amavis. Therefore, typical removal of clamAV commands will not remove it. When RAM is really low, Linux kills amavis and this will cause mail not being delivered. Therefore, if we run amavis to manage anti-virus and spam, consider a minimum of 2G or 4G RAM VM/Cloud servers. The steps to disable clamav and amavisd are: (1) edit postfix conf - note amavis uses a special port 10024 and 10026. Therefore, if you are not using these ports, consider closing them in your firewall settings. nano /etc/postfix/main.cf # content_filter = amavis:[127.0.0.1]:10024 # receive_override_options = no_address_mappings (2) Under ISPConfig 3.1, comment additional 2 lines nano /etc/postfix/tag_as_foreign.re # /^/ FILTER amavis:[127.0.0.1]:10024 nano /etc/postfix/tag_as_originating.re # /^/ FILTER amavi
1 comment
Read more