[EMAIL PROTECTED] wrote on 08/15/2007 11:48:05
AM:
> handler simulator {
> entity_root = "{SYSTEMk_CHASSIS,5}"
> name = "test"
> }
I don't think this is your problem, but there is a typo in the entity root
above. A lower case 'k' that should not be.
>
> I found out something interesting which I do not understand yet:
>
> * When using openhpi 2.7.3 - the version from which I started -
> and I start it like this
>
> # openhpid -c /home/sperl/nat/openhpi.conf
>
> I get this "no handler defined in configuration" error. The daemon
> keeps running but due to the lack of a valid handler it cannot
> transmit any messages to the MCH.
>
> * When I start the daemon like that:
>
> # /home/sperl/nat/openhpi-2.7.3/openhpid/openhpid -c \
> /home/sperl/nat/openhpi.conf
>
> all defined plugin handler are found and everything seems to
> work fine. With some modifications I even was able to control
> our cooling units in our MTCA shelf.
>
The fact that running openhpid normally gives you problems and openhpid
2.7.3 from the tree does not, leads me to believe there is something wrong
with your 2.7.3 installation.
Have you tried cleaning out your installation? That is, removing all the
binaries and libraries, and then re-installing 2.7.3 to see if you get the
same error.
--Renier
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Openhpi-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openhpi-devel
