Translations of this page:

Osmius

Osmius Agent for Linux
Agent name: osm_ag_LINUX001Agent code: LINUX001
Content: Osmius agent for Linux Operating Systems
Date: 11/02/2010 Revision Date: 15/02/2011

General Information

This agent can monitor various parameters of Linux systems. It has been tested in different linux servers. However, we recommend checking its functionality before implanting it in a production environment.

Linux agent has been developed using functionalities and enhancements of Osmius framework and ACE libraries, so it is necessary to install the ACE libraries for the proper deployment and operation of Linux agent. See chapter: installation.

LINUX001 agent provides up to 26 basic events with configuration parameters to allow scaling of a very simple way and 9 info events about the system. Events have been selected by the Research and Development Osmius Team as the most useful and easy.

All events are local, so intrusive. The Linux agent needs to read certain system files and run some calls to the kernel so it should run on the same computer that you want to monitor

Linux Instance

As a general rule each Osmius agent can monitor one instance type. If you are not familiar with these concepts check out the glossary. Each instance is individually defined in the configuration file (if you want further information go to agents and instances); depending on agent type is the instance type and depending on instance is the connection info.

CONNECTION_INFO

The connection information or connection_info is data that the agent needs to know to connect to the instance. (See more about the connection_info

In linux instance the connection info is void because we have not to connect to anything

CONNECTION_INFO=

TYPE

The type defines the instance type to be monitored. Every declared instance must be associated with a type as you can see here

For Linux:

TYPE= LINUX001

Event summary table for Linux

Here's briefly the capabilities of this agent, further down on this page each event is described in more detail.

EVENT DESCRIPTION c w a tseconds Extra parameters / Remarks
OSUPTIME Uptime in seconds1 600 300 600 Silent mode ( -s) recommmended
OSPRCCPU CPU load percentage 0 90 95 60 Silent mode ( -s) recommmended
OSPRCMEM Memory used percentage 0 70 90 60 Silent mode ( -s) recommmended
OSPRCSWP Swap memory used percentage 0 50 80 600 Silent mode ( -s) recommmended
OSIP4INT Number of active IP4 interfaces 1 Administrator Administrator 600 Silent mode ( -s) recommmended
OSIP6INT Number of active IP6 interfaces 1 Administrator Administrator 600 Silent mode ( -s) recomendado
OSPRDWN0 Check if a process is running 1 0 0 600 -P “process_name”
“Silent mode ( -s) recommmended
OSPROC00 Instances number of a running process 0 X Y 300 -P “process_number”
“Silent mode ( -s) recommmended
OSCPUP00 CPU percentage by process 0 3 15 300 -P “proc1”
“Silent mode ( -s) recommmended
OSPRCUFS Check available space percentage of a filesystem 0 70 90 3600 -L “filesystem1”
Silent mode ( -s) recommmended
OSMEMP00 % Memory used by process 0 3 15 300 -P “proc1”
“Silent mode ( -s) recommmended
OSKBSI00 KB/s IN (incoming) by net interface 0 100 1000 300 -L “interface_name” \
“Silent mode ( -s) recommmended
OSKBSO00 KB/s OUT by net interface 0 100 1000 300 -L “interface_name”
“Silent mode ( -s) recommmended
OSFREMFS Free MB on filesystem 1 100 10 3600 -L “filesystem1”
“Silent mode ( -s) recommmended
OSNUMPRC Total number of processes 0 Administrator Administrator 600 Silent mode ( -s) recommmended
OSNUMCPU Number of system processors 1 Administrator Administrator 604800 Silent mode ( -s) recommmended
OSINTEMP Internal system temperature 0 60 80 600 Silent mode ( -s) recommmended
OSLOG001 Search text in a log file 0 1 1 600 -S “text” -L “absolute path”
You can set OSLOG000 to OSLOG099 (100 events)
Silent mode ( -s) recommmended
OSBINCHG Detects changes on system binaries directories 0 1 1 1800 [-L “dir1”]
If this parameter is not set a directory list by default will be used
OSVIFCHG Detects changes on very important (vital) files and directories 0 1 1 1800 [-L “dir_or_file1”]
If this parameter is not set a directory and file list by default will be used
OSIPCHAG Detects changes on system IP addresses 0 1 1 1800 -
OSNICCHG Detects changes on system NICs configuration 0 1 1 1800 -
OSNTPOFF Offset measured in seconds between local and NTP server time 0 1 5 600 [-S “ntp_server”]
If this parameter is not set, ntp server es.pool.ntp.org will be used by default
OSWRPERF Check disk write performance measured in MB/s 1 100 50 600 -
OSRDPERF Check disk read performance measured in MB/s 1 100 50 600 -
OSZOMBIE Counts the number of zombie processes 0 1 1 600 -

Information Events

Info events retieve general data about instance, usually this data doesn't change over time. This kind of events have no severity, simply provides instance details.

EVENT DESCRIPTION tseconds Observations
OSINFNAM Host Name 86400 (1 day) Name of the host
OSINFOSK Operating System version 86400 (1 day) Distribution and Kernel information
OSINFMCH Hardware information 86400 (1 day) Remote hardware info
OSINFMEM Memory 86400 (1 day) Physic memory detected
OSINFCPU Processors information 86400 (1 day) CPU models
OSINFNET Network devices 86400 (1 day) -
OSINFFSM Filesystems 86400 (1 day) -
OSINFTOP First lines of top command 86400 (1 day) You can see more active processes
OSINFUSR Users information 86400 (1 day) It shows you up to 40 system users

Linux agent events

OSUPTIME

System uptime (time since last reboot/restart) in seconds.

Return values:

VALUE MEANING
-1 Error
X Number of seconds

Recommended parameters:

Comparison type Inverse. The lower value the higher severity (-c 1)
Monitoring interval 60 seconds – 1 hour –> depends on instance importance
Warning threshold 60 - Consult your Linux administrator
Alert threshold 60 - Consult your Linux administrator

Parameter setting example:

OSUPTIME = -t 300 -c 1 -w 60 -a 60 -T "Linux uptime"

Comment: An easy read format will be returned in the associated text: Days[X] Hours[Y] Mins[Z].
This event use /proc/uptime kernel file. Be careful with changes and feed back us. Anyway this is free software so you can make the appropriate changes to suit your needs.

OSPRCCPU

Returns the percentage of CPU used during the last monitoring second.

Return values:

VALUE MEANING
-1 Error
0 - 100 % CPU used

Recommended parameters:

Comparison type Direct. The higher value the higher severity (-c 0)
Monitoring interval 60 seconds – 1 hour –> depends on instance importance
Warning threshold 90 - depends on system load
Alert threshold 95 - depends on system load

Parameter setting example:

OSPRCCPU = -t 300 -c 0 -w 90 -a 95 -T "CPU usage"

Comment: You can use this event to know if system is overloaded. It is useful to make capacity plannins.
This event use “top” system command. Be careful with changes and feed back us. Anyway this is free software so you can make the appropriate changes to suit your needs.

OSPRCMEM

Returns memory usage percentage.

Return values:

VALUE MEANING
-1 Error
0 - 100 % memory usage

Recommended parameters:

Comparison type Direct. The higher value the higher severity (-c 0)
Monitoring interval 60 seconds – 1 hour –> depends on instance importance
Warning threshold 70 - depends on system load
Alert threshold 90 - depends on system load

Parameter setting example:

OSPRCMEM = -t 600 -c 0 -w 70 -a 90 -T "Memory usage"

Comment: You can use this event to know how a process or group of precessesare consuming system memory, you also can use this values to make capacity planning reports
This event use /proc/meminfo kernel file. Be careful with changes and feed back us. Anyway this is free software so you can make the appropriate changes to suit your needs.

OSPRCSWP

Returns swapping files and devices usage percentage.

Return values:

VALUE MEANING
-1 Error
0 - 100 % swap usage

Recommended parameters:

Comparison type Direct. The higher value the higher severity (-c 0)
Monitoring interval 60 seconds – 1 hour –> depends on instance importance
Warning threshold 50 - depends on system load
Alert threshold 80 - depends on system load

Parameter setting example:

OSPRCSWP = -t 600 -c 0 -w 50 -a 80 -T "Swap usage"

Comment: You can use this event to know how swap memory is used, you also can use this values to make capacity planning reports
This event use /proc/meminfo kernel file. Be careful with changes and feed back us. Anyway this is free software so you can make the appropriate changes to suit your needs.

OSIP4INT

This OSIP4INT returns number of active IPv4 interfaces in the sytem.

Return values:

VALUE MEANING
-1 Error
X Interfaces IP4

Recommended parameters:

Comparison type Inverse. The lower value the higher severity (-c 1)
Monitoring interval 60 seconds – 1 hour –> depends on instance importance
Warning threshold Number of IP4 interfaces that you need
Alert threshold Number of IP4 interfaces that you need

Parameter setting example:

OSIP4INT = -t 300 -c 1 -w 4 -a 4 -T "Interfaces IP4"

Comment: It's an event portable. You can see in the code that we only used ACE wrappers functions.

OSIP6INT

This OSIP6INT returns number of active IPv6 interfaces in the sytem.

Return values:

VALUE MEANING
-1 Error
X Interfaces IP6

Recommended parameters:

Comparison type Inverse. The lower value the higher severity (-c 1)
Monitoring interval 60 seconds – 1 hour –> depends on instance importance
Warning threshold Number of IP6 interfaces that you need
Alert threshold Number of IP6 interfaces that you need

Parameter setting example:

OSIP4INT = -t 300 -c 1 -w 4 -a 4 -T "Interfaces IP6"

Comment: It's an event portable. You can see in the code that we only used ACE wrappers functions.

OSPRCDWN

Check if a process is running or not.

Extra parameters:
This event need an extra parameter to work:

PARAMETER MEANING Mandatory
-L “proc1” - Process Yes

Return values:

VALUE MEANING
-1 Error
0 Pprocesses is not running
1 Process is running

Recommended parameters:

Comparison type Direct. The higher value the higher severity (-c 0)
Monitoring interval 60 seconds – 1 hour –> depends on instance importance
Warning threshold 1
Alert threshold 1

Parameter setting example:

OSPRCDWN = -t 300 -c 0 -w 1 -a 1 -L "osmius" -T "No active process"

OSPRCUFS

Chek if the filesystem used more than a percentage defined by user.

Extra parameters:
This event need an extra parameter to work:

PARAMETER MEANING Mandatory
-L -L “fs1” - Filesystem. Yes

Return values:

VALUE MEANING
-1 Error
0 - 100 % used space on filesystem

Recommended parameters:

Comparison type Direct. The higher value the higher severity (-c 0)
Monitoring interval 60 seconds – 1 hour –> depends on instance importance
Warning threshold 70
Alert threshold 90

Parameter setting example:

OSPRCUFS = -t 3600 -c 0 -w 70 -a 90 -T "Uso sistemas de ficheros" -L "/tmp"

OSNUMPRC

Returns the number of processes running on the Linux system.

Return values:

VALUE MEANING
-1 Error
X number of running processes

Recommended parameters:

Comparison type Direct. The higher value the higher severity (-c 0)
Monitoring interval 60 seconds – 1 hour –> depends on instance importance
Warning threshold Consult your Linux administrator
Alert threshold Consult your Linux administrator

Parameter setting example:

OSNUMPRC = -t 300 -c 0 -w 3000 -a 5000 -T "processes running"

Comment: This event use “ps” system command. Be careful with changes and feed back us. Anyway this is free software so you can make the appropriate changes to suit your needs.

OSNUMCPU

Returns number of detected CPUs on the system.

Return values:

VALUE MEANING
-1 Error
X CPUs detected

Recommended parameters:

Comparison type Inverse. The lower value the higher severity (-c 1)
Monitoring interval 1 week - 3 months
Warning threshold architecture dependent - consult your linux administrator
Alert threshold architecture dependent - consult your linux administrator

Parameter setting example:

OSNUMCPU = -t 2592000 -c 1 -w 1 -a 1 -T "# CPUs"

Comment: This event use “grep” and “wc” system commands and the ”/proc/cpuinfo” linux kernel file. Be careful with changes and feed back us. Anyway this is free software so you can make the appropriate changes to suit your needs.

OSINTEMP

This event returns system internal temperature degrees.

Return values:

VALUE MEANING
-1 Error
X temperature degrees

Recommended parameters:

Comparison type Direct. The higher value the higher severity (-c 0)
Monitoring interval 60 seconds - 1 hour
Warning threshold 60
Alert threshold 80

Parameter setting example:

OSINTEMP = -t 3600 -c 0 -w 40 -a 50 -T "Temperature"

Comment: This event uses /proc/acpi/thermal_zone/THM/temperature linux kernel information file. Be careful with changes and feed back us. Anyway this is free software so you can make the appropriate changes to suit your needs.

OSPROC00

This event counts number of instances of a process, number of simultaneous executions of a program.

Extra parameters:
This event need an extra parameter to work:

PARAMETER MEANING Mandatory
-P -P “proc1” - Process name to monitor. Yes

Return values:

VALUE MEANING
-1 Error
X Process instances number

Recommended parameters:

Comparison type Direct. The higher value the higher severity (-c 0)
Monitoring interval 60 seconds – 1 hour –> depends on instance importance
Warning threshold X - dependent value, consult your linux administrator
Alert threshold Y - dependent value, consult your linux administrator

Parameter setting example:

OSPROC00 = -t 300 -c 0 -w 2 -a 2 -P "mysqld" - T "Instances of MySQL server"

Comment: Useful both as a process need not run more than N times, like when if less than N instances may fail This is achieved by changing the type of comparison.
You can monitor up to 5 processes: OSPROC00, OSPROC01, OSPROC02, OSPROC03 and OSPROC04.

OSCPUP00

This event computes cpu consumption percentage of a process.

Extra parameters:
This event need an extra parameter to work:

PARAMETER MEANING Mandatory
-P -P “proc1” - Process name to monitor. Yes

Return values:

VALUE MEANING
-1 Error
X CPU consumption percentage

Recommended parameters:

Comparison type Direct. The higher value the higher severity (-c 0)
Monitoring interval 60 seconds – 1 hour –> depends on instance importance
Warning threshold 3
Alert threshold 15

Parameter setting example:

OSCPUP00 = -t 300 -c 0 -w 3 -a 5 -P "osm_master_agent" - T "Master agent CPU"

Comment: This event uses “ps” system command
You can monitor up to 5 processes: OSCPUP00, OSCPUP01, OSCPUP02, OSCPUP03 and OSCPUP04.

OSKBSI00

OSKBSI00 event returns the number of kilobytes per second incoming by network interface. \ \ The return value is the average downloaded KB/s download for that interface in the monitoring interval.

Extra parameters:
This event need an extra parameter to work:

PARAMETER MEANING Mandatory
-L -L “interface_name” - Interface name to monitor (default eth0). No

Return values:

VALUE MEANING
-1 Error
X KB/s incoming

Recommended parameters:

Comparison type Direct. The higher value the higher severity (-c 0)
Monitoring interval 60 seconds – 1 hour –> depends on instance importance
Warning threshold 100
Alert threshold 1000

Parameter setting example:

OSKBSI00 = -t 300 -c 0 -w 100 -a 1000 -L "wlan0" - T "incoming speed wlan0"

Comment: This event uses ”/proc/net/dev” kernel linux file
If, for example, the eth0 interface has been downloaded for one minute at 300 KB / s and the monitoring interval is 10 minutes, the return value is 30 KB / s, and the average is performed over the monitoring interval ; take this into account in applying the thresholds for warning and alarm
You can monitor up to 5 interfaces: OSKBSI00, OSKBSI01, OSKBSI02, OSKBSI03 and OSKBSI04.

OSKBSO00

OSKBSO00 event returns the number of kilobytes per second outgoing by network interface.

Extra parameters:
This event need an extra parameter to work:

PARAMETER MEANING Mandatory
-L -L “interface_name” - Interface name to monitor (por defecto eth0). No

Return values:

VALUE MEANING
-1 Error
X KB/s outgoing

Recommended parameters:

Comparison type Direct. The higher value the higher severity (-c 0)
Monitoring interval 60 seconds – 1 hour –> depends on instance importance
Warning threshold 100
Alert threshold 1000

Parameter setting example:

OSKBSO00 = -t 300 -c 0 -w 100 -a 1000 -L "wlan0" - T "Outgoing speed wlan0"

Comment: Este evento hace uso del fichero del kernel de Linux”/proc/net/dev”
If, for example, the eth0 interface has been uploaded for one minute at 300 KB / s and the monitoring interval is 10 minutes, the return value is 30 KB / s, and the average is performed over the monitoring interval ; take this into account in applying the thresholds for warning and alarm
You can monitor up to 5 interfaces: OSKBSO00, OSKBSO01, OSKBSO02, OSKBSO03 and OSKBSO04.

OSFREMFS

This event returns amount free MB of space in a filesystem. If you set a list of filesystem, the event returns the fuller one and its name.

Extra parameters:
This event need an extra parameter to work:

PARAMETER MEANING Mandatory
-F -L “fs1[,fs2,fsN]” - List of filesystems to monitor (You have not use spaces between commas). Yes

Return values:

VALUE MEANING
-1 Error
X Free MB

Recommended parameters:

Comparison type Inverse. The lower value the higher severity (-c 1))
Monitoring interval 60 seconds – 1 hour –> depends on instance importance
Warning threshold 100
Alert threshold 10

