# /lib64/liboneagentproc.so symbol lookup error

**URL:** <https://community.dynatrace.com/t/lib64-liboneagentproc-so-symbol-lookup-error/34449>\
**Category:** Cloud platforms\
**Tags:** aws, oneagent\
**Created:** [March 11, 2022, 1:00am UTC](https://community.dynatrace.com/t/lib64-liboneagentproc-so-symbol-lookup-error/34449 "2022-03-11T01:00:24Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![rcamara](https://avatars.discourse-cdn.com/v4/letter/r/9e8a1a/32.png) [@rcamara](https://community.dynatrace.com/u/rcamara)\
**Post date:** [March 11, 2022, 1:00am UTC](https://community.dynatrace.com/t/lib64-liboneagentproc-so-symbol-lookup-error/34449/1 "2022-03-11T01:00:24Z")

</div>

Update

=======

It was very simple. I just had to upgrade our amazon-ssm-agent 🙂

Question

========

I would like to know how critical&nbsp; **/lib64/liboneagentproc.so** is. It’s because when I installed Dynatrace Oneagent in an Amazon-Linux-2 running amazon-ssm-agent, the amazon-ssm-agent systemd service failed to start. The error that shows up when I run “systemctl status amazon-ssm-agent” is

Mar 11 00:35:19 apiproxywebapps-07cd-172\_20\_19\_167.us-east-1.dev amazon-ssm-agent[12552]: **/usr/bin/amazon-ssm-agent: symbol lookup error: /lib64/liboneagentproc.so: undefined symbol: \_\_environ**

Once I delete **/lib64/liboneagentproc.so** , the amazon-ssm-agent will start fine. The oneagent systemd service also starts fine after restarting it.

However, I’d like to know the proper solution.

Thank you,

Neil

 ![Screen Shot 2022-03-10 at 6.16.33 PM.png](https://global.discourse-cdn.com/dynatrace/original/2X/c/ca15ab0a64a8d7044a1105dd61f10b2d0f744e52.png)

---

<div class="post-metadata">

**Author:** ![ChadTurner](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/chadturner/32/161_2.png) [@ChadTurner](https://community.dynatrace.com/u/ChadTurner)\
**Post date:** [March 31, 2022, 2:01pm UTC](https://community.dynatrace.com/t/lib64-liboneagentproc-so-symbol-lookup-error/34449/2 "2022-03-31T14:01:55Z")

</div>

[@rcamara](https://community.dynatrace.com/user/967)&nbsp;Thanks for sharing this out!!&nbsp;:dancing\_penguin:

---

<div class="post-metadata">

**Author:** ![bJohnson](https://avatars.discourse-cdn.com/v4/letter/b/e9a140/32.png) [@bJohnson](https://community.dynatrace.com/u/bJohnson)\
**Post date:** [April 8, 2022, 2:28pm UTC](https://community.dynatrace.com/t/lib64-liboneagentproc-so-symbol-lookup-error/34449/3 "2022-04-08T14:28:20Z")

</div>

This is a major issue for teams using AWS SSM agent for access to their servers and deleting the file causes error messages to be displayed in the console. Can the Dynatrace team provide some guidance on this issue?

---

<div class="post-metadata">

**Author:** ![tuomas\_metsamaa](https://avatars.discourse-cdn.com/v4/letter/t/f9ae1b/32.png) [@tuomas\_metsamaa](https://community.dynatrace.com/u/tuomas_metsamaa)\
**Post date:** [April 13, 2022, 11:09am UTC](https://community.dynatrace.com/t/lib64-liboneagentproc-so-symbol-lookup-error/34449/4 "2022-04-13T11:09:33Z")

</div>

Hi, any info this issue?

---

<div class="post-metadata">

**Author:** ![hannahmac](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/hannahmac/32/41823_2.png) [@hannahmac](https://community.dynatrace.com/u/hannahmac)\
**Post date:** [April 13, 2022, 12:05pm UTC](https://community.dynatrace.com/t/lib64-liboneagentproc-so-symbol-lookup-error/34449/5 "2022-04-13T12:05:59Z")

</div>

did you upgrade&nbsp;amazon-ssm-agent? Did that not resolve this behaviour for you?

---

<div class="post-metadata">

**Author:** ![bJohnson](https://avatars.discourse-cdn.com/v4/letter/b/e9a140/32.png) [@bJohnson](https://community.dynatrace.com/u/bJohnson)\
**Post date:** [April 13, 2022, 12:54pm UTC](https://community.dynatrace.com/t/lib64-liboneagentproc-so-symbol-lookup-error/34449/6 "2022-04-13T12:54:21Z")

</div>

The latest version (v 3.1.1188.0) of the SSM agent has this issue. I was able to confirm that the issue is not present on SSM version 3.1.1141.0.

UPDATE: This issue is resolved in SSM agent v3.1.1208.0.

---

<div class="post-metadata">

**Author:** ![hannahmac](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/hannahmac/32/41823_2.png) [@hannahmac](https://community.dynatrace.com/u/hannahmac)\
**Post date:** [April 13, 2022, 2:37pm UTC](https://community.dynatrace.com/t/lib64-liboneagentproc-so-symbol-lookup-error/34449/7 "2022-04-13T14:37:22Z")

</div>

That’s great. Thanks for confirming. I can see that there was some work to resolve this to work on higher versions with OneAgent 1.237. What version are you using?

---

<div class="post-metadata">

**Author:** ![bJohnson](https://avatars.discourse-cdn.com/v4/letter/b/e9a140/32.png) [@bJohnson](https://community.dynatrace.com/u/bJohnson)\
**Post date:** [April 13, 2022, 2:40pm UTC](https://community.dynatrace.com/t/lib64-liboneagentproc-so-symbol-lookup-error/34449/8 "2022-04-13T14:40:49Z")

</div>

We are using One Agent v1.233.190.20220314-111259

---

<div class="post-metadata">

**Author:** ![hannahmac](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/hannahmac/32/41823_2.png) [@hannahmac](https://community.dynatrace.com/u/hannahmac)\
**Post date:** [April 13, 2022, 2:44pm UTC](https://community.dynatrace.com/t/lib64-liboneagentproc-so-symbol-lookup-error/34449/9 "2022-04-13T14:44:25Z")

</div>

OK, thanks. So it looks like&nbsp;SSM version 3.1.1141.0 is the one you will need to use until you update your OneAgent to the latest, 1.237.
