[San-Diego-pm] Help!
Joel Fentin
joel at fentin.com
Fri Jun 30 19:37:12 PDT 2017
Tim, Brian, Urivan,
As I understand it, The newer version of Perl requires me to remove the
"fatalsToBrowser" line from the program. By doing so I lose the ability
to see a die statement and errors in the browser. If I want to know the
score, I need to find the error log.
If that's pretty much true, I'll let this die here.
In any case, I hope/intend to make it to the next San Diego Perl Mongers
meeting. That alone might make you want to avoid it.
======================================================
On 6/21/2017 10:15 AM, Tim Bollman wrote:
> I believe the relevant section of your failing error log is this:
>
> [Wed Jun 21 time 2017] [error] [client ip-address] Response header name
> '[Wed Jun 21 10' contains invalid characters, aborting request, referer:
> http://pacoweb.net/cgi-bin/Admin/CDprivateMenu.pl
> [Wed Jun 21 time 2017] [error] [client ip-address] SoftException in
> Application.cpp:256: File "/home4/pacowebn/public_html/500.php" is
> writeable by group, referer:
> http://pacoweb.net/cgi-bin/Admin/CDprivateMenu.pl
> [Wed Jun 21 time 2017] [error] [client ip-address] Premature end of
> script headers: 500.php, referer:
> http://pacoweb.net/cgi-bin/Admin/CDprivateMenu.pl
> [Wed Jun 21 time 2017] [error] [client ip-address] (-3)Unknown error
> 18446744073709551613: Failed to flush CGI output to client, referer:
> http://pacoweb.net/cgi-bin/Admin/CDprivateMenu.pl
>
> I've never done CGI programming, but from what I gather the first line
> says that the content CGI::Carp is putting in *STDOUT is ending up being
> treated as a header line in the HTTP response. Since the date stamp
> starts with a '[', it isn't a valid header so the server assumes you're
> spewing junk and kills you.
>
> Perhaps try having it output to *STDERR, which potentially ends up in
> one of those logs you've posted or (assuming you have permissions to
> write to somewhere -- perhaps your applications www directory) append to
> your own log file on the server so you can see the rest of what it's
> trying to produce.
>
>
> On Wed, Jun 21, 2017 at 9:47 AM, Joel Fentin <joel at fentin.com
> <mailto:joel at fentin.com>> wrote:
>
> I got in. Attached is a text file with 3 logs. Errors when it works.
> Errors when it doesn't work. And php errors; I don't use php.
>
> It's all pretty much Greek to me.
>
> -------
>
> Physical issues prevented me from attending the last two meetings. I
> hope to attend the upcoming meeting.
>
> =================================
>
> On 6/20/2017 6:16 AM, Brian Manning wrote:
>
> On Mon, Jun 19, 2017 at 10:13 PM, Joel Fentin <joel at fentin.com
> <mailto:joel at fentin.com>> wrote:
>
> The result is the same; a blank white screen. A control U
> displays:
> <!-- SHTML Wrapper - 500 Server Error -->
> as before.
>
>
> The reason for the HTTP 500 error is most likely in the error
> logs for
> your hosting provider's web server.
>
> If your hosting provider doesn't give you access to the error
> logs for
> your virtual host, I suggest switching to a hosting provider
> that does
> give you access, as access to the error logs is crucial for
> troubleshooting when there's issues with your CGI scripts, as you're
> now finding out.
>
> Thanks,
>
> Brian
>
>
>
>
> --
> Joel Fentin tel: 760-749-8863 <tel:760-749-8863>
> Personal Website: http://fentin.com
>
> _______________________________________________
> San-Diego-pm mailing list
> San-Diego-pm at pm.org <mailto:San-Diego-pm at pm.org>
> http://mail.pm.org/mailman/listinfo/san-diego-pm
> <http://mail.pm.org/mailman/listinfo/san-diego-pm>
>
>
--
Joel Fentin tel: 760-749-8863
Personal Website: http://fentin.com
More information about the San-Diego-pm
mailing list