Parameter setting example:

OSFREMFS = -t 300 -c 1 -w 100 -a 10 -L "/,/home" - T "MB libres de los FS"

OSLOG001

This OSLOG001 search a text in a text file.

Extra parameters: This event need two extra parameter to work:

PARAMETER MEANING Mandatory
-S -S “text to search” - Text to search in the text file . Yes
-L -L “abosulte_path_of_the_file” - Text file. Yes

Return values:

VALUE MEANING
-1 Error
0 No matches found
1 At least one match

Recommended parameters:

Comparison type Direct. The higher value the higher severity (-c 0)
Monitoring interval 60 seconds – 1 hour –> depends on instance importance
Warning threshold 1
Alert threshold 1

Parameter setting example:

OSLOG001 = -t 4 -c 0 -w 1 -a 1 -S "error" -L "/home/osmius/osmius/test.txt"

Observaciones: This event remembers the last position read. In the next execution only reads and analyzes from the last position until the end.
You can define OSLOG000 to OSLOG099, ie, 100 events of this type.

OSBINCHG

OSBINCHG event look for changes on system binaries directories to detect possible unauthorized modifications.
The default directories list is used when user doesn't set the -L parameter; and here is the list:

  • /usr/local/sbin
  • /usr/local/bin
  • /usr/sbin
  • /usr/bin
  • /sbin
  • /bin
  • /usr/games

