An unknown issue happened on 3rd March that caused the shared health record, terminology service, client registry and the HIM to be restarted by the NDC. From that day, the Health Information Mediator couldn't receive messages from remote Health centers. The Jembi Technical team made a deep diagnosis and identified some issue that might have caused the crash and try to fix them.

This page is for documenting the the fixes applied to the registries after the crash.

Hostname Issue

After migration, the hostname were set in a non persistent way using the command 

hostname registryname

which doesn't persist the hostname into the file located in /etc/hostname

The best way to persist it is edit that file and add the host name the current registry you are applying changes to.

Type the following command and change the name to your desired name.

sudo vi /etc/hostname

and save changes.

Note that the hostname will be full set after restarting the registry.

/boot full issue

The ubuntu instances that the various registries are running have automatically been updating the linux kernel. Without the old kernels being removed, the /boot partitions on some of the registries have become full as the old kernels remain there. Due to this Ubuntu then fails to install the latest kernel, breaking the package manager. The following is a possible fix for this issue (and was successfully applied to the HIM server):

•  Establish the status of the /boot drive by running

  df -ah

  If /boot is not indeed full then this fix will not apply.

• Manually remove old kernels from the /boot directory to free up space. Make sure to leave at least one or two of the newest kernels.

• With space free, the installation of the latest kernel can proceed:

  sudo aptitude build-dep
  sudo apt-get -f install

• If all goes well, the latest kernel should be installed. The old manually deleted kernel still just need to be cleanup up from the package manager:

  sudo apt-get remove linux-image- #{for each kernel manually deleted}