From 3d2b0d62ed1567ffba53ffb44d0a8617869ea08c Mon Sep 17 00:00:00 2001 From: Matt Spinler Date: Thu, 29 Mar 2018 08:48:37 -0500 Subject: Move down error entry trace 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 --- fault-monitor/fru-fault-monitor.cpp | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) (limited to 'fault-monitor') diff --git a/fault-monitor/fru-fault-monitor.cpp b/fault-monitor/fru-fault-monitor.cpp index cb6c4e4..4a600f7 100644 --- a/fault-monitor/fru-fault-monitor.cpp +++ b/fault-monitor/fru-fault-monitor.cpp @@ -147,14 +147,17 @@ void Add::created(sdbusplus::message::message& msg) //Not a new error entry skip return; } - log(objectPath.c_str()); - auto iter = logEntry.second.find("org.openbmc.Associations"); if (iter == logEntry.second.end()) { return; } + //Nothing else shows when a specific error log + //has been created. Do it here. + std::string message{objectPath + " created"}; + log(message.c_str()); + auto attr = iter->second.find("associations"); if (attr == iter->second.end()) { -- cgit v1.2.1