Extra parameter:
This event allows the following additional parameter:

PARAMETER MEANING Mandatory
-L -L “dir1” - Binary Directory to monitor. No

Return values:

VALUE MEANING
-1 Error
0 No changes detected
N Changes detected

Recommended parameters:

Comparison type Direct. The higher value the higher severity (-c 0)
Monitoring interval 60 seconds – 1 hour –> it depends on instance importance
Warning threshold 1
Alert threshold 1

Parameter setting example:

OSBINCHG = -t 1800 -c 0 -w 1 -a 1 -L "/usr/bin"

Notes:
This event store the monitoring data in a file, so monitoring is restarting persistent.
Any directory that has been affected by changes will be shown in the text associated with the event
This is a system security event and it can help us to detect unauthorized access or modification
If any of the directories defined doesn't exist the agent detect it and no errors are shown, it is useful to define templates

OSVIFCHG

OSVIFCHG event looks for changes on very important (vital) system directories anf files to detect possible unauthorized modifications or attacks.
The default files and directories list is used when user doesn't set the -L parameter; and here is the list:

  • /etc/passwd
  • /etc/shadow
  • /etc/group
  • /etc/shells
  • /etc/skel
  • /etc/apt/sources.list
  • /etc/yum.conf
  • /etc/fstab
  • /etc/hosts
  • /etc/networks
  • /etc/sysconfig/network
  • /etc/services
  • /etc/protocols
  • /etc/hosts.allow
  • /etc/hosts.deny
  • /etc/resolv.conf
  • /etc/network/interfaces
  • /etc/sysconfig/network-scripts
  • /etc/rc0.d
  • /etc/rc1.d
  • /etc/rc2.d
  • /etc/rc3.d
  • /etc/rc4.d
  • /etc/rc5.d
  • /etc/rc6.d
  • /etc/rc.local
  • /etc/rcS.d

