Apache VCL logo Apache Software Foundation logo
Apache current event

Upgrade From 2.3.1 to 2.3.2

This page provides information on how to upgrade from VCL 2.3.1 to VCL 2.3.2. Please note it only applies for the upgrade from 2.3.1 to 2.3.2, this may or may not work for other versions.

The basic steps that will be performed

There are no updates to the VCL database schema between 2.3.1 and 2.3.2.

Detailed steps for upgrade from 2.3 to 2.3.2

  1. follow instructions on the VCL download page to download and verify apache-VCL-2.3.2.tar.bz2 and put in in /root

  2. extract VCL 2.3.2 code

    tar xjf apache-VCL-2.3.2.tar.bz2
    
  3. Shutdown the httpd and vcld services

    service httpd stop or /etc/init.d/httpd stop
    service vcld stop or /etc/init.d/vcld stop
    
  4. We will create a backup of the vcl database. This will provide a restore point if necessary.

    mysqldump vcl > ~/vcl-pre2.3.2-upgrade.sql
    
  5. Update the web code. This step we will move the 2.3 web directory out of the way, so we can copy in the new web code base. After copying in the new code, we will migrate your configuration changes. These instructions assume that you installed the vcl web code at /var/www/html/vcl. If you installed it elsewhere, replace /var/www/html/vcl with your vcl web root.

    cd /var/www/html
    mv vcl ~/vcl_2.3_web
    
  6. Copy the new code in place

    cd /root/apache-VCL-2.3.2
    cp -r web /var/www/html/vcl
    
  7. Copy your 2.3 config files

    cd ~/vcl_2.3_web/.ht-inc
    cp conf.php secrets.php pubkey.pem keys.pem /var/www/html/vcl/.ht-inc
    
  8. Make the maintenance directory writable by the web server user. Normally this is the apache user, if using a different user change below cmd accordingly.

    chown apache /var/www/html/vcl/.ht-inc/maintenance
    
  9. Restart httpd service

    service httpd start or /etc/init.d/httpd start
    
  10. Update management node code This step will make a backup copy of the 2.3 vcl code base and then copy the new code over the existing code to preserve any drivers or other files you’ve added.

    cd <your vcl MN code root path>
    ie. cd /usr/local/
    cp -r vcl ~/vcl_2.3_managementnode
    
  11. Copy in the 2.3.2 code base to /usr/local, copying in should preserve any drivers or other files you’ve added.

    /bin/cp -r /root/apache-VCL-2.3.2/managementnode/* /usr/local/vcl
    
  12. Run install_perl_libs.pl to add any new perl library requirements:

    /usr/local/vcl/bin/install_perl_libs.pl
    
  13. Restart vcld service

    service vcld start or /etc/init.d/vcld start
    
  14. Make some test reservations and watch the vcld.log to verify everything is working correctly.

    tail -f /var/log/vcld.log