# Strange MODX behaviour!

**URL:** <https://community.modx.com/t/strange-modx-behaviour/4378>\
**Category:** Support\
**Created:** [September 9, 2021, 1:22pm UTC](https://community.modx.com/t/strange-modx-behaviour/4378 "2021-09-09T13:22:41Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![halftrainedharry](https://community.modx.com/user_avatar/community.modx.com/halftrainedharry/32/1063_2.png) [@halftrainedharry](https://community.modx.com/u/halftrainedharry)\
**Post date:** [September 10, 2021, 10:29am UTC](https://community.modx.com/t/strange-modx-behaviour/4378/13 "2021-09-10T10:29:53Z")

</div>

Maybe this post helps to locate the error log.

> [@Modx api how to use runSnippet?](https://community.modx.com/t/modx-api-how-to-use-runsnippet/3546/11):
>
> That completely depends on your server configuration and is independent of MODX entirely. Common locations are within a server control panel, /usr/local/apache/logs/error\_log, var/log/httpd/error\_log, /var/log/apache2/error.log, as error\_log files in the directory the error was triggered in, or elsewhere. On MODX Cloud it’s in your home directory \> log. If you check the phpinfo() output (which MODX has a utility for, in manage \> reports \> system info \> phpinfo()) find the error\_log directive. …

---

_[View the full topic](https://community.modx.com/t/strange-modx-behaviour/4378)._