Extra parameter:
This event allows the following additional parameter:

PARAMETER MEANING Mandatory
-L -L “dir_or_file1,” - File or directory to monitor. No

Return values:

VALUE MEANING
-1 Error
0 No changes detected
N Changes detected

Recommended parameters:

Comparison type Direct. The higher value the higher severity (-c 0)
Monitoring interval 60 seconds – 1 hour –> it depends on instance importance
Warning threshold 1
Alert threshold 1

Parameter setting example:

OSVIFCHG = -t 1800 -c 0 -w 1 -a 1 -L "/etc/passwd"

Notes:
This event store the monitoring data in a file, so monitoring is restarting persistent.
Any directory or file that has been affected by changes will be shown in the text associated with the event
This is a system security event and it can help us to detect unauthorized access or modification or attacks
If any of the directories or files defined doesn't exist the agent detect it and no errors are shown, it is useful to define templates

OSIPCHAG

OSIPCHAG event looks for changes on system IP addresses to detect possible unauthorized modifications or attacks.
This event monitors IP addresses of every system interface.

Return values:

VALUE MEANING
-1 Error
0 No changes detected
1 Changes detected on IP addresses

Recommended parameters:

Comparison type Direct. The higher value the higher severity (-c 0)
Monitoring interval 60 seconds – 1 hour –> it depends on instance importance
Warning threshold 1
Alert threshold 1

