9.4 patches are substantially big and the normal 2GB size of the /tmp of the gateway is insufficient for dealing with it.
here is a way to increase the space on the /tmp:
1) in your VMWare, create a new 10-15GB HDD for that VM
2) log in the gateway in ssh and log in as super user
3) run fdisk -l
the new drive should show as /dev/sdX (where X is the next available letter of the alphabet, for the next steps we will assume that it is /dev/sdb)
N.B.: there is a possibility that the drive will not show, in which case you have to trigger the scanning manually with the
following command for each:
Do perform an fdisk -l after that to determine the /dev/sdX that was added.
(sometimes even fdisk -l will not see it, check with lsblk if you can see the disk, if that fails too, then ask Infrastructure to check that they added the disk correctly.)
IF you see the disk via lsblk , you can continue with the steps herebelow
After which, here is the list of commands:
in here issue the following combo in that order:
n (← to create a new partition)
p (← to mention that it is a primary partition)
1 (← to mention that it is the first one)
<Enter> (← to accept the default first byte of the disk)
<Enter> (← to accept the default last byte of the disk)
t (← to change the type of the partition)
8e (← to specify LVM format for that partition)
w (← to write the changes to disk)
vgextend vg00 /dev/sdb1
lvextend -l +100%FREE /dev/vg00/lv_tmp
Now you can resume the patching.