Overview

Kernel events are not being posted

Verify the Event Manager daemon log file for errors by entering the following command:

	 	 	 	 			 # more /var/evm/adm/logfiles/evmdaemon.log

Examine for the presence of the kernel interface pseudo device by entering the following command:

# ls -l /dev/kevm

If this pseudo device is not present, create it by entering the following command:

	 	 		 	# /sbin/mknod/dev/kevm c $major 0

Major can be obtained by entering the following command:

# lsdev | awk ‘/kevm/ {print $1;}’

A subscribing application fails to receive expected events

Verify that the poster is authorized to post these events by examining the authorization file with the following command:

	 	 		 # more /etc/evm.auth

Verify that the event is registered by entering the following command:

	 	 	 # evmwatch -i -f ‘[name event_name]’ |
  	 	 	 	 		evmshow -t "@name"

If the events are still not shown, enter evmreload and examine the output again. If they are still not visible, verify that the template files are correctly installed.

Verify that the subscriber is authorized to access these events by entering the following command:

		 	 	 	 		 #  more /etc/evm.auth

Verify that the expected events are actually being posted by entering the following command:

	 	 	 	 		 # evmwatch | evmshow -t "@name @@"

Run the program that posts the event, and verify that the preceding evmwatch command displays them correctly.

A posting program is unable to post events

Verify that the Event Manager daemon is running by entering the following command:

	 	 		 	 	 # ps -aef | grep evmd

Verify that the poster is authorized to post these events by examining the authorization file by using the following command:

	 		# more /etc/evm.auth

Verify that the event is registered by entering the following command:

	 	# evmwatch -i -f ‘[name event_name]’ |
  	 	 evmshow -t "@name"

If the events are still not shown, run the evmreload command and examine it again. If they are still not visible, verify that the template files are correctly installed.

Event retrieval through evmget is slow

Examine the sizes of all log files, particularly the evmlog files (/var/evm/evmlog).

Use the ls -L command for listing file sizes.

Event Manager retrieves events from the archive log file. Hence, starting a new log may not immediately reduce the number of events available to the Event Manager. You can use the cron utility to perform a regular archiving task. You can reduce the sizes of the evmlog files by changing configuration values in the /etc/evmlogger.conf file and the /etc/evmchannel.conf file.

Expected events are not being logged

Examine the event priority. Only events with a priority of 200 or higher are logged by the Event Manager logger.