Parameter setting example:

OSIPCHAG = -t 1800 -c 0 -w 1 -a 1

Notes:
This event store the monitoring data in a file, so monitoring is restarting persistent.
This is a system security event and it can help us to detect unauthorized access or modification or attacks

OSNICCHG

OSNICCHG event looks for changes on system NICs configuration to detect unauthorized modifications or attacks.

Return values:

VALUE MEANING
-1 Error
0 No changes detected
1 Changes detected on NICs configuration

Recommended parameters:

Comparison type Direct. The higher value the higher severity (-c 0)
Monitoring interval 60 seconds – 1 hour –> it depends on instance importance
Warning threshold 1
Alert threshold 1

Parameter setting example:

OSNICCHG = -t 1800 -c 0 -w 1 -a 1

Notes:
This event store the monitoring data in a file, so monitoring is restarting persistent.
This is a system security event and it can help us to detect unauthorized access or modification or attacks

OSNTPOFF

OSNTPOFF event monitors the offset measured in seconds between system local time and a NTP server time.
The user can set the NTP server via -S parameter (explained below), if this parameter is not set then es.pool.ntp.org will be used as default NTP server.

Extra parameter:
This event allows the following additional parameter:

PARAMETER MEANING Mandatory
-S -S “ntp_server” - NTP server to check offset. No

