<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.1f1ea193f6735cf0wmi-callto
{mso-style-name:1f1ea193f6735cf0wmi-callto;}
span.f55bbb4eeef208e8wmi-sign
{mso-style-name:f55bbb4eeef208e8wmi-sign;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal" style="margin-bottom:12.0pt">Classification: <b><span style="color:#08298A">HCL Internal</span></b><o:p></o:p></p>
<p class="MsoNormal">Hello All,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I pulled the latest commit and tested the image in my target and able to access the target through SSH.<o:p></o:p></p>
<p class="MsoNormal">Also systemctl and reboot command works.<span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">
<br>
<br>
<o:p></o:p></span></p>
<p class="MsoNormal">Commit - <a href="https://github.com/openbmc/openbmc/commit/c3d88e4d9fcc08e1aae7cc9d0337c0261e996c64">
https://github.com/openbmc/openbmc/commit/c3d88e4d9fcc08e1aae7cc9d0337c0261e996c64</a><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal">Regards,<o:p></o:p></p>
<p class="MsoNormal">Jayashree<span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p></o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><a name="_____replyseparator"></a><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Konstantin Klubnichkin <kitsok@yandex-team.ru>
<br>
<b>Sent:</b> Monday, October 5, 2020 4:38 PM<br>
<b>To:</b> Jayashree D <jayashree-d@hcl.com>; openbmc@lists.ozlabs.org<br>
<b>Cc:</b> Vijay Khemka <vijaykhemka@fb.com>; geissonator@yahoo.com; joel@jms.id.au; Patrick Williams <patrick@stwcx.xyz>; George Keishing <gkeishin@in.ibm.com><br>
<b>Subject:</b> Re: Connection issue in OpenBMC image<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;line-height:12.0pt;background:#FFEB9C">
<span style="font-size:10.0pt;color:red">[CAUTION: This Email is from outside the Organization. Unless you trust the sender, Don’t click links or open attachments as it may be a Phishing email, which can steal your Information and compromise your Computer.]</span><o:p></o:p></p>
<div>
<div>
<p class="MsoNormal">Hello all!<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Looks like I'm struggling with the same issue, here is how it looks:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">After normal reboot BMC replies to pings, connection to port 22 (SSH) is opened but ssh handshake is not passing.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Moreover BMC debug console does not respond to input.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">I'm able to reset SoC by external system, usually it helps and after reboot BMC behaves normally, but sometimes this hang happens again.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">To investigate this I've detached dropbear from systemd socket, now it's more or less independent from systemd and starts right after network.service, so I can log in to BMC.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">So I've catched this stall and found that dbus-broker process consumes a lot of CPU, systemctl does not work (just no output), reboot process just stays in a process list. To at least be able to reboot BMC I've killed dbus-broker, then
it was restarted and BMC rebooted.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">I think all this points to a deadlock in dbus. As it doesn't happen each time, I think there is a race condition somewhere.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">I have no idea yet how to find what causes dbus-broker stall, but will try to dig into it.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Thank you!<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">05.10.2020, 11:30, "Jayashree D" <<a href="mailto:jayashree-d@hcl.com">jayashree-d@hcl.com</a>>:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p>Classification: HCL Internal<br>
<br>
Regarding SSH connection, an issue has been created in openbmc and I also see others having this same issue.<br>
From the comments, I have run "dropbear -E -p 5022" in the target (UART-console) and tried to connect the target using "ssh -p 5022 <ip>" and ssh connection established.<br>
But, reboot and systemctl commands hangs.<br>
<br>
Issue - <a href="https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fopenbmc%2Fopenbmc%2Fissues%2F3701&data=02%7C01%7Cjayashree-d%40hcl.com%7C8306510c906e43a333d108d8691ee925%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C637374928788166348&sdata=sYnNyjgdISA5l2ECtUeT3wC%2FYeIlmn%2BH1TX8IEHXsSs%3D&reserved=0">
https://github.com/openbmc/openbmc/issues/3701</a><br>
<br>
<a href="mailto:root@tiogapass">root@tiogapass</a>:~# dropbear -E -p 5022<br>
[348] Jan 01 00:06:48 Failed loading /etc/dropbear/dropbear_dss_host_key<br>
[348] Jan 01 00:06:48 Failed loading /etc/dropbear/dropbear_ecdsa_host_key<br>
[348] Jan 01 00:06:48 Failed loading /etc/dropbear/dropbear_ed25519_host_key<br>
[349] Jan 01 00:06:48 Running in background<br>
<br>
[<a href="mailto:root@odc">root@odc</a> ~]# ssh -p 5022 <a href="mailto:root@10.0.128.108">
root@10.0.128.108</a> <a href="mailto:root@10.0.128.108">root@10.0.128.108</a>'s password:<br>
<a href="mailto:root@tiogapass">root@tiogapass</a>:~#<br>
<br>
Hi George,<br>
<br>
We are facing connection issue in accessing the target after flashing the latest image.<br>
In openbmc-test-automation, whether any test cases are present in CI to identify these issues ?<br>
Please let us know your comments on this.<br>
<br>
Regards,<br>
Jayashree<br>
<br>
-----Original Message-----<br>
From: Jayashree D<br>
Sent: Friday, September 25, 2020 10:29 AM<br>
To: <a href="mailto:openbmc@lists.ozlabs.org">openbmc@lists.ozlabs.org</a><br>
Cc: Konstantin Klubnichkin <<a href="mailto:kitsok@yandex-team.ru">kitsok@yandex-team.ru</a>>; Vijay Khemka <<a href="mailto:vijaykhemka@fb.com">vijaykhemka@fb.com</a>>;
<a href="mailto:geissonator@yahoo.com">geissonator@yahoo.com</a>; <a href="mailto:joel@jms.id.au">
joel@jms.id.au</a>; Patrick Williams <<a href="mailto:patrick@stwcx.xyz">patrick@stwcx.xyz</a>><br>
Subject: RE: Connection issue in OpenBMC image<br>
<br>
Classification: HCL Internal<br>
<br>
Hi Team,<br>
<br>
In the latest openbmc build, after image upgradation in the target, not able to connect the target through SSH but able to ping the IP Address.<br>
<br>
After analysing the latest commits, reverted the below commit in the latest build and checked by flashing the image. Now the target is connecting through SSH. Please help us on fixing this issue.<br>
<br>
Commit Link - <a href="https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fopenbmc%2Fopenbmc%2Fcommit%2F635e0e4637e40ba03f69204265427550fd404f4c&data=02%7C01%7Cjayashree-d%40hcl.com%7C8306510c906e43a333d108d8691ee925%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C637374928788176343&sdata=tpzZyvAsIDQfnIpEFSK%2F0VCA84dLUhZgV4tpxbLX174%3D&reserved=0">
https://github.com/openbmc/openbmc/commit/635e0e4637e40ba03f69204265427550fd404f4c</a><br>
<br>
<br>
Observation on UART-console after flashing latest image without any changes:<br>
<br>
1. reboot command is not working.<br>
2. systemctl status <service_name> is not providing any status. ( Failed to get properties: Connection timed out) 3. I tried "ssh -vvv <ip>" and logs are attached for working and non-working image.<br>
4. From controller, I tried to upgrade image using redfish and image is being copied and following logs shown.<br>
<a href="mailto:root@tiogapass">root@tiogapass</a>:~# journalctl | grep image Jan 01 00:00:37 tiogapass phosphor-image-updater[246]: Error in mapper GetSubTreePath Jan 01 10:43:59 tiogapass phosphor-image-updater[246]: BMC image activating - BMC reboots are
disabled.<br>
<br>
5. Using Rest API command,<br>
<br>
[<a href="mailto:root@odc">root@odc</a> ]# curl -k -H "X-Auth-Token: $token" -H "Content-Type: application/json" -X PUT -d '{"data":"xyz.openbmc_project.Software.Activation.RequestedActivations.Active"}'
<a href="https://$%7bbmc%7d/xyz/openbmc_project/software/a77348be/attr/RequestedActivation">
https://${bmc}/xyz/openbmc_project/software/a77348be/attr/RequestedActivation</a><br>
{<br>
"data": {<br>
"description": "org.freedesktop.DBus.Error.NoReply"<br>
},<br>
"message": "Method call timed out",<br>
"status": "error"<br>
}<br>
<br>
<br>
Regards,<br>
Jayashree<br>
<br>
-----Original Message-----<br>
From: Jayashree D<br>
Sent: Friday, September 18, 2020 3:18 PM<br>
To: Patrick Williams <<a href="mailto:patrick@stwcx.xyz">patrick@stwcx.xyz</a>>; <a href="mailto:openbmc@lists.ozlabs.org">
openbmc@lists.ozlabs.org</a><br>
Cc: Konstantin Klubnichkin <<a href="mailto:kitsok@yandex-team.ru">kitsok@yandex-team.ru</a>><br>
Subject: RE: Connection issue in OpenBMC image<br>
<br>
Classification: HCL Internal<br>
<br>
Hello Patrick,<br>
<br>
I saw the post about dropbear, but that commit was updated on July16 and my target is connecting till August last week image. I don't think that will be an issue. Also on working image, I tried with 'ssh -vvv ' and I got below information.<br>
<br>
OpenSSH_7.4p1, OpenSSL 1.0.2k-fips 26 Jan 2017<br>
debug1: Reading configuration data /etc/ssh/ssh_config<br>
debug1: /etc/ssh/ssh_config line 58: Applying options for *<br>
debug2: resolving "10.0.128.108" port 22<br>
debug2: ssh_connect_direct: needpriv 0<br>
debug1: Connecting to 10.0.128.108 [10.0.128.108] port 22.<br>
debug1: Connection established.<br>
debug1: permanently_set_uid: 0/0<br>
debug1: key_load_public: No such file or directory<br>
debug1: identity file /root/.ssh/id_rsa type -1<br>
debug1: key_load_public: No such file or directory<br>
debug1: identity file /root/.ssh/id_rsa-cert type -1<br>
debug1: key_load_public: No such file or directory<br>
debug1: identity file /root/.ssh/id_dsa type -1<br>
debug1: key_load_public: No such file or directory<br>
debug1: identity file /root/.ssh/id_dsa-cert type -1<br>
debug1: key_load_public: No such file or directory<br>
debug1: identity file /root/.ssh/id_ecdsa type -1<br>
debug1: key_load_public: No such file or directory<br>
debug1: identity file /root/.ssh/id_ecdsa-cert type -1<br>
debug1: key_load_public: No such file or directory<br>
debug1: identity file /root/.ssh/id_ed25519 type -1<br>
debug1: key_load_public: No such file or directory<br>
debug1: identity file /root/.ssh/id_ed25519-cert type -1<br>
debug1: Enabling compatibility mode for protocol 2.0<br>
debug1: Local version string SSH-2.0-OpenSSH_7.4<br>
debug1: Remote protocol version 2.0, remote software version dropbear_2020.80<br>
debug1: no match: dropbear_2020.80<br>
debug2: fd 3 setting O_NONBLOCK<br>
debug1: Authenticating to 10.0.128.108:22 as 'root'<br>
debug3: hostkeys_foreach: reading file "/root/.ssh/known_hosts"<br>
debug3: record_hostkey: found key type RSA in file /root/.ssh/known_hosts:68<br>
debug3: load_hostkeys: loaded 1 keys from 10.0.128.108<br>
debug3: order_hostkeyalgs: prefer hostkeyalgs: <a href="mailto:ssh-rsa-cert-v01@openssh.com">
ssh-rsa-cert-v01@openssh.com</a>,rsa-sha2-512,rsa-sha2-256,ssh-rsa<br>
debug3: send packet: type 20<br>
debug1: SSH2_MSG_KEXINIT sent<br>
debug3: receive packet: type 20<br>
debug1: SSH2_MSG_KEXINIT received<br>
debug2: local client KEXINIT proposal<br>
debug2: KEX algorithms: <a href="mailto:curve25519-sha256,curve25519-sha256@libssh.org">
curve25519-sha256,curve25519-sha256@libssh.org</a>,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha256,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1,ext-info-c<br>
debug2: host key algorithms: <a href="mailto:ssh-rsa-cert-v01@openssh.com">ssh-rsa-cert-v01@openssh.com</a>,rsa-sha2-512,rsa-sha2-256,ssh-rsa,<a href="mailto:ecdsa-sha2-nistp256-cert-v01@openssh.com">ecdsa-sha2-nistp256-cert-v01@openssh.com</a>,<a href="mailto:ecdsa-sha2-nistp384-cert-v01@openssh.com">ecdsa-sha2-nistp384-cert-v01@openssh.com</a>,<a href="mailto:ecdsa-sha2-nistp521-cert-v01@openssh.com">ecdsa-sha2-nistp521-cert-v01@openssh.com</a>,<a href="mailto:ssh-ed25519-cert-v01@openssh.com">ssh-ed25519-cert-v01@openssh.com</a>,<a href="mailto:ssh-dss-cert-v01@openssh.com">ssh-dss-cert-v01@openssh.com</a>,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519,ssh-dss<br>
debug2: ciphers ctos: <a href="mailto:chacha20-poly1305@openssh.com">chacha20-poly1305@openssh.com</a>,aes128-ctr,aes192-ctr,aes256-ctr,<a href="mailto:aes128-gcm@openssh.com">aes128-gcm@openssh.com</a>,<a href="mailto:aes256-gcm@openssh.com">aes256-gcm@openssh.com</a>,aes128-cbc,aes192-cbc,aes256-cbc<br>
debug2: ciphers stoc: <a href="mailto:chacha20-poly1305@openssh.com">chacha20-poly1305@openssh.com</a>,aes128-ctr,aes192-ctr,aes256-ctr,<a href="mailto:aes128-gcm@openssh.com">aes128-gcm@openssh.com</a>,<a href="mailto:aes256-gcm@openssh.com">aes256-gcm@openssh.com</a>,aes128-cbc,aes192-cbc,aes256-cbc<br>
debug2: MACs ctos: <a href="mailto:umac-64-etm@openssh.com">umac-64-etm@openssh.com</a>,<a href="mailto:umac-128-etm@openssh.com">umac-128-etm@openssh.com</a>,<a href="mailto:hmac-sha2-256-etm@openssh.com">hmac-sha2-256-etm@openssh.com</a>,<a href="mailto:hmac-sha2-512-etm@openssh.com">hmac-sha2-512-etm@openssh.com</a>,<a href="mailto:hmac-sha1-etm@openssh.com">hmac-sha1-etm@openssh.com</a>,<a href="mailto:umac-64@openssh.com">umac-64@openssh.com</a>,<a href="mailto:umac-128@openssh.com">umac-128@openssh.com</a>,hmac-sha2-256,hmac-sha2-512,hmac-sha1<br>
debug2: MACs stoc: <a href="mailto:umac-64-etm@openssh.com">umac-64-etm@openssh.com</a>,<a href="mailto:umac-128-etm@openssh.com">umac-128-etm@openssh.com</a>,<a href="mailto:hmac-sha2-256-etm@openssh.com">hmac-sha2-256-etm@openssh.com</a>,<a href="mailto:hmac-sha2-512-etm@openssh.com">hmac-sha2-512-etm@openssh.com</a>,<a href="mailto:hmac-sha1-etm@openssh.com">hmac-sha1-etm@openssh.com</a>,<a href="mailto:umac-64@openssh.com">umac-64@openssh.com</a>,<a href="mailto:umac-128@openssh.com">umac-128@openssh.com</a>,hmac-sha2-256,hmac-sha2-512,hmac-sha1<br>
debug2: compression ctos: <a href="mailto:none,zlib@openssh.com">none,zlib@openssh.com</a>,zlib<br>
debug2: compression stoc: <a href="mailto:none,zlib@openssh.com">none,zlib@openssh.com</a>,zlib<br>
debug2: languages ctos:<br>
debug2: languages stoc:<br>
debug2: first_kex_follows 0<br>
debug2: reserved 0<br>
debug2: peer server KEXINIT proposal<br>
debug2: KEX algorithms: <a href="mailto:curve25519-sha256,curve25519-sha256@libssh.org">
curve25519-sha256,curve25519-sha256@libssh.org</a>,ecdh-sha2-nistp521,ecdh-sha2-nistp384,ecdh-sha2-nistp256,diffie-hellman-group14-sha256,<a href="mailto:kexguess2@matt.ucc.asn.au">kexguess2@matt.ucc.asn.au</a><br>
debug2: host key algorithms: rsa-sha2-256,ssh-rsa<br>
debug2: ciphers ctos: <a href="mailto:chacha20-poly1305@openssh.com">chacha20-poly1305@openssh.com</a>,aes128-ctr,aes256-ctr<br>
debug2: ciphers stoc: <a href="mailto:chacha20-poly1305@openssh.com">chacha20-poly1305@openssh.com</a>,aes128-ctr,aes256-ctr<br>
debug2: MACs ctos: hmac-sha1,hmac-sha2-256<br>
debug2: MACs stoc: hmac-sha1,hmac-sha2-256<br>
debug2: compression ctos: <a href="mailto:zlib@openssh.com">zlib@openssh.com</a>,none<br>
debug2: compression stoc: <a href="mailto:zlib@openssh.com">zlib@openssh.com</a>,none<br>
debug2: languages ctos:<br>
debug2: languages stoc:<br>
debug2: first_kex_follows 0<br>
debug2: reserved 0<br>
debug1: kex: algorithm: curve25519-sha256<br>
debug1: kex: host key algorithm: rsa-sha2-256<br>
debug1: kex: server->client cipher: <a href="mailto:chacha20-poly1305@openssh.com">
chacha20-poly1305@openssh.com</a> MAC: <implicit> compression: none<br>
debug1: kex: client->server cipher: <a href="mailto:chacha20-poly1305@openssh.com">
chacha20-poly1305@openssh.com</a> MAC: <implicit> compression: none<br>
debug1: kex: curve25519-sha256 need=64 dh_need=64<br>
debug1: kex: curve25519-sha256 need=64 dh_need=64<br>
debug3: send packet: type 30<br>
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY<br>
debug3: receive packet: type 31<br>
debug1: Server host key: ssh-rsa SHA256:3WwhPmIIxzrw0+cm/0vN3hifY4kh9sJhClVNw6zrJ7Y<br>
debug3: hostkeys_foreach: reading file "/root/.ssh/known_hosts"<br>
debug3: record_hostkey: found key type RSA in file /root/.ssh/known_hosts:68<br>
debug3: load_hostkeys: loaded 1 keys from 10.0.128.108<br>
debug1: Host '10.0.128.108' is known and matches the RSA host key.<br>
debug1: Found key in /root/.ssh/known_hosts:68<br>
debug3: send packet: type 21<br>
debug2: set_newkeys: mode 1<br>
debug1: rekey after <span class="1f1ea193f6735cf0wmi-callto">134217728</span> blocks<br>
debug1: SSH2_MSG_NEWKEYS sent<br>
debug1: expecting SSH2_MSG_NEWKEYS<br>
debug3: receive packet: type 21<br>
debug1: SSH2_MSG_NEWKEYS received<br>
debug2: set_newkeys: mode 0<br>
debug1: rekey after <span class="1f1ea193f6735cf0wmi-callto">134217728</span> blocks<br>
debug2: key: /root/.ssh/id_rsa (0x558ea3ad3640), agent<br>
debug2: key: /root/.ssh/id_rsa ((nil))<br>
debug2: key: /root/.ssh/id_dsa ((nil))<br>
debug2: key: /root/.ssh/id_ecdsa ((nil))<br>
debug2: key: /root/.ssh/id_ed25519 ((nil))<br>
debug3: send packet: type 5<br>
debug3: receive packet: type 7<br>
debug1: SSH2_MSG_EXT_INFO received<br>
debug1: kex_input_ext_info: server-sig-algs=<ssh-ed25519,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,rsa-sha2-256,ssh-rsa,ssh-dss><br>
debug3: receive packet: type 6<br>
debug2: service_accept: ssh-userauth<br>
debug1: SSH2_MSG_SERVICE_ACCEPT received<br>
debug3: send packet: type 50<br>
debug3: receive packet: type 51<br>
debug1: Authentications that can continue: publickey,password<br>
debug3: start over, passed a different list publickey,password<br>
debug3: preferred gssapi-keyex,gssapi-with-mic,publickey,keyboard-interactive,password<br>
debug3: authmethod_lookup publickey<br>
debug3: remaining preferred: keyboard-interactive,password<br>
debug3: authmethod_is_enabled publickey<br>
debug1: Next authentication method: publickey<br>
debug1: Offering RSA public key: /root/.ssh/id_rsa<br>
debug3: send_pubkey_test<br>
debug3: send packet: type 50<br>
debug2: we sent a publickey packet, wait for reply<br>
debug3: receive packet: type 51<br>
debug1: Authentications that can continue: publickey,password<br>
debug1: Trying private key: /root/.ssh/id_rsa<br>
debug3: sign_and_send_pubkey: RSA SHA256:YfteufmWUV8W7EQEycZ+38skgUWGDTYFHw93a7SwwLM<br>
debug3: send packet: type 50<br>
debug2: we sent a publickey packet, wait for reply<br>
debug3: receive packet: type 51<br>
debug1: Authentications that can continue: publickey,password<br>
debug1: Trying private key: /root/.ssh/id_dsa<br>
debug3: no such identity: /root/.ssh/id_dsa: No such file or directory<br>
debug1: Trying private key: /root/.ssh/id_ecdsa<br>
debug3: no such identity: /root/.ssh/id_ecdsa: No such file or directory<br>
debug1: Trying private key: /root/.ssh/id_ed25519<br>
debug3: no such identity: /root/.ssh/id_ed25519: No such file or directory<br>
debug2: we did not send a packet, disable method<br>
debug3: authmethod_lookup password<br>
debug3: remaining preferred: ,password<br>
debug3: authmethod_is_enabled password<br>
debug1: Next authentication method: password<br>
<br>
<br>
In non-working image, the logs are stopped after below lines and it is not providing any errors.<br>
<br>
debug1: Enabling compatibility mode for protocol 2.0<br>
debug1: Local version string SSH-2.0-OpenSSH_7.4<br>
<br>
Also one more observation in UART-Console, after flashing latest image.<br>
<br>
1. reboot command is not working.<br>
2. systemctl status <service_name> is not providing any status. ( Failed to get properties: Connection timed out) 3. I can able to ping the ip address but scp is not working.<br>
<br>
Thanks,<br>
Jayashree<br>
<br>
<br>
-----Original Message-----<br>
From: Patrick Williams <<a href="mailto:patrick@stwcx.xyz">patrick@stwcx.xyz</a>><br>
Sent: Thursday, September 17, 2020 9:16 PM<br>
To: Jayashree D <<a href="mailto:jayashree-d@hcl.com">jayashree-d@hcl.com</a>><br>
Cc: Konstantin Klubnichkin <<a href="mailto:kitsok@yandex-team.ru">kitsok@yandex-team.ru</a>>;
<a href="mailto:openbmc@lists.ozlabs.org">openbmc@lists.ozlabs.org</a><br>
Subject: Re: Connection issue in OpenBMC image<br>
<br>
Hello Jayashree,<br>
<br>
I saw an output `ssh -v` from you earlier, but there really wasn't any useful information there. It looked like the connection was being made and keys were exchanged and then the log just stopped abruptly. This tells me it likely isn't a networking issue but
an issue in the handshake between the ssh-client (your computer) and ssh-server (dropbear). You can continue to add '-v' parameters up to `ssh -vvv` and you'll get increasingly more information.<br>
<br>
Joseph Reynolds recently posted a reminder about dropbear disabling weak ciphers[1]. Is it possible that your client is using an old cipher?<br>
<br>
On Wed, Sep 16, 2020 at 11:35:28AM +0000, Jayashree D wrote:<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"> <a href="mailto:root@tiogapass">root@tiogapass</a>:~# journalctl | grep drop<o:p></o:p></p>
</blockquote>
<p>...<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"> Jan 01 00:15:28 tiogapass systemd[1]: <a href="mailto:dropbear@0-10.0.128.108">
dropbear@0-10.0.128.108</a>:22-10.0.0.1:51810.service: Succeeded.<br>
Jan 01 00:15:44 tiogapass dropbear[2753]: Child connection from<br>
::ffff:10.0.0.1:51944 Jan 01 00:15:50 tiogapass dropbear[2753]: PAM<br>
password auth succeeded for 'root' from ::ffff:10.0.0.1:51944<o:p></o:p></p>
</blockquote>
<p style="margin-bottom:12.0pt"><br>
This looks like a valid connection was established.<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"> 15.09.2020, 16:12, "Jayashree D" <<a href="mailto:jayashree-d@hcl.com">jayashree-d@hcl.com</a><<a href="mailto:jayashree-d@hcl.com">mailto:jayashree-d@hcl.com</a>>>:<br>
<br>
OpenSSH_7.4p1, OpenSSL 1.0.2k-fips 26 Jan 2017<br>
debug1: Reading configuration data /etc/ssh/ssh_config<br>
debug1: /etc/ssh/ssh_config line 58: Applying options for *<br>
debug1: Connecting to 10.0.128.108 [10.0.128.108] port 22.<br>
debug1: Connection established.<br>
debug1: permanently_set_uid: 0/0<br>
debug1: key_load_public: No such file or directory<br>
debug1: identity file /root/.ssh/id_rsa type -1<br>
debug1: key_load_public: No such file or directory<br>
debug1: identity file /root/.ssh/id_rsa-cert type -1<br>
debug1: key_load_public: No such file or directory<br>
debug1: identity file /root/.ssh/id_dsa type -1<br>
debug1: key_load_public: No such file or directory<br>
debug1: identity file /root/.ssh/id_dsa-cert type -1<br>
debug1: key_load_public: No such file or directory<br>
debug1: identity file /root/.ssh/id_ecdsa type -1<br>
debug1: key_load_public: No such file or directory<br>
debug1: identity file /root/.ssh/id_ecdsa-cert type -1<br>
debug1: key_load_public: No such file or directory<br>
debug1: identity file /root/.ssh/id_ed25519 type -1<br>
debug1: key_load_public: No such file or directory<br>
debug1: identity file /root/.ssh/id_ed25519-cert type -1<br>
debug1: Enabling compatibility mode for protocol 2.0<br>
debug1: Local version string SSH-2.0-OpenSSH_7.4<o:p></o:p></p>
</blockquote>
<p style="margin-bottom:12.0pt"><br>
This is the log that also looks like a good connection. Identity files were attempted to be exchanged. Version strings were exchanged. And then the log just abruptly stops. Was the connection dropped? Is it hung?<br>
<br>
1. <a href="https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.ozlabs.org%2Fpipermail%2Fopenbmc%2F2020-September%2F023071.html&data=02%7C01%7Cjayashree-d%40hcl.com%7C8306510c906e43a333d108d8691ee925%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C637374928788176343&sdata=DBgtZcOuCLN8VHCE%2BYrh1eS8oaUGu2V4fj1ystV4qEw%3D&reserved=0">
https://lists.ozlabs.org/pipermail/openbmc/2020-September/023071.html</a><o:p></o:p></p>
<p class="MsoNormal"><span class="f55bbb4eeef208e8wmi-sign">-- </span><br>
<span class="f55bbb4eeef208e8wmi-sign">Patrick Williams</span><br>
<span class="f55bbb4eeef208e8wmi-sign">::DISCLAIMER::</span><br>
<span class="f55bbb4eeef208e8wmi-sign">________________________________</span><br>
<span class="f55bbb4eeef208e8wmi-sign">The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted,
lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any,
presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message
without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses
and other defects.</span><br>
<span class="f55bbb4eeef208e8wmi-sign">________________________________</span><o:p></o:p></p>
</blockquote>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">-- <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Best regards,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Konstantin Klubnichkin,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">lead firmware engineer,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">server hardware R&D group,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Yandex Moscow office.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">tel: +7-903-510-33-33<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
</div>
</body>
</html>