HelioHost Posted September 14, 2017 Posted September 14, 2017 I'm testing CGIs and when I get a 500 Internal Server Error I expect to see= the error in the log. In fact, when I was in Johnny doing the exact same t=esting, the log was being populated correctly. Thanks, James -----Original Message-----From: support@heliohost.org [mailto:support@heliohost.org]=20Sent: Wednesday, September 13, 2017 11:28 PMTo: Weissman, James Subject: Re: Error log not being populated What kind of errors were you expecting to see there? I will try to replicat=e the issue. On 2017-09-13 17:05, Weissman, James wrote:> I donated and was moved from Johnny to Tommy last evening. Since then,=20> my Errors page=20> [https://tommy.heliohost.org:2083/cpsess2946513647/frontend/paper_lant> ern/stats/errlog.html]does not populate; i.e. nothing in the text box=20> "Last 300 Error Log messages in reverse order:">=20> User: darden>=20> Primary Domain: darden.heliohost.org>=20> Thanks.
Krydos Posted September 14, 2017 Posted September 14, 2017 I can't get anything useful to show up in the Johnny error log either. I intentionally created a 500 error on a cgi script and the Johnny error log just says it couldn't find a custom 500 error document. Is that what you're referring to?
HelioHost Posted September 14, 2017 Author Posted September 14, 2017 I'll decide what is useful The problem is that the error screen is completely empty on Tommy:http://oi65.tinypic.com/n9k8.jpg On Johnny, I'd get error messages when my CGI failed.=20 Thanks, James -----Original Message-----
Krydos Posted September 15, 2017 Posted September 15, 2017 I suppose I didn't word it very well, but what I was trying to ask was what error messages did you see on Johnny that you don't see on Tommy? I can get error messages to show up on both servers. I'm just not sure what error messages you would like to see on Tommy.
HelioHost Posted September 15, 2017 Author Posted September 15, 2017 I'm sorry for prolonging this. You wrote:> I can get error messages to show up on both servers. If they are generated, why is my text box always blank? If you generated an= error, it would certainly be among the last 300. Why can't I see it in my =browser?? If you are seeing them, why am I not? It's the same log, no? Anytime, my CGI caused a 404 or 500 I would see the error on Johnny. I have= never seen anything on Tommy. Are you sure something isn't misconfigured? Maybe I don't have permissions =to the file form which the errors are being pulled? The absence of an error log makes debugging an order of magnitude more diff=icult Thanks,James -----Original Message-----Sent: Thursday, September 14, 2017 09:41 PM I suppose I didn't word it very well, but what I was trying to ask was what= error messages did you see on Johnny that you don't see on Tommy? I can ge=t error messages to show up on both servers. I'm just not sure what error m=essages you would like to see on Tommy.=20
Krydos Posted September 15, 2017 Posted September 15, 2017 Technically 404 errors shouldn't show up in an error_log since they're not a server error but rather a browser error. 404 errors can be found in your access logs on both servers https://tommy.heliohost.org:2083/frontend/paper_lantern/raw/index.html It's probably a misconfiguration of some sort on Johnny that allowed you to see them as an error. 500 errors show up on Johnny and Ricky, but don't on Tommy. I suspect the reason is because Johnny and Ricky are running prefork mpm, and Tommy is running event. Unfortunately I can't switch Tommy back to prefork because prefork isn't compatible with http2 which we offer on Tommy. I'll see if I can change the way 500 errors are logged on Tommy. Thanks for being patient with me.
Krydos Posted September 15, 2017 Posted September 15, 2017 I increased the apache error_log verbosity. Are you getting anything on cgi 500 errors now?
HelioHost Posted September 15, 2017 Author Posted September 15, 2017 Thanks. Yeah, it's quite verbose but I am definitely seeing data now.=20 It may be just that cPanel does not provide it but it would be truly useful= to have a tail of 300 for the normal server log, not just the errors. I actually solved most of my python problems the biggest of which arose fro=m copying /pasting from a Windows text editor into the helio code editor. O=dd to think line ends would get copied, but something made it sick. Thanks,James -----Original Message-----
Krydos Posted September 15, 2017 Posted September 15, 2017 Another trick we recommend for people trying to debug cgi 500 errors is to use cron to email you the error. Here is a guide I wrote on how to do that https://www.helionet.org/index/topic/29544-python-27-module-request500-error-troulbeshooting/?p=133824 Keep in mind that you're limited to 2 cron jobs per day though.
Recommended Posts