[LON-CAPA-admin] View warnings from resource that doesn't publish

[Bynum, Lee Hamilton]

Thank you Stuart!  That makes a lot of sense.  We'll take a look at that certificate.

Lee

> -----Original Message-----
> From: LON-CAPA-admin <lon-capa-admin-bounces at mail.lon-capa.org> On
> Behalf Of Raeburn, Stuart
> Sent: Tuesday, March 26, 2019 4:52 PM
> To: list about administration and system updating <lon-capa-
> admin at mail.lon-capa.org>
> Subject: Re: [LON-CAPA-admin] View warnings from resource that doesn't
> publish
> 
> Lee,
> 
> The "443 warnings" suggests that this is related to port 443 (i.e., https).
> 
> My guess is that response coming back from an LWP request to render "Lee
> Test Problem 3.problem" (with POSTed args: grade_target'=>'web',
> 'return_only_error_and_warning_counts' => 1),  when you attempt to
> publish, is the string:
> 
> Can't connect to hostname.lon-capa.illinois.edu:443
> 
> which LON-CAPA then splits on the colon into an "errorcount" of:  "Can't
> connect to hostname.lon-capa.illinois.edu" (which is listed as 0 errors) and a
> "warningcount" of 443 (which is listed as: 443 warnings).
> 
> For the URL of your standalone server/VM, whatsmychaincert.com reports
> that your SSL chain is misconfigured, whereas for your production library
> server whatsmychaincert.com reports that the SSL chain is correct.
> 
> I would compare the Apache SSL config (specifically the certificate chain) on
> this server/VM with the one on your production library server (for which the
> script below does not report an error).
> 
> I tested requests for the URL: ht  tp s : // hostname.lon-
> capa.illinois.edu/adm/about.html
> (removing the spaces from ht  tp s : //  which I put there to stop Proofpoint
> modifying the URL in this post to the list, and replacing hostname with the
> actual hostname of your server/VM).
> 
> (a) from a web browser, and
> (b) from a script on CentOS 7 which uses LWP.
> 
> The browser fetched the page OK, but the script returned:
> Can't connect to hostname.lon-capa.illinois.edu:443
> 
> Here is the script:
> 
> #!/usr/bin/perl
> 
> use strict;
> use LWP::UserAgent();
> 
> my $ua=new LWP::UserAgent;
> my $request=new HTTP::Request('GET',"https://hostname.lon-
> capa.illinois.edu/adm/about.html");
> my $response=$ua->request($request);
> print $response->content;
> 
> 
> Stuart Raeburn
> LON-CAPA Academic Consortium
> 
> ________________________________________
> From: LON-CAPA-admin <lon-capa-admin-bounces at mail.lon-capa.org> on
> behalf of Bynum, Lee Hamilton <leebynum at illinois.edu>
> Sent: Tuesday, March 26, 2019 4:08 PM
> To: list about administration and system updating
> Subject: Re: [LON-CAPA-admin] View warnings from resource that doesn't
> publish
> 
> Publishing /priv/uiuc/lcdcatlas/Lee Test Problem 3.problem
> 
> Warnings and Errors
> /priv/uiuc/lcdcatlas/Lee Test Problem 3.problem:
> *         443 warnings
> *         0 errors [https://libraryexam.lon-
> capa.illinois.edu/adm/lonMisc/bomb.gif]
> The document contains errors and cannot be published.
> 
> 
> From: LON-CAPA-admin <lon-capa-admin-bounces at mail.lon-capa.org> On
> Behalf Of Bynum, Lee Hamilton
> Sent: Tuesday, March 26, 2019 11:45 AM
> To: 'lon-capa-admin at mail.lon-capa.org' <lon-capa-admin at mail.lon-
> capa.org>
> Subject: [LON-CAPA-admin] View warnings from resource that doesn't
> publish
> 
> We have an isolated library server that I am attempting to publish resources
> on.  Creating the course and authoring space appears to have gone well, but
> when I attempt to publish a resource I am getting a bunch of warnings, no
> errors and a failure to publish.  A similar thing occurs when I attempt to clean
> the problem.
> 
> Is there a good way to view those warnings?  They aren't visible in the
> normal interface and I'm hoping they might shed some light on what I've
> configured wrong.
> 
> Lee