Fan control service issues - service will not start "Uncaught DBus service lookup failure exception"
Stephen Boylan
sboylan at ircona.com
Thu Apr 25 02:24:56 AEST 2019
Hello all,
I've run into an issue with my fan control. I have a simple two fan system which is failing to start phosphor-fan-control at .service<mailto:phosphor-fan-control at .service>
This is the status
root at evb-ast2500:/lib/systemd/system# systemctl status phosphor-fan-control at 0.service --no-page
? phosphor-fan-control at 0.service - Phosphor Fan Control Daemon
Loaded: loaded (/lib/systemd/system/phosphor-fan-control at .service; static; vendor preset: enabled)
Active: failed (Result: exit-code) since Wed 2019-04-24 16:22:36 UTC; 16s ago
Process: 1218 ExecStart=/usr/bin/env phosphor-fan-control --control (code=exited, status=1/FAILURE)
Main PID: 1218 (code=exited, status=1/FAILURE)
Apr 24 16:22:36 evb-ast2500 systemd[1]: phosphor-fan-control at 0.service: Service RestartSec=1s expired, scheduling restart.
Apr 24 16:22:36 evb-ast2500 systemd[1]: phosphor-fan-control at 0.service: Scheduled restart job, restart counter is at 2.
Apr 24 16:22:36 evb-ast2500 systemd[1]: Stopped Phosphor Fan Control Daemon.
Apr 24 16:22:36 evb-ast2500 systemd[1]: phosphor-fan-control at 0.service: Start request repeated too quickly.
Apr 24 16:22:36 evb-ast2500 systemd[1]: phosphor-fan-control at 0.service: Failed with result 'exit-code'.
Apr 24 16:22:36 evb-ast2500 systemd[1]: Failed to start Phosphor Fan Control Daemon.
And I noticed this in the journalctl
{
"__CURSOR" : "s=efc0b033c5f243798b56446bcaffc0f5;i=23d;b=2de3ccbcea7940f5b51652e55e900cd2;m=2f22198c;t=5874871dec1c2;x=f1ba902c2ec1feae",
"__REALTIME_TIMESTAMP" : "1556120101372354",
"__MONOTONIC_TIMESTAMP" : "790763916",
"_BOOT_ID" : "2de3ccbcea7940f5b51652e55e900cd2",
"_UID" : "0",
"_GID" : "0",
"_MACHINE_ID" : "4c5bf4049b5e4751b70a17eaeeb55a49",
"_HOSTNAME" : "evb-ast2500",
"_TRANSPORT" : "journal",
"_CAP_EFFECTIVE" : "3fffffffff",
"CODE_FILE" : "/home/ircadmin/OpenBMC/openbmc/build/tmp/work/armv6-openbmc-linux-gnueabi/phosphor-fan/1.0+gitAUTOINC+4b258ac8b6-r1/recipe-sysroot/usr
/include/phosphor-logging/log.hpp",
"CODE_LINE" : "105",
"CODE_FUNC" : "helper_log",
"PRIORITY" : "3",
"MESSAGE" : "Uncaught DBus service lookup failure exception",
"TRANSACTION_ID" : "114915536",
"PATH" : "/xyz/openbmc_project/sensors/fan_tach/fan0",
"INTERFACE" : "xyz.openbmc_project.Control.FanPwm",
"SYSLOG_IDENTIFIER" : "phosphor-fan-control",
"_PID" : "1273",
"_COMM" : "phosphor-fan-co",
"_EXE" : "/usr/sbin/phosphor-fan-control",
"_CMDLINE" : "phosphor-fan-control --control",
"_SYSTEMD_CGROUP" : "/system.slice/system-phosphor\\x2dfan\\x2dcontrol.slice/phosphor-fan-control at 0.service",
"_SYSTEMD_UNIT" : "phosphor-fan-control at 0.service",
"_SYSTEMD_SLICE" : "system-phosphor\\x2dfan\\x2dcontrol.slice",
"_SYSTEMD_INVOCATION_ID" : "21572a9f879c44cab2b9b6b4c5e9a504",
"_SOURCE_REALTIME_TIMESTAMP" : "1556120101372269"
}
I know the PATH exists, though I'm not entirely sure about the INTERFACE. I've checked systemctl to see if I can find it and I don't see it. Should I be checking elsewhere for it?
I can see my fan_tach sensors and my chassis entries as such
/xyz/openbmc_project/sensors/fan_tach/enumerate
{
"data": {
"/xyz/openbmc_project/sensors/fan_tach/fan0": {
"CriticalAlarmHigh": false,
"CriticalAlarmLow": false,
"CriticalHigh": 5500,
"CriticalLow": 1000,
"MaxValue": 0,
"MinValue": 0,
"Scale": 0,
"Unit": "xyz.openbmc_project.Sensor.Value.Unit.RPMS",
"Value": 4292,
"WarningAlarmHigh": false,
"WarningAlarmLow": false,
"WarningHigh": 5000,
"WarningLow": 1500
},
"/xyz/openbmc_project/sensors/fan_tach/fan1": {
"CriticalAlarmHigh": false,
"CriticalAlarmLow": false,
"CriticalHigh": 5500,
"CriticalLow": 1000,
"MaxValue": 0,
"MinValue": 0,
"Scale": 0,
"Target": 255,
"Unit": "xyz.openbmc_project.Sensor.Value.Unit.RPMS",
"Value": 3551,
"WarningAlarmHigh": false,
"WarningAlarmLow": false,
"WarningHigh": 5000,
"WarningLow": 1500
}
},
"message": "200 OK",
"status": "ok"
}
/xyz/openbmc_project/inventory/system/chassis/motherboard/enumerate
{
"data": {
"/xyz/openbmc_project/inventory/system/chassis/motherboard/fan0": {
"Functional": true,
"Present": true,
"PrettyName": "fan0"
},
"/xyz/openbmc_project/inventory/system/chassis/motherboard/fan0/fan0": {
"Functional": true
},
"/xyz/openbmc_project/inventory/system/chassis/motherboard/fan1": {
"Functional": true,
"Present": true,
"PrettyName": "fan1"
},
"/xyz/openbmc_project/inventory/system/chassis/motherboard/fan1/fan1": {
"Functional": true
}
},
"message": "200 OK",
"status": "ok"
}
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20190424/7c58858c/attachment-0001.htm>
More information about the openbmc
mailing list