Red Hat : Global File System

- native file system.
- Interfaces directly with Linux kernel file system interface (VFS Player).
- Can be implemented on Standalone System.
- Can be a part of cluster configuration.
- GFS can be created on LVM logical volume.
- GFS is based on 64 bit architecture, can accommodate 8 EB file system.
- Red Hat GFS nodes can be configured and managed with Red Hat Cluster Suite configuration and management tools.
- LVM logical volumes in a Red Hat Cluster Suite are managed by CLVM, which is cluster wide implementation of LVM (clvmd daemon).
- daemon allow all nodes in cluster to share the volume.

OTRS: How to set the Generic Agent?

Taken from, lists.otrs.org.

So you need to create as many jobs as you have agents.
The idea behind GenericAgent is very simple: search for tickets using the
values in sections shaded grey and set new values in tickets in sections
shaded black. You should have all your ticket types, queues, agents,
customers defined before you start making a GenericAgent job.

For example, we are building a job to assign Hardware problems to Mark
Twain.

In Admin, go to Generic Agent. Type in the job name Hardware_to_Twain and
click Add. A new job form appears. Study it a little. There are sections
with title shaded gray. The values you put into these sections' fields are
used to select the tickets for processing by the job. You select Agent/Owner
= root at localhost. You select ticket state = new. You select Ticket lock =
unlock, you select ticket type = Hardware problem. How do you plan to deal
with email tickets btw? They will not get tycket type set correctly.

Now we move to sections with titles shaded black. That's where we program
new values for ticket fields:
You select new Agent = Mark Twain. You select the new Queue = Hardware, New
ticket lock = lock.
You may add a note to leave trace of what has been done for your customer.
(It's reflected in the history for the agents anyway).
Check Send no notifications flag .

Go back to the beginning and think of the schedule for the job. How often it
should run?

AS soon as you save the job - you're done. If there are problems with the
job - look in the System Log.

OTRS: How survey module works?

There are no steps given anywhere about how survey module works.
Here are the steps given,
1. Download and install Survey module
2. Login as OTRS Admin i.e. root@localhost by default.
3. Navigate to SysConfig setting under "Misc" section.
4. Search for Survey, then go to Core -> Survey::SendPeriod.
5. Change this value to 0, to send mail always whenever agent close the ticket.
6. Also created survey should have status as "Master". This is the setting when you create the survey.

This is where you can find more details, this post is translation from German.
http://translate.google.com/translate?hl=en&sl=de&u=http://wiki.otrs-forum.de/index.php%3Ftitle%3DSurvey&ei=3VWxSdOZCozMmQeRxJjfBQ&sa=X&oi=translate&resnum=8&ct=result&prev=/search%3Fq%3DSurvey::SendPeriod%26hl%3Den%26client%3Dsafari%26rls%3Den-us%26sa%3DG

Ganglia Installation errors and solutions.

Error:
Checking for apr
checking for apr-1-config... no
configure: error: apr-1-config binary not found in path
make: *** No targets specified and no makefile found. Stop.

Resolution:
Install respective version of apr-devel. for me it was apr-devel-1.2.7-11.i386.rpm

Error:
Checking for confuse
checking for cfg_parse in -lconfuse... no
Trying harder including gettext
checking for cfg_parse in -lconfuse... no
Trying harder including iconv
checking for cfg_parse in -lconfuse... no
libconfuse not found

Resolution:
Install "libconfuse" and "libconfuse-devel" packages.

Error:
mod_python.c error: Python.h: No such file or directory
Resolution:
Install "python-devel" package if not installed.

- nilesh

Nagios: How to suppress notifications when host goes down.

There are two ways to avoid extra notifications of services when host goes down.

1. Configure ping (use check-host-alive) as the host check, when the host is unreachable, the notifications for the services will not be sent.

2. Can have service dependency configuration file like this,
define servicedependency {
hostgroup_name all_servers
service_description ping check
dependent_hostgroup_name all_servers
dependent_service_description *
execution_failure_criteria w,c
notification_failure_criteria w,u,c
}