search

IATI / IATI-Datastore

An open-source datastore for IATI data with RESTful web API providing XML, JSON, CSV plus ETL tools
http://datastore.iatistandard.org/
Other
1 stars 0 forks source link

No access logs to debug 500 errors #290

Closed hayfield closed 3 years ago

hayfield commented 6 years ago

There do not appear to be any logs to track what caused 500 errors.

This was identified in #289

andylolz commented 6 years ago

I don’t follow (but also: I am bad at devops.)

It looks like the server uses apache. Do error logs redirect to /dev/null or something? If not, wouldn’t you find error logs at /var/log/apache/error.log or similar? Or some custom error log location?

hayfield commented 6 years ago

If not, wouldn’t you find error logs at /var/log/apache/error.log or similar?

Is exactly what I'd expect, though there's nothing relevant there.

@dalepotter has indicated that based on sleuthing from ages back there might be something somewhere, though if there is then it's hidden somewhere mysterious and undocumented.

andylolz commented 6 years ago

Is exactly what I'd expect, though there's nothing relevant there.

I guess /etc/apache/sites-enabled/[site-name] (or similar) would be the best bet, then? Maybe it specifies custom logfile locations?

though if there is then it's hidden somewhere mysterious and undocumented.

Unfortunately it’s not uncommon for site setup to be undocumented… I suppose the good news is apache makes following the breadcrumbs doable.

andylolz commented 6 years ago

Is exactly what I'd expect, though there's nothing relevant there.

Oh sorry, I misunderstood. I thought you were saying the logfile wasn’t there, but I think you’re saying there’s nothing relevant in the logfile. Yeah, that’s probably what I’d expect, because a) nothing changed in the code, and b) every page was affected. So I guess the relevant logging is maybe a bit cryptic.