Return values:

VALUE MEANING
-1 Error
N Offset measured in seconds

Recommended parameters:

Comparison type Direct. The higher value the higher severity (-c 0)
Monitoring interval 60 seconds – 1 hour –> it depends on instance importance
Warning threshold 1
Alert threshold 5

Parameter setting example:

OSNTPOFF = -t 600 -c 0 -w 1 -a 5 -S "es.pool.ntp.org"

Notes:
It is necessary the installation of ntpdate.

OSWRPERF

OSWRPERF event measure the disk write performance in MB/s.

Return values:

VALUE MEANING
-1 Error
N Disk writing MB/s

Recommended parameters:

Comparison type Inverse. The lower value the higher severity (-c 1)
Monitoring interval 60 seconds – 1 hour –> it depends on instance importance
Warning threshold 100
Alert threshold 50

Parameter setting example:

OSWRPERF = -t 600 -c 1 -w 100 -a 50

Notes:

OSRDPERF

OSRDPERF measure the disk read performace in MB/s.

Return values:

VALUE MEANING
-1 Error
N Disk reading MB/s

Recommended parameters:

Comparison type Inverse. The lower value the higher severity (-c 1)
Monitoring interval 60 seconds – 1 hour –> it depends on instance importance
Warning threshold 100
Alert threshold 50

