From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Authentication-Results: lists.ozlabs.org; spf=pass (mailfrom) smtp.mailfrom=linux.ibm.com (client-ip=148.163.158.5; helo=mx0a-001b2d01.pphosted.com; envelope-from=msbarth@linux.ibm.com; receiver=) Authentication-Results: lists.ozlabs.org; dmarc=none (p=none dis=none) header.from=linux.ibm.com Received: from mx0a-001b2d01.pphosted.com (mx0b-001b2d01.pphosted.com [148.163.158.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 44dq4R4hPNzDqJL for ; Wed, 10 Apr 2019 00:12:32 +1000 (AEST) Received: from pps.filterd (m0098420.ppops.net [127.0.0.1]) by mx0b-001b2d01.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x39E5vdq141291 for ; Tue, 9 Apr 2019 10:12:29 -0400 Received: from e31.co.us.ibm.com (e31.co.us.ibm.com [32.97.110.149]) by mx0b-001b2d01.pphosted.com with ESMTP id 2rrup5mtxj-1 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=NOT) for ; Tue, 09 Apr 2019 10:12:27 -0400 Received: from localhost by e31.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Tue, 9 Apr 2019 15:12:25 +0100 Received: from b03cxnp08027.gho.boulder.ibm.com (9.17.130.19) by e31.co.us.ibm.com (192.168.1.131) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256/256) Tue, 9 Apr 2019 15:12:24 +0100 Received: from b03ledav003.gho.boulder.ibm.com (b03ledav003.gho.boulder.ibm.com [9.17.130.234]) by b03cxnp08027.gho.boulder.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id x39ECNrt43778122 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 9 Apr 2019 14:12:23 GMT Received: from b03ledav003.gho.boulder.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id EAB0A6A047; Tue, 9 Apr 2019 14:12:22 +0000 (GMT) Received: from b03ledav003.gho.boulder.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id A81E16A058; Tue, 9 Apr 2019 14:12:22 +0000 (GMT) Received: from [9.10.99.66] (unknown [9.10.99.66]) by b03ledav003.gho.boulder.ibm.com (Postfix) with ESMTP; Tue, 9 Apr 2019 14:12:22 +0000 (GMT) Subject: Re: using phosphor-dbus-monitor To: Matt Spinler , Wim Vervoorn , Lei YU Cc: "openbmc@lists.ozlabs.org" References: <8daf9ac9deee4bc0808a55733681d67e@Eltsrv03.Eltan.local> <0f2fc6f7-be66-ab65-7b90-b0bdd45d5fcd@linux.ibm.com> From: Matthew Barth Date: Tue, 9 Apr 2019 09:12:22 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: <0f2fc6f7-be66-ab65-7b90-b0bdd45d5fcd@linux.ibm.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-TM-AS-GCONF: 00 x-cbid: 19040914-8235-0000-0000-00000E7C1F3D X-IBM-SpamModules-Scores: X-IBM-SpamModules-Versions: BY=3.00010895; HX=3.00000242; KW=3.00000007; PH=3.00000004; SC=3.00000284; SDB=6.01186610; UDB=6.00621488; IPR=6.00967371; MB=3.00026361; MTD=3.00000008; XFM=3.00000015; UTC=2019-04-09 14:12:25 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 19040914-8236-0000-0000-000045148251 Message-Id: X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-04-09_06:, , signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1904090090 X-BeenThere: openbmc@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Development list for OpenBMC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Apr 2019 14:12:44 -0000 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@gmail.com] >> Sent: Tuesday, April 9, 2019 5:44 AM >> To: Wim Vervoorn ; Matthew Barth >> >> Cc: openbmc@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/example/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. >> >>