MiniHow to: Upgrading ISPconfig3 Debian Wheezy to Jessie in OpenVZ

Discussion in 'General' started by SamTzu, May 14, 2015.

?

SystemD - Mistake or not?

  1. Yes

    3 vote(s)
    60.0%
  2. No

    2 vote(s)
    40.0%
  1. SamTzu

    SamTzu Member HowtoForge Supporter

    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
     
    Last edited: May 14, 2015
    till likes this.
  2. SamTzu

    SamTzu Member HowtoForge Supporter

    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.
     
  3. SamTzu

    SamTzu Member HowtoForge Supporter

    Ugly !!!
    Code:
    [email protected]:~# /etc/init.d/snmpd restart
    [....] Restarting SNMP services::pcilib: Cannot open /proc/bus/pci
      [email protected]:~# /etc/init.d/snmpd status
    [ ok ] snmpd is running.
     
    Last edited: May 14, 2015
  4. gOOvER

    gOOvER Member

    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. ;)
     
  5. SamTzu

    SamTzu Member HowtoForge Supporter

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

    webguyz Member HowtoForge Supporter

    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
     
  7. gOOvER

    gOOvER Member

    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.
     
  8. webguyz

    webguyz Member HowtoForge Supporter

    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.
     
  9. gOOvER

    gOOvER Member

    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
     
  10. SamTzu

    SamTzu Member HowtoForge Supporter

    Like I mentioned in the first line...
     
  11. SamTzu

    SamTzu Member HowtoForge Supporter

    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.
     
  12. till

    till Super Moderator Staff Member ISPConfig Developer

    How do you run the unattended updates?
     
  13. SamTzu

    SamTzu Member HowtoForge Supporter

    With dpkg-reconfigure unattended-upgrades.
     
  14. till

    till Super Moderator Staff Member ISPConfig Developer

    Did you try a different time for the upgrade cronjob?
     
  15. SamTzu

    SamTzu Member HowtoForge Supporter

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

    till Super Moderator Staff Member ISPConfig Developer

    aptitude and apt are just 2 different frontends, it should not matter which one is used. But you cant run apt nor aptitude twice at the same time, so if ispconfig queries the package database with apt or aptitude and then the unattended update tries to do the same, then it must fail. So my recommendation is to try a different time for the cronjob
     

Share This Page