show sidebar
Upgrading an OpenSSI Cluster from Prior Releases on Debian 3.1(Sarge)

These instructions describe how to upgrade an OpenSSI 
cluster on Debian Testing (3.1, Sarge) from  previous
releases of openssi. Openssi can be upgraded on Debian 
using apt-get utility following the steps mentioned below.

1. Comment out the entry used for installing 'openssi 
  1.0.0' in the file "/etc/apt/sources.list" and add 
  following entries in addition to entries used for 
  Debian installation. 

  deb ./

  deb-src ./

2. Add following entries to /etc/apt/preferences if it 
  is not already there. 

  Package: * 

  Pin: origin

  Pin-Priority: 1001

3. Configure http proxy. In the bash shell , you can 
  export environment variable "http_proxy" by setting its 
  value to local proxy server.

4. Add necessary drivers list to 
  "/etc/mkinitrd/modules". Most important drivers are 
  network drivers, depending upon the network cards 
  used in the participating nodes in the cluster (Ex: 
  e100, eepro100 etc.), which would be used while 
  booting cluster nodes. If it is already there , no problem.

5. Execute:

  # apt-get update 

  # apt-get dist-upgrade

  This would upgrade openssi from previous release to 
  new release . Please see the 'known problems' in this 
  document if apt-get fails due to any error or configuration 
  and get the work around with few manual steps as 

6. Reboot the cluster .

  NOTE: It has been observed that some time tftp server 
  will not respond to request once it already responded 
  to client's request. So restart the inetd on the init 
  node if client could get IP address , but could not 
  continue booting.

  # invoke-rc.d inetd restart

7. After booting execute(If few manual steps are 
  executed as mentioned in the workaround for the kown problems).

  # apt-get dist-upgrade.

 Known Problems

1. Initrd doesn't get unmounted.

2. Added new configuration "OPENSSI_CLUSTER=yes" in the 
  /etc/mkinitrd.conf. Either allow the mkinitrd.conf to 
  be rewritten while upgrading the mkinitrd package Or 
  add above entry manually and rebuild the ramdisk. You 
  can follow the mkinitrd manpage to find out how to 
  rebuild the ramdisk. It is shown below how to use 

3. If you are creating the kernel and initrd image 
  manually, make sure the kernel name and initrd name 
  should follow the format shown below.. The file 
  /cluster/kernel_version is written when installing 
  the kernel package.

  VERSION=`cat /cluster/kernel_version` 


    /usr/sbin/mkinitrd -o 

4. 'apt-get dist-upgrade' may fail with following error 
  messages while upgrading from openssi 1.0. This is 
  due to a bug with the OpenSSI 1.0 release kernel . To 
  fix this run the mkinitrd command and create ramdisk 
  image as shown below. Please see man page of mkinitrd 
  if you need more details about mkinitrd and how to 
  use it.

  # /usr/sbin/mkinitrd -o 
  /boot/initrd.img-2.4.22-ac1-ssi-686-smp 2.4.22-ac1-ssi-686-smp


  Error Messages:

    dpkg: dependency problems prevent configuration of 
    kernel-image-2.4-686-smp:  kernel-image-2.4-686-smp 
    depends on kernel-image-2.4.22-ac1-ssi-686-smp; 
    however:   Package 
    kernel-image-2.4.22-ac1-ssi-686-smp is not 
    configured yet. dpkg: error processing 
    kernel-image-2.4-686-smp (--configure):  dependency 
    problems - leaving unconfigured dpkg: dependency 
    problems prevent configuration of openssi:  openssi 
    depends on kernel-image-2.4-686-smp; however:   
    Package kernel-image-2.4-686-smp is not configured 
    yet. dpkg: error processing openssi (--configure):  
    dependency problems - leaving unconfigured Errors 
    were encountered while processing:  
    kernel-image-2.4-686-smp  openssi E: Sub-process 

    returned an error code (1)

5. Update the grub configuration, if the new kernle is 
  not listed in the "menu.list"(or any grub configuration 
  file that you are following). The below command will 
  add the new kernel and initrd to the menu.lst file .

  # /sbin/update-grub 

6. While creating initrd images using mkinitrd during 
  upgrade, you may see following messages. These 
  messages are expected and would not cause any problem 
  in upgrading opessi.

  cpio: ./dev/cciss: No such file or directory cpio: 
  ./dev/ide: No such file or directory cpio: 
  ./dev/mapper: No such file or directory cpio: 
  ./dev/md: No such file or directory cpio: ./dev/scsi: 
  No such file or directory

Maintained by Gopalakrishna <>

This page last updated on Wed Mar 22 08:41:44 2006 GMT
privacy and legal statement