MiniHow to: Upgrading ISPconfig3 Debian Wheezy to Jessie in OpenVZ

Ok. 4 all of you who have (Proxmox) OpenVZ containers with ISPconfig here is how you can upgrade to Debian Jessie. (E-mail services are not covered here.)

First we get rid of systemd and fail2ban.
Fail2ban can break your upgrade with Failed to get D-Bus connection: Unknown error -1

Code:

apt-get install sysvinit-core sysvinit sysvinit-utils
apt-get remove --purge --auto-remove systemd
apt-get remove --purge --auto-remove fail2ban
rm -Rf /etc/fail2ban/

reboot
Now we can start the Jessie dist-upgrade without having it break down on us in the middle of upgrade.
Make sure that you have updated your sources.list to Jessie repositories with your favorite editor

Code:

vi /etc/apt/sources.list

deb http://ftp.fi.debian.org/debian testing main contrib non-free
deb http://ftp.debian.org/debian/ jessie-updates main contrib non-free
deb http://security.debian.org/ jessie/updates main contrib non-free

Code:

apt-get update && apt-get dist-upgrade

...waiting ...waiting ...waiting & million ENTER keys strokes
reboot
Then we fix default-ssl and check that apache restarts (only needed if you have it enabled. Notice the file name might be different in your setup!)

Code:

cd /etc/apache2/sites-enabled/
rm 000-default-ssl
ln -s ./../sites-available/default-ssl.conf
/etc/init.d/apache2 restart
/etc/init.d/apache2 status

(You probably want to change 000-default.conf to point to /var/www.)
Then we upgrade ISPconfig and run "Resync Websites" on Tools menu. (You have to run a ispconfig update after you upgraded to Debian Jessie so ispconfig can update all config files to the syntax of the newly installed software versions, there is no need to manually edit the ispconfig vhost file.)

Code:

ispconfig_update.sh

 

Problem
After starting the snmpd service, the following messages appear in /var/log/syslog or /var/log/net-snmpd.log

error on subcontainer ‘ia_addr’ insert (-1)
error on subcontainer ‘ia_addr’ insert (-1)

The error occurs every a few seconds and fills the log.

Solution
The problem is snmpd reports all errors to syslog, because of default setting in /etc/defaults/snmpd.

To log only up to info level, and not debug, change these to lines as follows:

SNMPDOPTS=’-LS6d -Lf /dev/null -u snmp -g snmp -I -smux -p /var/run/snmpd.pid’
TRAPDOPTS=’-LS6d -p /var/run/snmptrapd.pid’

going from -Lsd to -LS6d lowers the debug level sent to syslog. Refer to
Logging Options section in snmpcmd manpage for more information.

 

Ugly !!!

Code:

root@rs1:~# /etc/init.d/snmpd restart
[....] Restarting SNMP services::pcilib: Cannot open /proc/bus/pci
  snmpdroot@rs1:~# /etc/init.d/snmpd status
[ ok ] snmpd is running.

 

I don't know, what Image are you used, but for me these simple steps upgraded my openvz container to Jessie:

apt-get update && upgrade
-> change source.list to Jessie
apt-get update
apt-get install dpkg apt
apt-get update
apt-get dist-upgrade

Never had one of the errors you descripe.

 

Then you are probably not using OpenVZ containers with Proxmox.
We use OpenVZ debian-7.0-standard template for Proxmox.

 

Sami,

Did you use Roundcube on your Wheezy installs? And if you did, where there any problems with Roundcube after upgrading to Jessie?

Thanks!
Andy

 

There is no longer a Roundcube Package in Jessie. So you must install/update it manually. But for this, there is allready a Thread about Roundcube and Jessie.

 

So you saying during the upgrade it deletes the exisiting Roundcube installation? I understand that when starting fresh you have to manually install Roundcube, but I thought since it was working under Wheezy it would keep working when upgraded.

 

i never said, that the package will be deleted. i only said, that there is no debian Package for Roundcube in Jessie. You will get a "No Release Candidate..." Warning.

Yes, with fresh Installation you need to install Roundcube manually.

Or work with Apt Pinning.
https://packages.debian.org/stretch/roundcube

 

Like I mentioned in the first line...

 

There seems to be a problem with Debian Jessie (OpenVZ), ISPconfig3 with Unattended Upgrades. Somehow the Unattended upgrades gets stuck in Jessie version of Perfect Server.

 

With dpkg-reconfigure unattended-upgrades.

 

Not yet. I'm wondering though why ISPconfig is using aptitude rather than apt-get? Could that be conflicting with unattended-upgrades?

 

Ok, I don't use any of the things that you do but I AM having issues with systemd when upgrading. When I reboot after the Jessie dist-upgrade, the server won't boot up at all.
Should I do this sequence:
0. backup backup backup
1. with Wheezy repositories: do apt-get update and upgrade, then dist-upgrade.
2. change to Jessie repos and do this mini-how to to get ride of systemd/ add
apt-get install sysvinit-core sysvinit sysvinit-utils
3. then do the apt-get update, upgrade, and dist-upgrade
4. reboot
5. run the manual ISPconfig update and reconfigure services
6. log into ispconfig and tools->resync?
7. Reinstall fail2ban

 

Do we all use OpenVZ if we have a Wheezy perfect server?