Parameter setting example:

OSRDPERF = -t 600 -c 1 -w 100 -a 50

Notes:

OSZOMBIE

OSZOMBIE event counts the number of zombie processes.

Return values:

VALUE MEANING
-1 Error
N Number of zombie processes

Recommended parameters:

Comparison type Direct. The higher value the higher severity (-c 0)
Monitoring interval 60 seconds – 1 hour –> it depends on instance importance
Warning threshold 1
Alert threshold 1

Parameter setting example:

OSZOMBIE = -t 600 -c 0 -w 1 -a 1

Notes:
This event execute the following command: ps -A -ostat,ppid,pid,cmd | grep -e '^[Zz]' | wc -l

Linux agent prerequisites

In order to compile, this agent requires a set of prerequisites, which are generic to compile any Osmius agent, you can see these prerequisites.

Linux agent makefiles and compilation

  • Make Project Creator (MPC) is used by Osmius, so creating Makefiles is a trivial task. If you want to learn more about MPC and Osmius check out the section of Makefiles on Osmius.
  • In the particular case of Linux agent you can easily generate Makefile as follows:

From the agent directory using console or terminal.

$ACE_ROOT/bin/mpc.pl -type gnuace osm_ag_linux.mpc
  • Now that you have created the Makefile, agent compiling is extremely simple.
make -f GNUmakefile.Osm_Ag_LINUX001_Osmius

Binaries are automatically installed in the bin directory of OSM_ROOT base directory.

Run Linux agent

Linux agent have the same running features of the other Osmius agents. You can check it out int he section Start and Stop Agents.

To run Linux agent without Osmius web console:

osm_ag_LINUX001 -c osm_ag_LINUX001.ini -m MASTERAG -p 1950 -d [>> osm_ag_LINUX001.log]1)

Running in standalone mode

Linux Osmius agent, like the others Osmius agents, allows the execution in standalone mode. This option may be particularly useful when developing a new agent or to perform specific agent tests.

Basically you have to add a new value, called SNDCMD, to Linux via Osmius agent configuration file (osm_ag_LINUX001.ini) as shown here.

Then you must run the Linux Osmius agent setting Master Agent communications port to zero, for example:

osm_ag_LINUX001 -c osm_ag_LINUX001.ini -m 00000000 -p 0 -d

Tests list

Performed test for Linux Osmius agent.

Date: 14/02/2011
Test Results Comment
Creating an instance with all its events in silent mode OK N/A
Creating an instance with all its events with custom text OK N/A
Creating an instance with all its events but no custom text OK N/A
Declaration of 3 instances with all its events to 5 seconds and keep it
running for 48 hours
Only one instance (intrsive) Memory OK
Declare 2 instances, cause a disconnect and then reconnect OK N/A
Declare 1 instance and test each event OK N/A
Elimination of general parameter and check unbootable OK PORTCM erased
Elimination of instance CONN_INFO and check unbootable OK N/A
1) Optional, to store agent messages in a file
 
en/agentes/linux001.txt · Last modified: 2012/12/05 18:14 by osmius
 
Recent changes RSS feed Creative Commons License Donate Powered by PHP Valid XHTML 1.0 Valid CSS Driven by DokuWiki