Skip to main content

CPU hungry gam_server process in OEL 4U5

Today, we noticed a CPU hungry gam_server process using 100% CPU in some (32 bit) VM running Oracle Enterprise Manager. Not knowing what is did, we did some research.
gam_server belongs to the gamin file alteration monitor, a part of FAM. By default, it monitors all /mnt/* and /media/* mounts. We happen to have an NFS share for common configs, sources and ISOs and such. So it makes some sense.
Searching Google turns up a surprising amount hits for the same problem, dating back as far as 2004. There were some memory leaks with versions older than 0.1.7 but most problems should be fixed starting with that version. So update gamin if you don't have that version. The next issue is the default config for gamin. Two seperate solutions (1|2) both outline the solution: adjust the /etc/gamin/.gaminrc and set appropriate poll intervals for the file systems of your choice. In our case, we'll adjust NFS polls to every 30 seconds, ext3 to 10 secs.

fsset nfs poll 30
fsset ext3 poll 10

You could also adjust the mount points being monitered. Might try that later.

Comments

Popular posts from this blog

Preventing PuTTY timeouts

Just found a great tip to prevent timeouts of PuTTY sessions. I'm fine with timeouts by the host, but in our case the firewall kills sessions after 30 minutes of inactivity... When using PuTTY to ssh to your Linux/Unix servers, be sure to use the feature to send NULL packets to prevent a timeout. I've set it to once every 900 seconds, i.e. 15 minutes... See screenshot on the right.

Removing VGs or LVs from LVM

While are many excellent tutorials about creating and using LVM on Linux, not may show you how you can remove disks from LVM Volume Groups (VG) and reclaim storage or how to remove a Logical Volume (LV) from your LVM set-up. Here is what I did: Use -t to TEST ANY LVM action first! We are going to release 1 TB from LVM. The Volume group was extended with 1 TB storage to serve as a cheap NFS/CIFS file server when setting up our data center. It is now deprecated and replaced by a NAS so it's no longer needed. 1) check LVM; note the four 256 GB LUNs [root@server ~]# pvscan -v Wiping cache of LVM-capable devices Wiping internal VG cache Walking through all physical volumes PV /dev/sdb1 VG vgdata lvm2 [50.00 GB / 0 free] PV /dev/sdc1 VG vgdata lvm2 [256.00 GB / 0 free] PV /dev/sdd1 VG vgdata lvm2 [256.00 GB / 0 free] PV /dev/sde1 VG vgdata lvm2 [256.00 GB / 0 free] PV /dev/sdf1 VG vgdata lvm2 [256.00 GB / 0 free] PV /dev/sdg ...

Tuning the nscd name cache daemon

I've been playing a bit with the nscd now and want to share some tips related to tuning the nscd.conf file. To see how the DNS cache is doing, use nscd -g. nscd configuration: 0 server debug level 26m 57s server runtime 5 current number of threads 32 maximum number of threads 0 number of times clients had to wait yes paranoia mode enabled 3600 restart internal passwd cache: no cache is enabled [other zero output removed] group cache: no cache is enabled [other zero output removed] hosts cache: yes cache is enabled yes cache is persistent yes cache is shared 211 suggested size 216064 total data pool size 1144 used data pool size 3600 seconds time to live for positive entries 20 seconds time to live for negative entries 66254 cache hi...