summaryrefslogtreecommitdiffstats
path: root/fault-monitor
Commit message (Collapse)AuthorAgeFilesLines
* Move down error entry traceMatt Spinler2018-04-121-2/+5
| | | | | | | | | | | | | | | | | | It's possible that multiple services can provide the /xyz/openbmc_project/logging paths, which means the interfaces added handler can get multiple callbacks for a single error. That being the case, move down the trace that shows the new error log object path until after the code checks that the association interface is present, as that interface will only be present on one object. Another option would have been to remove the trace completely, but it is fairly useful for debug. Change-Id: I98659562ef024455762110e20109bf3079b96cbe Signed-off-by: Matt Spinler <spinler@us.ibm.com>
* Use interfaces-removed for association removesMatt Spinler2017-12-052-28/+3
| | | | | | | | | | | The mapper will no longer emit properties-changed signals when the last endpoints property is removed from the fault association object. It will only emit an interfaces-removed signal in that case, so change the code to subscribe to the interfaces-removed signal instead. Change-Id: I225376e550d21b82473015324cd9a261e16fe6db Signed-off-by: Matt Spinler <spinler@us.ibm.com>
* Remove incorrect error log when no errors present.Dhruvaraj Subhashchandran2017-09-191-6/+1
| | | | | | | | | | An error was logged while starting the fru fault monitor with no existing error logs, which is not correct. Resolves openbmc/openbmc#2330 Change-Id: I6b222b45dd99b653443c58d9982d6576f8af0bfa Signed-off-by: Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com>
* Assert LEDs for existing callouts while service startsDhruvaraj Subhashchandran2017-09-072-2/+92
| | | | | | | Resolves openbmc/openbmc#1631 Change-Id: I1639c84cbb180dfe7f6494b5e80ca45514a3e730 Signed-off-by: Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com>
* Fix for mapper errors during logging service restartDhruvaraj Subhashchandran2017-07-261-36/+19
| | | | | | | | | | | There was a race condition while calling mapper from led monitoring after error logs started persisting, to avoid such errors the callout information is now extracted from the message received as part of interface added signal. Resolves openbmc/openbmc#1853 Change-Id: Ie913992bdcb3b1cb93677d64331db34202f8ae72 Signed-off-by: Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com>
* use new sdbusplus match constructorsPatrick Williams2017-06-012-54/+39
| | | | | Change-Id: Id833073b9e45fae24d6bd0e7f9310ef0ba8658de Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
* Implement led assert and deassert based on faultsDhruvaraj Subhashchandran2017-05-232-2/+221
| | | | | Change-Id: I28378b155da15282b1b5bf0403075b55bda5b70d Signed-off-by: Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com>
* Add class and stub for fru fault monitor applicationDhruvaraj Subhashchandran2017-05-234-0/+215
This application waits for new fault entries and resolution of exiting faults to assert or deassert LED for the corresponding FRUs, respectively. Change-Id: I92ead0c8d3132dd7a6740b536231d6588ac42471 Signed-off-by: Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com>
OpenPOWER on IntegriCloud