search

openbmc / phosphor-net-ipmid

Network IPMI server
Apache License 2.0
9 stars 11 forks source link

Zaius: phosphor-ipmi-net.service: Main process exited, code=killed, status=11/SEGV #2

Open gkeishin opened 5 years ago

gkeishin commented 5 years ago 
#(CDT) 2019/03/13 01:26:32.826300 - 1.007735 - Issuing: Run External IPMI Standard Command power reset -N 10 -R 1
#(CDT) 2019/03/13 01:26:32.835538 - 0.009238 - Issuing: ipmitool -I lanplus -C 3 -U root -P ******** -H zaiusxxxx -vvv power reset -N 10 -R 1
version_id: 2.7.0-dev-70-g1bbfcfa

Error from journald log

Mar 13 06:26:36 zaius netipmid[2067]: Transition request initiated successfully
Mar 13 06:26:36 zaius systemd[1]: phosphor-ipmi-net.service: Main process exited, code=killed, status=11/SEGV
Mar 13 06:26:36 zaius systemd[1]: phosphor-ipmi-net.service: Failed with result 'signal'.
Mar 13 06:26:38 zaius systemd[1]: phosphor-ipmi-net.service: Service RestartSec=1s expired, scheduling restart.
Mar 13 06:26:38 zaius systemd[1]: phosphor-ipmi-net.service: Scheduled restart job, restart counter is at 1.
Mar 13 06:26:43 zaius netipmid[2120]: Executing the IPMI message failed

netipmid restarted

 2120     1 root     S    11120   1%   0% netipmid
 1167     1 root     S    11056   1%   0% ipmid
{
    "__CURSOR" : "s=27411a03ab184d5b8d663cb5c7d97ee8;i=fb1;b=57b22e04e96a46daaa8aeb73616c2580;m=3dc4afc6;t=583f3e33a83e0;x=6ee4fd69c55198b1",
    "__REALTIME_TIMESTAMP" : "1552458396107744",
    "__MONOTONIC_TIMESTAMP" : "1036300230",
    "_BOOT_ID" : "57b22e04e96a46daaa8aeb73616c2580",
    "PRIORITY" : "6",
    "_MACHINE_ID" : "539937e36e514cdfa3de9703c5b6fc8f",
    "_HOSTNAME" : "zaius",
    "_UID" : "0",
    "_GID" : "0",
    "_SYSTEMD_SLICE" : "system.slice",
    "_TRANSPORT" : "journal",
    "_CAP_EFFECTIVE" : "3fffffffff",
    "CODE_LINE" : "105",
    "CODE_FUNC" : "helper_log",
    "CODE_FILE" : "/home/bmcbuild/releases/obmc909/Builds/ob909.1911.20190312a/1bbfcfa78b2ef9e396c38a1b6006eec8fabdf644/build/tmp/work/armv6-openbmc-linux-gnueabi/phosphor-ipmi-host/1.0+gitAUTOINC+1bb0c7fc55-r1/recipe-sysroot/usr/include/phosphor-logging/log.hpp",
    "MESSAGE" : "Transition request initiated successfully",
    "TRANSACTION_ID" : "40138903",
    "SYSLOG_IDENTIFIER" : "netipmid",
    "_PID" : "2067",
    "_COMM" : "netipmid",
    "_EXE" : "/usr/sbin/netipmid",
    "_CMDLINE" : "netipmid",
    "_SYSTEMD_CGROUP" : "/system.slice/phosphor-ipmi-net.service",
    "_SYSTEMD_UNIT" : "phosphor-ipmi-net.service",
    "_SYSTEMD_INVOCATION_ID" : "8c03820bce09451fa4f2330cb7d39bc6",
    "_SOURCE_REALTIME_TIMESTAMP" : "1552458396104943"
}
gkeishin commented 5 years ago

@vmauery Take a look.. Thanks

gkeishin commented 5 years ago

@wak-google we were expecting to work out band but it looks like its in-band only supported on Zaius ?

wak-google commented 5 years ago

We don't use netipmid and it's not in the default zaius build so I have no idea. I thought netipmid was going away in favor of a unified ipmid.

vmauery commented 5 years ago

netipmid is no longer a stand-alone execution queue. Now it is just a bridge that forwards commands onto ipmid for execution. But that is still waiting for the WS issue to be resolved so the autobump can pull this into the mainstream. Does this issue still exist if netipmid/ipmid are pinned to their respective HEADs?