Troubleshooting HTTP 500 Internal Server Error

[Patrick Yolian]

Hello!

We just upgraded from MunkiReport 4.x to 5.7.1, running on an IIS server.  Our clients are able to check-in but they are not sending any other device information up to the portal.

When looking through the client logs we see the HTTP500. In an effort to troubleshoot we've set DEBUG=TRUE in the .env file but we are not seeing any additional information anywhere.  We've looked at the logs for IIS, php, and munkireport client but haven't gotten any closer to a solution.

Any thoughts on why debug in the .env file isn't working?

Any advice is much appreciated

[Xavier Xavier]

Patrick,

Did you install the required MunkiReport python package? It was mentioned along with the 5.7.0 release 

https://github.com/munkireport/MunkiReport-Python/releases/latest

https://github.com/munkireport/munkireport-php/releases

Mat X

--
You received this message because you are subscribed to the Google Groups "munkireport" group.
To unsubscribe from this group and stop receiving emails from it, send an email to munkireport...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/munkireport/f5a3cf1b-be3a-47ea-9375-eb8c84e07938n%40googlegroups.com.

[Patrick Yolian]

Hello!

Yes, we did install that package but that didn't resolve it for us.

The issue ended up being the 'timemachine' module.  We removed that module from the .env file and devices started to report correct info.  We looked at the MySQL logs and saw that as the server was attempting to process the timemachine query it would stop.  Attached is a snippet of the log.