Error Creating A Connection To The Event Server
Problem(Abstract) posteifmsg (or postemsg, postzmsg) can make error message "Error creating a connection to the Event Server" if cache file does not have read/write permission properly. Resolving the problem The cache file specified with BufEvtPath parameter has to have read/write permission by the execution user. If it does not have the permission properly, "Error creating a connection to the event Server" message is returned and the event message is not cached. -r--r--r-- 1 netcool ncoadmin 0 May 23 17:49 posteifmsg.cache -r--r--r-- 1 netcool ncoadmin 126 May 02 2012 posteifmsg.conf -rwxrwxrwx 1 netcool ncoadmin 28748 May 30 2011 posteifmsg.out $ ./posteifmsg -f ./posteifmsg.conf 2222222222 33333 Error creating a connection to the Event Server Also, if the configuration file does not have the READ permission, posteifmsg failed with "Can not fopen" error message. -rw-rw-rw- 1 netcool ncoadmin 0 May 23 17:47 posteifmsg.cache ---x--x--x 1 netcool ncoadmin 126 May 02 2012 posteifmsg.conf -rwxrwxrwx 1 netcool ncoadmin 28748 May 30 2011 posteifmsg.out $ ./posteifmsg -f ./posteifmsg.conf ssss cccc ./posteifmsg.conf: Can not fopen Document information More support for: Tivoli Netcool/OMNIbus Software version: All Operating system(s): AIX, HP-UX, Linux, Solaris Reference #: 1638623 Modified date: 2016-05-06 Site availability Site assistance Contact and feedback Need support? Submit feedback to IBM Support 1-800-IBM-7378 (USA) Directory of worldwide contacts Contact Privacy Terms of use Accessibility
on it. The commands and output are shown below. IfI try the exact same commands on my workstation (Windows XP SP1) which alsohas no Tivoli software on it, it works. I tried searching for the errormessages below, but came up dry. I did verify that I can connect to theEvent Server on port 5529 from both machines.Any ideas?Thanks.postzmsg http://www.ibm.com/support/docview.wss?uid=swg21638623 -S
Typical Errors "Error creating a connection to the Event Server" Tips Humor Etc Sending a Tivoli event from a script involves several steps: Finding a suitable existing or defining a new event class. http://www.softpanorama.org/Admin/Tivoli/TEC/sending_events_to_tec_from_scripts.shtml Creating a suitable invocation of wpostzmsg or postzmsg utilities (message adapters). There are also two older versions of the same utilities wpostemsg and postemsg. You can use them too, I do not see much difference. To invoke message adapter at minimum you need: Specify the text of the message Specify class of the message. Every TEC event must have an class name that identifies it and this error creating class name should be used in invocation of wpostzmsg or postzmsg utilities which are usually used for sending events from script. The wpostzmsg used on the servers on which there is an Tivoli endpoint installed and command postzmsg that is used when there is no endpoint. Specify source of event. It should be a valid value. The source is defined by the adapter type or it can be error creating a set to a default source in the event adapter configuration file. For example LOGFILE. Optionally you can do a lot of thing and populate any slot of the message. For example: Specify the severity of the message Specify hostname Close of change status of existing message. Once an event is sent to the TEC, it will remain until it is removed. Events can be removed manually from the TEC console display, or by two automatic methods. Either a closing event can be sent, or a timer can be set on the event so that it will be closed after a specified period of time. To use a “closing” event, send a message with the same hostname and class, but with an attribute status=CLOSED. To close events based on a timer, you need to set a timer for a specific class, and specify the duration for the timer. Diagnostic can be called either non existent or very bad as both wpostzmsg and postzmsg do minimal job to validate input. Also they cannot check the existence of the class of messages you are sending so it is wrong it will be discarded. That means that typing class of the message is a bad