Subject: RE: using phosphor-dbus-monitor

Wim Vervoorn wvervoorn at eltan.com
Thu Apr 11 20:46:58 AEST 2019


Hello,

I ran into another issue with the phosphor-dbus-monitor. The mechanism is working fine for me as long as I am using Boolean items like CriticalAlarmHigh etc.

For some reason it doesn't work if I try to use a real Value like the Value in the xyz.openbmc_project.Sensor.Value interface or  the CriticalHigh in the xyz.openbmc_project.Sensor.Threshold.Critical interface.

If I do this the "get value" always returns 0 (while in the case of the Boolean it correctly returns either 0 or 1.

One thing to mention is that I am using dbus-sensors. As far as I can see this always deals with "double" Values and I can't specify this in the yaml so I used a uint64 instead.

Any suggestions?

Best regards,

Wim Vervoorn

-----Original Message-----
Subject: RE: using phosphor-dbus-monitor
Message-ID: <eb2c8def113944bfacad1d5aeafb94af at Eltsrv03.Eltan.local>
Content-Type: text/plain; charset="utf-8"

Hello Matt,

I just found the reason why this wasn?t working. I overlooked a typo in the interface : Sensors instead of Sensor.

Best ergards,

Wim Vervoorn

-----Original Message-----
From: Matthew Barth [mailto:msbarth at linux.ibm.com]
Sent: Tuesday, April 9, 2019 4:12 PM
To: Matt Spinler <mspinler at linux.ibm.com>; Wim Vervoorn <wvervoorn at eltan.com>; Lei YU <mine260309 at gmail.com>
Cc: openbmc at lists.ozlabs.org
Subject: Re: using phosphor-dbus-monitor



On 4/9/19 8:50 AM, Matt Spinler wrote:
> Hi Wim,
> 
> If you could post your YAML somewhere, I could take a look for any 
> obvious problems.
If you could also provide a little more details on the error your attempting to log would be helpful (i.e. is there a dbus interface?).
> 
> On 4/9/2019 2:23 AM, Wim Vervoorn wrote:
>> Hello Lei,
>>
>> Thanks for your response. I know this example too and it helps a bit 
>> but it doesn?t really clarify all issues.
>>
>> As you've worked with this as well. Do you understand the meta item? 
>> The example indicates it has different meaning but doesn't provide 
>> any pointers to what those meanings are. Have you been able to find out?
What meta item are you referring to?
>>
>> Best Regards,
>> Wim Vervoorn
>>
>> -----Original Message-----
>> From: Lei YU [mailto:mine260309 at gmail.com]
>> Sent: Tuesday, April 9, 2019 5:44 AM
>> To: Wim Vervoorn <wvervoorn at eltan.com>; Matthew Barth 
>> <msbarth at linux.ibm.com>
>> Cc: openbmc at lists.ozlabs.org
>> Subject: Re: using phosphor-dbus-monitor
>>
>>> I am trying to use phosphor-dbus-monitor to create logging of sensor 
>>> exceptions like a Critical state on a specific sensor.
>>> I am able to create a solution with a building yaml but at the end 
>>> it doesn?t deliver me the desired result.
>>> As there are very limited examples (on a few in the witherspoon) it 
>>> is very hard to figure out where the mistake is.
>> There is an example yaml config in the repo:
>> https://github.com/openbmc/phosphor-dbus-monitor/blob/master/src/exam
>> ple/example.yaml
>>
>>
>> And I have the same feeling that it's hard to know what's wrong if 
>> something is wrong.ei
>>
>>> Are there any tools that can be used to make this easier?
>> @Matthew Barth Could you kindly help to add some doc/tool to make it 
>> easier to use?
Originally, the example yaml was meant to be the document which I understand is probably not the greatest form when it comes to this. 
Unfortunately enhancing the documentation would be a low priority at this time but feel free to create/update the documentation from your findings and push them up for review if you'd like.
>>
>>> Additionally is this the correct method to achieve this goal or 
>>> should I use something else to define conditions for logging?
>> I think so. This repo is intended to watch the dbus and do stuff as 
>> yaml config.
Correct. This repo was intended to perform error logging and/or system level actions, such as a shutdown, based on object properties on dbus.
>>
>>






More information about the openbmc mailing list