[LON-CAPA-admin] Republish Course Content?

[Raymond Batchelor]

Sweet!
Thanks for this.R
----- Original Message -----
From: Stuart Raeburn <raeburn at msu.edu>
To: lon-capa-admin at mail.lon-capa.org
Sent: Mon, 28 Aug 2017 05:56:34 -0700 (PDT)
Subject: Re: [LON-CAPA-admin] Republish Course Content?

Ray,

Currently, neither of the two utilities: 'Verify Content' or 
'Check/Set Resource Versions' (accessible via the Course Editor), when 
used on a library server will push the updated resources from the 
library server to a domain's access servers.

Equally, neither utility will pull updated resources from a library 
server to access server when used on an access server, if the resource 
was previously replicated.

Using Check/Set Resource Versions with display of: "All Resources 
(possibly large output)" will retrieve versioned metadata files, but 
will not pull unversioned metadata and/or resource files, if the 
resource was previously replicated.

Anyway, I have now added some code so that "Verify Content" includes 
an option to check if files replicated from elsewhere are outdated 
(because the "update" transaction was delayed).

So in the future, a Course Coordinator could visit each access server 
in turn (e.g., using /adm/switchserver to hop from one access server 
to the next) and use Verify Content to pull updates of any outdated 
resources from that resource's homeserver.

The tactic (currently available) to a Domain Coordinator of using Main 
Menu > "Status of domain servers" > "Update Connections and Refresh 
Status Information" on a library server to complete delayed 
transactions will continue to be available.

The nightly run of loncron at 5:10 am local time on each server, also 
automatically attempts to complete delayed transactions, so a user 
with command line access and rights to become the www user, could also 
run /home/httpd/perl/loncron from the command line on a library server 
to propagate delayed updates.


Stuart Raeburn
LON-CAPA Academic Consortium


> Hmm.
> I don't truly know, but I am wondering if in the "Course Editor" you 
> select the tab 'Content Utilities" and try the 'Adminstration' 
> option 'Verify Content' and/or the option 'Check/Set Resource 
> Versions'.
> ----- Original Message -----
> From: Young, Joyce E <young257 at purdue.edu>
> To: LON-CAPA-admin at mail.lon-capa.org
> Cc: Huckleberry, David W <dhuckleb at purdue.edu>, 
> 'elt-dev at lists.purdue.edu' <elt-dev at lists.purdue.edu>
> Sent: Fri, 25 Aug 2017 08:01:30 -0700 (PDT)
> Subject: [LON-CAPA-admin] Republish Course Content?
>
> All, We had an incident where our library server was 
> not communicating with our application servers for a time. Users 
> were all logging into the library server and all seemed fine until 
> the library server got overloaded, we saw
> what was happening, and got all servers communicating again. 
> During the time when activity was only happening on the 
> library server, some course problems were edited and republished. 
> When we re-connected all servers and students were then re-routed to 
> the application servers, we learned
> that the students were not seeing the updated problem versions. The 
> updated problems were not pushed to the application servers as they 
> would have been during normal circumstances. We found 
> that if the problems were re-published, once all servers were 
> connected, then the version push happened as it should. To rectify 
> our issue, we went in and manually republished any problems that 
> were edited during
> the ?dark? period. Is there an easier way to handle 
> this situation if it should happen again? Is there a way to 
> ?refresh? a whole course, re-publishing any content currently used 
> in that course? Could we have just copied the affected .problem
> and .problem.meta files from the library server over to the 
> application servers? The authorspace directories that 
> we pull from have unpublished resources in them (works in progress), 
> so republishing at the directory level wouldn?t work for us. Any 
> advice or ideas would be appreciated. We don?t expect
> this to happen again, but it would be nice to have a plan in place 
> in case it does. 
> Thanks, 
> 
> Joyce Young Joyce Young
>
> Programmer/Analyst
>
> ITAS - Student Systems Competency Center
>
> Purdue University
>
> 3495 Kent Avenue, Suite 100
>
> West Lafayette, IN 47906
>
> Phone: (765) 427-6340
>
> Fax: (765) 464-2233
>
> Campus Mail: ROSSyoung257 at purdue.edu
>
> --
> Raymond J. Batchelor, PhD.
> Department of Chemistry
> Simon Fraser University
>
> Phone: 778-782-5635



_______________________________________________
LON-CAPA-admin mailing list
LON-CAPA-admin at mail.lon-capa.org
http://mail.lon-capa.org/mailman/listinfo/lon-capa-admin

-- 
Raymond J. Batchelor, PhD.
Department of Chemistry
Simon Fraser University

Phone: 778-782-5635
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.lon-capa.org/pipermail/lon-capa-admin/attachments/20170828/8d08c8b5/attachment.html>