Yes, I'm aware Dell doesn't officially support Debian, I was hoping someone in the community had some experience with this error and could point me to a fix. FWIW, the segfault is occurring in ld-2.xx.so, where xx is dependent upon which Debian version I'm running, so seems to be related to libc, in case that rings any bells with anyone.
Thanks. -- ray Raymond Clotfelter, IT Director Carl R. Ice College of Engineering Kansas State University r...@ksu.edu (785) 532-3017 0012 Seaton Hall 920 N. 17th St. On Fri, Jan 7, 2022 at 5:28 AM Sapra, Puneet <puneet.sa...@dell.com> wrote: > > This email originated from outside of K-State. > > > Hello Raymond Clotfelter, > > Thank you for reaching out to us. > > The OpenManage Server Administrator (OMSA) does not support Debian OS > officially. Could you please try with other Linux OS that OMSA supports. > For more details, you can refer OMSA support matrix guide with the following > link: > https://www.dell.com/support/manuals/en-us/openmanage-server-administrator-v10.2.0.0/om_10.2_sw_sm_pub/introduction?guid=guid-c6a7ccaa-cfef-4a63-9df7-a583974a7ee5&lang=en-us > > Thanks and Regards, > Puneet Sapra - Dell EMC > > > Internal Use - Confidential > > -----Original Message----- > From: Linux-PowerEdge <linux-poweredge-boun...@dell.com> On Behalf Of > linux-poweredge-requ...@dell.com > Sent: Wednesday, December 29, 2021 11:30 PM > To: linux-poweredge@dell.com > Subject: Linux-PowerEdge Digest, Vol 198, Issue 2 > > Send Linux-PowerEdge mailing list submissions to > linux-poweredge@dell.com > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.us.dell.com/mailman/listinfo/linux-poweredge > or, via email, send a message with subject or body 'help' to > linux-poweredge-requ...@dell.com > > You can reach the person managing the list at > linux-poweredge-ow...@dell.com > > When replying, please edit your Subject line so it is more specific than "Re: > Contents of Linux-PowerEdge digest..." > > > Today's Topics: > > 1. OpenManage datamgrd segfault (Raymond Clotfelter) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 29 Dec 2021 07:16:16 -0600 > From: Raymond Clotfelter <r...@ksu.edu> > To: linux-powere...@lists.us.dell.com > Subject: [Linux-PowerEdge] OpenManage datamgrd segfault > Message-ID: > <CAPvuuS61tz_UtPrcAvfZmnHZjQkgzSwjHr5_e1N0ZEe9=wi...@mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > I have 2 new R640 PowerEdges that cannot start dsm_sa_datamgrd, they simply > segfault. I have tried Debian 10 and 11, I have tried OpenManage 9.4, 9.5, > 10.1 and 10.2. Same behavior on each. I also put Windows 2019 on one of the > servers and tried OM 9.5, and it worked fine. I have another PowerEdge R640 > that was on Debian 10 and was recently upgraded to Debian 11, and it has no > issues running OM 9.4 or 9.5. > > The new servers have NVMe storage, whereas the older one does not, I suspect > that might be the issue. > > Below is my journalctl from a failed startup: > > Dec 29 07:04:35 yorkshire systemd[1]: Starting Systems Management Data > Engine... > ?? Subject: A start job for unit dsm_sa_datamgrd.service has begun execution > ?? Defined-By: systemd ?? Support: https://www.debian.org/support ?? > ?? A start job for unit dsm_sa_datamgrd.service has begun execution. > ?? > ?? The job identifier is 84260. > Dec 29 07:04:48 yorkshire kernel: dsm_sa_datamgrd[452461]: segfault at 31f ip > 00007f170cf31d21 sp 00007ffe378612f0 error 4 in > ld-2.33.so[7f170cf1d000+24000] Dec 29 07:04:48 yorkshire kernel: Code: 00 48 > 8d 3d f1 bc 01 00 ff 15 > d3 c2 01 00 e9 3e fa ff ff 66 0f 1f 44 00 00 55 48 89 fd 48 8d 3d ad bc 01 00 > ff 15 af c2 01 00 <80> bd 1f 03 00 00 00> Dec 29 07:04:48 yorkshire > systemd[1]: dsm_sa_datamgrd.service: Control process exited, code=exited, > status=255/EXCEPTION ?? Subject: Unit process exited ?? Defined-By: systemd > ?? Support: https://www.debian.org/support ?? > ?? An ExecStart= process belonging to unit dsm_sa_datamgrd.service has exited. > ?? > ?? The process' exit code is 'exited' and its exit status is 255. > Dec 29 07:04:48 yorkshire systemd[1]: dsm_sa_datamgrd.service: Failed with > result 'exit-code'. > ?? Subject: Unit failed > ?? Defined-By: systemd > ?? Support: https://www.debian.org/support ?? > ?? The unit dsm_sa_datamgrd.service has entered the 'failed' state with > result 'exit-code'. > Dec 29 07:04:48 yorkshire systemd[1]: Failed to start Systems Management Data > Engine. > ?? Subject: A start job for unit dsm_sa_datamgrd.service has failed ?? > Defined-By: systemd ?? Support: https://www.debian.org/support ?? > ?? A start job for unit dsm_sa_datamgrd.service has finished with a failure. > ?? > ?? The job identifier is 84260 and the job result is failed. > Dec 29 07:04:48 yorkshire systemd[1]: dsm_sa_datamgrd.service: > Consumed 2.499s CPU time. > ?? Subject: Resources consumed by unit runtime ?? Defined-By: systemd ?? > Support: https://www.debian.org/support ?? > ?? The unit dsm_sa_datamgrd.service completed and consumed the indicated > resources. > > Any thoughts are appreciated. > > -- ray > > Raymond Clotfelter, IT Director > Carl R. Ice College of Engineering > Kansas State University > r...@ksu.edu (785) 532-3017 > 0012 Seaton Hall 920 N. 17th St. > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Linux-PowerEdge mailing list > Linux-PowerEdge@dell.com > https://lists.us.dell.com/mailman/listinfo/linux-poweredge > > ------------------------------ > > End of Linux-PowerEdge Digest, Vol 198, Issue 2 > *********************************************** _______________________________________________ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge
