Skip to Content.
Sympa Menu

grouper-users - [grouper-users] How is the Grouper Loader meant to be run?

Subject: Grouper Users - Open Discussion List

List archive

[grouper-users] How is the Grouper Loader meant to be run?

Chronological Thread 
  • From: "Waldbieser, Carl" <>
  • To: Gouper Users List <>
  • Subject: [grouper-users] How is the Grouper Loader meant to be run?
  • Date: Fri, 25 Sep 2015 10:17:33 -0400 (EDT)

At Lafayette College, we have been running the Grouper Loader as a system
service from /etc/init (according to the host's man pages, "init - Upstart
process management daemon").
This has typically worked well for us, though I was a bit surprised today
when my Grouper status URL reported that a few new SIMPLE_SQL jobs I recently
added had not run in a couple days.
The logs showed no errors, and if I ran the jobs from GSH, they ran without

I finally ran a report from the database and realized the jobs were not
recorded as having been run.

I tried changing one of the job times, and I could see in the grouper logs
that a session started and ended at the appropriate time, but there was still
no log entry.
Finally, I rescheduled the job *and* stopped and restarted the Loader
process. Now the job was picked up and recorded in the loader history table.

Based on these observations, I am assuming that an existing Loader session
won't see newly scheduled jobs.

I was wondering if I am running the Loader in the expected manner, and it is
just an operation step to bounce the service to get it to recognize new jobs,
or if it was intended to be run intermittently or perhaps something else.

Carl Waldbieser
ITS Systems Programmer
Lafayette College

Archive powered by MHonArc 2.6.16.

Top of Page