AOOI Installer swap/oom-killer issue

[WesB]

Good day,

I was running centos4.7 installed from one of your earlier aooi installers think it put 4.3 on originally but through upgrades finished at 4.7. Anyways had a few issues with the raid on it and oom-killer. I completed a backup of the server and tried to run the aooi installer to put the system upto centos 5. But the installer complained about lilo. So i reimaged the server then used the aooi to install centos 5. did all the updates and installed plesk 9.0.1 then went through and restored all my sites ( Only 7 domains running on the server). For a couple days everything seemed alright but then started getting oom killer again. I don't know much about this i'm learning as I go here. But it seems to me something is messed up with the partitioning. For 1 I don't think swap is set right. When I do a free -m i see the following:

Code: Select all

             total       used       free     shared    buffers     cached
Mem:           986        725        260          0         70        288
-/+ buffers/cache:        367        618
Swap:            0          0          0

Also doing a cat /proc/mdstat provides the following output:

Code: Select all

Personalities : [raid1]
md1 : active raid1 sdb1[1] sda1[0]
      264960 blocks [2/2] [UU]

md0 : active raid1 sdb3[1] sda3[0]
      153340352 blocks [2/2] [UU]

unused devices: <none>

And fdisk -l shows the following:

Code: Select all

Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1          33      265041   fd  Linux raid autodetect
/dev/sda2             124         367     1959930   82  Linux swap / Solaris
/dev/sda3             368       19457   153340425   fd  Linux raid autodetect

Disk /dev/sdb: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *           1          33      265041   fd  Linux raid autodetect
/dev/sdb2             124         367     1959930   82  Linux swap / Solaris
/dev/sdb3             368       19457   153340425   fd  Linux raid autodetect

Disk /dev/md0: 157.0 GB, 157020520448 bytes
2 heads, 4 sectors/track, 38335088 cylinders
Units = cylinders of 8 * 512 = 4096 bytes

Disk /dev/md0 doesn't contain a valid partition table

Disk /dev/md1: 271 MB, 271319040 bytes
2 heads, 4 sectors/track, 66240 cylinders
Units = cylinders of 8 * 512 = 4096 bytes

Disk /dev/md1 doesn't contain a valid partition table

The following is my /etc/fstab:

Code: Select all

/dev/md0                /                       ext3    defaults        1 1
/dev/md1                /boot                   ext3    defaults        1 2
devpts                  /dev/pts                devpts  gid=5,mode=620  0 0
tmpfs                   /dev/shm                tmpfs   defaults        0 0
proc                    /proc                   proc    defaults        0 0
sysfs                   /sys                    sysfs   defaults        0 0

I think the swap issue is whats causing the oom-killer but like I said I'm still learning here. What ever it is I have to get it sorted as its taken down the server a couple times a day and i have to reboot the server from the 1and1 admin panel as it locks right up.

Any help you can give me on this will greatly be appreciated.

[scott]

Yup thats right, you just need to activate your swap partitions:


mkswap /dev/sda2
mkswap /dev/sda3

add to the bottom of /etc/fstab
/dev/sda2 swap swap defaults 0 0
/dev/sdb2 swap swap defaults 0 0

run: swapon -a

[WesB]

Thanks scott. Was pretty sure thats all I had to do but wasn't positive. Hopefully that settles the damn oom-killer now it was getting to be a little much, waking up every morning to the server being locked up. Thanks again.

[scott]

yeah not sure why that didnt get set up at install time, it created the partitions it just didnt add them to fstab. Do you remember if you did a net or local install?

[WesB]

Local install, as I read of issues with the network install so I figured to minimize the downtime I'd do the way that I knew worked.

[scott]

Ok, I made a note of it. Its not that big of a deal to add in a %post event to make sure that gets added after the fact.